Vercel vs Cloudflare Pages 2026: Cost, Speed and Developer Experience

Cloudflare wins on price for almost any site that is mostly static: requests to static assets are free and unlimited, and the Workers Paid plan that runs the dynamic part costs $5/mo for the whole account. Vercel wins for a Next.js app whose team wants the framework's features to work without an adapter, at $20/mo for the first deploying seat and the same again for each extra one.

Prices and limits below were read on 17 October 2026 on Vercel's pricing page and plan docs, and on Cloudflare's Workers, Pages and plans pages. One thing changed in 2026 that older comparisons miss: Cloudflare now tells developers to start new projects on Workers, not Pages. Workers serves static assets the same way Pages does, so this page compares Vercel with the Cloudflare pair, Pages and Workers, and says where the two Cloudflare products differ.

Toolradar data: the hosting and deployment ranking we run evaluated 317 tools, updated 15 October 2026. Vercel is the most cross-shopped product in that category, listed as an alternative to 55 other tools and compared 535 times in the last 90 days, against 388 for Cloudflare Workers.

At a glance

Product	Best for	Starting price	Standout
Vercel	A commercial Next.js app with one or two people who deploy	Pro at $20/mo, Hobby free for non-commercial use	Native Next.js, Fluid compute, skew protection, a usage credit equal to the fee
Cloudflare Pages	A static or mostly static site at any traffic level	Free, 500 builds a month	Static asset requests free and unlimited, no bandwidth meter
Cloudflare Workers	A dynamic app that must stay cheap as requests grow	Free at 100,000 requests a day; Paid $5/mo	10 million requests included, then $0.30 per million

A frontend host, for a developer, is a git-connected build, a CDN for the static output, and a function runtime for the server-rendered part. Vercel sells all three as one product with one invoice. Cloudflare splits them: the CDN and static serving cost nothing, and only the function runtime is metered.

The single-product writeups are the Vercel review and the seat-and-usage breakdown in Vercel pricing. The wider free-tier picture is in best free static hosting, and cheaper Vercel alternatives prices Workers against Netlify, Render and Railway for one team size.

Four costed scenarios

Each total multiplies the vendors' published rates. None of them is a quote, and taxes are excluded on both sides.

Scenario, one month	Vercel	Cloudflare	Cheaper
Solo commercial marketing site, static, 50 GB of transfer, 20 deploys	One Pro fee, because Hobby bans commercial use	$0 on Pages Free	Cloudflare, by the whole Pro fee
Next.js app, 3 deployers, 1 TB of transfer, 5 million function requests	$60 on Pro, three seats, usage inside the credit	The Workers Paid subscription alone, if the average request uses 6 ms of CPU or less	Cloudflare by $55
Docs site, static, 5 TB of transfer, no functions	$40: Pro plus the first paid Flat Rate CDN tier, which covers up to 50 TB	$0 on Pages or Workers static assets	Cloudflare by $40
API-heavy app, 30 million function requests, 10 ms of CPU each	On-demand compute at $0.128 per CPU hour plus memory, after the credit	$16.40 on Workers Paid	Cloudflare, unless the Vercel app caches most responses at the CDN

The 5 TB row is the one to remember. Vercel's Pro plan includes a Flat Rate CDN tier of 1 million CDN requests and 1 TB of data transfer a month; the next tier costs the same as the platform fee and covers 10 million requests and 50 TB. Without that tier, the pricing page lists data transfer from $0.15 per GB, which would make 4 TB of overage $600. Cloudflare publishes no transfer price for static assets at all.

The 30 million request row is where Workers' flat model shows its shape. Workers Paid includes 10 million requests and 30 million CPU milliseconds; the extra 20 million requests cost $6 at $0.30 per million, and the extra 270 million CPU milliseconds cost $5.40 at $0.02 per million, on top of the subscription. The equivalent Vercel bill depends on memory size and region, so it does not fit in one cell, which is itself a difference: Cloudflare's bill is predictable from request count alone.

What each free plan refuses to host

