Netlify Pricing (2026): What a Month Costs in Credits

Netlify pricing starts at $0 for Free, $9/month for Personal, and $20/month for Pro with unlimited members. Under credit billing, a modest marketing site can stay free, while the illustrative Next.js app below costs $14/month and a 10-site agency costs $20/month.

Verified against Netlify's live pricing page, October 2026, checked on 4 October. All prices are in US dollars. The usage quantities in the worked examples are explicit assumptions, and the calculations use the rates on that page.

Netlify is a platform for building and hosting websites and apps. Its credit plans bundle deployment, traffic and runtime usage into a shared allowance. Your monthly cost therefore starts with a subscription, then depends on how quickly your projects spend that allowance and whether you authorize more credits.

For a developer, the useful question is how often you publish and what runs when someone visits. For an agency, add a second question: which client sites share the same budget?

Netlify Pricing Plans: Monthly Prices and Credit Limits

Free is a hard $0 cap, Personal buys a larger solo allowance, and Pro starts at $20 for a shared team. The higher Pro credit tiers have higher prices; selecting 20,000 credits does not leave the price at $20.

These are the monthly prices verified in October 2026. The Pro selector on the pricing page supplies the higher-tier prices, also listed in Netlify's Pro plan documentation.

Free and Personal each allow one full team member. Pro includes unlimited members across its credit tiers. Free reviewer roles let people give feedback, but a reviewer is different from a colleague who needs full development access. Netlify pricing and membership FAQ

Personal is the economical solo plan until usage changes the bill

Personal's $9 monthly subscription includes 1,000 credits, with an optional $5 recharge for each additional 500. It fits a solo developer who needs more room than Free but does not need another full member or Pro's collaboration features.

An occasional top-up can be cheaper than upgrading. At the assumed app workload below, Personal costs $14 for the month. Paying $20 for Pro would make sense if you also need its team features; usage alone would not justify that upgrade yet.

Pro buys collaboration as well as credits

Pro starts at $20/month for 3,000 credits and unlimited members. It adds organization-owned private repositories, shared environment variables and three concurrent builds, meaning three builds can run at the same time. Those features can decide the plan before traffic does. Netlify pricing

A small agency should price Pro as one team subscription with pooled usage. Adding another developer does not create another Pro seat fee, but adding another active site creates more work for the meters.

The credit tiers above the base plan suit sustained usage or a predictable busy season. They also introduce rollover, discussed below. Choose them from expected total credit consumption across the team.

Enterprise requires a quote

Enterprise has custom pricing and allowances. The vendor's page lists an uptime service agreement, enterprise networking, organization management and dedicated support. A small agency should reach for a quote when those requirements are concrete, rather than guessing an Enterprise budget from Pro.

The current page displays monthly self-serve credit prices and does not advertise a discounted annual rate for them. Budget from these monthly figures. A separately negotiated Enterprise contract has its own terms.

Netlify Free Plan: Who Can Keep Paying $0

Stay on Free when one developer can run the projects comfortably inside 300 monthly credits. A portfolio, a quiet brochure site or a lightly used prototype can meet that rule without needing a paid subscription.

Free includes custom domains with SSL, the encryption behind HTTPS, plus a global content delivery network, Functions, Netlify Database and Blob storage. It also includes unlimited Deploy Previews, the temporary versions used to review a change before publishing. Free plan features

That makes Free useful for more than a disposable demo. The limit is the shared credit allowance, not a requirement to pay as soon as the site looks professional.

The developer who never needs to pay publishes selectively, serves a modest amount of content and keeps background usage small. Review changes in previews, release finished changes to production, and check the credit balance when traffic changes. If that workload continues to fit, Free continues to cost $0.

The operational consequence matters: using up the allowance pauses the projects that share it. Visitors see a site-unavailable page. Free cannot buy extra credits; you wait for the next billing cycle or upgrade. Its hard limit protects the bill, while your release and traffic budget protect availability. How credits work

For a client site with a deadline or important lead flow, leave headroom. A plan that only fits an average month is a weak operating budget for a busy month.

What Consumes Netlify Credits?

Production releases, compute, delivered data, web requests and AI inference consume credits. They draw from the same pool, so one activity can affect several meters.

The live pricing page publishes these hosting rates:

• Production deploys: 15 credits each. A successful production release publishes the version served at your main domain.
• Compute: 10 credits per GB-hour. This covers runtime resources such as Functions, agents and the database.
• Bandwidth: 20 credits per GB. This measures data delivered, including site files, images, downloads, function responses and outgoing database data.
• Web requests: 2 credits per 10,000 requests. Pages, assets, function requests, redirects and Edge Functions contribute.

