Vercel or Cloudflare Pages? Bandwidth Costs Matter More Than Speed

|Author: QUASA Editorial Team|6 min read| 7
Vercel or Cloudflare Pages? Bandwidth Costs Matter More Than Speed

For a startup serving mostly static pages, Cloudflare Pages has the clearer delivery-cost advantage as traffic grows. Cloudflare’s Workers pricing makes static asset requests free and unlimited, bills Pages Functions as Workers, and lists a $5 monthly minimum for Workers Paid with 10 million requests and 30 million CPU milliseconds included. Vercel may be the better fit for a dynamic Next.js application, but its Pro pricing starts at $20 per month, with one deploying seat included and additional developer seats at $20 each.

That makes the route mix more useful than a generic speed ranking. A visitor fetching a static file, a request invoking server-side code and a developer triggering a build consume different resources. Cloudflare’s static-delivery advantage is strongest when most traffic stays on the first path; a team relying on Next.js server features must weigh deployment fit and compute usage alongside the monthly fee.

Where bandwidth enters the Vercel bill

Vercel Pro offers a Flat Rate CDN option that groups requests and transfer into capacity tiers. The published CDN tiers include 1 million requests and 1 TB of transfer with Pro; an additional $20 per month raises capacity to 10 million requests and 50 TB. The tier is based on typical monthly usage, so an isolated busy day does not by itself change the charge. Teams must enable the option and select the appropriate tier; otherwise, their CDN usage follows Vercel’s on-demand model.

This is a capacity cost, rather than a charge for every extra gigabyte within a selected tier. It still matters for a growing publication: either requests or transfer can push its usual workload beyond the included tier. The flat-rate option also excludes bulk downloads and large-scale file or media delivery when those uses dominate bandwidth, so a content site distributing substantial files cannot assume that the larger tier covers its traffic.

Cloudflare Pages treats a request as static only when it does not invoke a Function. A site that routes every page through code can therefore move its traffic into Workers billing even if the response looks like an ordinary page. On Vercel, caching can prevent a Function invocation, while delivery still counts toward CDN usage. Page views alone conceal both distinctions.

Three workload cards using published prices

The modeled content-heavy static site costs $80 per month on Vercel and $0 for Cloudflare Pages static delivery under the stated assumptions.

These are conditional calculations using prices checked on November 7, 2026. Each assumes one month, US dollars before taxes, no paid storage or add-ons, and Vercel Pro with Flat Rate CDN enabled. The static cards assume assets are built before upload and no Functions run. They estimate the specified platform and delivery charges, not domain registration or other services a site might buy.

  • Static marketing site: Assume 200,000 static requests, 20 GB transferred, 20 prebuilt deployments and one deploying developer. Cloudflare Pages static delivery is $0. Vercel is $20: its Pro fee includes the seat, and the modeled traffic fits the included CDN tier. The deployment count adds no modeled build-machine charge because the assets arrive prebuilt.
  • Content-heavy editorial site: Assume 5 million static requests, 5 TB transferred, 100 prebuilt deployments and three deploying developers. Assume ordinary website delivery, without bulk downloads or media distribution that would make Flat Rate CDN ineligible. Cloudflare Pages static delivery is $0. Vercel is $80: $20 for Pro, $40 for two additional developer seats and $20 for the larger CDN tier. Both traffic measures fit that selected tier.
  • Application with dynamic requests: Assume 2 million requests invoke Pages Functions, each using 5 milliseconds of CPU time, with one developer and deployments prepared elsewhere. That is 10 million CPU milliseconds, within the Workers Paid allowances, so the modeled Cloudflare runtime charge is $5. Vercel starts at its $20 Pro fee, but a complete function estimate also needs memory, execution duration and any other billable feature usage. The $5 figure describes Pages Functions under the stated workload; it does not establish that a full-stack Next.js app can be moved to Pages unchanged.

The editorial-site card shows why a static traffic calculation can outweigh a small latency difference: Cloudflare’s modeled delivery charge remains at zero while Vercel’s seats and selected CDN tier produce a fixed monthly cost. The application card has a different constraint. Its request and CPU assumptions are enough to price the specified Cloudflare Functions workload, but insufficient to quote Vercel function execution or the work of adapting the application.

Builds and framework requirements change the choice

Free static requests do not mean unrestricted publishing. Cloudflare’s Pages limits allow 500 builds per month on Free, one build at a time, with a 20-minute timeout; the listed Pro and Business plans allow more monthly and concurrent builds. A publication that rebuilds for every edit, preview and automated update can encounter a build constraint even while its delivery charge stays at zero. The number of deployed assets also matters: Pages lists a per-site file limit and a maximum size for an individual asset.

Vercel charges for some build-machine time, with rates varying by machine, so deployment frequency and build duration belong in its estimate. A prebuilt upload avoids the particular build-minute assumption used in the static cards; a repository connected to automatic builds may produce a different bill. For teams with several deployers, the additional seat fee can be more predictable than build usage but still exceed the delivery charge of a small site.

A static Next.js export is a natural Pages candidate because its finished pages can be served as assets. Server rendering, route handlers, middleware and other server-side behavior require a separate runtime assessment. For a full-stack Next.js project, the relevant Cloudflare deployment route may be Workers rather than a direct Pages upload. The decision is therefore about the application’s actual server features as well as its traffic: a lower modeled request charge has value only if the required code runs in the chosen environment.

What the latency sample establishes

A single US connection measured cached median response times of 108, 110, 111 and 205 milliseconds across four different web properties.

A StackVerified latency sample made eight sequential cached requests to each of four different websites from one US residential connection. It reported median time to first byte of 108 milliseconds for vercel.com, 110 for nextjs.org, 111 for developers.cloudflare.com and 205 for pages.cloudflare.com. Three results clustered closely, but the targets were different properties, and the fourth was a heavier page.

Those measurements describe cached responses for those sites from that connection. They do not isolate the hosting platforms or predict a startup’s performance for uncached server routes in other regions. If an application’s latency is decisive, its own routes and user locations are the relevant test conditions. For the static workloads modeled here, the published billing rules already expose a clearer difference: transfer and seats change the Vercel estimate, while static requests remain free on Pages.

Also read:

Share:

Subscribe to our newsletter

Get the latest Web3, AI, and crypto news delivered straight to your inbox.

0