A single Next.js app serving 50 TB per month on Vercel will run you roughly $500 in bandwidth alone as of Q2 2026. That figure surprises teams who onboarded during the generous free-tier era and never modeled what happens when traffic scales past the first terabyte. Understanding Vercel CDN pricing at the per-TB and per-GB level is now a prerequisite for any architecture review that touches frontend delivery. This article gives you the exact 2026 numbers, a provider-by-provider cost comparison, regional pricing variance, a workload-profile decision matrix you will not find in any competing breakdown, and the thresholds where switching providers pays for itself inside a single billing cycle.
Vercel prices bandwidth under a single label it calls "Fast Data Transfer." As of May 2026, the rate is flat: $0.01 per GB, which works out to $10.24 per TB. This applies to all plan tiers (Pro and Enterprise) once you exceed the included allotment. Pro plans include 1 TB per month; anything above that is metered.
Enterprise contracts can negotiate volume discounts, but Vercel does not publish a tiered rate card the way hyperscalers do. In practice, teams report negotiated rates in the range of $0.007–$0.009 per GB at multi-hundred-TB commitments, though these are NDA-bound and vary quarter to quarter. If you are modeling costs without an enterprise agreement in hand, $0.01/GB is the number to use.
One detail that catches teams off guard: Vercel's Fast Data Transfer meter counts all egress from edge to client, including preview deployments, branch deploys, and any asset served from the edge cache or origin. There is no separate "origin shield" billing line because Vercel abstracts that layer, but the traffic still counts toward your bandwidth total.
Raw per-GB price only tells half the story. The table below uses publicly listed rates as of Q2 2026 and normalizes to a 10-TB-per-month baseline so you can see effective cost at a common mid-scale workload.
| Provider | Per-GB Rate | Cost at 10 TB/mo | Notes |
|---|---|---|---|
| Vercel (Pro) | $0.01 | ~$102 | Flat rate; 1 TB included in Pro plan |
| AWS CloudFront | $0.085 (first 10 TB, NA/EU) | ~$850 | Tiered; Asia/SA regions significantly higher |
| Google Cloud CDN | $0.08 (NA/EU) | ~$800 | Cache egress only; origin fetch billed separately |
| Cloudflare (Pro) | $0.05 | ~$500 | Bandwidth technically "unmetered" on paid plans; overages negotiated |
| BlazingCDN | $0.004 | ~$40 | $100/mo includes 25 TB; overage at $0.004/GB |
The gap is stark. At 10 TB per month, Vercel costs roughly 2.5× what a volume-oriented CDN charges and roughly one-eighth of CloudFront's list rate. At 100 TB, the spread widens further because Vercel's rate stays flat while volume-priced providers drop per-GB costs with commitment.
Vercel does not publish region-differentiated bandwidth rates. Whether your traffic is served from an edge in Frankfurt, Tokyo, or São Paulo, the metered rate remains $0.01/GB. This is a deliberate simplification and one of Vercel's genuine advantages for teams that serve a globally distributed audience without wanting to model regional cost weighting.
Compare that to CloudFront, where serving 1 TB from India costs $0.109/GB versus $0.085/GB from the US, or Google Cloud CDN, where Oceania egress is $0.14/GB. If a significant share of your traffic originates outside North America and Europe, Vercel's flat rate can actually undercut hyperscalers in those specific regions, even though it appears more expensive on a headline NA/EU comparison.
Cost per GB is necessary but insufficient. The right CDN depends on the intersection of traffic volume, geographic distribution, integration requirements, and tolerance for vendor lock-in. The matrix below maps common workload profiles to the provider that minimizes total cost of ownership, not just bandwidth price.
| Workload Profile | Monthly Bandwidth | Best Fit | Why |
|---|---|---|---|
| Next.js SaaS with preview deploys | < 1 TB | Vercel | Included bandwidth covers it; zero-config DX saves eng hours |
| Next.js SaaS, scaling past product-market fit | 5–50 TB | Vercel + external CDN for static assets | Keep SSR on Vercel; offload images/video to a cheaper edge |
| Media-heavy site or software distribution | 50–500 TB | BlazingCDN | At $0.003–$0.004/GB, the savings fund an entire engineering headcount |
| Multi-cloud platform with AWS-native backends | 100+ TB | CloudFront (committed pricing) or BlazingCDN | CloudFront avoids cross-network egress; BlazingCDN wins on raw cost |
| Global audience, APAC/LATAM heavy | Any | Vercel or Cloudflare | Flat-rate pricing eliminates regional cost surprises |
The hybrid approach in row two is underused. Running Vercel for SSR and ISR while pointing a CNAME for your asset subdomain at a dedicated CDN cuts bandwidth bills by 40–70% without sacrificing Vercel's deployment workflow. The split takes about two hours to implement via a rewrite rule in your middleware.
Three patterns reliably blow up Vercel bandwidth bills:
Auditing these three vectors before scaling typically recovers 15–30% of projected bandwidth cost with no architectural change.
For teams whose delivery workloads have outgrown Vercel's pricing curve, the math increasingly favors a dedicated CDN for the bulk-transfer layer. BlazingCDN is worth evaluating here: starting at $4 per TB for volumes up to 25 TB and dropping to $2 per TB at the 2 PB tier, it delivers fault tolerance and uptime guarantees comparable to CloudFront at a fraction of the cost. The platform scales under demand spikes without manual intervention, and flexible configuration means it slots into existing CI/CD pipelines with minimal integration overhead. Enterprises like Sony use BlazingCDN in production, which speaks to the platform's readiness for high-stakes workloads.
As of Q2 2026, Vercel charges $0.01 per GB for Fast Data Transfer, which comes to approximately $10.24 per TB. This rate applies uniformly across all edge regions once you exceed the 1 TB included in the Pro plan. Enterprise contracts may include negotiated discounts.
Every gigabyte beyond the 1 TB Pro-plan allotment is billed at $0.01. There is no tiered reduction for higher volumes on the standard Pro plan. If you anticipate sustained multi-TB usage, requesting an Enterprise quote is the only path to a lower per-GB rate.
No. Vercel applies a single global rate of $0.01/GB regardless of which edge location serves the request. This contrasts with AWS CloudFront and Google Cloud CDN, which both use region-differentiated pricing that can vary by 40–65% between North America and Asia-Pacific.
The published rate is $0.01 per GB as of May 2026. "Fast Data Transfer" is Vercel's billing label for all bandwidth served from its edge to end users, including static assets, SSR responses, and optimized images.
At list prices, yes. Vercel's $0.01/GB is significantly lower than CloudFront's $0.085/GB starting rate in North America. However, CloudFront offers committed-use discounts and a free tier of 1 TB per month, so the comparison shifts at very high volumes or when CloudFront is already embedded in an AWS-native stack.
Among providers with published pricing, BlazingCDN offers the lowest per-TB rate at $4/TB (25 TB tier) down to $2/TB at 2 PB commitments. Cloudflare's paid plans include unmetered bandwidth but require higher base subscription fees. Vercel sits in the middle at $10/TB.
Pull your last 90 days of Vercel Fast Data Transfer from the Usage tab in your team dashboard. Break it down by deployment type: production versus preview. Multiply the production number by $0.01 and compare it against the same volume at $0.004 on a dedicated CDN. If the delta exceeds $200 per month, a two-hour CNAME migration for your static asset subdomain pays for itself in the first billing cycle. If you are already past 50 TB per month and still on Vercel's flat rate, the question is not whether to split your delivery layer but why you have not done it yet.