Updated September 23, 2026 · 12 min read
Netlify vs Cloudflare Pages for agencies hosting static client sites: free limits, seats, drag-and-drop, domains, forms, and the shift to Workers.
Short answer: For a plain static site, Cloudflare Pages is more generous: unlimited bandwidth, requests, and seats, even on the free plan. Netlify’s Free plan gives 300 credits a month and pauses every project when they run out. Netlify wins on built-in forms and easier custom domains (official docs, checked September 2026). Cloudflare now says: “Start new projects with Workers.”
In this guide
- Netlify vs Cloudflare Pages at a glance
- Free limits: what happens when you hit them
- Netlify vs Cloudflare cost for a small agency: a worked example
- Drag-and-drop and other deploy methods compared
- Custom domains: the DNS difference that matters for client sites
- Forms and functions: where Netlify wins
- Cloudflare says “Start new projects with Workers”: what it changes
- Performance and trust: what we can honestly say
- Netlify vs Cloudflare Pages: which should your agency pick?
- Where sofast fits
- Frequently asked questions
Most Netlify vs Cloudflare comparisons are written for developers choosing a platform for a JavaScript app. Many still quote Netlify prices that new accounts can no longer choose. This guide is for a small agency like Studio Marchand, which hosts static client sites and wants zero non-billable hosting chores. It compares Netlify and Cloudflare Pages on free limits, team seats, drag-and-drop, domains, forms, and what happens at the limit. For the full background on one side, read our pillar guide what is Cloudflare Pages.
Netlify vs Cloudflare Pages at a glance
Both platforms host static websites, give each project a free address, and support Git and drag-and-drop deploys. A static website is a set of ready-made files, such as HTML, CSS, JavaScript, and images, sent to the browser as they are. Netlify gives projects a netlify.app address. Cloudflare Pages gives them a pages.dev address, served from Cloudflare’s network in 348 cities (cloudflare.com/network, checked September 2026).
The table compares the free plans row by row. Sources: Netlify pricing page and docs, Cloudflare Pages product page and docs, all checked September 2026.
| Criterion | Netlify (Free plan) | Cloudflare Pages (Free plan) |
|---|---|---|
| Price | $0; Personal $9/month; Pro from $20/month | $0; “unlimited sites, seats, requests, and bandwidth” on all plans |
| Monthly allowance | 300 credits, hard limit | 500 builds; static requests unlimited |
| Bandwidth | 20 credits per GB (15 GB maximum if you spend nothing else) | Unlimited |
| Deploys | 15 credits per production deploy | 500 builds per month, 1 at a time |
| Team members | 1 free member (Pro: unlimited members) | Unlimited seats |
| Commercial use | No non-commercial rule on the pricing page | No non-commercial rule on the product or limits pages |
| Deploy methods | Git, Netlify CLI, API, Netlify Drop drag-and-drop | Git (GitHub, GitLab), Wrangler CLI, dashboard drag-and-drop |
| Drag-and-drop limits | No account needed to start; under 50 MB works best | Up to 1,000 files and 25 MiB per file; folder or ZIP |
| Custom domains | Included with automatic HTTPS; works with any DNS provider | 100 per project; root domain requires Cloudflare nameservers |
| Forms | Netlify Forms, free and unlimited | No built-in service; Static Forms plugin needs Pages Functions |
| Server-side functions | Netlify Functions, 10 credits per GB-hour of compute | Pages Functions, 100,000 requests per day (shared with Workers) |
| What happens at the limit | All projects paused until the next billing cycle | Static requests keep being free; Functions capped per day |
| Status in 2026 | Current product | Supported; Cloudflare says “Start new projects with Workers” |
In plain terms: Bandwidth is the amount of data your site sends to visitors. Every page view downloads your HTML, CSS, and images, and that volume adds up.
Free limits: what happens when you hit them
This is the row that decides most Netlify vs Cloudflare choices for static sites. Netlify’s credit-based plans apply to all accounts created since September 4, 2025. The Free plan includes 300 credits per month as a hard limit. A production deploy costs 15 credits, and each GB of bandwidth costs 20 credits. Every 10,000 requests cost 2 credits (Netlify credit-based plans docs, updated September 1, 2026).
When Netlify Free credits run out, the consequence is strict. Netlify’s docs say “all of your web projects (sites/apps) are paused.” Visitors “will find a Site not available page” until the next billing cycle (How credits work, updated August 12, 2026). The pricing page adds: “We’ll notify you by email and in-app as you approach” the limit. For an agency, one busy client site can pause every other site on the same team.
In plain terms: A credit is Netlify’s single unit of usage. Deploys, bandwidth, requests, and compute each cost a set number of credits from one monthly pool.
Cloudflare Pages works the other way round for static files. Its product page states: “All plans come with unlimited sites, seats, requests, and bandwidth.” The Pages Functions pricing page confirms that “requests to static assets are free and unlimited” on free and paid plans (updated September 8, 2026). The free limits that remain are about building and file counts, not traffic.
The Cloudflare Pages free plan allows 500 builds per month, one at a time, with a 20-minute timeout. Each site can hold 20,000 files of up to 25 MiB, and each account 100 projects (Pages limits docs, updated September 5, 2026). A MiB (mebibyte) is about 1.05 MB. For a typical brochure site, none of these limits comes close.
A warning about older articles: if a comparison quotes Netlify Pro at $19 per member, it describes legacy plans. Netlify’s docs say new accounts cannot pick legacy plans, and switching to credits is irreversible (Legacy pricing plans docs, updated January 10, 2026). Our Netlify pricing guide explains every credit cost with worked scenarios.
Netlify vs Cloudflare cost for a small agency: a worked example
Imagine a small agency like Studio Marchand with eight static client sites. Each site is updated four times a month, sends 2 GB of data, and serves 20,000 requests. These numbers are hypothetical; the arithmetic uses the official credit costs above.
The Netlify calculation
On Netlify, one site uses 60 credits for 4 deploys, 40 credits for 2 GB, and 4 credits for 20,000 requests. That is 104 credits per site, or 832 credits for eight sites. This estimate exceeds the Free plan’s 300 credits. It fits inside the Personal plan’s 1,000 credits at $9 per month.
The catch is seats. Netlify’s pricing page says the Free plan is “Limited to 1 free member,” and Personal is “$9/month for 1 member.” An agency with three people who deploy would need Pro, which costs “$20/month for unlimited members” with 3,000 credits (Netlify pricing page, checked September 2026). Since April 14, 2026, Pro has no per-seat charge, which is good news for growing studios.
The Cloudflare Pages calculation
On Cloudflare Pages, the same eight static sites cost $0. Bandwidth and static requests are unlimited, seats are unlimited, and 100 projects per account leaves plenty of room. The only counter that moves is builds. Eight sites × 4 Git builds = 32 builds a month, far below 500.
The honest conclusion: for pure static hosting, Cloudflare Pages costs less in this example, and the gap grows with traffic. Netlify’s price buys other things, covered below: built-in forms and simpler domains on client-owned DNS.
Drag-and-drop and other deploy methods compared
Many agency sites start as a folder from an AI tool or a design app, so the no-Git path matters. Both platforms offer one, with different rules.
Netlify Drop lives at app.netlify.com/drop. You drag “a project folder containing your site files” onto the page (Create deploys docs), and there is “no account required.” A drop made without signing in “is protected with a temporary password until you claim it.” Deploys under 50 MB work best, and single files over 10 MB may get stuck (Netlify Drop quickstart, updated July 28, 2026). Unclaimed drops are temporary and expire unless you claim them with an account.
To update a Netlify site, you use the dropzone at the bottom of the site’s Deploys page. You drag in “the project’s updated output folder” (Create deploys docs, updated July 28, 2026). Each production update costs 15 credits on credit-based plans. Netlify also documents Git deploys, the Netlify CLI, the API, and deploys started by AI agents from its dashboard.
Cloudflare Pages Direct Upload is the dashboard drag-and-drop path. You go to Workers & Pages, select Create application, then “Drag and drop your files,” name the project, and select Deploy site. The dashboard accepts “A zip file or single folder of assets,” up to 1,000 files and 25 MiB per file. The Wrangler command-line tool raises that to 20,000 files (Direct Upload docs, updated April 21, 2026).
Two Direct Upload rules matter for agencies. First, “If you choose Direct Upload, you cannot switch to Git integration later.” You would need a new project. Second, “Drag and drop deployments made from the Cloudflare dashboard do not currently support compiling a functions folder.” To update a Direct Upload site, you open the project and select Create a new deployment, for production or preview.
In plain terms: Git is a system that records every version of a set of files. A Git deploy publishes your site automatically each time someone pushes a change.
Custom domains: the DNS difference that matters for client sites
Both Netlify and Cloudflare Pages include custom domains on the free plan. The difference is where the domain’s DNS must live. DNS (Domain Name System) is the internet’s address book that points a name like example.com to a server.
Netlify works with the client’s current DNS provider. For www, you add a CNAME record pointing to the project’s netlify.app address. For the root domain, Netlify recommends an ALIAS, ANAME, or flattened CNAME to apex-loadbalancer.netlify.com, or an A record to 75.2.60.5. Netlify’s docs confirm this does not require moving nameservers (External DNS docs, updated October 28, 2025). Netlify then issues free Let’s Encrypt HTTPS certificates automatically.
Cloudflare Pages treats roots and subdomains differently. For an apex (root) domain such as example.com, its docs say “you will need to add your site as a Cloudflare zone and configure your nameservers.” For a subdomain, “it is not necessary for your site to be a Cloudflare zone.” A CNAME record to the pages.dev address is enough (Custom domains docs, updated April 21, 2026).
In plain terms: Nameservers decide which company manages all of a domain’s DNS records. Moving them moves everything, including the email (MX) records.
For Studio Marchand, this is the practical difference. Many small-business clients keep their domain and email at a registrar they chose years ago. With Netlify, you add two records and leave the rest alone. With Cloudflare Pages on a root domain, the client moves the whole DNS zone to Cloudflare. Cloudflare says to “wait up to 24 hours” for a registrar to update nameservers. Plan that step with the client, and check every email record before the switch.
Forms and functions: where Netlify wins
Many static client sites need a contact form. This is the clearest Netlify vs Cloudflare Pages win for Netlify. Netlify Forms is free and unlimited on all credit-based plans, including Free (Forms usage and billing docs, updated September 16, 2026). You enable form detection under Forms, add data-netlify="true" to your HTML form, and redeploy. Submissions then appear in the Forms section of the Netlify dashboard (Forms setup docs, updated September 16, 2026).
Cloudflare Pages has no equivalent built-in form service. Cloudflare’s Static Forms plugin “intercepts all form submissions made which have the data-static-form-name attribute set.” But it is a Pages Functions plugin, installed with npm. You must write code to store the data (Static Forms docs, updated April 21, 2026). Remember the Direct Upload rule: dashboard drops cannot compile a functions folder.
In plain terms: A serverless function is a small program the host runs on demand, for example when a visitor sends a form.
For server-side code in general, both platforms offer functions. Netlify Functions are included on Free, and compute costs 10 credits per GB-hour. Cloudflare Pages Functions are “billed as Cloudflare Workers requests.” On the free plan, they share a daily limit of 100,000 requests with Workers, which “resets at midnight UTC” (Pages Functions pricing, updated September 8, 2026). For a form-only need, a third-party form service also works on either host. Our list of the best form builders for static sites compares them.
Cloudflare says “Start new projects with Workers”: what it changes
Any Netlify vs Cloudflare Pages decision in 2026 must include Cloudflare’s own direction. The Pages docs homepage now says: “Workers supports most Pages use cases and offers a broader feature set. It is Cloudflare’s primary platform for building applications. Start new projects with Workers” (updated August 25, 2026).
This follows an April 2025 announcement. Cloudflare wrote that Pages “will continue to be supported, but, going forward, all of our investment, optimizations, and feature work will be dedicated to improving Workers.” No official Cloudflare page we checked calls Pages deprecated or gives an end date. The accurate summary: still supported, but new development goes to Workers.
Workers static assets keep the key advantage: “Requests to static assets are free and unlimited” (Workers pricing docs, updated August 28, 2026). But the Workers setup is more technical than a Pages dashboard drop. Our comparison of Cloudflare Pages vs Workers explains the deploy paths and the migration steps.
For an agency, the practical reading is simple. Existing Cloudflare Pages sites keep working, and nothing forces a move today. For a new client project, a developer on your team should start on Workers, as Cloudflare advises. A designer who only wants to drag a folder will find Netlify, or a drag-and-drop host, more direct.
Performance and trust: what we can honestly say
Cloudflare says its network spans 348 cities. We have not run a speed benchmark, and we do not repeat third-party latency charts. For a static brochure site, image weight and fonts are the first things to optimize on either host. On trust, both companies publish dated pricing and limits documentation. Neither free plan is limited to non-commercial use on the pages we checked, unlike Vercel’s Hobby plan. For a wider view, see our Vercel vs Netlify vs Cloudflare Pages comparison.
Netlify vs Cloudflare Pages: which should your agency pick?
Choose Cloudflare Pages if your sites are purely static, traffic may spike, and several people need access at $0. You accept that root domains need Cloudflare nameservers, and that Cloudflare now points new projects to Workers.
Choose Netlify if client sites need a no-code contact form, or clients keep DNS at their registrar. It also suits teams that update by dragging a folder onto a dashboard. You accept the 300-credit Free limit, the one-member Free plan, and paused projects if credits run out.
Use this decision tree and stop at the first “yes”:
- Do your sites need built-in form handling with no code? Choose Netlify; Netlify Forms is free and unlimited.
- Must the client keep DNS and email at their current registrar, on a root domain? Choose Netlify, which works with external DNS.
- Will more than one person deploy, on a $0 budget? Choose Cloudflare Pages for unlimited seats.
- Could traffic exceed about 15 GB a month on one free account? Choose Cloudflare Pages for unlimited bandwidth.
- Is a developer starting a brand-new Cloudflare project? Follow Cloudflare’s advice and start with Workers.
- Do you want neither Git, credits, nor a developer dashboard? Look at drag-and-drop hosts in our list of Netlify alternatives.
Where sofast fits
sofast is not a third developer platform in this comparison. It answers the last question in the decision tree. sofast hosts static HTML sites by drag-and-drop upload: no Git, no command line, and automatic SSL (Secure Sockets Layer, the certificate behind HTTPS). sofast says a typical upload is live in about 15 seconds. It is built on Cloudflare’s global network, but it does not run on the Cloudflare Pages product.
The Free plan costs $0 for one site, 50 MB, and a sofast subdomain, with no credit card, and commercial use is allowed. Custom domains start on paid plans: Starter at $5 per month, Pro at $10, and Large at $20, billed annually. Monthly billing is $6, $12, and $24. Details are on the sofast pricing page.
The limits are real. sofast has no Git workflow, no form handling, no server-side functions, and no build step. Unknown paths return a 404, so each page needs its own HTML file. Netlify and Cloudflare Pages both include free custom domains, and sofast does not. sofast is also a new service. Choose sofast if your team wants client folders online without learning a developer platform.
Frequently asked questions
For plain static hosting, usually yes. Cloudflare Pages includes unlimited bandwidth, requests, and seats on its free plan, with 500 builds per month (Cloudflare docs, checked September 2026). Netlify’s Free plan gives 300 credits a month and one member. Netlify is better if you need built-in forms, want root domains without moving nameservers, or prefer its drag-and-drop update flow.
Yes, with a hard limit. Netlify’s Free plan costs $0 and includes 300 credits per month. A production deploy costs 15 credits and each GB of bandwidth costs 20 credits, so 20 deploys use the whole month. When credits run out, all projects are paused and show a “Site not available” page until the next billing cycle (Netlify docs, checked September 2026).
Netlify has four plans on its credit-based pricing. Free costs $0 for 300 credits. Personal costs $9 per month for 1,000 credits and one member. Pro starts at $20 per month for 3,000 credits with unlimited members, and tiers go up to $126 for 20,000 credits. Enterprise is custom (Netlify pricing page and docs, checked September 2026).
Three stand out for static sites. The Free plan’s 300 credits run out fast if you deploy often, since each production deploy costs 15 credits. When credits run out, every project on the team is paused until the next cycle. And the Free plan allows only one member, so agencies with several people usually need Pro at $20 per month (Netlify docs, checked September 2026).
Yes. Cloudflare Pages is the closest free alternative for static sites, with unlimited bandwidth and seats, though Cloudflare now recommends Workers for new projects. GitHub Pages is free for public repositories but prohibits online businesses. Drag-and-drop hosts such as sofast offer a free plan too: one site, 50 MB, and a subdomain, with commercial use allowed.
Not as a built-in service. Netlify Forms is free and unlimited on all credit-based plans. Cloudflare offers a Static Forms plugin that intercepts submissions from forms with a data-static-form-name attribute, but it runs as a Pages Function and needs code to store data. Dashboard drag-and-drop deploys cannot compile a functions folder (Cloudflare docs, checked September 2026).
Only for a subdomain. Cloudflare’s docs say a subdomain such as www.example.com can point to your pages.dev address with a CNAME record at your current DNS provider. A root domain such as example.com must be added as a Cloudflare zone, with nameservers pointed to Cloudflare (Cloudflare docs, updated April 21, 2026). Netlify supports both without a nameserver change.
No. Cloudflare Pages is still supported, and no official Cloudflare page we checked in September 2026 gives an end date. However, Cloudflare said in April 2025 that all new feature work would go to Workers. Since August 2026, the Pages documentation says: “Start new projects with Workers.” Existing Cloudflare Pages sites keep working.
Sources
- Netlify pricing page (Free “Limited to 1 free member”, Personal “$9/month for 1 member”, Pro “$20/month for unlimited members”, paused state and email notification, no non-commercial restriction stated; checked 2026-09-23)
- Netlify Docs, Credit-based pricing plans (300 / 1,000 / 3,000 credits, Pro tiers to $126; updated 2026-09-01)
- Netlify Docs, How credits work (credit costs; projects paused, “Site not available”; updated 2026-08-12)
- Netlify Docs, Legacy pricing plans (new accounts cannot pick legacy plans; updated 2026-01-10)
- Netlify Blog, Pricing Netlify for 3 billion builders (unlimited Pro members, 2026-04-14)
- Netlify Docs, Netlify Drop quickstart (no account required, temporary password, 50 MB / 10 MB guidance; updated 2026-07-28)
- Netlify Docs, Create deploys (Git, CLI, API, drag and drop, update via Deploys page dropzone, AI agents; updated 2026-07-28)
- Netlify Docs, Configure external DNS (CNAME, ALIAS to apex-loadbalancer.netlify.com, A record 75.2.60.5, no nameserver change; updated 2025-10-28)
- Netlify Docs, HTTPS (SSL) (automatic Let’s Encrypt certificates)
- Netlify Docs, Forms setup (enable form detection, data-netlify=”true”, submissions in Forms section; updated 2026-09-16)
- Netlify Docs, Forms usage and billing (free and unlimited on credit-based plans; updated 2026-09-16)
- Cloudflare Pages product page (“All plans come with unlimited sites, seats, requests, and bandwidth”; no non-commercial restriction stated; checked 2026-09-23)
- Cloudflare Pages limits (500 builds, 1 concurrent, 20-minute timeout, 20,000 files, 25 MiB, 100 custom domains, 100 projects; updated 2026-09-05)
- Cloudflare Pages Direct Upload (dashboard path, ZIP or folder, 1,000 files via dashboard, 20,000 via Wrangler, cannot switch to Git, no functions folder, Create a new deployment; updated 2026-04-21)
- Cloudflare Pages custom domains (apex requires Cloudflare zone and nameservers; subdomain CNAME; updated 2026-04-21)
- Cloudflare Pages Functions pricing (billed as Workers requests, 100,000 requests/day on free, resets midnight UTC, static assets free and unlimited; updated 2026-09-08)
- Cloudflare Pages Static Forms plugin (data-static-form-name, Pages Function via npm; updated 2026-04-21)
- Cloudflare Pages docs homepage (“Start new projects with Workers”; updated 2026-08-25)
- Cloudflare blog, Full-stack development on Cloudflare Workers (2025-04-08)
- Cloudflare Workers pricing (static asset requests free and unlimited; updated 2026-08-28)
- Cloudflare DNS full setup (nameserver update up to 24 hours)
- Cloudflare network (348 cities; checked 2026-09-22)
- Vercel fair use guidelines (Hobby non-commercial; updated 2026-09-14)
Start free — no credit card required → Create your free site