Cloudflare launches isolated preview environments for Workers

Cloudflare has introduced Worker Previews, a feature designed to provide developers with isolated, production-like environments for testing changes to Cloudflare Workers before they reach production. The tool addresses a common pain point in software development: changes that behave as expected in staging but fail in production due to differences in configuration, state, or runtime conditions.

How Worker Previews work

Worker Previews assign a dedicated environment to each Git branch, complete with its own code, configuration, URL, observability tools, and state. When a developer runs npx wrangler preview, the system generates a new environment that mirrors production but operates independently. This isolation extends to stateful resources like Durable Objects and Containers, which are scoped to the branch to prevent conflicts with production or other previews.

Each preview environment includes its own variables, secrets, and bindings, allowing developers to test migrations, schema changes, or API integrations without risking production data. The environments persist across deployments, enabling iterative testing and debugging. Observability tools—such as logs, metrics, and traces—are also scoped to the preview, so developers can monitor performance and diagnose issues in isolation.

The feature supports custom domains for preview URLs, ensuring that authentication flows, cookies, and cross-origin policies behave as they would in production. For example, a preview for a login feature could run at feature-login.previews.example.com, allowing developers to test OAuth redirects and session management in a realistic setting. Cloudflare Access can be used to restrict access to these URLs, adding a layer of security for sensitive changes.

Practical applications and early adoption

Worker Previews are particularly useful for complex workflows where changes interact with multiple systems. Cloudflare has been using the feature internally to test CloudflareOS, an open-source platform for managing agent access to company systems. Gatekeepers in CloudflareOS control permissions for services like Google, GitHub, and Slack, making thorough testing critical. By deploying isolated previews for each change, the team can validate OAuth callbacks, permission flows, and application state in a production-like environment before merging.

Early adopters outside Cloudflare have also reported benefits. IKEA uses Worker Previews to test edge deployments for its e-commerce platform, avoiding issues with Content Security Policy and cookies. Supermemory, a developer tool company, leverages the feature to validate HTTP flows and Durable Object-backed routes before production. Ramp, a financial technology company, has integrated Worker Previews into its agent-based development workflow, enabling automated testing of pull requests.

"Previews gives us the ability to iterate earlier at the edge. For IKEA.com, custom domain support helps us avoid Content Security Policy and cookie issues. We’re especially excited for Service Binding support, which will enable communication between Previews and be a game changer for end-to-end testing across our Worker chain." — Santosh Kumar Dwivedi, Senior Software Engineer, IKEA

Limitations and future improvements

While Worker Previews represent a significant step forward, some limitations remain. Currently, service bindings from a preview still call the bound Worker’s production deployment, meaning the entire request path cannot yet be isolated within matching previews. Similarly, previews can send messages to Queues but cannot consume them, and isolating Workflow executions requires separate configuration. Cloudflare has acknowledged these gaps and is working on solutions to fully scope asynchronous flows to individual branches.

Another area of focus is support for long-lived previews. Many teams maintain staging, QA, or per-developer environments that persist across sprints, and Cloudflare is exploring ways to accommodate these use cases. The company has invited feedback from users to shape the roadmap, emphasizing that the feature is designed to evolve based on real-world needs.

Worker Previews are available now for all Cloudflare Workers users. Developers can get started by configuring a previews block in their Wrangler configuration file and running npx wrangler preview from any branch. Documentation and community support are available through Cloudflare’s developer resources.