For a free host that can run a paid product, Cloudflare wins. Vercel's fair use guidelines restrict Hobby to non-commercial personal use, and the definition is wide: any payment from visitors, any product advertising, any ads, any site a paid contractor built, and any site whose main purpose is affiliate links. Donations are the one listed exception.

Cloudflare's Pages and Workers docs publish no such restriction. The Free limits are hard caps instead: Workers Free allows 100,000 requests a day across Workers and Pages Functions combined, resetting at midnight UTC, and 10 ms of CPU per invocation. Pages Free allows 500 builds a month, one at a time, and 20,000 files per site, which is plenty for a docs or marketing site and tight for a monorepo that rebuilds on every commit.

Hobby's limits are monthly, and they pause rather than bill. Vercel's Hobby plan doc lists 100 GB of fast data transfer, 1 million CDN requests, 1 million function invocations, 4 hours of active CPU and 360 GB-hours of provisioned memory, and says that in most cases an exceeded limit means waiting until 30 days have passed. There is no paid overage on Hobby, so a personal project that goes viral goes dark rather than costing money.

The practical split: a side project that makes no money can live on either free plan. A side project that sells anything needs Vercel Pro from day one, or a Cloudflare account that costs nothing until the 100,000-requests-a-day line is crossed.

Pricing, plan by plan

Vercel bills a platform fee, then seats, then usage after a credit. Cloudflare bills a flat Workers subscription plus per-unit overage, and separately a website plan that only matters for Pages build caps. Rates are on the Vercel pricing page, the Vercel Pro plan doc, the Workers pricing page and the Cloudflare plans page.

Plan	What you pay (USD)	What a developer should read
Vercel Hobby	Free	Non-commercial only. 100 GB transfer, 1 million invocations, 4 CPU hours, 200 projects, 100 deployments a day
Vercel Pro	$20/mo platform fee	One deploying seat and a usage credit of the same amount, which expires at month end. Extra Owner or Member seats match the fee; viewers are free
Vercel Pro add-ons	SAML $300/mo, HIPAA BAA $350/mo, password protection one platform fee per protected project, Flags Explorer $250/mo	Priced per team or per project, on top of seats
Vercel Enterprise	Custom quote	SCIM and the uptime SLA live here
Cloudflare Workers Free	Free	100,000 requests a day, 10 ms CPU per invocation, 100 Workers, 3,000 build minutes
Cloudflare Workers Paid	$5/mo per account	10 million requests and 30 million CPU ms included, then $0.30 and $0.02 per million. CPU up to 5 minutes per request, 500 Workers, 6,000 build minutes then $0.005 per minute
Cloudflare Pages Free	Free	500 builds a month, 1 concurrent build, 20,000 files, 100 custom domains per project
Cloudflare Pro website plan	$25/mo month to month, or $240 a year billed annually	5,000 Pages builds a month, 5 concurrent. Business at $200/mo annual raises that to 20,000 and 20

Three reading notes. First, the Workers Paid subscription is per account, not per person: Cloudflare does not sell a deploying seat, and Pages lists unlimited dashboard users per site. On Vercel, five people who can deploy cost $100 a month before any traffic, because each deploying seat matches the platform fee and only read-only viewers are free.

Second, Pages Functions and Workers share one meter. Cloudflare's Pages Functions pricing says requests to Functions count against the Workers plan, Free or Paid, and only requests that never invoke a Function are the free static kind. A Pages site with a contact-form Function is on the Workers meter for that route only.

Third, Vercel's credit covers every usage line, so a small app rarely sees an on-demand charge. Five million invocations at $0.60 per million is $3, well inside the credit, which is why the three-seat scenario above ends at $60 flat. The seats, not the usage, are the Vercel bill for most small teams.

Next.js: native versus the OpenNext adapter

For an app that uses the newest Next.js features on the day they ship, Vercel wins. Vercel builds Next.js, and features arrive there first with no adapter to wait for. Skew protection, which keeps a long-lived browser session on the deployment it started on, is included on Pro.

Cloudflare runs Next.js through the OpenNext Cloudflare adapter. As of October 2026 it supports every Next.js 16 release and the latest minors of 14 and 15, with App Router, Pages Router, SSR, SSG, ISR, Partial Prerendering, standard middleware, image optimization, use cache and after(). Node middleware from Next.js 15.2 is listed as not yet supported.