A request is an individual fetch of content, not a person. Loading a page can fetch its HTML, scripts, styles and images. Budgeting from visitor count alone misses those separate requests.

Compute uses allocated memory multiplied by runtime. A GB-hour combines how much memory a function reserves with how long it executes. It is separate from the bytes the function sends back to a visitor. Netlify's docs include Serverless, Scheduled and Background Functions, Preview Servers, Agent Runners and Database compute; Edge Functions use the web-request meter rather than the compute meter. Compute definitions and scope

This is why a dynamic app needs a fuller estimate than a static marketing site. Rendering a page on the server can spend compute credits as well as traffic credits. Caching a result can avoid repeating runtime work; serving the cached content still produces delivery and request usage.

Preview deployment is free; preview usage still counts

Deploy Previews and branch deploys use no deployment credits. Failed deploys and rollbacks to an earlier production deploy also do not consume deployment credits. Build minutes are no longer a separate billing meter on credit-based plans. Deployment rules

A preview's visitors can still generate web requests and delivered data, and a running Preview Server uses compute. “Unlimited previews” describes the deployment allowance; include preview activity when you estimate the team's usage.

Netlify Forms Pricing

Netlify Forms, the hosted service for collecting submissions from site forms, is free and unlimited on credit-based plans. There is no separate submission charge. The page and files around a form still belong to your site's ordinary traffic budget, and a paused site cannot keep serving that experience. Forms billing

For a marketing site, using Forms removes the need to budget a separate per-submission package. It does not remove the need to budget hosting.

AI usage can compete with hosting usage

Netlify's docs price AI inference at 180 credits per $1 of model usage through Agent Runners and AI Gateway. Inference means the model processing a request and generating a response. An agent run can also use compute. AI credit rules

The pricing page links model-specific rates. Keep those separate from function hosting estimates: an app API request is not automatically an AI request, and a function calling an independently billed provider can have that provider's own bill. The examples below assume no AI-model usage.

Netlify Hosting Pricing: Three Monthly Budgets

The three assumed workloads cost $0, $14 and $20 per month on their recommended plans. Every conversion rate and plan price comes from Netlify's current pricing page. The traffic and release quantities are illustrative inputs you can replace with your own usage.

For hosting, the calculation is:

Monthly credits = production deploys × 15 + compute GB-hours × 10 + delivered GB × 20 + web requests ÷ 10,000 × 2.

Each example starts a fresh billing cycle with no previously purchased or rollover credits. It assumes no separately billed domains, extra build capacity, extra Preview Servers, external services or additional AI, agent and database activity. The paid examples assume sufficient top-ups are authorized to serve the whole workload.

A marketing site: 240 credits, $0 on Free

Assume a static marketing site makes 8 production releases, delivers 5 GB and serves 100,000 requests during the month. It uses no function compute.

The releases consume 8 × 15 = 120 credits. Delivery consumes 5 × 20 = 100 credits. Requests consume 100,000 ÷ 10,000 × 2 = 20 credits.

Total: 240 credits. Free bill: $0. Remaining allowance: 60 credits.

This is a sensible Free workload because it fits with some room left. Collecting enquiries through Netlify Forms adds no submission charge. But a campaign that increases delivery, or repeated production publishing while copy is still being reviewed, can use the remaining balance.

For this site, make preview review part of the publishing process. A copy edit does not need to become a public release until it is approved. The saving comes from fewer production releases, while preview visitors still count toward traffic usage.

A Next.js app with functions: 1,500 credits, $14 on Personal

Assume a solo developer's app makes 20 production releases, delivers 30 GB, receives 500,000 requests and uses 50 GB-hours of function compute.

Next.js is a framework for building React websites and apps. Netlify's adapter provisions a serverless Function for server rendering, API routes and other server work. The adapter also supports edge caching, so the compute needed depends on how much work reaches a function. Next.js on Netlify

The monthly ledger is 300 deployment credits + 600 delivery credits + 100 request credits + 500 compute credits = 1,500 credits.

Personal supplies the first 1,000. One 500-credit recharge costs $5.

Total bill: $9 + $5 = $14. Base Pro would cost $20.

Personal wins for this assumed solo workload. Pro wins earlier if another developer needs full access or you need an organization-owned private repository.

The 500,000 requests include the app's total web requests, including function requests. Counting those function requests again as a second traffic quantity would inflate the estimate. Their runtime is already accounted for separately in the assumed 50 GB-hours.

An agency with 10 client sites: 1,100 credits, $20 on Pro

Assume the agency keeps 10 static client sites on one team. Each site makes 4 production releases, delivers 2 GB and serves 50,000 requests per month, with no function compute.

Together they make 40 releases, deliver 20 GB and serve 500,000 requests:

