Vercel vs Cloudflare Pages vs Netlify for Static Sites (Free Tier 2026)
Same Hugo blog on three platforms. Compare build time, bandwidth, SSL, redirects — and which host I pick for ad-monetized blogs.
Test site: Hugo blog, 120 pages, 340MB total (mostly images), May 2026 Method: Same git repo, three remotes, identical output folder.
TL;DR
- Vercel: fastest DX, 100 GB/mo bandwidth, best for JS frameworks.
- Cloudflare Pages: unlimited bandwidth, great for image-heavy blogs.
- Netlify: readable _redirects, solid middle ground for migrations.
Build times (avg of 5 deploys)
| Platform | Cold build | Cached build |
|---|---|---|
| Vercel | 42s | 18s |
| Cloudflare Pages | 55s | 22s |
| Netlify | 48s | 25s |
All acceptable for a blog. Vercel edge cache on node_modules wins slightly.
Bandwidth (simulated 50k pageviews)
| Platform | Free limit | My usage |
|---|---|---|
| Vercel Hobby | 100 GB/mo | ~38 GB |
| Cloudflare Pages | Unlimited* | ~38 GB |
| Netlify Free | 100 GB/mo | ~38 GB |
*Cloudflare "unlimited" fair use — fine for normal blogs.
Image-heavy viral post → Cloudflare wins on bandwidth anxiety.
Custom domain + SSL
All three: free SSL, auto-renew. Vercel easiest UI. Cloudflare best if domain already on CF DNS. Netlify solid middle ground.
Redirects / headers
- Vercel:
vercel.json— powerful regex - Netlify:
netlify.toml+_redirects— very readable - Cloudflare:
_redirectsfile or dashboard rules
Netlify _redirects is my favorite for simple migrations:
/old-post /posts/new-post 301
Preview deploys
All support PR previews. Vercel GitHub integration fastest setup (2 clicks).
Downsides I hit
Vercel: Bandwidth stress on image blogs. Next.js bias in docs. Cloudflare: Env var UX clunkier. Build log less pretty. Netlify: Free tier build minutes cap (300 min/mo) — fine for blog, tight for monorepo.
My picks
| Use case | Pick |
|---|---|
| Dev portfolio, JS framework | Vercel |
| High-traffic content + images | Cloudflare Pages |
| Simple blog, lots of redirects | Netlify |
| Already on Cloudflare DNS | Cloudflare Pages |
I kept production on Cloudflare, staging on Vercel previews. Best of both.
Latency spot check (TTFB, 10 requests each)
| Platform | p50 TTFB |
|---|---|
| Vercel | 42ms |
| Cloudflare | 28ms |
| Netlify | 51ms |
From EU — your edge may differ. All sub-100ms for static HTML.
Migration effort
Moving Hugo public/ folder between hosts: ~30 min each. DNS TTL 300s — plan a low-traffic window.
Decision matrix I give clients
- Already on Cloudflare? → Pages
- Heavy Next/SvelteKit previews? → Vercel
- Non-dev editor needs Netlify UI? → Netlify
FAQ
Which is best for a static blog on free tier?
Cloudflare Pages for bandwidth-heavy sites; Vercel for best developer experience; Netlify for simple redirect-heavy migrations.
Can I use custom domain free on all three?
Yes — Vercel, Cloudflare Pages, and Netlify all include free SSL and custom domain support on free tiers.
Which host is best for ad-monetized static blogs?
Cloudflare Pages if traffic spikes worry you; Vercel if you want fastest deploys and preview URLs.