The adapter has a size ceiling that Vercel does not: the Worker bundle must compress to 3 MiB on Free or 10 MiB on Paid. A large app with heavy server dependencies can hit that before it hits any request limit, and the fix is dependency surgery, not a bigger plan.

The adapter runs on the Node.js runtime, not the Edge runtime, so an app that leans on Vercel's edge middleware idioms is rewritten, not ported. Our guide to running Next.js off Vercel covers what that port usually touches.

Vercel's native support has its own meters. Image transformations start at $0.05 per 1,000 on Pro, cache reads at $0.40 per million and cache writes at $4 per million, where Hobby includes 5,000 transformations a month. On Cloudflare the adapter's image optimization runs inside the Worker, so it is CPU milliseconds and requests, not a separate line.

Builds, previews and the git loop

On the build loop, tie, with different failure modes. Both products deploy from a git push, build every pull request to its own preview URL and keep the production branch separate.

Vercel's build is the metered part. Pro teams pay $0.007 per build minute on Basic machines, or $0.0035 per CPU minute on larger ones, and a Hobby team gets Basic machines included. A project that builds 200 times a month for five minutes each is 1,000 minutes, or $7 on Basic, and any deployment count up to 6,000 a day on Pro.

Cloudflare's build is capped, not metered, on the free side. Workers Builds includes 3,000 minutes a month on Free and 6,000 on Paid, then $0.005 per minute; Pages counts builds instead of minutes, 500 a month on Free. Both products time a build out at 20 minutes, and Free allows one build at a time, so two busy repos on one free account queue behind each other; a team that pushes often will feel that queue before any cap.

Preview access differs. Vercel password protection is a paid add-on per project on Pro, and Vercel Authentication (team login) is included on every plan. Cloudflare Pages previews are public by default and can be locked behind Cloudflare Access, configured from the project settings.

Pages still has three things Workers lacks, according to Cloudflare's own migration guide: native Early Hints, file-based routing without a framework, and custom domains on zones outside Cloudflare. Workers has the longer list: gradual deployments, cron triggers, Workers Logs and Logpush, queues, rate limiting and Durable Objects. A new project that needs any of those starts on Workers, which is what Cloudflare now recommends.

Compute, logs and the long tail of limits

For a request that waits on a database, Vercel's Fluid compute bills more honestly than it looks, because active CPU pauses during I/O. Only provisioned memory keeps billing while the request waits, at $0.0106 per GB-hour in the cheapest US regions. A function that spends 100 ms computing and 400 ms waiting bills 100 ms of CPU.

Workers CPU time works the same way, only wall-clock time waiting on fetch is free, and the per-request CPU budget is 10 ms on Free and up to 5 minutes on Paid, where 30 seconds is the default. Memory is a fixed 128 MB per isolate on both plans, which rules out the memory-hungry PDF render or image pipeline that a 4 GB Vercel function handles.

Logs are shorter-lived than most teams expect on both. Vercel keeps runtime logs for 1 hour on Hobby and 1 day on Pro; drains to an external store are a Pro feature billed by volume. Workers Paid includes 20 million log events a month in Workers Logs, then $0.60 per million. Either way an incident that must outlive the dashboard needs one of the log management tools or a monitoring tool.

Devshot sends one daily note on what developers need to ship. Subscribe here.

Who should pick which

Pick Cloudflare Pages Free for any static site, commercial or not, that builds fewer than 500 times a month: a docs site, a marketing site, a blog. Its traffic bill is zero at any size, which no Vercel plan matches once the site makes money.

Pick Cloudflare Workers Paid for a dynamic app where request volume is the cost driver and the team is bigger than two deployers. The flat subscription covers 10 million requests and nobody pays for a seat, so the three-deployer Next.js team above saves $55 a month, provided the app fits the adapter's 10 MiB compressed bundle and 128 MB memory limits.

Pick Vercel Pro for a Next.js product with one or two deployers that wants new framework features on release day, skew protection and a single invoice. Make everyone who does not deploy a viewer, since viewers are free, and leave the Flat Rate CDN toggle on so a traffic spike moves you up a tier next month rather than onto on-demand rates.

