Vercel Pricing in 2026: Hobby, Pro and the Bandwidth Overage Trap

Vercel makes the first deploy feel like magic: push to Git, get a URL, done. The pricing is where the magic gets a little murkier. The headline numbers are simple, but the real bill depends on seats, bandwidth, function usage and build minutes, and those are the parts people forget to model until an invoice shows up.

This guide walks through what each Vercel plan costs in 2026, what you actually get, where the overages tend to bite, and when Netlify, Render or a cheap VPS is the better deal. Prices below come from our product database. Vercel adjusts limits and usage rates fairly often, so check their pricing page before you commit.

The Short Version

▸Hobby (free): $0. Unlimited deployments, preview URLs and about 100GB of bandwidth, but strictly for personal, non-commercial projects.
▸Pro: $25 per month (our database lists it as a flat monthly figure; Vercel bills Pro per team seat). Commercial use, team collaboration, more bandwidth and analytics.
▸Enterprise: custom quote. SLA, SSO, advanced security and dedicated support.

If you are a solo developer with a hobby site, Hobby is hard to beat. If you are making money from what you deploy, you are on Pro whether you like it or not.

Hobby: Generous, With One Big Catch

Hobby gives you unlimited deployments, a preview URL for every branch, a global CDN and around 100GB of bandwidth a month. For a portfolio, a blog, a demo or a weekend project, that is more than enough, and the developer experience is the same as the paid tiers.

The catch is the word personal. Vercel's terms restrict Hobby to non-commercial use. A client site, a side project with ads, or a product with paying users technically needs Pro. Plenty of people ignore this, and Vercel does not police every project, but it is a real risk if your project suddenly gets popular and someone notices. If you are building anything with revenue attached, budget for Pro from day one.

The other limit to know about: Hobby has no team features. You cannot invite collaborators the way you can on Pro, so even a two-person side project will bump into it.

Pro: Where Most Real Projects Land

Pro is listed at $25 per month in our database and adds the things a working team needs: commercial use rights, team collaboration, more bandwidth, more build capacity and analytics. For a small startup with one to three developers, this is usually the right tier and the price is reasonable for what it replaces. Zero-config CI/CD, preview deployments on every pull request and a global edge network would take real engineering time to rebuild yourself.

The thing to understand is that Pro is a base price plus usage. The included allowances cover a lot of small and mid-sized projects, but anything beyond them is metered. That is where the cost curve changes shape.

Per-seat pricing adds up

Pro is priced per team member. One developer is $25. A team of five is $125 a month before any usage. That is still modest next to a salary, but it is worth noticing that the people who need a seat are not only developers. Designers and product people who want to comment on preview deployments, or contractors you bring in for a month, can all count toward the bill depending on how you set up the team. Review who actually needs a seat each quarter.

The bandwidth overage trap

This is the one that gets people. Bandwidth looks cheap when you are small, because the included allowance swallows your traffic. Then something goes right: a post hits the front page of a link aggregator, a campaign lands, or you simply add heavy images and video without a separate CDN. Traffic grows, you pass the included amount, and every extra gigabyte is billed at a usage rate.

Nothing about that is dishonest, since it is how usage-based hosting works. But the combination of a flat, friendly headline price and a metered tail means the bill is hard to predict. A few things make it worse:

▸Unoptimized images. Serving large originals instead of properly sized ones burns bandwidth fast. Use the built-in image optimization carefully, and be aware that image transformations are themselves a metered feature.
▸Large downloads and video. Hosting big files directly on your Vercel deployment is the fastest way to blow through an allowance. Put them on object storage or a media CDN.
▸Bots and scrapers. Automated traffic counts like any other traffic. A site that gets hammered by crawlers can rack up usage with no real visitors behind it.
▸Uncached dynamic responses. If pages that could be cached are rendered fresh on every request, you pay for both function time and the bandwidth that goes out.

The practical defense is boring: turn on spend management and set a spending cap or alert before you need it. Do this on day one, not after the first surprise.

Function and build costs

Serverless and edge functions are metered on invocations and execution time. For a typical marketing site or blog, that is nearly free. For an app with chatty API routes, server-rendered pages on every request, or anything calling slow third-party APIs, function time becomes a real line item. Slow upstream calls are particularly expensive here, because you pay while your function waits.

Build minutes are the other limit that surprises teams. Our database notes that build minute limits can catch people out. A monorepo that rebuilds everything on every commit, or a project with a slow test step in the build, can chew through minutes quickly. Cache aggressively, ignore builds for unaffected packages, and keep heavy checks in a separate CI job.

