Hosting
Cloudflare Pages
Serve a static frontend from Cloudflare, with optional request-handling functions.
Sources checked
Our recommendation
When to choose it
Choose Pages for static output. For a full-stack app, check whether the current Workers route and adapter are the better fit.
A good fit for
- Static sites and built frontends
- Projects already using Cloudflare
Choose something else when
Do not select Pages just because a framework can build locally; first verify its production runtime.
Watch out for
- A static host does not run arbitrary server code. Verify your framework output and adapter.
- Pages Functions use Workers billing and limits; static assets have a different cost model.
How costs work
Static hosting and Workers-based function usage
Review function usage separately from static requests, and confirm the current Pages or Workers deployment route.
Check current official terms and pricing ↗This is a pricing model, not a monthly quote. Check your region, intended usage and current plan before buying.
What connects to it
- Static framework build output
- Cloudflare Workers and R2
These are technical connections you can configure. Selecting a card creates no accounts or resources.
Compare the alternatives
Learn the boundary before you connect it
Lessons open through your account and the kits you own.
Check the evidence
Feature sources were reviewed on 4 Oct 2026. Plans and availability can change.
- Pages overview ↗
Static framework hosting and functions.
- Function billing ↗
Functions use Workers plans.
- Workers migration ↗
Current alternative deployment route for Pages projects.