Netlify changed how it charges, and the change matters more to small projects than to large ones. If you are a freelance developer hosting client sites, a side project, or a publication, the number you need is not the monthly price. It is the point at which the free tier stops serving your site.

What this article is: a reading of Netlify's official pricing and billing documentation, checked on 7 August 2026, with the arithmetic worked out. What it is not: a review. Yangworks has never run a production site on Netlify, has never received a Netlify bill, and measures nothing here. Every figure below is quoted from Netlify's documentation; every calculation is stated so you can redo it; every opinion is labelled.

First: find out which pricing system you are on

There are two, and they share no units.

Netlify's legacy pricing page states: Starting on September 4, 2025, all new Netlify accounts will use the new credit-based pricing plans, and If you've created your Netlify account with a Free, Starter, or Pro plan before September 4, 2025, then your pricing plan is now considered a legacy pricing plan.

Legacy accounts are not being forced to move — the changelog says You can stay on your legacy plan with no action required. But the move is one-way: You cannot revert to a Legacy plan from a Credit-based plan. This change is permanent.

So before you use any number from any pricing article, including this one, check Usage & billing → Billing details in your Netlify dashboard.

The credit model, at the documented rates

Credit-based plans meter five things. Netlify's rates:

Production deploy        15 credits each
Bandwidth                20 credits per GB
Web requests              2 credits per 10,000
Compute                  10 credits per GB-hour
AI inference            180 credits per $1 of model usage

Deploy previews           free
Branch deploys            free
Failed deploys            free
Rollbacks                 free
Form submissions          free and unlimited

The plans: Free is $0/month with 300 credits/month with credit hard limit; Personal is $9/month with 1,000 credits and auto recharge at 500 credits for $5; Pro Starts at $20/month with 3,000 credits, scaling to 20,000 credits at $126/month, with auto recharge at 1,500 credits for $10.

Two details freelancers should notice immediately. Free and Personal have no team seats — Only 1 Team Owner — so the first client who needs dashboard access puts you on Pro. And rollover credits only exist on Pro plans with 5,000+ monthly credits; on Free, Personal, and base Pro, unused credits expire.

What 300 free credits actually buys

This is just division, but it is the part that changes decisions.

Taken one line at a time, 300 credits is 20 production deploys, or 15 GB of bandwidth, or 1.5 million web requests. You do not get all three; you get 300 credits total across all of them, for every project on the team.

A realistic small-site month:

12 production deploys      12 x 15  = 180 credits
3 GB bandwidth              3 x 20  =  60 credits
400,000 web requests       40 x  2  =  80 credits
                                     -----------
                                       320 credits   over the 300 limit

Author judgment: the surprising term in that sum is the first one. On a content site with modest traffic, deploying is more expensive than being read. Twelve pushes to main cost more than three gigabytes of traffic. A freelancer who commits small and often — the normal way to work — burns the free allotment on the act of shipping, not on an audience.

The documented mitigations are real, though: deploy previews and branch deploys cost nothing, and failed deploys cost nothing. Batching work on a branch and merging once is a genuine cost lever rather than a trick.

What happens at zero

This is the most important paragraph in Netlify's billing documentation, and it is worth quoting in full:

Once your monthly credit allotment is used up for all web projects on your team, all of your web projects (sites/apps) are paused and visitors to your web projects will find a Site not available page at each of your web project's URLs.

The docs continue: while paused, projects will not receive new web requests, web traffic, or form submissions and you cannot trigger new production deploys. And the blast radius is the account, not the project: if one site/web project exceeds its limits, all sites/projects on your account will be paused.

Warnings arrive at 50%, 75%, 90%, and 100% of your monthly credit allotment by email and in-app. On Free there are exactly two ways out — wait till the start of the next billing cycle or upgrade to a higher plan — because credit packs cannot be bought on Free.

