Cloudflare Pages

Free static hosting on Cloudflare’s network with unlimited bandwidth, integrating with Workers for edge compute; a generous free tier.

Visit Cloudflare Pages →

Some links may be affiliate links — we may earn a commission if you sign up, at no extra cost to you. It never affects our rankings. Learn more.

Cloudflare Pages is a Git-connected hosting platform for static sites and Jamstack front-ends, serving assets from Cloudflare's global edge network with no bandwidth limits. It pairs static hosting with Pages Functions (serverless code on the Workers runtime) for server-side rendering and dynamic APIs, and offers native bindings to Cloudflare storage services such as KV, D1, and R2. As of 2025-2026, Cloudflare recommends Workers with static assets as the default path for new full-stack projects, while existing Pages projects remain fully supported.

Key features

Git integration with automatic deploys from GitHub or GitLab
Per-branch and per-pull-request preview deployments
Global edge delivery with no bandwidth caps
Custom domains with automatic free SSL/TLS
Pages Functions for serverless SSR and APIs on the Workers runtime
Native bindings to Cloudflare KV, D1, R2, and Workers

Specs

Category	Static / Jamstack
Pricing model	tiered
Free tier	Yes
Managed database	Yes
Regions	global edge
Self-hostable	No
Docker-native	No
Git deploy	Yes
Open source	No

Last reviewed 2026-07-16 — see our methodology. Specs, pricing and free tiers change often, so confirm current details on the provider before deciding.

Pros & cons

Our editorial assessment — not vendor-stated facts.

Pros

Unlimited bandwidth and requests for static assets, including on the free tier
Low-latency global delivery from Cloudflare's edge network
Tight integration with the broader Cloudflare developer ecosystem
Git-based CI/CD with automatic preview environments per branch and PR

Cons

Cloudflare now steers new full-stack projects toward Workers with static assets, and several newer platform capabilities (for example, Containers and Workflows) land on Workers first or only
The free-tier build system is constrained: 500 builds per month and a single concurrent build
A 25 MiB per-file cap and a 20,000-file limit on the free plan can be limiting for asset-heavy sites
Dynamic functionality relies on the Cloudflare-specific Functions/Workers model, adding some platform lock-in

Pricing

The free tier includes unlimited bandwidth, free SSL, and a capped monthly build allowance (500 builds per month, one concurrent build); paid plans raise build counts, build concurrency, and the per-site file limit. Pages Functions are billed on a usage basis at the same rates as Cloudflare Workers, and their requests count toward your Workers quota.

Who should use Cloudflare Pages?

Developers deploying static sites, SPAs, or Jamstack front-ends who want unlimited bandwidth, global edge performance, and Git-based deploys, especially teams already using the Cloudflare ecosystem. Those starting substantial new full-stack apps may prefer Workers with static assets, which Cloudflare now recommends as the default going forward.

Frequently asked questions

Does Cloudflare Pages have a free tier?: Yes.
How much does Cloudflare Pages cost?: The free tier includes unlimited bandwidth, free SSL, and a capped monthly build allowance (500 builds per month, one concurrent build); paid plans raise build counts, build concurrency, and the per-site file limit. Pages Functions are billed on a usage basis at the same rates as Cloudflare Workers, and their requests count toward your Workers quota.
Who should use Cloudflare Pages?: Developers deploying static sites, SPAs, or Jamstack front-ends who want unlimited bandwidth, global edge performance, and Git-based deploys, especially teams already using the Cloudflare ecosystem. Those starting substantial new full-stack apps may prefer Workers with static assets, which Cloudflare now recommends as the default going forward.