January 29, 2026 (2mo ago)
Written by Temps Team
Last updated March 7, 2026 (1mo ago)
Netlify's free tier promises 100GB bandwidth, 300 build minutes, and 125,000 serverless function invocations per month according to their pricing page. Those numbers look generous for a side project. But what happens when your site actually gets traffic?
This post breaks down exactly what Netlify costs as you scale -- with real formulas, actual overage rates, and the pricing dimensions that catch teams off guard. Whether you're evaluating Netlify for a new project or wondering why your bill keeps climbing, you'll find concrete numbers here.
TL;DR: Netlify charges $55 per 100GB bandwidth overage and $19/seat/month on Pro. A 5-person team with 100K monthly visitors can easily spend $160+/month once you add analytics and error tracking. Understanding these thresholds helps you budget accurately -- or decide when self-hosting makes more sense.
Netlify's free tier provides 100GB bandwidth, 300 build minutes, and 125K serverless function invocations per month as listed on their pricing page. These limits apply across all sites on your account, not per site. For a solo developer with a low-traffic blog, it's genuinely enough.
Here's the full breakdown:
| Resource | Free Limit | What That Means in Practice |
|---|---|---|
| Bandwidth | 100GB/month | Shared across all your sites |
| Build minutes | 300/month | Roughly 60-100 deploys |
| Sites | Unlimited | But they share your bandwidth pool |
| Team members | 1 | Solo developer only |
| Form submissions | 100/month | Fills up fast with contact forms |
| Serverless functions | 125K invocations | 10-second execution timeout |
The catch? These limits interact. Run three sites under one account and that 100GB bandwidth splits between them. Add a teammate and you're forced onto Pro at $19/seat/month.
Netlify charges $55 per 100GB of bandwidth overage beyond the free tier according to their pricing page. The average web page now weighs about 2.5MB based on HTTP Archive data, which means 100GB supports roughly 40,000 page views before overages kick in.
Here's the formula:
Monthly page views x average page weight = total bandwidth
(Total bandwidth - 100GB) / 100GB x $55 = overage cost
Some real scenarios:
| Monthly Page Views | Avg Page Weight | Bandwidth Used | Overage Cost |
|---|---|---|---|
| 40,000 | 2.5MB | 100GB | $0 (within free tier) |
| 80,000 | 2.5MB | 200GB | $55 |
| 150,000 | 2.5MB | 375GB | $151.25 |
| 300,000 | 2.5MB | 750GB | $357.50 |
What about a Hacker News front page appearance or a viral tweet? A single traffic spike can burn through your monthly bandwidth in hours. There's no built-in spending cap on the free tier -- the overages just accumulate.
Most developers don't realize bandwidth is measured at the CDN edge, not at origin. Cached assets, images, and fonts all count toward your 100GB limit. A site with heavy imagery can hit the cap with far fewer page views than expected.
We've seen documentation sites -- the kind with lots of code blocks and minimal images -- still hit 150GB/month at around 50,000 visitors because of asset-heavy pages and bots crawling aggressively.
Netlify Pro costs $19 per team member per month per their pricing page. Unlike platforms that charge per project or per resource, Netlify ties cost directly to headcount. Every developer, contractor, or intern who needs access adds to the bill.
Here's what that looks like at different team sizes:
| Team Size | Monthly Cost (Pro) | Annual Cost |
|---|---|---|
| 2 developers | $38 | $456 |
| 5 developers | $95 | $1,140 |
| 10 developers | $190 | $2,280 |
| 20 developers | $380 | $4,560 |
The per-seat model creates a perverse incentive. Need to bring on a contractor for two weeks? That's $19 for the month. Onboarding three interns for the summer? That's $57/month extra. Teams start sharing credentials to avoid costs, which creates security problems.
In our experience running deployment infrastructure, teams that grow from 3 to 10 people often don't budget for the hosting cost increase. The platform bill quietly doubles or triples while everyone focuses on product work.
Is the per-seat model fair for teams where only two people actually deploy, but eight need dashboard access? That's worth considering when you evaluate Netlify Pro against flat-rate or resource-based pricing.
Netlify Functions cap at 125,000 invocations per month on the free tier, with a hard 10-second execution timeout as documented in their functions overview. Pro bumps invocations to 2 million but keeps the same 10-second ceiling. Only Business tier ($99/seat/month) extends the timeout to 26 seconds.
| Tier | Invocations | Timeout | Monthly Cost |
|---|---|---|---|
| Free | 125K | 10 seconds | $0 |
| Pro | 2M | 10 seconds | $19/seat |
| Business | 6M | 26 seconds | $99/seat |
Ten seconds sounds like plenty until you need to:
When a function hits the timeout, it fails. No graceful degradation. Your user sees an error, and you might not even know it happened unless you've wired up external error tracking.
How fast can 125,000 invocations disappear? If your site uses serverless functions for API routes -- a common pattern with Next.js -- every API call counts. A single user session might trigger 10-20 function invocations. At 500 daily active users, you'd burn through the free tier in under two weeks.
We've calculated that a typical Next.js app using API routes for authentication, data fetching, and form handling generates roughly 15 function invocations per session. At that rate, the free tier supports about 275 daily active users before you hit the cap.
Netlify doesn't include analytics, error tracking, or session replay. Sentry's Team plan starts at $26/month according to Sentry's pricing, and Netlify's own analytics add-on costs $9/month. When you factor in these essentials, the total cost of running a production app grows well beyond the platform fee alone.
Here's what a typical production setup looks like on Netlify:
| Service | What It Covers | Monthly Cost |
|---|---|---|
| Netlify Pro (5 seats) | Hosting, builds, CDN | $95 |
| Bandwidth overage (200GB) | Traffic beyond free tier | $55 |
| Netlify Analytics | Server-side page views | $9 |
| Sentry Team | Error tracking | $26 |
| LogRocket or FullStory | Session replay | $99+ |
| Total | $284+/month |
That's $3,408+ per year for a 5-person team with moderate traffic. And this doesn't include build minute overages or additional function invocation costs.
Netlify gives you deploy logs and basic function logs. But production debugging requires more. Without error tracking, you're flying blind when users hit bugs. Without analytics, you don't know which pages matter. Without session replay, you can't reproduce issues.
The cost that's easy to overlook isn't just the dollar amount -- it's the integration tax. You're now managing accounts, billing, and configurations across 4-5 separate services. Each has its own dashboard, alert system, and pricing tiers. We've found that this operational overhead often costs more in developer time than the subscriptions themselves.
Netlify restructured its pricing in September 2025, introducing credit-based billing for bandwidth and build minutes. The free tier limits remained similar on paper, but the billing mechanics changed. Overages now draw from a prepaid credit balance rather than being invoiced retroactively.
The credit system means you prepay for expected usage. If you underestimate, you still face overage charges -- but now you've also locked capital into credits you might not fully use. It's a shift that benefits Netlify's cash flow more than your budgeting flexibility.
For teams already on Pro, the per-seat pricing stayed at $19/month. The fundamental cost structure didn't change. The credit system is primarily a billing mechanism update, not a price reduction.
Have you noticed the trend across PaaS providers? Vercel, Netlify, and others are all moving toward usage-based models that look cheap at low volume but scale aggressively. It's worth reading the fine print before committing.
Netlify genuinely works well for specific use cases. It would be dishonest to pretend otherwise. The free tier's 100GB bandwidth and 300 build minutes cover plenty of real-world scenarios without costing a cent.
The economics break down when you cross two or more of these thresholds:
If you're a solo developer with a portfolio site, Netlify's free tier is excellent. Don't switch just because you can. But if you're running a production app with a team, do the math.
According to Market.us, the self-hosting infrastructure market is projected to grow from $15.6 billion to $85.2 billion by 2034. That growth reflects a clear trend: developers want more control over their deployment infrastructure without sacrificing modern DX.
Self-hosted options give you a fixed monthly cost based on server resources, not usage:
If you prefer managed infrastructure but want different pricing models:
We've helped teams evaluate all these options. The right choice depends on your team size, traffic patterns, and how much operational overhead you're willing to accept. There's no universal answer.
According to Netlify's pricing page, the free tier includes 100GB bandwidth, 300 build minutes, 125,000 serverless function invocations, and 100 form submissions per month. These limits are shared across all sites on your account. You're limited to one team member on the free plan -- adding anyone requires upgrading to Pro at $19/seat/month.
Netlify charges $55 per additional 100GB of bandwidth beyond the free tier. With average page weights at 2.5MB according to HTTP Archive, you'll exceed the free 100GB at roughly 40,000 monthly page views. There's no spending cap, so a traffic spike can generate a significant unexpected bill.
Netlify imposes a 10-second timeout on serverless functions for Free and Pro tiers. Business tier ($99/seat/month) extends this to 26 seconds. Operations like PDF generation, image processing, or slow third-party API calls frequently exceed 10 seconds, causing silent failures.
A 5-person team on Netlify Pro pays $95/month in seat fees alone. Add typical bandwidth overage ($55), analytics ($9), and error tracking via Sentry ($26/month), and you're at $185+/month or $2,220+/year. Actual costs vary based on traffic and serverless usage.
For teams of 3 or more with moderate traffic, self-hosting typically costs 60-80% less than Netlify. A capable VPS runs $20-50/month regardless of team size, while Netlify Pro scales at $19/seat plus usage overages. The self-hosting market's projected growth to $85.2 billion by 2034 suggests many teams are reaching the same conclusion.
Netlify's pricing isn't predatory -- it's just designed for a different scale than most growing teams realize. The free tier works at low traffic and solo use. But once you add team members at $19/seat, cross 100GB bandwidth, or need observability tools, costs compound quickly.
The key numbers to remember: $55 per 100GB bandwidth overage, $19 per seat per month, and a 10-second function timeout that no amount of money on Pro can extend. A 5-person team with moderate traffic easily spends $200+/month across Netlify and essential third-party tools.
Before committing to any platform, run the math with your actual traffic numbers and team size. The formulas in this post give you everything you need to project costs accurately -- whether you stay on Netlify, self-host, or pick something else entirely.
Pricing data verified against public pricing pages as of March 2026. Always confirm current rates on Netlify's pricing page before making decisions.