Author judgment: this is a defensible design and a bad fit for client work. The Free tier's hard limit is a genuine feature if the thing you fear is a surprise invoice; Netlify says as much — By using the Free plan, you can ensure you won't incur charges. But "one project overruns, every client site on the account goes dark" is not a risk profile you can accept on someone else's behalf. If you host client work, either put each client on their own team or do not use the free tier for production.

If you are on a legacy plan, the numbers are different

Legacy Free and Starter: 100 GB bandwidth per month and 300 minutes of build time, 1 concurrent build, and Limited to 1 free member, with free & unlimited Git Contributors. On legacy Free those are hard limits; on Starter, exceeding them costs $55 per 100GB of bandwidth and $7 per 500 build minutes. Legacy Pro raises the allowances to 1 TB and 25,000 minutes at the same overage rates, with seats at $19 /month per member and extra concurrent builds at $40 each.

Legacy free-tier exhaustion behaves similarly to the credit model: If the build limit is reached, your sites will still be served to visitors, but new builds will be disabled for all sites on your account, while for other metered features new builds will be disabled and all sites on your account will be paused. One footnote with teeth: deleting the site with overages will not restore the account.

The factual contrast with Cloudflare

Yangworks runs on Cloudflare Workers Static Assets, so treat this section as an interested party quoting the other side's documentation. Both columns are official statements, checked 7 August 2026 — not benchmarks.

                       Netlify Free (credit)      Cloudflare Workers Free
Price                  $0                         $0
Static asset requests  2 credits / 10k requests   "free and unlimited"
Bandwidth              20 credits per GB          no separate asset charge
Production deploys     15 credits each            not metered
Build minutes          (counted as compute)       3,000 per month
Concurrent builds      1                          1
Team seats             1 Team Owner               n/a for static assets
At the limit           all projects paused        documented per-feature

Cloudflare's pricing page states that Requests to static assets are free and unlimited and that storing them carries no additional cost; the Workers Free plan allows 100,000 Worker requests per day, and Workers Builds includes 3,000 per month build minutes on Free against 6,000 per month (then, +$0.005 per minute) on Paid.

Author judgment, and the honest asymmetry: for a purely static site with no server-side code, Cloudflare's free tier has no deploy meter and no request meter, which removes exactly the two costs that dominate the Netlify arithmetic above. That is a real structural difference, not a marketing one. It is also a narrow comparison — it says nothing about build ergonomics, preview workflow, or the framework integrations Netlify is genuinely good at, and I have not run a Netlify project to weigh those.

When Netlify's pricing is the right call

Everything in this section is judgment from the documentation, not from operating experience.

The free tier fits a personal site or a demo you deploy rarely, where a hard stop is preferable to a bill and the site going dark for a few days is survivable.

Personal at $9 is the tier for a solo developer shipping regularly: 1,000 credits is roughly 66 production deploys before anything else, and auto recharge exists as a backstop — though note it is off by default and only Team Owners can enable it.

Pro at $20 is the real freelancer tier, and not because of the credits. It is the first plan with Unlimited seats, audit logs, and 30-day analytics retention. Compare that with legacy Pro's $19 /month per member: for a two-or-three-person collaboration the credit-based Pro plan is straightforwardly cheaper.

Switch away when your workload is mostly static delivery with frequent deploys, since that is the shape the credit model prices least favourably. Stay when you are using the parts Netlify meters generously — free deploy previews, free branch deploys, unlimited forms — or when your framework's Netlify adapter is the reason the project ships at all.

What this article does not establish

No Netlify site was operated, deployed, or billed in the writing of this guide. There is no measured build time, no measured bandwidth, no observed invoice, no support-quality assessment, and no reliability claim. Enterprise pricing is excluded because it is not published. Every plan figure comes from Netlify's public documentation on the date shown and pricing changes — the credit model itself is less than a year old and was revised in April 2026 — so re-check the source pages before making a decision. No affiliate relationship exists with Netlify or Cloudflare, and nothing here earns a commission.

For how the Cloudflare side of that comparison actually works in practice, see the Workers Static Assets review and the deploy guide.