Cloudflare Pages Alternatives (2026): Static Hosts Compared

The main Cloudflare Pages alternatives in 2026 are Cloudflare's own Workers with static assets, which Cloudflare now recommends for new projects; Netlify, for built-in forms on a free plan; Vercel, for Next.js; Render, for a static site beside a backend; GitHub Pages and Surge, for simple free hosting; and Statpio, for static business sites with forms, statistics and a password included. Pages itself is still supported, and it remains the better Cloudflare option when your domain's DNS stays with another provider and the site lives on a subdomain such as www.

Disclosure: this guide is published by Statpio, one of the tools compared. We link every competitor fact to its official source. Every price and limit below was checked on the vendor's official pages on 10 November 2026.

Is Cloudflare replacing Pages with Workers?

Not replacing it, but steering new projects away from it. The Cloudflare Pages docs, last updated on 25 August 2026, open with "Are you sure you want to use Pages?" and answer: "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." Cloudflare set the direction on its blog in April 2025: "Cloudflare Pages will continue to be supported, but, going forward, all of our investment, optimizations, and feature work will be dedicated to improving Workers."

For a static site the cost is about the same: "Like Pages, requests for static assets on Workers are free" (Pages to Workers migration guide). A Worker with static assets serves your build folder, reads the same _headers and _redirects files, and counts only the requests that run Worker code toward your plan, 100,000 a day on Workers Free (Workers pricing).

When is Cloudflare Pages still the right choice?

Cloudflare's migration guide, its compatibility matrix and its April 2025 blog post point to three cases:

• Your DNS stays with another provider. Pages can serve a subdomain through a CNAME at your current DNS host, but "Workers does not support any domain whose nameservers are not managed by Cloudflare" (migration guide). A root domain on Pages needs Cloudflare's nameservers too (Pages custom domains).
• You rely on Pages' Git workflow. Branch deploy controls and Pages Functions' file-based routing and plugins are supported on Pages and marked "Unsupported, workaround available" on Workers (compatibility matrix).
• Your Pages project already works. Cloudflare says Pages "will continue to be supported" (April 2025 blog), and its docs give no end date for it.

For anything new, Cloudflare's advice is to start with Workers.

What are Cloudflare Pages' limits?

Sources, as of November 2026: Pages limits, Pages Functions pricing, Workers limits, Workers pricing, Workers Builds limits and the migration guide.

Paid Cloudflare plans raise the Pages build allowance to 5,000 a month on Pro and 20,000 on Business (Pages limits), and the Workers Paid plan costs "a minimum charge of $5 USD per month for an account" (Workers pricing). Two gaps matter more than the numbers. There's no form inbox: the Static Forms plugin hands each submission to code you write, for example to save it to KV. And there's no password setting: the built-in access policy "will only protect your preview deployments", not your *.pages.dev address or custom domain (preview deployments). Putting those behind Cloudflare Access sign-in takes a manual Zero Trust setup, described on Cloudflare's known issues page. Zero Trust asks for payment details even on its Free plan, which isn't charged (Zero Trust setup).

How do the Cloudflare Pages alternatives compare?

Sources, as of November 2026: Cloudflare Pages limits, Functions pricing, Access on Pages, Workers custom domains, Workers and Cloudflare Access, Web Analytics on Pages, Web Analytics setup and Cloudflare terms; Netlify pricing, credit plans and Netlify vs Vercel guide; Vercel Hobby, fair use and password protection; Render pricing, custom domains and terms; GitHub Pages limits, GitHub pricing and GitHub's plans; Surge pricing, analytics and terms. Statpio figures come from the pricing page.

Cloudflare Pages vs Netlify: which should you use?

Use Netlify if you want forms without writing code; stay on Cloudflare if traffic is the concern. Netlify's forms service is "free and unlimited for all credit-based plans", its Free plan includes custom domains with SSL, and Netlify says its free plan "can be used for commercial projects and businesses" (how credits work, Netlify pricing, Netlify vs Vercel guide). But Netlify meters what Cloudflare gives away: as of November 2026 the Free plan has a hard limit of 300 credits a month, bandwidth costs 20 credits per GB, and when the credits run out every project on the account pauses (how credits work). Analytics on Free cover the current or past day, and password protection is Pro only, at $20 a month (credit plans, Netlify pricing). New Free projects show a "Powered by Netlify" badge by default, which you can switch off (badge docs).

Best for: a modest-traffic site that needs a contact form today. See our Netlify alternatives for more.

Cloudflare Pages vs Vercel: which should you use?

Use Vercel for a Next.js app that needs server rendering, and Cloudflare for a static site on a free plan. Vercel's Hobby plan includes 100 GB of Fast Data Transfer, 1,000,000 CDN requests and Web Analytics with 50,000 events a month, but "Hobby teams are restricted to non-commercial personal use only", and over a limit you usually wait 30 days (Hobby plan, fair use). Pro is $20 a month for one deploying seat with $20 of usage credit (Pro plan), and password protection on Pro costs $20 a month per project (password protection).

