Running Next.js on Cloudflare Workers reaches a milestone
Since the adapter was first announced at Builder Day 2024, the project has been reworked to sit directly inside OpenNext, the build tool that packages Next.js applications for non-Vercel platforms. That integration means the adapter now tracks Next.js features more closely and benefits from OpenNext's end-to-end test suite. The result is the 1.0.0-beta release of @opennextjs/cloudflare, which Cloudflare now recommends over its previous Pages-based approach.
What the adapter supports now
Most Next.js 15 features are functional through the adapter, with the full compatibility list maintained on the OpenNext site. The current feature picture includes:
Caching | The Cloudflare adapter provides a cache handler for Next.js, optimizing the management of ISR/SSG and the data cache to speed up your apps. |
|---|---|
Partial Prerendering (PPR) | PPR immediately sends the pre-rendered HTML and begins streaming from the server in parallel. |
Middleware | Middleware allows modifying the response by rewriting, redirecting, or modifying the request and response headers, or responding directly before the request hits the app. |
App and Pages routers | Both the new App router and Pages routers are supported. |
Image Optimization | The adapter easily integrates with Cloudflare Images to deliver optimized images. |
Several gaps remain before the 1.0 release. Windows is not fully supported for development. The adapter also targets Next.js's Node runtime only — apps using the Edge runtime must remove export const runtime = "edge" for now, though Cloudflare notes that Workers already run close to users regardless of the runtime used. Composable caching with use cache, a canary feature in Next.js, is deferred until it stabilizes upstream and lands in OpenNext.
Ecosystem changes behind the improvements
The broader Workers platform has also closed gaps that previously blocked Next.js apps. The Node.js compatibility layer now natively implements the crypto, dns, timers, tls, and net modules, with remaining Node.js features filled in by the unenv polyfill project. Worker size limits were raised to 3 MiB on free plans and 15 MiB on paid plans, giving larger applications more headroom.
Release roadmap
The beta is expected to handle most existing Next.js 14 and 15 applications. Cloudflare plans to ship the stable 1.0 once early-adopter issues from the GitHub repository are resolved. A v2 release is already being scoped, with work centered on reducing bundle size, improving performance through caching changes, and enabling deployment across multiple Workers.
Getting started
The setup path stays close to a standard Next.js workflow. Scaffold a project from the official template:
npm create cloudflare@latest -- my-next-app --framework=next
--platform=workersDevelopment uses the normal Next.js dev server via npm run dev. To test against Workers locally before shipping, run npm run preview; production deployment is handled by npm run deploy.
Detailed guidance is available in the Cloudflare framework documentation and on the OpenNext site. Bugs and contributions go to the opennextjs/opennextjs-cloudflare repository, with community discussion on the OpenNext Discord.