600 deployment credits + 400 delivery credits + 100 request credits = 1,100 credits.

Base Pro bill: $20/month, or $2 per client if you allocate it evenly. Pro includes unlimited members, so colleagues can work on the shared team without multiplying the subscription by the site count.

A genuinely solo agency could cover this usage on Personal for $14. Choose Pro when collaborators need full access; client feedback alone can use free reviewer roles.

Now increase publishing while keeping traffic unchanged. At 12 releases per site, the agency consumes 2,300 credits. Pro still costs $20; Personal would cost $24 after three $5 packs.

At 30 releases per site, the agency consumes 5,000 credits. The 5,000-credit Pro tier costs $33/month, or $3.30 per client on an even allocation. Base Pro plus two $10 recharge packs would cost $40.

The per-client amount is an accounting allocation, not a Netlify per-site license. The practical limitation is pooled usage: a busy client can consume credits needed by the other sites. Shared project allowance

When Pro Becomes Cheaper Than Personal

For a fresh month without banked credits, base Pro first beats Personal on price above 2,000 credits. The difference comes from the size of the recharge packs.

Personal at 2,000 credits costs $9 + two $5 packs = $19. Above that, another 500-credit pack takes the bill to $24. Pro covers up to 3,000 credits for $20. At 3,000 credits, Personal costs $29. These are calculations from the published plan and recharge prices.

That gives a useful decision rule: remain on Personal when your solo workload regularly fits below the crossover; choose Pro when sustained usage passes it or collaboration features already justify the price.

Extra production releases also have a useful cost equivalent. Personal's recharge rate is $0.01 per credit, so a 15-credit release consumes $0.15 worth of extra credits. Pro's $10-per-1,500 rate makes that $0.10.

At those same marginal rates, a compute GB-hour consumes $0.10 worth of Personal credits or about $0.067 on Pro. A delivered GB consumes $0.20 or about $0.133, respectively. These equivalents help you identify an expensive habit, but the invoice buys whole credit packs rather than individual releases or gigabytes.

Higher Pro tiers have their own crossover. Base Pro plus one recharge costs $30 and supplies 4,500 credits. Above 4,500, another recharge takes the fresh-month bill to $40. If your predictable workload fits within 5,000, the $33 tier is then $7 cheaper and also qualifies for monthly-credit rollover.

Rollover or previously purchased credits can change a particular month's cash payment. Use the comparison for choosing a steady plan, then inspect your actual balance before buying anything.

What Adds to the Bill or Pauses a Site

Auto recharge decides whether exhausted credits lead to another purchase or a pause. It is turned off by default, applies to the whole team, and can only be enabled or disabled by a Team Owner. You cannot enable it for just one project in that team. Recharge rules

When the shared balance runs out, the affected projects stop serving visitors. Keeping recharge off controls spending at the cost of availability when the allowance is exhausted. Enabling it lets eligible paid plans replenish their balance in the published increments.

For an agency, make that policy a business decision. Put a person in charge of the shared balance and decide how client usage is allocated. Where clients require independent budgets and outage boundaries, consider separate teams and account for each team's plan.

Monthly credits and purchased credits expire differently

Free, Personal and base Pro monthly allowances reset each billing cycle without rollover. On Pro tiers with at least 5,000 monthly credits, unused plan credits roll into one additional cycle, then expire. Keeping the same tier matters. Purchased credit packs and remaining auto-recharge credits have no set expiry. Credit lifecycle

Buying a larger monthly tier solely to accumulate an indefinite reserve will not work. Rollover helps with an uneven following month; purchased credits serve a different purpose.

Plan changes can move your billing date

Increasing a Pro credit tier takes effect immediately and resets the billing cycle, with a prorated refund for the previous plan. A downgrade takes effect at the end of the current cycle. Changing the tier removes unused monthly and rollover credits when it takes effect, while purchased extra credits remain. Plan-change rules

For a launch, schedule the decision around expected usage and the existing renewal date. The steady monthly prices above are easier to compare than a mid-cycle invoice containing proration.

Capacity add-ons and domain purchases sit outside the examples

The pricing page lists an additional concurrent build at $40/month and additional Preview Servers at $15/month on eligible paid plans. Concurrent builds buy the ability to build simultaneously; they are separate from production deployment credits.

Connecting a custom domain with SSL is included, while buying and renewing the domain is a separate purchase. Applicable taxes also affect the invoice. An independently billed database, email service or AI provider adds its own cost to the application budget.

Netlify Against Vercel and Cloudflare

Netlify is attractive when several developers need full access to a modest shared workload. Vercel Pro starts at $20/month, with full developer seats priced at $20 each: three developer seats create a $60 subscription floor, against Netlify base Pro's $20 with unlimited members.

