· deployment / cloudflare-pages / vercel

Best deploy platform for static sites in 2026

Cloudflare Pages wins for most static sites: unlimited bandwidth, 500 builds/month free, fastest global edge network, no commercial-use restriction. Vercel wins only if you're on Next.js with a Pro budget.

By Ethan

1,477 words · 8 min read

Cloudflare Pages is the best deploy platform for most static sites in 2026: unlimited bandwidth, 500 builds/month free, fastest global TTFB, no commercial-use restriction. If you’re on Next.js with a Pro budget, Vercel still has the tightest framework DX. Everyone else is behind on at least one axis that matters.

One note before the breakdown: Cloudflare has no standard affiliate program, so this recommendation costs toolchew nothing to make. Vercel and Netlify both have affiliate programs; toolchew has no active accounts with either. The top pick here is chosen on merit, not margin.

Who this is for

Developers deploying Astro blogs, Next.js static exports, or SvelteKit pre-rendered sites who want to know where to host in 2026. If your site uses server-side rendering, edge functions, or dynamic routes at request time, you’re picking a compute platform — the tradeoffs are different and this comparison won’t cover them well.

What we looked at

Three representative workloads: an Astro blog (~50 pages), a Next.js 14 static export (~500 pages), and a SvelteKit pre-rendered site. Build config and CLI DX were hands-on. CDN performance is assessed from documented platform specifications (PoP count, cache reach) and published third-party benchmarks — toolchew did not run independent TTFB tests.

Platform summary

PlatformBandwidth (free)Builds/monthPreview deploysCommercial OKPaid starts at
Cloudflare PagesUnlimited500UnlimitedYes$20/mo
Vercel Hobby100 GB6,000 minUnlimitedNo$20/user/mo
Netlify Free~15 GB~20 deploysFree (not metered)Yes$20/mo
GitHub Pages100 GB (soft)10/hr (soft)NoneYesGitHub Enterprise
Render Static100 GB500 minYes (PR)YesFree (static)

Cloudflare Pages

Free tier: Unlimited bandwidth, 500 builds/month, 20-minute build timeout, unlimited preview deployments.

The unlimited bandwidth is the number that changes the calculus. Every other platform imposes a monthly cap that you have to track; Cloudflare Pages doesn’t. At 500 builds/month, a team running CI on every commit will hit the limit on active projects, but most single-developer sites won’t.

CDN performance is the other differentiator. Cloudflare operates 300+ points of presence globally. Published benchmarks consistently show Cloudflare’s edge network delivering sub-50ms TTFB across all tested regions; Vercel’s smaller network shows wider variance, with meaningfully higher latency outside its primary US/EU presence. On warm cache both are fast enough for most users, but the gap matters for international audiences and uncached requests.

Two limitations worth flagging. First: the free tier caps deployments at 20,000 files per build. A Next.js static export of 500 pages easily exceeds this once you count JS chunks, CSS, and image assets — check your next export output before assuming you’re within limits. Second: Next.js support is not first-class. There’s no official Vite plugin; you need the Workers Assets workaround instead. Astro, by contrast, gets full native support — The Astro Technology Company joined Cloudflare in January 2026, deepening the integration. SvelteKit works cleanly with adapter-cloudflare.

Pick Cloudflare Pages if: you want maximum bandwidth headroom, the fastest global CDN for static assets, and no commercial-use restrictions. Verify your file count for large Next.js exports.

Vercel

Free tier: 100 GB bandwidth, 6,000 build minutes/month, unlimited preview URLs, 100 deploys/day.

The commercial-use restriction on Hobby is broader than most users expect. Affiliate links on the site, banner ads, donations, or a single paid employee touching the project — any of these require upgrading to Pro at $20/user/month. Hobby is genuinely free only for personal side projects with no monetization path. Discover this after launch and the migration is not painless.

For Next.js teams on Pro, Vercel is still unmatched on DX. Incremental Static Regeneration, Partial Prerendering, and React Server Components all work natively — no adapter, no workaround. The vercel CLI is one command from repo to preview URL.

Pick Vercel if: you’re on Next.js, you have Pro budget, and you want zero-config framework DX with native ISR and RSC support. Don’t use Hobby for any project that earns revenue.

Netlify

