Every figure on this page was read off netlify.com/pricing and the Netlify billing docs on 30 August 2026. Netlify no longer bills in gigabytes and seats. It bills in credits, and a single credit balance is drained by five different meters at once, which is why the $20 sticker on Pro tells you almost nothing about your invoice. Below is the published rate card, the arithmetic that turns credits back into dollars, and the traffic level where a server you rent yourself costs less.
# free plan · no credit card required
Provisions on Hetzner, DigitalOcean, AWS, Vultr, Linode, OVHcloud or any VPS you already own
Netlify pricing has four tiers: Free at $0 with 300 credits, Personal at $9 with 1,000 credits, Pro at $20 with 3,000 credits and unlimited team members, and Enterprise on quote. Everything you use is billed from one credit balance: 20 credits per GB of bandwidth, 2 credits per 10,000 web requests, 10 credits per GB-hour of compute and 15 credits per production deploy. At the Pro rate of $0.0067 a credit that works out to about $0.13 per GB. The Free plan is a hard limit with no auto recharge, so 20 production deploys consume the entire monthly allowance before you serve a single byte.
Last updated August 2026
This is the meter that ends most Netlify plans. Every gigabyte you serve costs 20 credits, so a Pro plan's 3,000 credits is about 150 GB if bandwidth were the only thing you spent them on. At the Pro credit rate that is roughly $0.13 per GB. For comparison, a $12 DigitalOcean droplet includes 2 TB of transfer at a flat rate, which is more than thirteen times the Pro allowance for less money.
This is the line nobody expects and the reason small sites outgrow the Free plan without any traffic. Each production deploy costs 15 credits. The Free plan's 300 credits therefore covers exactly 20 production deploys a month, and once they are gone the allowance is gone. A team that merges to main twice a day is spending 900 credits a month, or almost a third of a Pro plan, on deploys alone.
Requests are metered separately from bandwidth, so a page made of many small assets costs twice. Two credits per 10,000 requests works out to about $1.33 per million at Pro rates. This is the meter that punishes uncached API routes and image-heavy pages, because every asset on the page is its own request even when the bytes are trivial.
Serverless and edge function execution is billed on memory multiplied by time, at 10 credits per GB-hour, or about $0.067 per GB-hour on Pro. Short functions are cheap and long-running ones are not. This is the meter that makes server side rendering more expensive on Netlify than serving a static build, and it is worth measuring before you move a rendered app onto functions.
Netlify's billing documentation prices AI inference at 180 credits per $1 of inference. At the Pro credit rate of $0.0067 those 180 credits cost you $1.20, so routing model calls through Netlify carries roughly a 20 percent premium over the underlying inference price. Whether that is worth paying for the convenience is a real decision, but you should make it knowingly.
Netlify removed per-seat pricing from Pro in 2026. Its own announcement is explicit about the before and after: Pro used to cost $20 for one seat with every additional seat or git contributor costing another $20, and it now costs $20 a month with unlimited seats. For a team of any size this is the single most favorable thing about Netlify pricing, and it is where Netlify genuinely beats Vercel.
Estimate four numbers for the month: gigabytes served, web requests, GB-hours of function compute and production deploys. Multiply them by 20, 0.0002, 10 and 15 respectively. The total is your credit burn. Doing it in this order matters, because the plan price is chosen by credits and not by any one resource.
Free gives 300 credits, Personal gives 1,000 for $9 and Pro gives 3,000 for $20. If your burn is under 300 and you deploy fewer than twenty times a month, Free genuinely works. If it is over 3,000 you are on Pro and buying packs, which is where the arithmetic in the next step starts to matter.
Overage is bought in packs: 500 credits for $5 on Personal, 1,500 credits for $10 on Pro. The Pro pack works out to the same $0.0067 a credit as the base plan, so Pro overage is at least honest and does not escalate. Multiply your excess credits by that rate and add it to the plan fee. That is your realistic monthly bill.
Take the bandwidth number on its own and price it against a VPS. A $12 droplet carries 2 TB of transfer and a $18 one carries 3 TB, both flat. Below roughly 150 GB a month Netlify is comfortably cheaper and simpler. Above about 500 GB the gap moves decisively the other way, and it keeps moving.
These are Netlify's published plan allowances and credit rates, not our estimates. The gigabyte figures in the bandwidth row are our arithmetic from the published 20 credits per GB rate, and they assume you spend the whole allowance on bandwidth and nothing else, which no real site does. Where a cell says custom, Netlify does not publish a figure and neither will we.
swipe to see all columns →
| Free | Personal | Pro | Enterprise | |
|---|---|---|---|---|
| Price per month | $0 | $9 | $20 | Custom |
| Credits included | 300 | 1,000 | 3,000 | Custom |
| Team members | Individual | Individual | Unlimited | Unlimited |
| Billed per seat | n/a | No | No, flat per team | Custom |
| Bandwidth if spent only on bandwidth | About 15 GB | About 50 GB | About 150 GB | Custom |
| Production deploys if spent only on deploys | 20 | 66 | 200 | Custom |
| Auto recharge available | No, hard limit | Yes | Yes | Custom |
| Credit pack | None | 500 for $5 | 1,500 for $10 | Custom |
| Effective cost per credit | n/a | $0.009 | $0.0067 | Custom |
| Bandwidth rate | 20 credits per GB | 20 credits per GB | 20 credits per GB | Custom |
| Web request rate | 2 per 10,000 | 2 per 10,000 | 2 per 10,000 | Custom |
| Compute rate | 10 per GB-hour | 10 per GB-hour | 10 per GB-hour | Custom |
| Production deploy rate | 15 credits | 15 credits | 15 credits | Custom |
| Form submissions | Included | Included | Included | Included |
Netlify wins this and we will not pretend otherwise. If you serve under 15 GB and deploy fewer than twenty times a month, the Free plan costs nothing and there is no server to patch. Personal at $9 covers about 50 GB and lifts the hard limit. There is no honest argument for renting a server to save nine dollars a month.
This is where Netlify is genuinely underrated. Because Pro is $20 for the whole team rather than $20 a head, five developers cost the same as one. Serve 120 GB, make 60 deploys and run a few GB-hours of compute and you land near 4,300 credits, so Pro plus one $10 pack is about $30 a month. Very little beats that.
Here the credit model turns against you hard. A terabyte of bandwidth alone is 20,000 credits, and with requests and deploys on top a realistic month lands near 26,600 credits. That is Pro plus about sixteen $10 packs, roughly $180 a month. The same terabyte fits inside the flat 3 TB allowance on an $18 droplet.
One credit balance covering every project makes per-client cost attribution awkward, and bandwidth across a portfolio adds up faster than any single site suggests. Agencies usually want per-client isolation, their own backups and a flat, predictable line item they can mark up. That is a different shape of problem from what a credit balance solves.
Netlify costs $0 a month on Free, $9 on Personal, $20 on Pro and a quoted figure on Enterprise. Every paid tier includes a monthly credit allowance rather than a list of resource limits: 300 credits on Free, 1,000 on Personal and 3,000 on Pro. Usage above the allowance is bought in packs, at 500 credits for $5 on Personal and 1,500 credits for $10 on Pro.
The important structural point is that Pro is priced per team and not per seat. Netlify removed seat pricing from Pro in 2026, and its own announcement states the change plainly: Pro previously cost $20 for one seat with each additional seat or git contributor costing another $20, and it now costs $20 a month with unlimited seats. If headcount is what drives your hosting bill, this single change probably makes Netlify the cheapest option on this site.
Netlify publishes credit costs, not dollar costs, so the conversion is worth doing once. On Pro, 3,000 credits cost $20, which is $0.0067 a credit. The overage pack of 1,500 credits for $10 works out to exactly the same rate, so Pro overage does not escalate. On Personal, 1,000 credits for $9 is $0.009 a credit, and the 500 credit pack at $5 is $0.010, so Personal overage is slightly more expensive than the plan itself.
Applying the Pro rate to Netlify's published meters gives the dollar figures most people are actually looking for. These are our arithmetic from Netlify's published rates, not prices Netlify quotes in dollars.
| Resource | Published credit rate | Cost at Pro credit rate |
|---|---|---|
| Bandwidth | 20 credits per GB | About $0.13 per GB |
| Web requests | 2 credits per 10,000 | About $1.33 per million |
| Functions compute | 10 credits per GB-hour | About $0.067 per GB-hour |
| Production deploy | 15 credits each | About $0.10 each |
| AI inference | 180 credits per $1 | About $1.20 per $1 of inference |
Yes, Netlify has a genuinely free plan at $0 a month with 300 credits, but it is a hard limit with no auto recharge. Netlify's billing documentation is explicit that the Free plan carries a credit hard limit and that auto recharge is only available on paid plans. You cannot buy more credits on Free. When they are gone, they are gone until the month resets.
The number that surprises people is how little 300 credits buys once deploys are counted. At 15 credits per production deploy, 20 deploys consume the entire free allowance before a single byte is served. A developer who merges to main once a working day is already at 315 credits. This, not bandwidth, is what pushes most small projects onto Personal.
If you spend the whole allowance on bandwidth instead, 300 credits is about 15 GB. That is enough for a personal portfolio and not much else.
Netlify replaced a long list of separate resource meters with a single credit balance. Every plan tops that balance up monthly, and five meters draw it down: bandwidth, web requests, functions compute, production deploys and AI inference. Form submissions are included and do not consume credits.
The practical consequence is that no single resource has its own ceiling. On the older model you could blow a bandwidth limit while your build minutes went unused. Now a bandwidth spike, a deploy-heavy sprint and a burst of function traffic all compete for the same pool, and any one of them can drain it. That makes the model simpler to reason about in aggregate and much harder to forecast per resource.
The formula is short enough to do on paper. Take gigabytes served times 20, plus web requests divided by 10,000 times 2, plus GB-hours of compute times 10, plus production deploys times 15. Compare the total against 300, 1,000 or 3,000 to pick a plan, then price anything above that at $0.0067 a credit on Pro.
A single sticker price is impossible because usage genuinely varies, so here is the arithmetic instead. The three scenarios below use Netlify's own published rates and nothing else. They are our calculation from that rate card, not packages Netlify quotes.
Eight GB of bandwidth is 160 credits. Three hundred thousand web requests is 60 credits. Twelve production deploys is 180 credits. That totals 400 credits, which is already past the Free allowance of 300, entirely because of the deploys. Personal at $9 covers it with room to spare. Total: $9.00 a month.
One hundred and twenty GB of bandwidth is 2,400 credits. Four million web requests is 800 credits. Sixty production deploys is 900 credits. Twenty GB-hours of compute is 200 credits. That totals 4,300 credits against the 3,000 included on Pro, so 1,300 credits of overage, covered by a single 1,500 credit pack at $10. Headcount adds nothing because Pro is flat per team. Total: $30.00 a month.
One thousand GB of bandwidth is 20,000 credits on its own. Thirty million web requests is 6,000 credits. Forty production deploys is 600 credits. That totals 26,600 credits against 3,000 included, leaving 23,600 credits of overage. At 1,500 credits per $10 pack that is sixteen packs, or $160. Total: about $180.00 a month.
The same terabyte fits inside the flat 3 TB transfer allowance of an $18 a month DigitalOcean droplet with 2 GB of RAM and 2 vCPUs. That is the whole argument on this page in one line: below roughly 150 GB the credit model is cheap and effortless, and somewhere past 500 GB it stops being either.
These two are priced on opposite principles, and which one is cheaper depends almost entirely on whether your bill is driven by people or by traffic. Vercel figures below were read off vercel.com on 29 August 2026.
| Netlify Pro | Vercel Pro | |
|---|---|---|
| Base price | $20 per team | $20 per developer seat |
| Five developers | $20 | $100 |
| Bandwidth included | About 150 GB | 1 TB |
| Bandwidth overage | About $0.13 per GB | $0.15 per GB |
| Requests included | Shared credit pool | 10 million edge requests |
| Request overage | About $1.33 per million | $2.00 per million |
| Included usage credit | None beyond the plan credits | $20 per month |
Netlify's unit rates are slightly cheaper and its included allowance is far smaller. Vercel bundles nearly seven times the bandwidth into the same $20, then charges more per gigabyte past it. Netlify charges less per gigabyte but starts charging much sooner.
The crossover is easy to state. If your team is large and your traffic is modest, Netlify is dramatically cheaper, because five seats cost $100 on Vercel and nothing extra on Netlify. If your team is small and your traffic is heavy, Vercel is cheaper, because that included terabyte is worth more than the small per-gigabyte saving. Our Vercel vs Netlify pricing comparison works four full monthly bills through both rate cards, and the full Vercel rate card sits on our Vercel pricing breakdown.
The honest answer is later than most self-hosting advocates claim and sooner than the credit model suggests. The break-even is a bandwidth question, because bandwidth at 20 credits per GB is the meter that scales without limit while a VPS transfer allowance is flat.
At 150 GB a month you are inside the Pro allowance and Netlify costs $20. At 300 GB you have spent 6,000 credits, so Pro plus two packs is $40 against $12 for a droplet that includes 2 TB. At 1 TB the gap is roughly $180 against $18. The line crosses somewhere near 200 GB and never comes back.
What that arithmetic leaves out is real and worth naming. A server has to be provisioned, firewalled, patched, certificated and monitored, and somebody has to be responsible when a deploy fails at 2am. That work has a cost even when it does not appear on an invoice. The reason this comparison is worth making at all is that the work is now largely automatable: provisioning, atomic zero downtime releases, one click rollback, certificate renewal, firewall rules, cron and queue workers can all be driven from a panel rather than a runbook. If you want the mechanics, our guide to hosting multiple websites on one server covers the isolation model, and deploying from git covers the release pipeline.
There is a middle path worth knowing about. Several open source platforms give you a Netlify-like deploy experience on hardware you rent, with no credit meter at all. We compare that whole category on our Coolify alternative page.
Being straight about the gaps matters more on a pricing page than anywhere else, because a confident-sounding invented number is worse than an admitted blank.
Prices move. Everything here was read on 30 August 2026, and if you are making a budget decision on it, check netlify.com/pricing before you commit.
Ready to stop managing servers by hand? DeployManage provisions, deploys and monitors your fleet from one dashboard.
$ get started freeNetlify costs $0 a month on Free, $9 on Personal, $20 on Pro and a quoted figure on Enterprise. Each tier includes a monthly credit allowance of 300, 1,000 and 3,000 credits respectively, and all usage is drawn from that single balance. Overage is bought in packs at 500 credits for $5 on Personal and 1,500 credits for $10 on Pro.
Yes, Netlify has a permanently free plan at $0 with 300 credits a month. It is a hard limit with no auto recharge, so you cannot buy more credits on the Free plan. Because each production deploy costs 15 credits, twenty deploys use the entire monthly allowance before you serve any traffic at all.
Credits are Netlify's single billing unit, replacing separate limits for each resource. Five meters draw them down: bandwidth at 20 credits per GB, web requests at 2 credits per 10,000, functions compute at 10 credits per GB-hour, production deploys at 15 credits each, and AI inference at 180 credits per $1 of inference. Form submissions are included free.
On Pro, 3,000 credits cost $20, which is about $0.0067 per credit, and the 1,500 credit overage pack at $10 works out to the same rate. On Personal, 1,000 credits for $9 is $0.009 per credit, while the 500 credit pack at $5 is $0.010, so Personal overage costs slightly more than the base plan.
Netlify no longer sells bandwidth as a fixed allowance. Bandwidth costs 20 credits per GB, so if you spent an entire allowance on bandwidth alone you would get about 15 GB on Free, 50 GB on Personal and 150 GB on Pro. Real sites also spend credits on deploys, requests and compute, so the usable figure is lower.
No. Netlify removed per-seat pricing from Pro in 2026. Pro is now $20 a month for the whole team with unlimited members. Its own announcement states that Pro previously cost $20 for one seat with each additional seat or git contributor costing another $20 per month, and now costs $20 with unlimited seats.
On paid plans you can enable auto recharge, which buys additional credit packs automatically so your projects keep running: 500 credits for $5 on Personal and 1,500 for $10 on Pro. Leaving auto recharge off keeps costs predictable. The Free plan has a hard credit limit and no auto recharge option at all.
Pro is worth it when your team is bigger than one or your usage passes 1,000 credits a month. Because it is flat at $20 for unlimited team members, the value rises with every developer you add. For a five person team it is exceptional value. For a solo developer on heavy traffic, the credit burn matters far more than the plan fee.
Unlimited. Since Netlify dropped seat pricing in 2026, the $20 Pro plan covers as many team members and git contributors as you want at no additional cost. This is the clearest structural advantage Netlify has over Vercel, which charges $20 per developer seat per month on its comparable Pro plan.
It depends on whether people or traffic drive your bill. Five developers cost $20 on Netlify Pro and $100 on Vercel Pro, so Netlify wins decisively on headcount. Vercel includes 1 TB of transfer against roughly 150 GB on Netlify Pro, so Vercel wins decisively on traffic. Netlify's per-unit rates are slightly cheaper on both bandwidth and requests.
Multiply gigabytes served by 20, web requests by 0.0002, GB-hours of compute by 10 and production deploys by 15, then add the results for your monthly credit burn. Subtract your plan's included credits and price the remainder at $0.0067 each on Pro. Add the plan fee for your total.
Netlify does not publish an Enterprise price and quotes it per organization. Any specific enterprise figure you find on a third party comparison site is an estimate rather than a published rate. If you need a number for a budget, you have to request a quote directly.
Bandwidth decides it. At 150 GB a month you sit inside Pro's allowance at $20. At 300 GB Netlify is about $40 against $12 for a droplet including 2 TB of flat transfer. At 1 TB it is roughly $180 against $18. The crossover falls near 200 GB a month and the gap widens from there.
Provision a server on your own DigitalOcean, Hetzner, AWS or Vultr account and deploy the same site to it from git, with atomic zero downtime releases, one click rollback, certificates, firewall, cron and queue workers managed from a single panel. Bandwidth arrives in terabytes at a flat rate, and no meter counts your deploys. Free to start.
# free plan · no credit card required