Enterprise: Quote Only

Enterprise adds an SLA, SSO, advanced security controls and dedicated support. There is no public price, so expect a sales call. Companies usually move here for compliance and support requirements rather than raw capability. If you are not required to have SSO or a contractual uptime guarantee, Pro with careful spend controls will take you a long way.

What Vercel Is Genuinely Good At

It is worth being fair, because the pricing complaints sit on top of a very good product:

▸Best-in-class Next.js support. Vercel builds Next.js, and new framework features tend to work best here first.
▸Preview URLs for every branch. This changes how teams review work. Designers and PMs can click a link instead of pulling a branch.
▸Zero-config deploys. Connect a repo and you have CI/CD, HTTPS, a CDN and rollbacks without writing a pipeline.
▸Strong observability. Analytics and speed insights are built in, which saves you wiring up separate tools.

The Honest Downsides

▸Hobby is not for commercial use. Easy to overlook, easy to get wrong.
▸Costs climb at scale. Bandwidth and function usage make the bill less predictable than a flat-rate host.
▸Build minute limits. Heavy or frequent builds can run into them.
▸Lock-in concerns. Edge functions and some platform-specific features are not trivially portable. Plain static output and standard Node apps move easily; leaning on proprietary features makes leaving harder.
▸Not ideal for heavy backends. Long-running jobs, big databases and compute-heavy services are a poor fit for a function-based model.

When Something Else Is Cheaper

Netlify. The closest alternative. Our database lists Netlify Pro at $19 per month with a free tier that includes 100GB of bandwidth and 300 build minutes. Pricing is in the same ballpark, so Netlify is rarely a dramatic saving, but its free tier has historically been friendlier to commercial side projects. If the Hobby restriction is your sticking point, it is worth a look. We compare the two directly in our Vercel vs Netlify guide.

Render. If you are running a real backend, Render is often a better match. Our database lists a free tier with unlimited static sites and 750 web service hours, then a Starter instance at $7 per month for an always-on 512MB service, and a Pro workspace at $25. Because you pay for an instance rather than per request, the bill is far more predictable for steady backend workloads.

Self-hosting. A small VPS plus a tool like Coolify can host a surprising number of sites for a few dollars a month, with no per-seat charges and no bandwidth surprises. The trade-off is that you are now the ops team: updates, backups, security and uptime are yours. For a single developer comfortable with servers, the savings are real. For a team that wants to ship product, they often are not worth the attention.

Cloudflare and other static hosts. If your site is mostly static, a static-first host with generous bandwidth can be far cheaper than a platform built around server rendering. You give up some Next.js-specific conveniences in return.

Which Plan Should You Pick?

Personal project, no revenue, solo? Hobby. Enjoy it.
Client work, a product with customers, or ads? Pro. Do not rely on Hobby for commercial use.
Small team shipping a Next.js app? Pro, with a spend cap and alerts configured on day one.
High-traffic content site with lots of media? Model bandwidth first. Offload images and video, or compare a static host before you commit.
Backend-heavy app with steady compute? Look at Render or a VPS for the backend and keep Vercel, if at all, for the frontend.
Compliance or SLA requirements? Ask for an Enterprise quote and compare it against what Pro plus add-ons would cost.

Tips to Keep the Bill Down

▸Set a spending limit and usage alerts the day you move to Pro.
▸Audit seats every few months and remove people who no longer need access.
▸Serve large media from dedicated storage rather than your deployment.
▸Cache pages and API responses wherever the data allows it.
▸Ignore builds for unchanged parts of a monorepo.
▸Check the usage dashboard weekly for the first month after any launch or campaign.

Our Verdict

Vercel is an excellent platform, and for most small teams the $25 Pro plan is fair value for the deployment workflow you get. The free tier is great for personal work. The problem is not the sticker price but the unpredictable tail: seats, bandwidth and function usage all scale with success, so the bill can grow faster than you expect.

If you are small, deploying Next.js and happy to set spending limits, Vercel is easy to recommend. If you are running a high-traffic, media-heavy or backend-heavy product, price out Netlify, Render or a self-hosted setup before you let the usage meter decide for you.

Pricing reflects the plans listed in our product database at publication. Vercel changes limits and usage rates periodically, so confirm current numbers on their pricing page before you buy. Some links on this site may be affiliate links; they never affect our rankings.