Workers vs. Pages (compatibility matrix)

You can deploy full-stack applications, including front-end static assets and back-end APIs, as well as server-side rendered pages (SSR), to both Cloudflare Workers and Pages. The compatibility matrix below shows which features are available for each, to help you choose whether to build with Workers or Pages. Unless otherwise stated below, what works in Pages works in Workers, and what works in Workers works in Pages. Think something is missing from this list? Open a pull request ↗ or create a GitHub issue ↗.

We plan to bridge the gaps between Workers and Pages and provide ways to migrate your Pages projects to Workers.

Legend
✅: Supported
⏳: Coming soon
🟡: Unsupported, workaround available
❌: Unsupported

	Workers	Pages
Writing, Testing, and Deploying Code
Rollbacks	✅	✅
Gradual Deployments	✅	❌
Preview URLs	✅	✅
Testing tools	✅	✅
Local Development	✅	✅
Remote Development (--remote)	✅	❌
Quick Editor in Dashboard ↗	✅	❌
Static Assets
Early Hints	❌	✅
Custom HTTP headers for static assets	🟡 1	✅
Middleware	✅ 2	✅
Redirects	🟡 3	✅
Smart Placement	✅	✅
Serve assets on a path	✅	❌
Observability
Workers Logs	✅	❌
Logpush	✅	❌
Tail Workers	✅	❌
Real-time logs	✅	✅
Source Maps	✅	❌
Runtime APIs & Compute Models
Node.js Compatibility Mode	✅	✅
Durable Objects	✅	🟡 4
Cron Triggers	✅	❌
Bindings
AI	✅	✅
Analytics Engine	✅	✅
Assets	✅	✅
Browser Rendering	✅	✅
D1	✅	✅
Email Workers	✅	❌
Environment Variables	✅	✅
Hyperdrive	✅	✅
Image Resizing	✅	❌
KV	✅	✅
mTLS	✅	✅
Queue Producers	✅	✅
Queue Consumers	✅	❌
R2	✅	✅
Rate Limiting	✅	❌
Secrets	✅	✅
Service bindings	✅	✅
Vectorize	✅	✅
Builds (CI/CD)
Monorepos	✅	✅
Build Watch Paths	✅	✅
Build Caching	✅	✅
Deploy Hooks	❌	✅
Branch Deploy Controls	❌	✅
Custom Branch Aliases	❌	✅
Pages Functions
File-based Routing	❌ 5	✅
Pages Plugins	❌ 6	✅
Domain Configuration
Custom domains	✅	✅
Custom subdomains	✅	✅
Custom domains outside Cloudflare zones	❌	✅
Non-root routes	✅	❌

Footnotes

1. Similar to ³, to customize the HTTP headers that are returned by static assets, you can use Service bindings to connect a Worker in front of the Worker with assets. ↩

2. Middleware can be configured via the run_worker_first option, but is charged as a normal Worker invocation. We plan to explore additional related options in the future. ↩

3. You can handle redirects by adding code to your Worker (a community package ↗ is available for _redirects support), or you can use Bulk Redirects. ↩

4. To use Durable Objects with your Cloudflare Pages project, you must create a separate Worker with a Durable Object and then declare a binding to it in both your Production and Preview environments. Using Durable Objects with Workers is simpler and recommended. ↩

5. Workers supports popular frameworks, many of which implement file-based routing. ↩

6. Everything that is possible with Pages Functions can also be achieved by adding code to your Worker or by using framework-specific plugins for relevant third party tools. ↩