Netlify Pricing 2026: Free Tier Limits, Build Minutes & When to Upgrade

Netlify pricing confuses a lot of teams because it changed model recently. Since September 4, 2025, new Netlify accounts are on credit-based plans: every plan comes with a monthly pool of credits, and production deploys, bandwidth, compute, and web requests all draw from that pool. Accounts created before that date may still be on the older "legacy" plans (metered by build minutes, bandwidth, and function invocations) unless they've switched — and switching is one-way. This post covers the credit-based plans, what triggers an upgrade, and how it stacks up against Vercel for a typical Next.js project. Prices below are list prices at the time of writing; check netlify.com/pricing before you commit.

What Netlify's free tier actually gives you

The Free plan includes:

• 300 credits/month — a hard limit, with no option to buy more on Free
• Unlimited deploy previews and branch deploys — these aren't metered
• 1 concurrent build — means queued deploys when you push frequently
• Custom domains with SSL, functions, global CDN, basic firewall rules
• 1 Team Owner plus unlimited Reviewer seats (no Developer seats)

What eats credits:

Three hundred credits sounds like a lot until you do the maths. Twenty production deploys alone would use the whole allowance, and so would 15 GB of bandwidth. A Next.js + Sanity site that redeploys on every content publish, or serves unoptimised images from Netlify, will run out well before the month ends. Content sites that use on-demand revalidation instead of redeploying, and serve images from Sanity's CDN, stretch the free credits much further.

Paid plan breakdown

Pro is a flat team price rather than per-member, which is a real difference from Netlify's legacy Pro plan (and from Vercel, which charges per deploying seat).

Where costs actually spike

Production deploys. At 15 credits each, deploy frequency matters more than build length. A site that triggers a full production deploy on every Sanity publish burns credits fast; on-demand revalidation via a webhook-triggered route handler costs a few requests instead.

Bandwidth. At 20 credits per GB, image-heavy marketing sites that serve unoptimised assets directly from Netlify feel this first. 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.

Compute. Functions are billed by GB-hour. For ISR-heavy Next.js apps that revalidate via Sanity webhooks, this is manageable. For apps doing full server-side rendering on every route, model your expected traffic before committing.

Running out. On Free, credits are a hard cap. On Personal and Pro you can enable auto-recharge (credit packs) to keep projects live when you exceed your monthly credits — leave it off if you'd rather have a predictable bill, but check what Netlify does to projects when credits run out.

Netlify vs Vercel: where the pricing actually differs

The pricing models are now different enough that per-line comparisons mislead — model your own deploy frequency, bandwidth, and team size on both calculators. For teams deploying Next.js specifically, Vercel's native ISR and on-demand revalidation support means fewer surprises; Netlify's Next.js support handles most App Router patterns, but new Next.js features tend to land on Vercel first.

The gap narrows if you're running a non-Next.js frontend (Astro, SvelteKit, plain React) or you want Netlify's form handling or its flat team pricing — those are genuinely useful for agencies with many collaborators.

When upgrading to Netlify Pro is the right call

Upgrade when you hit any of these:

1. Multiple people need deploy access — Free and Personal only allow a single Team Owner; Pro allows unlimited owners and developers
2. You're regularly queuing builds — one concurrent build on Free and Personal means deploys block each other; Pro gives three
3. You're running out of credits mid-month — Free stops at 300 credits with no top-up; paid plans can auto-recharge
4. You need a support channel you can rely on for client production sites — check which support tier each plan includes on Netlify's pricing page

When to skip Netlify entirely

For Next.js projects built with App Router, ISR, and Sanity CMS, Vercel remains the lower-friction deployment platform. Native ISR revalidation means fewer workarounds. Netlify is a reasonable choice if you're building for a mixed-framework environment, want flat team pricing, or want a single platform handling forms 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 300-credit hard cap and single-owner limit push serious projects to a paid plan or Vercel quickly.