Best for: Next.js projects that are commercial enough to pay for Pro. Our Vercel alternatives page compares it for static sites.

Is Render a good Cloudflare Pages alternative?

If your static site sits next to a backend, yes. Render's static sites are "fast and free to deploy", with redirect and rewrite rules in the dashboard, custom response headers and a preview for each pull request, and the same workspace runs web services and Postgres databases (Render static sites, Render pricing). The free Hobby workspace includes 5 GB of bandwidth a month and 2 custom domains (custom domains); past the bandwidth, Render charges $0.15 per GB if a payment method is linked and otherwise spins your services down until the next month (outbound bandwidth). Pro is $25 a month plus compute, with 25 GB of bandwidth.

Best for: a front end whose API or database also runs on Render. For a busy site with no backend, Cloudflare's free static requests are hard to beat.

Are GitHub Pages or Surge good free Cloudflare Pages alternatives?

Both are free and simpler than Cloudflare, with tighter rules. GitHub Pages publishes from a public repository for free, with custom domains and HTTPS, sites up to 1 GB and a soft bandwidth limit of 100 GB a month, but it "is not intended for or allowed to be used as a free web-hosting service to run your online business" (GitHub Pages limits); our GitHub Pages alternatives page covers it.

Surge publishes a folder from the command line. As of November 2026, its Free plan includes unlimited projects and domains, custom domains with automatic certificates and the last 100 revisions, with "no bandwidth billing and no overage charge", for projects up to 450 MB and 10,100 files (Surge pricing). Password protection and redirect rules are Pro, at $30 a month, and Surge's terms offer its surge.sh subdomains "for the purpose of testing, learning, and developing software projects" (Surge terms), so use your own domain for anything that matters.

Best for: GitHub Pages for open-source docs; Surge for developers and coding agents who want one command and nothing metered.

Is Statpio a good Cloudflare Pages alternative?

For a static business site, yes, and it doesn't take you off Cloudflare's network: Statpio serves websites from Cloudflare's global network. What changes is that the parts you'd build yourself on Pages come included:

• Forms without a Function: any <form method="POST"> without an action is captured, with a visible Turnstile check, a honeypot and file uploads, 250 submissions per website a month on Free Forever and 10,000 on Solo Pro. New messages arrive as browser notifications.
• Analytics: cookieless, on every plan, with campaigns, goals, funnels and Core Web Vitals from Solo Pro.
• A password on the live site, on every plan, where Pages' built-in policy covers previews only and the live site needs a manual Cloudflare Access setup.
• A staging address on Solo Pro and up: a new version goes to its own address first, for you and anyone you send the link to, then live in one click.
• Custom domains without moving nameservers: two CNAME records at your registrar, from Solo Pro; a root domain is served through www. Pages also takes a CNAME for a subdomain such as www, but a root domain served by Pages needs Cloudflare's nameservers (Pages custom domains).

The trade-offs are real. Statpio runs no server code, so there are no Functions, server-side rendering or API routes; it doesn't read _redirects or _headers files; and Free Forever allows 1 website with a Statpio badge and no custom domain. Solo Pro is $9 a month for 5 websites and 5 custom domains, with GitHub deploys. Bandwidth is listed as unmetered on every plan. For a React or Vite build, see how to deploy a React or Vite app for free.

Best for: a static site that needs forms, statistics and a password, without writing or maintaining Functions.

Which Cloudflare Pages alternative should you pick?

• A new project you want to keep on Cloudflare: Workers with static assets, as Cloudflare recommends.
• DNS staying outside Cloudflare, or a working Pages setup: stay on Pages.
• A contact form without code, on a free plan: Netlify, or Statpio if you also want statistics and a password on the free plan.
• Next.js with server rendering: Vercel, on Pro for commercial work.
• A static site plus an API or database: Render.
• Open-source docs: GitHub Pages. One command and nothing metered: Surge.

How do I move a site off Cloudflare Pages?

1. Build the site locally. Run your build and check that the output folder has index.html at the top.
2. List what needs host support. Pages Functions, a _worker.js file, _redirects and _headers all need a host that supports them. Functions and _worker.js are Cloudflare features (migration guide); Netlify also reads _redirects and _headers files (redirects, headers). On Statpio, an app with client-side routing uses SPA mode, and a site of separate pages can include a 404.html for missing pages; other redirect and header rules aren't supported.
3. Replace a form Function. On Statpio, keep method="POST", remove the action attribute and any JavaScript submit handler, and name every field.
4. Publish. Drag a ZIP of the output folder onto a new Statpio website, or connect the GitHub repository on Solo Pro and up.
5. Move the domain. Add it in the Statpio dashboard and create the two records it shows: a CNAME for www to cname.onstatpio.com and the _acme-challenge.www validation record. Forward the root domain to www.
6. Retire the Pages project. Once the new site loads on your domain over HTTPS, test a form, remove the domain from the Pages project and delete the project.

If you want forms, statistics and a password without writing Functions, start on Free Forever and compare Solo Pro on the pricing page for your own domain.