Cloudflare Launches Worker Previews: an Isolated Environment for Every Git Branch

What happened

Cloudflare launched Worker Previews on 22 September 2026. Each Git branch gets a production-like place to run, with its own code, configuration, URL, observability and state, all under the same Worker rather than as a separately managed deployment.

What we know

• A preview is deployed with npx wrangler preview. It uses its own variables, secrets and bindings, separate from production configuration and traffic.
• Each branch has a stable preview URL; every push updates the same running preview.
• Durable Objects and Containers are isolated per branch, so state changes, sessions, migrations and concurrent tests stay scoped to that preview.
• Logs, errors, metrics and traces are available per preview.
• Previews start from a "base configuration" the developer defines, the way a branch starts from main, and individual previews can override parts of it, such as pointing at their own database.
• Preview URLs can be served on a custom domain so authentication providers, cookies, CORS and OAuth redirects behave as in production.
• In the dashboard, production sits alongside previews in one view; Cloudflare contrasts this with Wrangler environments, which require a separate Worker per environment. Hundreds of previews can run at once.

What is not yet confirmed

The announcement excerpt reviewed here does not state pricing for previews, limits on their number or lifetime, or whether the feature is generally available or in beta. VoltKit has not tried the command.

Why it matters

Cloudflare frames this around AI coding agents producing more, and larger, changes that need testing before merge. Whether the author is a person or an agent, a per-branch environment with real bindings closes the "worked in staging, broke in production" gap, and isolated Durable Objects make it possible to test stateful changes without touching shared data.