Migrate from Vercel to Cloudflare
Next.js on Workers.
Cloudflare publishes an official guide for moving Next.js from Vercel to Workers. The main work is choosing an adapter and replacing the Vercel-specific pieces: vercel.json, image optimization, ISR cache and Vercel storage SDKs.
Facts checked against each provider's own pages
The short answer
Pick an adapter (Cloudflare recommends vinext, in beta, for new apps, with OpenNext as the established alternative[1]), move vercel.json rules into next.config, choose a persistent cache for ISR, set up Cloudflare Images for next/image, and replace @vercel/kv, blob and postgres with KV, R2, Hyperdrive or D1[2]. Then move the domain's DNS to Cloudflare and shift traffic.
What maps to what
| On Vercel | On Cloudflare | Notes |
|---|---|---|
| Next.js on Vercel | vinext (beta) or OpenNext adapter | OpenNext supports ISR, middleware and image optimization via Cloudflare Images; Node.js middleware isn't supported yet[3]. |
| vercel.json | next.config + wrangler.jsonc | Cloudflare's guide says vercel.json is not read[2]; Worker settings go in wrangler.jsonc[4]. |
| Image Optimization | Cloudflare Images | Without it, next/image requests return 400[2]. |
| @vercel/kv, @vercel/blob, @vercel/postgres | Workers KV, R2, Hyperdrive or D1 | Vercel's storage SDKs are unsupported on Workers[2]. |
| Environment variables | vars in Wrangler config; secrets via wrangler secret | 64 variables per Worker on Free, 128 on Paid, 5 KB each[5]. |
| Preview deployments | Workers Builds previews | Previews for non-production branches[6]. |
| Fast Data Transfer | No data transfer charge on Workers | [7]Billing is on requests and CPU time instead[7]. |
The migration, step by step
- 01
- 02
Move vercel.json into next.config
Redirects, rewrites and headers in vercel.json aren't read on Workers, so re-create them in next.config[2].
- 03
Replace Vercel storage and images
Swap @vercel/kv for Workers KV, @vercel/blob for R2, and @vercel/postgres for Hyperdrive (to an external Postgres) or D1; configure Cloudflare Images for next/image; pick a persistent cache for ISR[2].
- 04
Set variables and secrets
Put non-secret values in vars in your Wrangler config, per environment, and secrets in with wrangler secret or the dashboard[5].
- 05
Deploy and test
Deploy with wrangler deploy or connect Workers Builds to the repo[6], then test on the workers.dev or preview URL.
- 06
Move the domain
Workers Custom Domains need an active Cloudflare zone, meaning the domain's DNS is on Cloudflare, and can't be created on a hostname with an existing CNAME record[8]. Plan the DNS move as part of cutover.
Things the docs warn about
- Node.js middleware isn't supported yet with OpenNext on Cloudflare[3].
- vinext is in beta[1]; its own feature table marks image optimization as partially supported.
- Workers Free allows 10 ms of CPU per invocation; Paid allows up to 5 minutes (30 seconds by default)[7]. Heavy server rendering may need the Paid plan.
- Requests served by Worker code don't apply the static _redirects file[9], so keep app-level redirects in next.config.
Run both during cutover, then switch
AW3 Host connects both your Vercel and Cloudflare accounts, so the old and new deployments run side by side from one dashboard and API instead of a big-bang switch.
Weighted routing sends a small share of traffic to Cloudflare first (for example 5%, then 25%, 50% and 100%) while Vercel serves the rest. Health checks every 60 seconds watch both; if the Cloudflare side fails, failover moves traffic back automatically, and rollback to the previous release is one step. Daily cost sync shows what each provider costs during the overlap, and budget policies alert you if the double-running period gets expensive. Secrets for both are stored encrypted per environment. Because Workers Custom Domains need your DNS on Cloudflare, do the zone move early and keep the Vercel deployment as a weighted target until you're confident.
When Cloudflare has carried all traffic cleanly for long enough that you no longer need the fallback, point DNS at it for good and decommission Vercel.
Vercel vs Cloudflare at a glance
| Vercel | Cloudflare | |
|---|---|---|
| Category | Frontend platform | Edge platform |
| Pricing model | Per-seat plan plus metered usage; Pro's $20/mo fee includes one deploying seat and $20 of usage credit[10] | Workers Free or Workers Paid ($5/mo minimum) plus usage on requests and CPU time[7] |
| Compute billing granularity | Active CPU metered on actual CPU time and billed per CPU-hour; provisioned memory per GB-hour while an instance is alive[11] | Requests and CPU time, not wall-clock duration: Paid includes 10M requests + 30M CPU-ms, then $0.30/M requests and $0.02/M CPU-ms[7] |
| Internet egress (first paid tier) | $0.15/GB on-demand Fast Data Transfer in US regions (iad1); $0.15–$0.35/GB by region[12] | $0: no data transfer charge on Workers; R2 egress free (Containers egress is billed separately)[7] |
| Regions / locations | 19 compute regions; 126 points of presence[13] | Network page lists 348 cities in its data-center list (headline stats say 335+ cities, 125+ countries)[16] |
| Deploy model | Git push (GitHub, GitLab, Bitbucket) auto-deploys, or the Vercel CLI; OCI containers in beta[14] | wrangler deploy from the CLI, or Workers Builds on git push; Containers from Docker images[6] |
| Persistent volumes | — | No: Containers disks are ephemeral; persist to R2 or Durable Objects[17] |
| Config file | vercel.json (or vercel.toml / vercel.ts)[15] | wrangler.jsonc (recommended), wrangler.json or wrangler.toml[4] |
Frequently asked questions
- Can I run Next.js on Cloudflare Workers?
- Yes, through an adapter. Cloudflare recommends vinext (in beta) for new Next.js apps and documents the OpenNext adapter, which supports ISR, middleware and image optimization via Cloudflare Images. Node.js middleware isn't supported yet.
- Does Cloudflare read vercel.json?
- No. Cloudflare's Vercel migration guide says vercel.json is not read; move redirects, rewrites and headers into next.config.
- What replaces @vercel/kv and @vercel/blob on Cloudflare?
- Workers KV and R2. For Postgres, Cloudflare suggests Hyperdrive to an external database, or D1 (serverless SQLite).
Sources
- Cloudflare Docs: Next.js on Workers. https://developers.cloudflare.com/workers/framework-guides/web-apps/nextjs/ (checked 2026-11-16)
- Cloudflare Docs: Migrate Next.js from Vercel to Workers. https://developers.cloudflare.com/workers/static-assets/migration-guides/vercel-to-workers/nextjs/ (checked 2026-11-16)
- Cloudflare Docs: OpenNext on Workers. https://developers.cloudflare.com/workers/framework-guides/web-apps/opennext/ (checked 2026-11-16)
- Cloudflare Docs: Wrangler configuration. https://developers.cloudflare.com/workers/wrangler/configuration/ (checked 2026-11-16)
- Cloudflare Docs: Environment variables. https://developers.cloudflare.com/workers/configuration/environment-variables/ (checked 2026-11-16)
- Cloudflare Docs: Workers Builds. https://developers.cloudflare.com/workers/ci-cd/builds/ (checked 2026-11-16)
- Cloudflare Docs: Workers pricing. https://developers.cloudflare.com/workers/platform/pricing/ (checked 2026-11-16)
- Cloudflare Docs: Workers custom domains. https://developers.cloudflare.com/workers/configuration/routing/custom-domains/ (checked 2026-11-16)
- Cloudflare Docs: Static assets redirects. https://developers.cloudflare.com/workers/static-assets/redirects/ (checked 2026-11-16)
- Vercel: Pro plan. https://vercel.com/docs/plans/pro-plan (checked 2026-11-16)
- Vercel: Functions usage and pricing. https://vercel.com/docs/functions/usage-and-pricing (checked 2026-11-16)
- Vercel: Regional pricing, iad1. https://vercel.com/docs/pricing/regional-pricing/iad1 (checked 2026-11-16)
- Vercel: Regions. https://vercel.com/docs/regions (checked 2026-11-16)
- Vercel: Environments. https://vercel.com/docs/deployments/environments (checked 2026-11-16)
- Vercel: Project configuration. https://vercel.com/docs/project-configuration (checked 2026-11-16)
- Cloudflare: Network. https://www.cloudflare.com/network/ (checked 2026-11-16)
- Cloudflare Docs: Containers FAQ. https://developers.cloudflare.com/containers/faq/ (checked 2026-11-16)
Your next deploy
goes everywhere.
Connect a provider, point a service at it, and ship. Add the second provider when you're ready.
No card needed · Free tier · Pay as you go after that