Vercel vs Netlify (2026): The Static Site Case, Plus Netlify vs Cloudflare

Every Vercel vs Netlify comparison we read tests the same thing: a server-rendered Next.js app with middleware, ISR, and image optimization switched on. That's a fair test of Vercel's best case. Plenty of sites never touch any of it. This site, devtoolreviews.com, is a Next.js static export (output: "export" in next.config.ts) sitting on Vercel, and it uses almost none of the features those benchmarks measure. If your build ends in a folder of HTML files, pick the host by how it stores redirects and whether its free tier lets you run ads. Framework support barely matters. On those terms Cloudflare Pages edges both, Netlify beats Vercel for anyone who needs a form, and Vercel wins only when you expect to stop being static.

Vercel vs Netlify at a glance, for a static build

Rows come from our own testing and pricing checks, published in the 2026 three-way comparison and the Vercel vs Netlify deep dive. Netlify vs Cloudflare gets its own column because that's the matchup people search next.

Measure	Vercel	Netlify	Cloudflare Pages
Free tier allows commercial use	No (Hobby)	Yes	Yes
Included bandwidth, paid tier	1 TB	1 TB	Unlimited
Bandwidth overage	$40 per 100 GB	$55 per 100 GB	None
Cheapest paid entry	$20/user/month (Pro)	Pro tier (see note below)	$5/month (Workers Paid)
Mean build, our Next.js test app	42s	58s	45s
Cached static asset delivery	Within 3 to 7 ms of each other in every region we tested
Where redirects live	vercel.json	netlify.toml or _redirects	Its own redirect rules
Built-in form handling	No	Netlify Forms	No

Check the static asset row. For cached HTML, CSS, and JavaScript, the three CDNs are a wash, so the dynamic TTFB charts that decide most comparisons don't apply to you.

Note on Netlify pricing: our pages record two different Pro structures, $19 per seat in earlier checks and a flat $20 for the whole team after Netlify's April 2026 change. That swing is large for a five-person team ($20 a month versus roughly $100 on Vercel's per-seat Pro), so read Netlify's pricing page the day you decide.

What a static export throws away

Vercel's strongest argument is that it co-develops Next.js, so Server Actions, ISR, middleware, and image optimization work there first and best. A static export can't use any of them. There's no server. Our own repo learned this the slow way: a /api/subscribe route handler was committed for the newsletter, and it returned 404 in production for months, because a static export has nowhere to run a route handler. It shipped anyway.

That incident is the whole case in small. Once you've chosen static, Vercel is a very good CDN with a very good dashboard. You still get preview URLs on every pull request and the fastest builds we measured (42 seconds against Netlify's 58). Those are real. They're also things Netlify and Cloudflare Pages largely match for a folder of files.

The free tier license

Vercel's Hobby plan prohibits commercial use. This site runs AdSense, which makes it commercial, which puts it on the wrong side of that line on a free plan. Netlify and Cloudflare Pages both allow commercial projects on their free tiers. For a side project that might carry ads or an affiliate link someday, that clause settles more decisions than any benchmark does.

Redirects are the actual lock-in

None of the top-ranking Vercel vs Netlify pages we read mention it, and it's the first thing that would bite us if we moved. Our vercel.json holds 25 redirect rules. Three use path parameters like /blog/:slug, and one is conditional on the request host, which is how devtoolreviews.com gets sent to www.devtoolreviews.com:

{
  "source": "/:path*",
  "has": [{ "type": "host", "value": "devtoolreviews.com" }],
  "destination": "https://www.devtoolreviews.com/:path*",
  "permanent": true
}

A static export can't hand these to Next.js, because redirects() in next.config needs a server. So they live in the host's own format, and moving hosts means translating every one. On Netlify they become [[redirects]] blocks in netlify.toml or lines in a _redirects file. Simple path rules convert line for line. The host-conditional rule is the one to test by hand on a preview deploy before you cut DNS, since each platform expresses "only when the host is X" differently, and getting it wrong splits your canonical URLs between apex and www, which is exactly the kind of quiet mistake Search Console reports weeks later.

Our full direction-by-direction checklist (functions and forms included) is in the 2026 comparison. For a static site, redirects are most of it.

A Vercel cost nobody puts in the pricing table

Vercel's Skew Protection appends a deployment token (?dpl=dpl_...) to static asset URLs so a browser holding old HTML can still fetch the matching old chunks. Useful for apps. For us it produced a recurring SEO false alarm: Ahrefs crawled HTML from an older deploy, re-requested chunks after the protection window expired, and reported 404s on files that no longer existed. We logged it, confirmed the live deploy served every chunk with a 200, and moved on. Call it a small tax on attention, charged by the platform with the most app-shaped defaults.

Netlify vs Cloudflare Pages for static sites

Bandwidth decides this one. Cloudflare Pages has no bandwidth line item on any tier, and its $5 Workers Paid plan is the cheapest paid entry of the three; Netlify charges $55 per 100 GB past its allowance, the highest overage in the table. A docs site that gets linked from a popular repo can turn a quiet month on Netlify into an invoice, while the same spike on Cloudflare costs nothing extra. We dug into the fair-use fine print in Cloudflare Pages pricing and bandwidth limits.

Netlify keeps one real advantage for static builds, and it's specific. Netlify Forms captures submissions from a plain HTML form with data-netlify="true", no backend at all. Our newsletter form currently renders nothing, by design, because it has no endpoint to post to on a static Vercel deploy. On Netlify that problem would mostly not exist. If your static site needs one contact form and you'd rather not wire up a third-party service, that tips it.

Netlify also has the deeper bench for Hugo and Eleventy (Jekyll too), with native support that predates Vercel's interest in non-Next.js frameworks.

What we'd miss on another host

The dashboard, mostly, plus 16 seconds per build that make no difference at all to a site deploying a few times a day.

Verdict

For a static Next.js export, Vercel is the comfortable choice and rarely the necessary one. We're still on it. Moving would cost us an afternoon of redirect translation plus a careful DNS cutover, and the bill isn't hurting at our traffic, so the honest reason we stay is inertia with a nice dashboard. Starting fresh today, with ads on day one, we'd put a site like this on Cloudflare Pages for the license and the bandwidth, or on Netlify if it needed a form and we didn't want to touch a backend. Choose Vercel when the static export is a phase and you expect to add server rendering or middleware within the year, because then the Next.js integration earns its per-seat price. The 2026 pricing breakdown has the full tier tables.

How we evaluated this comparison

Build times, static delivery results, and overage prices come from our published 2026 Vercel, Netlify, and Cloudflare Pages tests. The redirect count, the host rule, the /api/subscribe incident, and the Skew Protection crawl reports come from this site's own repository and issue log. Plan names and prices change often; confirm each vendor's pricing page before budgeting. See our About page for methodology.