Netlify pricing changed enough that the account's billing model now matters as much as the plan name. Newer teams use monthly credits. Teams created before September 4, 2025 may still be on legacy plans. These models have different allowances, so start by checking your Team settings.
Current Netlify plans in October 2026
Netlify's current pricing page lists Free at $0 with 300 credits per month, Personal at $9 with 1,000 credits, Pro from $20 with 3,000 credits and unlimited members, and Enterprise at custom pricing. Pro has higher credit tiers for teams with more usage.
Free has a hard credit limit and no auto recharge. Personal and Pro can enable optional auto recharge. Pro adds team features such as shared environment variables and at least three concurrent builds. This is a different structure from the old per-seat Pro and Business plan descriptions.
What spends credits?
On the current rate card, a production deploy costs 15 credits, outbound bandwidth costs 20 credits per GB, web requests cost 2 credits per 10,000 requests, and compute costs 10 credits per GB-hour. A production deployment, its requests, the bytes delivered, and function time can all contribute to the same monthly allowance.
For a light content site with eight production deploys, 5 GB transferred, and 100,000 web requests, those three items total 240 credits: 120 for deploys, 100 for bandwidth, and 20 for requests. That leaves 60 credits on Free before any compute or other metered services. For a site with frequent CMS rebuilds, deployments alone can become the binding constraint.
Do not multiply visitors by an invented average page size and call it a budget. Inspect the project's actual bandwidth, request volume, deploy count, and function usage. A cached static site and a server-rendered app behave differently at the same visitor count.
Free: good for testing, tight for production
The Free plan documentation describes a 300-credit hard monthly limit. There is no auto recharge on Free. Once credits run out, projects can pause. This makes Free useful for prototypes and low-usage personal sites, but a risky default for a revenue-critical client campaign.
Unlimited deploy previews are valuable, but each push to production counts as a production deploy. Batch small editorial changes where practical and use previews for approval. Compress images and review usage before a launch.
Personal: one owner with more headroom
Personal is $9 per month for 1,000 included credits and one paid member. It suits a solo operator whose traffic or deploy frequency has outgrown Free. Optional auto recharge can prevent a mid-cycle pause, but set a spending expectation before using it for client work.
Pro: team workflow and flexible credit tiers
Pro starts at $20 per month with 3,000 credits and unlimited members. Netlify introduced larger Pro credit tiers up to 20,000 monthly credits, with rollover on qualifying higher tiers. Choose the tier from measured usage; do not assume a historic per-seat price or a single fixed Pro allowance.
Pro is the practical step when multiple developers need access, shared environment variables, concurrent builds, and a larger usage pool. Compare the included credits with the team's busiest month, not just its average.
Enterprise and legacy plans
Enterprise pricing is negotiated and adds procurement, security, support, and service commitments. It makes sense when contract requirements require those terms, not merely because a site is busy.
Teams that have stayed on pre-September 2025 plans should consult Netlify's legacy pricing documentation. Legacy Starter's 100 GB bandwidth and 300 build minutes are not the allowances for a new credit-based Free team. Compare the migration impact before switching.
Netlify also made form submissions unlimited on credit-based plans in its April 2026 pricing update. If a post or spreadsheet still treats 100 free form submissions as universal, it is mixing billing models.
Which plan should you choose?
Use Free when a pause at the cap would be tolerable and the measured workload fits 300 credits. Use Personal when one operator needs 1,000 credits and optional recharge. Use Pro when the team needs collaboration and production headroom. Ask for Enterprise terms when an SLA, security, or procurement requirement drives the purchase.
For an agency managing several client sites, decide whether each client should own its own billing team. A shared pool makes attribution harder and lets one client's traffic consume capacity intended for others.
FAQ
Can a free Netlify site get an unexpected overage bill?
The current credit-based Free plan has a hard limit and no auto recharge. An older legacy plan is different. Check the team's billing model, and do not apply credit-plan rules to legacy accounts.
Is Pro priced per team member?
On current credit-based pricing, Pro starts at $20 per month with unlimited members. Older per-seat descriptions refer to legacy plans.
What happens after Free credits run out?
Projects can pause until the allowance resets or the team upgrades. Monitor usage before important publishing windows.
Are build minutes still the main pricing metric?
Build minutes remain relevant to some legacy accounts. Credit-based plans charge for production deploys and other usage under one credit allowance.
For the free tier's practical limits and a worked example, read Netlify Free Tier Limits.