Last checked: 2026-10-27 — verify pricing/features on vendor sites before buying

Cloudflare Pages vs Netlify for Static Sites: Limits, DX, When to Pick

Both platforms make git-based static deploys easy. The differences that matter for indies are free-tier quotas, Functions/edge model, and how painful custom domains + previews feel day to day.

Quotas below are as of 2026-10 research notes. Cloudflare and Netlify change free plans—verify on official docs before you architect around a limit.

Side-by-side

Dimension	Cloudflare Pages	Netlify
Core job	Static + Pages Functions on Cloudflare network	Static + Netlify Functions / ecosystem
Free tier sketch	Historically generous builds/bandwidth — verify	Useful free tier with build minute caps — verify
DX	Fast once DNS lives on Cloudflare; wrangler for advanced	Very polished UI, drop-in forms/identity add-ons
Previews	Preview deployments on PRs	Deploy previews (a Netlify strength)
Edge / functions	Workers-aligned model	Netlify Functions + Edge Functions
Best fit	Already on Cloudflare DNS; want edge-native path	Want batteries-included Jamstack UX

Pick Cloudflare Pages if…

Your DNS already runs through Cloudflare.
You want a straight path into Workers/R2 later.
You are optimizing for free-tier headroom on static sites (still verify current quotas).

Pick Netlify if…

You want the smoothest preview + plugin ecosystem out of the box.
Your team already standardized on Netlify Identity/Forms/etc.
You value UI polish over Cloudflare-native coupling.

Smoke test both in one afternoon

Push the same Astro/Next static site to both from GitHub.
Attach a test subdomain; check HTTPS and redirect rules.
Open a PR and confirm preview URLs.
Hit one serverless function endpoint if you use functions.
Read build-minute and bandwidth counters after a few deploys.

Cloudflare (placeholder)Netlify (placeholder)

Last checked: 2026-10-27. Related: How we benchmark.

/go/ links are placeholders until affiliate programs approve. Last checked: 2026-10-27.