Netlify
Netlify · website builders · reviewed by Stan K. · Source: data snapshot · data as of 2026-11-13
The credit meter: 300 credits/month at a "Hard limit" — bandwidth 20 credits/GB, deploys 15 each — and when credits run out, every project is paused.
#11 of 11 in Website Builders
ToolScore breakdown — why 62/100
10 criteria × 10 points. Low pillars are visible on purpose — that's the point of a score you can audit. Methodology →
What it does well
- ▸Deploy Previews and branch deploys cost 0 credits — the CI-shaped features are outside the meter
- ▸Everything leaves: static files in your repo; deploys are reproducible elsewhere
- ▸Personal $9/mo lifts the cap to 1,000 credits — a knowable escape hatch
- ▸The credit arithmetic is published: 20 credits/GB bandwidth, 15 per production deploy
Where it costs you
- ▸Free is 300 credits/month at a "Hard limit" — when credits run out "all of your web projects (sites/apps) are paused" (Site not available)
- ▸Bandwidth costs 20 credits per GB and production deploys 15 each — 300 credits is ~15 GB or 20 deploys, not both
- ▸The credit model is mandatory for accounts created after 04.09.2025 — older accounts sit on legacy plans
- ▸Functions, Identity and forms glue would need rewrites on exit
Hidden traps — the stuff the pricing page doesn't say
When the 300 monthly credits run out, "all of your web projects (sites/apps) are paused" with a "Site not available" page — the meter doesn't throttle, it switches the sites off. With bandwidth at 20 credits/GB and production deploys at 15 each, 300 credits is roughly 15 GB of traffic or 20 deploys. A busy month plus a release day can go dark.
The credit model is mandatory for accounts created after 04.09.2025 — older accounts sit on legacy plans. Two neighbors on Netlify can be on materially different free tiers depending on signup date; don't model your bill from a colleague's invoice.
Know the limits before you pay: read the traps above, then decide with eyes open.
Visit official siteAffiliate link where available — never affects the score.
- official Netlify credits — hard limit, 20 cr/GB, 15 cr/deploy, paused projects (official docs, checked 2026-11-13) verified
Data as of 2026-11-13. Prices and limits change monthly — report anything stale. How we verify: methodology.
Closest alternatives
Designer-grade HTML with the most expensive fine print: 0 CMS items on Basic, forced upgrades on ban
A clean Free / Basic / Pro ladder at $10/mo with custom domain — metered at every joint: 30 pages on
The friendliest door — 3 days free, then $1/month for 3 months — with a country tax: 2% on Basic whe
Netlify review
In-depth analysis · last updated 2026-11-13
Credits, not bandwidth
Netlify lands at 62 in our export/lock-in table — the "credits, not bandwidth" row, well under its static rivals. The free tier is 300 credits/month at a "Hard limit", and the meter is documented to the credit: bandwidth costs 20 credits per GB, production deploys 15 each. The arithmetic that matters: 300 credits is roughly 15 GB of traffic or 20 production deploys — not both. Deploy Previews and branch deploys cost 0 credits, so the CI-shaped features sit outside the meter; the production meter is the one that bites.
The pause switch
The behavior that decides the score: when credits run out, "all of your web projects (sites/apps) are paused" (Site not available). The meter doesn't throttle — it switches every project off until the month rolls over or you pay. Personal at $9/mo lifts the cap to 1,000 credits, which is the knowable escape hatch. Note also that the credit model is mandatory for accounts created after 04.09.2025; older accounts sit on legacy plans, so two neighbors can be on materially different free tiers.
The exit is fine; the glue is not
As a static host the exit is clean: everything leaves, static files live in your repo, and deploys are reproducible elsewhere. The rewiring is the familiar static-host bill — Functions, Identity and forms glue would need rewrites — the same trade Cloudflare Pages and GitHub Pages make, scored here against rivals that don't pause your sites at the meter.
How the pillars land
Price/Value 5.5: $0 exists, but the hard meter and the pause switch price it honestly. Site & commerce limits 5: 300 credits/month is the tightest ceiling in the static trio — hard, not soft. Editor & publishing 8: deploys, previews and branch workflow are excellent while credits last. Export & ownership 7: static leaves cleanly; the platform glue rewires. Feature set 7: Functions, Identity and forms exist — and each is a rewrite on exit. Track record 6.5: the 04.09.2025 forced migration to credits reshaped the free tier mid-flight. Ease 6: Git + CLI, plus a credit budget to manage. Pricing transparency 7.5: every credit rate is published — the model, not the documentation, is the problem. Support & docs 5.5: the credits doc is the verified source; nothing beyond it was checked in this snapshot. Privacy isn't on this category's scorecard — this hub researches price, limits and exit, not data practices.
Verdict — AVERAGE, 62/100
Netlify is the right pick when the deploy previews and branch workflow are what you're buying and the traffic is modest and predictable. If the site needs to stay up through a busy month without credit-watching, Cloudflare Pages' unlimited free tier — or GitHub Pages' soft limits — is the same static output without the switch.