A client rang me in early 2024, proper panicked. She ran a Gatsby blog I'd set up for her on Netlify's free tier about eight months prior. The site got picked up by a newsletter with 60,000 subscribers, traffic spiked, and by the time she called me she'd already received an email from Netlify about bandwidth overages. The bill wasn't catastrophic. But she hadn't budgeted a penny for hosting because I'd told her "the free tier should be fine for now."
That word "now" cost me a client relationship and cost her a surprise invoice. I learned from it.
So. Netlify pricing. Let me actually walk you through what each plan does and doesn't cover in 2026, where the costs stack up in ways the pricing page doesn't shout about, and which plan makes sense depending on what you're building.
---
The Four Plans at a Glance
Netlify currently runs four tiers: Starter (free), Pro ($19/month per member or $19/month as a flat team rate depending on how you read the billing page), Business ($99/month), and Enterprise (custom pricing, call them).
Quick note on the Pro plan billing: it used to be per seat. Netlify has adjusted this a couple of times, so always check Netlify's official pricing page before committing. I've seen agencies get burned by assuming it's still the old structure.
---
Starter (Free): What You Actually Get
The Starter plan is genuinely useful. Not a crippled demo, not a bait-and-switch. For personal projects, proof-of-concepts, or low-traffic client sites, it holds up.
Here's what's included:
- 100GB bandwidth per month across your sites
- 300 build minutes per month
- 1 concurrent build
- Netlify Functions: 125,000 invocations/month, 100 hours runtime
- Forms: 100 submissions/month
- Identity (auth): 1,000 active users
- 1 member (it's a personal plan, effectively)
That bandwidth number sounds enormous. For a static marketing site or a portfolio, 100GB is plenty. But if you're running a site with unoptimised images, a lot of video thumbnails, or you get a sudden spike, it evaporates fast. That's exactly what happened to my client above.
The Build Minutes Trap
300 minutes sounds reasonable. It isn't, once you start deploying properly. If you're running a Next.js or Gatsby site with a lot of pages, a single build can eat 8-15 minutes. Add preview deploys, branch deploys, and any CI/CD hooks, and you can burn through 300 minutes in a week on an active project. I've done it. Not once.
If you're a freelancer managing five client sites on a free account, you'll hit the build minutes ceiling regularly. The fix is either to upgrade or to be very deliberate about what triggers a build.
---
Pro Plan ($19/month): The Sweet Spot for Freelancers
This is the plan I point most freelancers and small agencies toward. The jump from Starter is meaningful.
Key upgrades on Pro:
- 1TB bandwidth (10x the free tier)
- 25,000 build minutes/month (about 83x more)
- 3 concurrent builds (massive for agencies juggling multiple client deploys)
- Password-protected sites (huge for client staging environments)
- Analytics: basic, but functional
- Forms up to 1,000 submissions/month
- Identity up to 5,000 active users
The password protection alone is worth it for agency work. Sending a client a staging link and not having to cobble together a separate auth layer? That saves me probably two hours per project.
What Pro Still Doesn't Cover
Netlify Functions on Pro get a bump, but if you're running a serious serverless workload, you'll feel the limits. Background Functions (for longer-running tasks) are available on Pro but still constrained. If your application does anything resembling real-time data processing or has APIs that get hammered, you'll want to benchmark your invocations before assuming Pro covers it.
---
Business Plan ($99/month): When Teams Get Serious
At $99/month, Business is aimed at teams rather than solo operators. Seahawk had a fintech client last year where we needed collaborative branch deploys, role-based access, and a proper audit log for compliance reasons. Business plan, sorted.
The headline additions:
- 1TB bandwidth (same as Pro, weirdly)
- Shared environment variables across team members
- Role-based access control: Reviewer, Developer, Billing, Owner roles
- Background Functions with higher limits
- Log drains for shipping logs to Datadog, Splunk, etc.
- Priority support response times
The bandwidth parity with Pro catches people off guard. You're not paying for more bandwidth at Business, you're paying for team infrastructure and compliance features. If you just need bandwidth, Pro is almost always better value.
Log Drains Are Underrated
Seriously. If you're running a production app on Netlify and you're not piping logs somewhere searchable, you're flying blind. Log drains on the Business plan let you push to Datadog or similar, which is something I'd recommend the moment a client's site becomes revenue-critical. Debugging a Functions error at midnight without structured logs is miserable.
---
Enterprise: Custom Everything
Enterprise pricing isn't public. You talk to sales, they build a quote. That's normal for this tier.
What you're buying at Enterprise:
- Custom bandwidth limits
- SLA guarantees (99.99% uptime commitments in writing)
- SSO with SAML
- Custom build infrastructure
- Dedicated support with named account managers
- Security reviews and compliance documentation (SOC 2, etc.)
If you're an agency pitching to a mid-size brand or a regulated industry client (finance, healthcare), the Enterprise plan is often what makes the pitch credible. The SLA paperwork alone can be the thing that closes a deal.
I've subcontracted on two Enterprise-tier Netlify setups. Both involved procurement teams who wanted the SLA more than they wanted any specific feature. Fair enough.
---
The Hidden Cost Areas Nobody Talks About
Right. This is the section that would have saved my 2024 client.
Bandwidth Overages
On Starter, once you hit 100GB, Netlify starts charging per GB. The rate has historically been around $0.20/GB, which sounds small until a viral moment sends 500GB through your CDN in 48 hours. That's a $100 surprise on what was a free account.
On Pro and above, overages exist too. You get 1TB included, but sustained high-traffic sites will blow past that. Always check your bandwidth dashboard weekly if traffic is unpredictable.
Forms at Scale
Netlify Forms are brilliant for simple contact forms. But the submission limits on free and Pro tiers are low enough that any site with real form engagement, think a lead generation page or event registrations, will either hit the cap or require you to upgrade. At scale, I usually swap Netlify Forms out for Typeform or a custom serverless endpoint anyway. More control, cleaner data.
Build Minutes on CI/CD-Heavy Projects
If you've wired up Netlify to a GitHub Actions workflow that triggers deploys on every PR, and you have five developers committing frequently, you can burn 10,000 build minutes in a month without blinking. On Starter that's obviously impossible (you'll be blocked at 300). On Pro, you have room but not unlimited room.
My standard advice: set up deploy notifications in Slack so the team can see when a build fires. Visibility alone tends to reduce frivolous deploys.
Functions Compute Time
Netlify Functions on the free tier give you 100 hours of compute time. Sounds like a lot. But if you have a function that's slow (say, hitting a third-party API with no caching), every invocation chews compute time. I had a Shopify integration built on Netlify Functions where one endpoint was doing a synchronous fetch to a slow supplier API. We were eating 800ms per call. Fixed it with caching, but we'd already burned a chunk of our monthly allowance by the time I caught it.
---
Which Plan Should You Actually Choose?
Here's how I think about it:
- Personal project or one low-traffic client site: Starter is fine. Monitor your bandwidth.
- Freelancer with 3-10 active client sites: Pro, without question. The build minutes and concurrent builds alone justify it.
- Agency with a team of 4+: Business, for the RBAC and shared environment variables. The operational overhead of not having those is higher than $99/month.
- Enterprise client or regulated industry project: Talk to Netlify sales. The SLA and compliance docs are worth the call.
One thing worth knowing: Netlify lets you set spend management limits to cap overage charges. Turn that on immediately, regardless of which plan you're on. It won't save you from hitting a limit, but it'll stop a surprise bill from getting out of hand.
---
Netlify vs. The Alternatives (Brief Take)
Vercel is the obvious comparison. For Next.js projects specifically, Vercel's developer experience is hard to beat and the pricing structure is similar. Cloudflare Pages is free-tier-generous and the CDN performance is exceptional, though the build tooling is less mature. For pure static sites, even GitHub Pages or Render can work.
I still default to Netlify for most Jamstack projects because the ecosystem (Forms, Identity, Functions) is more integrated than anywhere else. But it's not automatic. Project requirements should drive the platform choice.
---
FAQ
Is Netlify's free plan actually free, or will I get charged without warning?
It's genuinely free up to the limits. The risk of surprise charges comes from bandwidth overages and form submission overages. Turn on spend limits in your account settings and you'll have a ceiling. Netlify does send email warnings before you hit the hard limits, but those emails are easy to miss.
Can I run a small e-commerce site on Netlify's free tier?
Depends on traffic and how you've built it. A headless commerce setup with Shopify as the backend and Netlify serving the frontend can work on Starter for low-traffic shops. The moment you're doing serverless cart logic or hitting Netlify Functions heavily, you'll want Pro.
Does Netlify charge per team member on the Pro plan?
This has changed a few times. As of 2025-2026, Pro is billed as a flat monthly rate for a small team rather than strictly per seat, but the exact structure is worth confirming directly on Netlify's pricing page before you commit. Billing page wording vs. actual invoicing has caught people out before.
What happens to my site if I exceed build minutes?
Builds queue and then fail until the next billing cycle resets your allowance, or until you upgrade. Your live site stays up (it's served from the CDN), but you won't be able to push new deploys. This is particularly painful if you discover a bug and need to push a hotfix.
Is Enterprise worth it for a mid-size agency?
Usually not unless you have a specific client requirement driving it, like a signed SLA or a compliance audit. Most agencies I know are on Business and manage fine. Enterprise is for situations where the contract with the end client demands it.
---
Netlify's pricing isn't complicated once you understand what the limits actually mean in practice. The free tier is honest. The Pro plan is good value. The hidden costs are mostly in bandwidth and build minutes, and both are visible in your dashboard if you look. Check them. Set spend limits. And maybe don't tell your clients the free tier is permanent.