Vercel pricing 2026: what you actually pay for a real Next.js project

Vercel pricing looks simple on the surface — free, $20/month plus $20 per extra deploying seat, call us — but the bill a real Next.js project generates depends almost entirely on a handful of usage meters that aren't obvious until you've already deployed. Here is what those meters actually are, what triggers them, and what a mid-traffic marketing site should expect to pay in 2026. Figures are from Vercel's pricing page and docs at the time of writing (October 2026); Vercel changes its meters fairly often, so check vercel.com/pricing before you budget.

What Hobby actually allows commercially

Hobby is free and it is not for commercial use. Vercel's fair use policy restricts Hobby to personal, non-commercial use. In practice that covers any site that generates revenue directly or indirectly, including lead-generation sites, e-commerce storefronts, and SaaS marketing pages. If you are building something for a client or for your own business, you are on Pro from day one.

What Hobby gives you if you are legitimately prototyping (per month): 100 GB of Fast Data Transfer, 1M CDN requests, 1M function invocations, 4 hours of Fluid Active CPU and 360 GB-hours of provisioned memory, and 5,000 image transformations. Hobby can't buy extra usage — once you hit a cap you're limited until the next cycle (for example, new images stop being optimized). That is fine for a portfolio or a learning project. It is not fine for anything a client will see in production.

Pro per-seat maths for small teams

Pro is a $20/month platform fee that includes one deploying seat and $20 of monthly usage credit. Each additional seat that can deploy or configure projects (Owner or Member role) is $20/month. Viewer seats — read-only access to deployments, analytics, and preview comments — are free and unlimited. Seat count is about team members with access to the Vercel dashboard, not end users of your site.

For a typical freelance engagement: you need one deploying seat for yourself, and the client can be a free Viewer if they only need to see deployments and comment on previews. That is $20/month. If the client's own developer also needs to deploy, add $20 for that seat.

For a small agency team of five developers who all deploy, you are at $100/month in seats ($20 platform fee plus four extra seats). That is a fixed cost before you touch any usage line item.

Pro's $20 monthly credit is spent across usage meters from the first unit, and Pro also includes a Flat Rate CDN tier with 1 TB of data transfer a month. Usage beyond the credit is billed on demand. The question is whether those included amounts are enough.

The usage line items that surprise people

Three meters catch teams off guard. These are the ones worth modelling before launch.

Function compute. Every route handler, dynamically rendered Server Component, and Server Action that runs on Vercel Functions is billed under Fluid compute: Active CPU time (from $0.128 per hour), provisioned memory (from $0.0106 per GB-hour), and invocations (from $0.60 per million). Active CPU only counts time the CPU is actually working, so a function waiting on a slow API isn't burning CPU time — but memory is still provisioned while it waits. For a mostly static marketing site this is small change inside the $20 credit. Long-running data aggregation routes, PDF generation, or AI calls that run for 10–30 seconds are where it shifts.

Image optimisation. Vercel bills next/image optimisation by image transformations (from $0.05 per 1,000), plus cache reads and cache writes. A transformation is billed on every cache MISS or STALE, so each unique image, width, and quality combination costs a transformation the first time it's requested and again whenever the cached copy expires. Many unique variants plus a short cache lifetime is how this meter grows. A long minimumCacheTTL helps, and using Sanity's own image CDN for transformation sidesteps the meter entirely.

Bandwidth. Pro's Flat Rate CDN tier includes 1 TB of data transfer a month. Most content sites stay under this, but if you are serving video previews, large PDFs, or downloadable assets directly from Vercel rather than from a dedicated object store, bandwidth climbs. Additional Fast Data Transfer starts at $0.15 per GB.

A less commonly discussed meter: build minutes. Builds are billed per minute based on the build machine (new Pro teams default to Elastic build machines). If you have many preview deployments or slow builds, this adds up. Note that ISR revalidation doesn't trigger a rebuild; it regenerates pages at runtime and is billed as function usage and ISR reads/writes instead.

Realistic monthly total for a mid-traffic marketing site

Assumptions: a Next.js App Router marketing site with a Sanity CMS backend, roughly 80,000 unique visitors per month, a 30-page site with a blog at 100 posts, image-heavy but with Sanity serving transformed images from its own CDN. One deploying seat (the developer) and the client on a free Viewer seat.

For this profile, the bill is mostly the platform fee, with usage absorbed by the credit. Where it breaks: many uncached image variants going through Vercel's optimiser, function duration inflated by uncached database queries, or lots of long builds. Each of those turns into on-demand charges once the $20 credit is gone.

A heavier project — e-commerce with personalised routes, server-rendered cart state, and ~500,000 monthly visits — will spend well beyond the credit; model it with your own traffic and function profile using the rates above rather than relying on a rule of thumb.

When Enterprise conversations start

Vercel does not publish Enterprise pricing publicly. The conversation typically starts when a team needs one or more of: custom SLAs, advanced security and compliance features, audit logs, or contractual commitments. (Some features that used to be Enterprise-only, like SAML SSO at $300/month, are now available as Pro add-ons.) Enterprise contracts are quoted individually, so get a quote rather than relying on figures from forums.

The realistic trigger for most Next.js product teams is the compliance requirement (SOC 2, audit logs) rather than raw traffic — Pro handles a lot of traffic just fine. If a procurement team asks for a DPA and SSO on day one, budget Enterprise from the start.

What to watch before your first invoice

Review Spend Management as soon as you create the team (it lives in the team's billing settings). Vercel enables notifications at a default $200 spend amount for new teams, and you can lower that, add a webhook, or have projects paused automatically when you hit the limit. Web Analytics is billed per event on Pro, and the optional Web Analytics Plus add-on is $10/month. And if you are using Sanity for images, route all image transformation through Sanity's CDN rather than Vercel's optimisation pipeline — you eliminate one entire meter.