Cloudflare Workers Paid starts at $5/month per account, with usage charges beyond its included allowances. It is worth pricing for a small app, and its static-asset requests are free. These are subscription floors; differing runtime meters and included usage determine the total bill. Cloudflare Workers pricing

For the platform decision beyond this bill, read Vercel vs Netlify. Choose from the workflow you need and the usage you can measure.

Set a Hosting Budget Before the Next Release

Use the team's actual consumption to set a plan and a recharge policy before publishing a busy release. A credit budget is easier to manage when releases and runtime have a named owner.

1. 1

   Inventory the whole team's usage

   Read usage from the Netlify team dashboard. Record production deploys, delivered GB, web requests and compute GB-hours, then include preview activity and any AI usage. For an agency, identify which clients share the allowance.

2. 2

   Choose the plan from usage and access

   Apply the credit formula to your monthly estimate. Use Free with headroom, Personal for a solo workload below its price crossover, or Pro for collaborators and higher sustained usage. Team Owners change plans and Pro tiers under Usage & billing > Plan details.

3. 3

   Set the behavior when credits run out

   Review the team's auto-recharge setting. Leave it off when pausing is acceptable to protect the budget, or authorize top-ups when continuity matters and assign someone to watch consumption. Revisit the estimate after the next complete billing cycle.

Netlify Pricing FAQ

How much does Netlify cost?

Free costs $0, Personal costs $9/month, and base Pro costs $20/month. Pro credit tiers rise to $33, $63, $95 and $126. Personal top-ups cost $5 per 500 credits; Pro top-ups cost $10 per 1,500. Enterprise is custom. Current prices

Is Netlify 100% free?

The Free plan is free, with a hard 300-credit monthly limit that cannot incur charges. Using up the shared balance pauses projects until the next cycle or an upgrade. Paid subscriptions, domain purchases and optional add-ons have their own costs.

What are the downsides of using Netlify?

Production releases consume credits, preview traffic still counts, and projects on the same team compete for one allowance. Exhausting that balance can pause every site sharing it. For an agency, pooled usage is the operational limitation to plan around.

Is Netlify or github better?

If you mean hosting, compare Netlify with GitHub Pages. GitHub Pages serves static HTML, CSS and JavaScript from a repository. Netlify is the more relevant choice when you need its Functions or Forms alongside deployments.

Is Netlify hosting free forever?

Netlify advertises Free as $0 forever. Keeping hosting active requires staying within the monthly credit allowance; running out pauses sites. An ongoing free plan does not provide unlimited usage. Free plan and limits

Is there an alternative to Netlify?

Yes. Vercel and Cloudflare are both worth comparing. Vercel Pro starts at $20/month with paid developer seats, while Cloudflare Workers Paid has a $5 monthly account minimum. Compare the workload and workflow, since subscription prices alone do not determine the total.

What big companies use Netlify?

Netlify's customer examples include Peloton and Nike, including a Nike campaign built by Matter Supply. Those examples establish use, not a budget for your site.

Which is better for free, Vercel or Netlify?

For a personal project, compare your runtime and usage needs. Vercel's Hobby plan is limited to personal, non-commercial use. Netlify Free's defining pricing condition is its shared 300-credit hard limit, so check both eligibility and capacity before choosing.

Is WordPress better than Netlify?

WordPress.com suits someone buying managed WordPress hosting for a content-led site. Netlify suits a developer deploying a site or app and budgeting its hosting resources. Choose the publishing workflow first, then compare the required plans.

Is Netlify Free Forever?

Free is an ongoing plan, rather than a timed paid-plan trial. Its monthly allowance renews, but unused Free monthly credits do not accumulate. If a quiet project's usage keeps fitting, there is no usage-driven reason to upgrade.

Does Netlify Offer a Student Discount?

The live pricing page does not advertise a general student discount. It lists Free and an Open Source plan for qualifying projects, with generous credits and free production deploys. Student status alone is not a published discounted price on that page. Netlify pricing FAQ

Can I Get a Refund if I Cancel Netlify?

The self-serve subscription agreement says early cancellation does not refund the unused subscription term, and access continues through the paid term. Documented prorated refunds when upgrading a plan are a separate billing adjustment.

When Did Netlify Pricing Change?

New accounts have used credit pricing since September 4, 2025; older accounts can keep legacy plans. On April 14, 2026, credit-based Pro moved to unlimited seats and Forms became free. On July 14, 2026, selectable Pro credit tiers and higher-tier rollover arrived.

Get the AI Business Workflow Audit Checklist

Map the hosting, data, access and recurring costs your business workflow needs before choosing a stack.