Netlify pricing confuses a lot of teams because the free tier looks generous until you hit one of its three real limits: build minutes, bandwidth, or serverless function invocations. This post breaks down what each Netlify plan actually includes in 2026, what triggers an upgrade, and how it stacks up against Vercel for a typical Next.js project.
What Netlify's free tier actually gives you
The Starter plan (free, one member) includes:
- 300 build minutes/month — the most common ceiling for active projects
- 100 GB bandwidth/month — generous for most content sites
- 125,000 serverless function invocations/month — fine for route handlers and ISR revalidation endpoints
- 1 concurrent build — means queued deploys when you push frequently
- No background functions on free
- No split testing or analytics
- Community support only
Three hundred build minutes sounds like a lot. A typical Next.js + Sanity full build (no ISR, full static export) takes 2–4 minutes. At 4 minutes per deploy you're capped at roughly 75 deploys a month. If you're running preview deploys on every PR — which Netlify's branch deploys make easy — you'll burn through that budget faster than you expect. A team doing daily content deploys plus CI previews will likely hit the ceiling by week three.
Paid plan breakdown
| Plan | Price | Build minutes | Bandwidth | Serverless invocations | Team members | Support |
|---|---|---|---|---|---|---|
| Starter | $0 | 300/mo | 100 GB | 125K/mo | 1 | Community |
| Pro | $19/mo per member | 1,000/mo (pooled) | 400 GB | 500K/mo | Up to 3 | |
| Business | $99/mo per member | 1,500/mo (pooled) | 600 GB | 1M+/mo | Up to 5 | Priority |
| Enterprise | Custom | Custom | Custom | Custom | Unlimited | SLA |
Pro is priced per member, so a three-person team pays $57/month minimum. That's the first sticker shock. Vercel's Pro tier is $20/month per member with similar per-seat math, so the headline numbers are close — but the overage rates differ significantly.
Where costs actually spike
Build minutes overages are $7 per 500 additional minutes on Pro. That sounds small but compounds. A project running Storybook previews, Playwright tests, and full Next.js builds across feature branches can easily consume 3,000 minutes a month — a $35 overage on top of the base $57 for three seats.
Bandwidth overages are $0.55 per GB beyond the plan limit. For image-heavy marketing sites that serve unoptimised assets directly from Netlify rather than through Sanity's image CDN or a dedicated image service, this adds up. If you're serving 50 GB over the 400 GB Pro limit you're looking at an extra $27.50. The practical fix is routing all Sanity images through the Sanity CDN with auto=format rather than proxying them through Netlify functions — but that's a separate architecture decision.
Serverless function execution time is charged after 125K invocations on Starter and 500K on Pro — at $2 per 500K additional invocations. For ISR-heavy Next.js apps that revalidate via Sanity webhooks, this is manageable. For apps doing full server-side rendering on every route, you'll want to model your expected invocation volume before committing.
Large Media (Netlify's Git LFS-based image storage) adds complexity. It's free up to 1 GB storage and 5 GB bandwidth per month, then $20 per 50 GB storage and $20 per 100 GB bandwidth. Most teams on Next.js skip this entirely in favour of Sanity's CDN, which is the right call.
Netlify vs Vercel: where the pricing actually differs
| Factor | Netlify Pro | Vercel Pro |
|---|---|---|
| Per-seat price | $19/member/mo | $20/member/mo |
| Build minutes included | 1,000/mo (pooled) | 6,000/mo (pooled) |
| Bandwidth included | 400 GB | 1 TB |
| Serverless function invocations | 500K/mo | 1M/mo |
| Edge functions | Included | Included |
| ISR / on-demand revalidation | Via Next.js plugin | Native |
| Overage (build minutes) | $7/500 min | $1/100 build-minutes ($5/500) |
Vercel's Pro plan includes six times the build minutes for roughly the same per-seat price. For teams deploying Next.js specifically, Vercel's native ISR and on-demand revalidation support is also meaningfully more reliable — Netlify's Next.js Runtime handles most patterns but has lagged on PPR and some App Router edge cases in practice.
The gap narrows if you're running a non-Next.js frontend (Astro, SvelteKit, plain React) or you want Netlify's form handling, identity (auth), or split testing — those are genuinely useful features with no direct Vercel equivalent.
When upgrading to Netlify Pro is the right call
Upgrade when you hit any of these:
- Multiple team members need deploy access — the Starter plan's single-member limit is a hard wall for any real team
- You're regularly queuing builds — one concurrent build on Starter means deploys block each other; Pro gives three
- You need branch deploys plus preview deploy URLs for client review — technically possible on free, but you'll burn minutes quickly
- You need email support with a response SLA — community-only on free is a real risk for client production sites
When to skip Netlify entirely
For Next.js projects built with App Router, ISR, and Sanity CMS, Vercel remains the lower-friction deployment platform. The build-minutes advantage on Vercel Pro is significant for teams running preview deploys, and native ISR revalidation means fewer workarounds. Netlify is a reasonable choice if you're building for a mixed-framework environment or want a single platform handling forms, identity, and edge functions across multiple non-Next.js sites.
Railway and Fly.io are worth evaluating if you need persistent server processes (a full Node.js backend, a Sanity Studio running on a custom port) and want to avoid per-seat pricing — though they require more infrastructure management.
For most Next.js + Sanity teams landing in 2026: Netlify free works as a scratchpad, but the build-minute ceiling and single-member Starter limit push serious projects to Pro or Vercel before the first billing cycle.