Free tier: ~15 GB bandwidth (~20 production deploys), branch deploys and PR previews don’t consume credits.

The free tier arithmetic is confusing: 300 credits ÷ 20 credits/GB = ~15 GB bandwidth; ÷ 15 credits/deploy = ~20 production deploys per month. That’s tight. The positive side: branch deploys and preview deployments don’t count against credits, which keeps PR-based workflows practical even on the free plan.

April 2026 brought a hidden price increase. The Pro plan moved to flat $20/month unlimited seats — a good change for teams — but bandwidth now costs 20 credits/GB. Legacy users on plans established before September 4, 2025 have better terms with no credit math. Check your billing page to confirm which plan you’re actually on.

Pick Netlify if: you’re on a legacy plan (pre-September 2025) with generous included limits, or you need stable PR-preview workflows with free branch deploys. For new projects, the credit math makes Cloudflare Pages the better default.

GitHub Pages

Free tier: 100 GB/month bandwidth (soft limit), 1 GB repository limit, 10 builds/hour, 10-minute build timeout. No preview deployments.

The no-preview-deployments constraint is a dealbreaker for any team workflow. You can’t review a branch before merging to main without setting up a separate preview mechanism yourself. For a single developer pushing directly to main on an open-source docs site, GitHub Pages is a reasonable zero-setup choice that requires no new account.

The 1 GB repository limit becomes relevant if you store binary assets in the repo. For docs or Markdown-heavy sites with externally hosted images it’s usually fine.

Pick GitHub Pages if: you’re maintaining open-source documentation, you work alone, and you don’t need preview deployments.

Render static sites

Free tier: 100 GB/month bandwidth, 500 shared build minutes, PR preview deployments included, 2 custom domains on Hobby (additional at $0.25/month).

Render’s strength is the same-platform story. If your backend already runs on Render — API servers, workers, databases — keeping the frontend on Render eliminates cross-provider friction, shared environment variables, and separate billing relationships. The PR preview support is a real differentiator over GitHub Pages.

Outside of that context, Render doesn’t have a compelling reason to choose it over Cloudflare Pages. Bandwidth is capped, the CDN routes through Cloudflare’s network anyway, and static sites are free — but paid workspace tiers add cost once you bring other services along.

Pick Render if: your backend already runs there and the single-platform consolidation is worth more to you than Cloudflare Pages’ unlimited bandwidth.

CDN and edge performance

For static assets served from cache, Cloudflare Pages leads. Cloudflare’s 300+ PoP network outperforms Vercel’s smaller edge footprint on uncached requests and international traffic — published benchmarks show Cloudflare delivering sub-50ms across all tested regions while Vercel’s latency climbs for non-US/EU users. Render’s CDN performance on static assets is not publicly benchmarked against Cloudflare Pages or Vercel; treat it as unranked on this axis.

Netlify’s CDN sits in the middle range. GitHub Pages routes through Fastly.

None of these gaps are catastrophic for domestic audiences with warm caches. If you’re optimizing for global audiences or uncached performance, Cloudflare is the clear choice.

Verdict

  • Cloudflare Pages: best for most static sites. Unlimited bandwidth, fastest global CDN, no commercial restriction, first-class Astro support. Check the 20,000-file deploy limit for large Next.js exports.
  • Vercel Pro: best if you need native Next.js DX (ISR, PPR, RSC) and have the budget. Never use Hobby for monetized projects.
  • Netlify: worth staying on if you’re a legacy user with the older plan terms. Not competitive for new projects at current credit pricing.
  • GitHub Pages: fine for open-source docs with a single developer. Not suitable for team workflows.
  • Render: makes sense if your backend already lives there. Otherwise, no advantage over Cloudflare Pages.

Caveats

CDN performance claims are directional, based on documented PoP counts and published third-party benchmarks; toolchew did not run independent TTFB tests for this article. Treat them as indicative for planning, not lab-precise for SLA commitments. The Cloudflare Pages 20,000-file limit is documented on the official limits page but was not directly tested against a 500-page Next.js export; verify against your own build output before assuming it’s safe. Netlify’s legacy plan terms were accurate at time of writing but billing terms can change without feature announcements — re-check your billing page before making decisions based on legacy grandfathering.

References