Netlify's Free Tier Has a Hard Cap — Hit It and Every Site on Your Account Goes Dark Until Next Month. If You Run Side Projects There, Read the Failure Mode.
Netlify's Free Tier Has a Hard Cap: Hit It and Every Site on Your Account Goes Dark Until Next Month. If You Run Side Projects There, Read the Failure Mode.
Netlify's free plan gives you 300 credits a month, and the important word is the one most people skip: hard. There's no overage billing, no auto-recharge, no grace period. When a project on the free plan burns through its credits, it doesn't get throttled or quietly billed. It pauses. And per Netlify's own docs, if one project exceeds its limits, every project on your account pauses until the next billing cycle.
Read that twice if you have more than one thing on Netlify. The failure mode isn't "one site gets slow." It's "all your sites go offline at once, and they stay offline until the first of next month."
Why this is the opposite of the usual free-tier risk
Almost everything written about free-tier danger is about the surprise bill. You leave a function running, traffic spikes, and you wake up to a four-figure invoice from a usage-based platform. That's a real risk on Vercel-style pricing, and it's the one people guard against.
Netlify's free tier inverts it. It will never send you a surprise bill, because there's no overage. The hard cap is the whole point. What it does instead is take you offline. For a solo operator that's arguably the worse failure, because you can dispute a bill but you can't un-ring an outage during a launch.
And the blast radius is the part that catches people. Most of us put all our side projects under one Netlify account because that's the obvious thing to do. The marketing site, the two abandoned experiments, the little tool that went semi-viral last month, the client demo you forgot to take down, all on one login, all sharing one 300-credit pool. The semi-viral tool eats the credits, and the client demo you're presenting tomorrow goes dark with it.
How the credit model works after the April refinement
Netlify moved to credit-based pricing and refined it on April 14, 2026. The headline change there was that the Pro plan became flat-fee with unlimited team members, which is good news if you're paying. The free tier's 300-credit hard cap survived the refinement unchanged.
Credits get consumed by the things you'd expect: build minutes, bandwidth, function invocations, and the other metered resources, each drawing from the same monthly pool. The free tier works out to roughly 15 GB of bandwidth-equivalent usage and a 10-second function timeout, though the exact mix depends on what your sites actually do. The mechanism that matters isn't the precise conversion; it's that everything draws from one capped bucket, the bucket doesn't refill mid-month, and emptying it pauses your account rather than charging you.
So the question for a solo operator isn't "how much is 300 credits." It's "what happens on the day I run out, and which of my sites can't afford to be down when it happens."
The honest read on when this matters
I'm not going to tell you to flee Netlify. For a huge number of solo projects the free tier is genuinely fine and the hard cap never comes up. Here's how to think about whether it's a problem for you specifically.
It's fine when your projects are low-traffic and nothing is load-bearing. A personal site, a couple of experiments, a portfolio: if the worst case is "my blog is down for a day and I notice and upgrade," the hard cap is a non-event. Don't over-engineer around a risk that costs you nothing.
It's a real risk the moment something becomes load-bearing on a shared account. The instant one of those projects starts mattering (a client is looking at it, it's making money, it's the thing you're demoing), it should not be sharing a credit pool with your unpredictable experiments. One spike on the experiment shouldn't be able to take down the thing that pays you.
It's a configuration problem you can solve cheaply. You don't have to pick between "all free" and "pay for everything." You can isolate the account, move the project that matters, or just turn on the $19 plan for the one site that can't go dark and leave the rest on free.
What I'd actually do
Three moves, in order of how much they matter.
Separate the load-bearing project from the experiments. If you have anything on Netlify that a client sees or that earns money, get it off the shared free account, either its own account or a paid plan. The whole risk here is one project's spike pausing another, and the fix is to not let the things you care about share a pool with the things you don't. This is a 20-minute job and it removes the scary failure mode entirely.
Know where your credits go before you hit zero, not after. Check the usage view on your account and get a rough feel for your monthly burn. If you're regularly using half your credits by mid-month, you're one viral link away from a pause. That's your signal to upgrade or isolate, and it's a much better signal than the email telling you your sites are already down.
Decide the $19 question deliberately. For a project that genuinely can't be offline, the paid plan isn't a cost, it's outage insurance, and it's cheap insurance. The mistake isn't paying. It's leaving a money-making site on a hard-capped free tier to save nineteen dollars, then losing a launch day to a pause you could have prevented.
The honest counter-take: most readers of this will never hit the cap, and I don't want to manufacture anxiety about a free tier that's serving you fine. Netlify's hard cap is also, in a real sense, a feature: it's the reason you'll never get a runaway bill, which is the failure mode that actually bankrupts people on other platforms. If you'd rather risk an outage than an invoice, the hard cap is working as designed and you should leave it alone.
But platform risk for a solo operator isn't only about money. It's about control over whether your stuff is up when you need it. A hard cap that pauses your whole account is a single point of failure hiding inside a convenience, and the fix (don't let the thing that matters share a pool with the thing that doesn't) costs you one afternoon. Spend the afternoon.
Author
Lukas
@lukcombinator