Pick Vercel Enterprise or the Cloudflare Business plan when you need SCIM, an uptime SLA or 20 concurrent builds; both vendors put those in a quote or a $200-plus tier.

Pick neither for a long-running process or a database you size yourself. That is the Railway review, the Render review or the wider serverless platforms ranking. If Netlify is the other host on your shortlist, Vercel vs Netlify prices that pair the same way.

How we compared

We read Vercel's pricing page, Pro and Hobby plan docs, Flat Rate CDN doc, Fluid compute pricing and fair use guidelines, plus Cloudflare's Workers pricing and limits pages, Pages limits and Functions pricing, Workers Builds limits, the Pages-to-Workers migration guide, the plans page and the OpenNext Cloudflare adapter docs, on 17 October 2026.

The four scenario totals multiply those published rates: three seats at the Pro fee, 20 million extra requests at $0.30 per million, 270 million extra CPU milliseconds at $0.02 per million, and 4 TB at $0.15 per GB. Vercel's exact function bill in the 30-million-request row depends on memory size and region, so it is described rather than totalled. Louis Corneloup, founder of Toolradar and Dupple, edited the verdict. Editorial rules are on the Devshot about page.

FAQ

Which is cheaper in 2026, Vercel or Cloudflare Pages?

Cloudflare is cheaper for almost every workload. Static asset requests on Pages and Workers are free and unlimited with no transfer meter, and the Workers Paid plan is $5/mo per account with 10 million requests included. Vercel Pro is $20/mo per deploying seat, and Hobby cannot host a commercial site, so a three-deployer Next.js app costs $60 on Vercel against the flat Workers subscription at 1 TB of transfer and 5 million function requests.

Is Cloudflare Pages being replaced by Workers?

Cloudflare's Pages docs now say to start new projects with Workers, which supports most Pages use cases and has a broader feature set. Pages remains available on every plan, and it still has native Early Hints, file-based routing and custom domains on non-Cloudflare zones, which Workers lacks. Workers serves static assets free the same way, and Pages Functions already bill on the Workers meter, so the cost is the same whichever you choose.

Can I run Next.js on Cloudflare Pages?

Yes, through the OpenNext Cloudflare adapter, which runs Next.js 16 and the latest minors of 14 and 15 on the Node.js runtime. App Router, SSR, ISR, Partial Prerendering, standard middleware and image optimization are supported; Node middleware from Next.js 15.2 is not yet. The Worker bundle must compress to 3 MiB on Free or 10 MiB on Paid, and memory is capped at 128 MB per isolate.

Does Vercel's free plan allow a commercial site?

No. Vercel's fair use guidelines restrict Hobby to non-commercial personal use, and commercial covers taking payments, advertising a product, showing ads, affiliate sites and any site a paid developer built. Donations are the exception. A commercial site needs Pro or Enterprise. Cloudflare's Pages and Workers free plans publish no commercial-use restriction, only daily request and monthly build caps.

How much does bandwidth cost on Vercel versus Cloudflare?

Cloudflare publishes no bandwidth price for static assets, so a 5 TB static site costs nothing on Pages. Vercel Pro includes a Flat Rate CDN tier of 1 TB and 1 million CDN requests, and the next tier, priced like the platform fee, covers 50 TB and 10 million requests. Without a tier, the pricing page lists data transfer from $0.15 per GB.

Which is faster, Vercel or Cloudflare Pages?

Neither vendor publishes a benchmark against the other, and we run no test lab, so this page does not claim one. What the docs do say: both serve static files from a global CDN, Cloudflare runs Workers in its edge locations with a 128 MB memory cap, and Vercel runs functions in a chosen region with Fluid compute, where Vercel's own pricing example sizes a function at 4 GB of memory. Latency depends on where your users and your database are.

Cite this: Devshot, "Vercel vs Cloudflare Pages 2026: Cost, Speed and Developer Experience", October 2026.

Devshot is the daily brief on tools and changes developers act on. Join at devshot.co.

Some offers on this page may be paid placements or contain affiliate links.