Vercel pricing 2026: the real 30-day bill

Quick Answer

Vercel pricing in 2026 has three tiers: Hobby (free, personal projects only), Pro ($20 per member seat per month plus usage), and Enterprise (custom). The sticker price is not the bill. Pro seats are the small line; content delivery is the meter that actually moves the number, and Vercel now meters it in steps rather than per gigabyte. Modeled on realistic traffic, a solo indie dev pays about $40 a month, a five-person startup lands near $200 a month, and a scaling SaaS with heavy traffic reaches about $507 a month. This is a 30-day breakdown of where each dollar goes, with every per-unit rate pulled from Vercel's own pricing pages (June 2026).

Correction, September 7, 2026: this teardown originally listed 1M function invocations and 5,000 image transformations among the Pro plan's included monthly allowances, and billed only the excess above them. Vercel's own documentation puts both figures in a column headed Hobby Included and states that it bills Pro invocations on demand, with its worked example charging all 1.5M invocations rather than the 500K above an allowance. Only fast data transfer (1 TB) and edge requests (10M) are genuinely included on Pro. Applying that lifts the invocation line in every cohort and the image line in two: the startup bill moves from about $197 to about $198 a month and its bandwidth share from 93 to 92 percent, while the solo and scaling totals are unchanged once the $20 usage credit is applied. The per-unit rates themselves did not change. They have also been re-scoped: $0.15 per GB and the other rates below are Vercel's Washington D.C. (iad1) rates, and Vercel publishes a regional range that reaches $0.35 per GB.

Correction, September 17, 2026: this teardown previously stated that Pro includes 10M edge requests a month, and billed content delivery as per-unit overage above 1 TB of transfer and 10M requests. Vercel now covers Pro content delivery through Flat Rate CDN, and its pricing table lists Flat Rate CDN rather than a numeric allowance in the Included (Pro) column for both fast data transfer and edge requests. Pro includes the lowest capacity tier at no extra cost, and that tier is 1M CDN requests and 1 TB of data transfer, not 10M requests. Exceeding your capacity does not bill smooth per-unit overage either: Vercel moves you to a higher tier at the start of the next billing cycle, and only past the top tier does it transition you to on-demand pricing. Re-modeling all three cohorts on the published tier ladder moves the solo bill from about $20 to about $40, leaves the startup bill at about $200, and moves the scaling bill from about $757 to about $507. It also changes which meter binds: every paid rung of the ladder carries the same 50 TB transfer ceiling, so request volume is what steps these cohorts up, not bandwidth. The per-unit rates below are unchanged and still apply to a team that leaves Flat Rate CDN off, or that passes the top tier.

The part the pricing page buries

Vercel sells three plans, and the two prices everyone quotes are $0 and $20. Both are true and both are misleading. Hobby is genuinely free forever, but only for non-commercial personal projects. Pro is $20 per member seat per month, ships with $20 of monthly usage credit, and comes with a set of included allowances. Above those allowances, every meter bills on its own.

Here is the plan table, current as of June 2026:

Pro's included allowances are narrower than most write-ups say, and content delivery no longer works the way those write-ups describe. Vercel's pricing table lists Flat Rate CDN rather than a number in the Included (Pro) column for fast data transfer and edge requests, and Pro includes the lowest Flat Rate rung at no extra cost: 1M CDN requests and 1 TB of fast data transfer. Function invocations, image transformations, active CPU and provisioned memory carry no Pro allowance at all. Vercel bills those on demand from the first unit and offsets them only with the $20 monthly usage credit; the 1M invocations and 5,000 transformations you see quoted are the Hobby allowances. The per-unit rates, from Vercel's published usage rates and its regional pricing table, are the numbers that decide your bill:

Content delivery has its own ladder, and it is a staircase rather than a slope. Each rung is a fixed monthly price for a monthly capacity, and Vercel moves you up a rung at the start of the next cycle if you exceed it (Flat Rate CDN, September 2026):

Read the second and third columns together, because that is the part nobody quotes. Every paid rung carries the same 50 TB of transfer, so for an ordinary web application it is request volume, not bandwidth, that steps you up. The per-GB and per-request rates in the table above only apply if you leave Flat Rate CDN switched off, or if you pass the top rung.

One caveat that changes the arithmetic if you deploy outside the United States: Vercel prices these meters by region, and the rates above are the Washington D.C. (iad1) end of the range, which is also its cheapest. Vercel's published range runs to $0.35 per GB of fast data transfer, $3.20 per 1M edge requests, $0.0812 per 1,000 image transformations, $0.221 per active CPU hour and $0.0183 per GB-hour of memory. Sao Paulo transfer is more than twice the US rate. Every bill below is modeled at iad1 rates.

Notice the ratio. The first rung of the delivery ladder costs the same as a developer seat, the third costs the same as fifteen of them. If your bill is climbing, it is almost never the seats.

Cohort A: the solo indie dev, about $20 a month

A single developer running one small commercial Next.js app. Modest traffic, one seat, no team overhead. Modeled 30-day estimate, June 2026:

