Cloudflare Pages vs Netlify — free-tier comparison
Cloudflare Pages and Netlify are mature frontend platforms with Git deploys, previews, HTTPS and functions. Cloudflare is strongest when Workers and its global network fit the architecture; Netlify offers a broad integrated workflow for Jamstack teams.
Last reviewed: 2026-07-15
At a glance
Choose Cloudflare Pages for edge-first projects and Workers integration. Choose Netlify when its deploy workflow, forms, functions and site-management ecosystem save more engineering time. Compare current plan accounting before a traffic-heavy launch.
Choose Cloudflare Pages if
- You want Pages Functions and the Workers ecosystem
- Cloudflare DNS, caching and security already serve the domain
- The app is designed around edge request handling
Choose Netlify if
- You value Netlify's integrated Jamstack workflow
- Forms, deploy previews and site tooling reduce custom code
- Your team already operates Netlify projects
Key differences
| Cloudflare Pages | Netlify | |
|---|---|---|
| Function runtime | Cloudflare Workers | Netlify Functions and Edge Functions |
| Plan accounting | Pages and Workers product limits | Current credit-based usage model |
| Ecosystem strength | Network, edge and security | Jamstack deployment workflow |
| Migration concern | Workers runtime compatibility | Netlify-specific features and configuration |
Static Hosting
Unlimited bandwidth, 500 builds/month
Paid from $20/month
- Unlimited bandwidth
- 500 builds/month
- Unlimited sites
- Unlimited bandwidth and requests on the free plan
- Global edge delivery from 300+ cities with free SSL
- 500 builds per month cap on the free plan
Best for
- Static sites and JAMstack apps (Astro, Next.js, SvelteKit)
- Projects that want edge functions close to users
Static Hosting
300 credits/month on the free plan
Paid from $9/month
- 300 monthly credits
- Free production deploys
- Deploy Previews
- Generous all-in-one free tier with functions, forms and identity
- Mature build pipeline with deploy previews and instant rollbacks
- Monthly credits can be limiting for frequent deploys or dynamic usage
Best for
- JAMstack and static front ends (React, Vue, Gatsby, Hugo)
- Sites that need forms or light serverless without a back end
The catch?
Cloudflare Pages
- No catch
Netlify
- No catch
Detailed comparison
| Cloudflare Pages | Netlify | |
|---|---|---|
| Free tier & pricing | ||
| Free tier ↑ better | Perpetual ★ | Perpetual ★ |
| Paid from ↓ better | $20/mo | $9/mo ★ |
| Regions ↑ better | 310+ cities ★ | Global CDN |
| Hébergement statique | ||
| Bandwidth ↑ better | Unlimited | Credit-based |
FAQ
Both work well. Cloudflare is compelling for edge integration; Netlify can be simpler when its built-in workflow features replace custom services.
Static output is portable. Functions, environment variables, redirects, forms and build plugins need platform-specific migration.
Both have supported Astro deployment paths. Choose from required adapters, function runtime, previews and the rest of your infrastructure.