The whole point of Cohort A: at real indie traffic the $2.22 of on-demand usage is fully absorbed by the $20 credit, so the bill is two subscriptions and nothing else. The 250 GB of transfer sits well inside the included rung. It is the 3M CDN requests that pass the included 1M and put this team on the $20 rung, which is the first thing most solo-dev write-ups get wrong. Priced on demand instead, the same delivery would be $43.50, so the rung is the cheaper path. This is still the tier where Vercel is inexpensive, and where most of the "Vercel is expensive" panic online does not apply.

Cohort B: the five-person startup, about $200 a month

Five seats, a real product with paying users, traffic that has started to matter. This is where the credit stops covering usage. Modeled 30-day estimate, June 2026:

Read the shares. Five seats are $100 and content delivery is another $100, a clean half and half, and the $20 credit swallows every other meter down to zero. It is the 18M requests that buy the $100 rung; the 1.6 TB of transfer would have fitted inside the $20 rung thirty times over. Priced on demand the same delivery would be $276, so the ladder is again the cheaper path. This is exactly the profile behind a widely upvoted r/nextjs thread, 2026 where a developer wrote, "I've been paying $300+/mo on Vercel for what would cost me $80 on AWS directly." The premium is real. Whether it is worth it depends on how much you value not running the infrastructure yourself.

Cohort C: the scaling SaaS, about $750 a month

Eight seats, heavy production traffic, image-heavy pages, a lot of server work. Modeled 30-day estimate, June 2026:

At this scale the eight seats are 32 percent of the bill and content delivery alone is 59 percent. You are paying more for one CDN rung than for all eight engineer seats. Priced on demand those delivery lines would be $720 rather than $300, which is the gap that makes the ladder worth switching on. This is the point where teams start pricing Enterprise, or start pricing an exit.

The one number to watch

Every cohort tells the same story: the seat price is a rounding error and content delivery is the bill. The break-even is clean, and it is now a staircase. Below 1M CDN requests and 1 TB of transfer a month you are paying for seats. Above that you pay $20, then $100 past 10M requests, then $300 past 50M, and every paid rung carries the same 50 TB ceiling, so for most applications it is request count that moves you rather than bandwidth. Leave Flat Rate CDN off and you are back on a slope instead, at $0.15 per GB and $2.00 per 1M requests. Before you optimize anything else, put your CDN request count on a dashboard next to your transfer number.

When Hobby is actually enough

The free tier is not a trap if you fit it. A personal, non-commercial project under 100 GB of transfer, 1M function invocations, and 4 hours of active CPU a month runs at $0 indefinitely. The catch is the license: Hobby is non-commercial, so the moment the project earns money you are on Pro. For side projects and portfolios, though, free is free.

The alternatives, priced honestly

If Cohort B or C is your reality, three moves cut the bill, each with a real tradeoff.

Same-shape hosts. Netlify's flat per-seat pricing and Cloudflare Pages follow the same seat-plus-usage model, though Cloudflare's free and edge tiers are more generous if your app fits a static or edge-first shape. You are trading one metered bill for another, so run your real transfer number through their calculators before you migrate.

Self-hosting. A plain VPS trades the bill for your time. Public cost calculators put a self-hosted Next.js app on a small box in the $7 to $50 a month range, but you now own deploys, scaling, and the pager. For a solo dev that math rarely wins; for a funded team with a platform engineer, it can.

Bundled hosting. If you build the app on a platform that folds hosting into the plan, the bandwidth line disappears into a flat number. Totalum, an AI app builder that folds hosting into a flat plan, generates a real Next.js app with hosting, CDN, SSL, and database included; its $59 a month Business tier is where Deploy and Hosting plus a custom domain turn on (Totalum pricing, 2026). The honest caveats: it is flat and priced per project, there is no free-forever hosting tier like Vercel Hobby, and because Totalum lets you download the source, if you export the code and self-host it on Vercel you are right back on the usage bill above. Bundled is not automatically cheaper. It is predictable, and for a Next.js SaaS with spiky bandwidth, predictable can be worth more than cheap. If you care whether a given builder actually ships a deployable Next.js app rather than a static single-page prototype, the independent, community-editable AI builder benchmarks are a better guide than any vendor's own page.

None of these is a free lunch. The right answer is whichever meter you would rather manage: Vercel's transfer overages, a VPS's ops load, or a builder's flat plan.

How we bill these

Same method as our other 30-day breakdowns: take the published rates, model realistic usage for three cohorts, and total every line instead of quoting the sticker. We used it on Claude Code pricing and OpenRouter pricing, and the lesson repeats: the headline number is never the number.

Math check: on Vercel Pro your bill is roughly (seats times $20) plus your Flat Rate CDN rung, with the rung set by whichever of CDN requests or transfer crosses first. Under 1M requests and 1 TB a month you are paying for seats. Above that you are paying $20, then $100, then $300 a month for delivery, and because every paid rung carries the same 50 TB ceiling it is usually requests that move you.