---
title: "Netlify pricing in 2026: Free, Personal, Pro and credits explained"
url: https://while.sh/en/comparisons/netlify-pricing/
author: "Grégoire Mougeolle, co-founder of Nextmap"
updated: 2026-11-18
---

# Netlify pricing in 2026, explained: credits, plans and the pause

Netlify replaced its meters with a single currency, credits, and no longer charges per person on Pro. It is simpler, as long as you know what a publish consumes and what happens when the credit runs out. We read its pricing page and documentation.

Netlify cleaned up its pricing. No more separate meters for bandwidth, functions and build minutes: **everything is paid in credits**, and the Pro plan **no longer charges per person**. It is easier to read, with two conditions: knowing what each use consumes, and knowing what happens when the month's credit runs out.

> **The short version.** Free gives 300 credits per month, Personal 1,000 for $9, Pro 3,000 for $20 with the whole team. A production publish costs 15 credits, a GB of transfer 20. When the credit runs out, projects are paused until the next month. For a modest team tool, Pro at $20 is often enough.

## Netlify's plans at a glance

| | Free | Personal | Pro | Enterprise |
|---|---|---|---|---|
| Price per month | $0 | $9 | From $20 | Custom |
| Credits per month | 300, hard limit | 1,000 | 3,000, up to 20,000 depending on tier | Custom |
| Extra credits | No | 500 for $5 | 1,500 for $10 | Custom |
| People | 1 | 1 | Unlimited, no paid seats | Custom |
| Password protection | No | No | Yes | Yes |
| Company single sign-on (SAML) | No | No | No | Yes |
| Activity history | No | No | 7 days | Full |

Prices are in US dollars, as shown on Netlify's page (sources 1 and 3).

## What each use consumes

Everything is counted in the same currency. Here is what each use costs in credits (source 2).

| Use | Credits |
|---|---|
| One production publish | 15 |
| One GB of transfer to visitors | 20 |
| One hour of compute with 1 GB of memory | 10 |
| 10,000 requests | 2 |
| One dollar of AI usage | 180 |

**Test versions** are free, and a failed publish or a rollback to a previous version uses nothing (source 2). Monthly credits reset each month, except on Pro tiers of 5,000 credits and more, where the remainder rolls over for one month (source 3).

## The math for a team tool

Take an internal tool published about forty times in the month, with 20 GB of transfer, 500,000 requests and 50 GB-hours of compute for its functions (source 2).

| The month's usage | Credits |
|---|---|
| 40 production publishes | 600 |
| 20 GB of transfer | 400 |
| 500,000 requests | 100 |
| 50 GB-hours of compute | 500 |
| **Total** | **1,600** |

The tool fits within **Pro's 3,000 credits**, at $20 per month, for the whole team. It would go over Personal's 1,000, which only allows one person anyway (source 1).

<figure class="illus"><img src="/illustrations/prix-netlify-credits-1200.webp" srcset="/illustrations/prix-netlify-credits-768.webp 768w, /illustrations/prix-netlify-credits-1200.webp 1200w" sizes="(min-width: 48rem) 46rem, 100vw" width="1536" height="1024" loading="lazy" decoding="async" alt="Netlify credits: each publish, each GB of transfer and each request draws from a single monthly pool, and projects pause when it is empty, next to while where a tool open to everyone is never cut off" /><figcaption>A single pool of credits, and a pause when it is empty.</figcaption></figure>

## When the credit runs out: the pause

This is the point to know before you choose. When a project hits the month's limit, it is **paused until the start of the next cycle**. Netlify warns you by email at 50%, 75% and 100%, and **one project going over pauses all projects on the account** (source 1).

On paid plans, **auto recharge** buys credits in small increments. It is **off by default**, and only team owners can turn it on (source 1). It is good protection against bill surprises, as long as you accept the pause.

## People and protection

Since April 14, **the credit-based Pro plan charges for no seats**, and reviewer roles are free on every plan. Free and Personal remain limited to one person (source 1).

**Password protection** comes with Pro. Team login with each person's own Netlify account and **company single sign-on through SAML** require Enterprise, on quote. New projects are private by default until you publish them (source 1).

## The same tool on while

**We built while for the team tool**, the one your AI builds in a few minutes and the whole company then uses. The price does not count people: **the Pro plan covers the whole team**, and everyone signs in with their email account, Google or Microsoft, with no plan on quote.

> You, to your AI: Take the repository of our field service tracker, put it on while with its data, keep it for the team and prepare a link for the client.

- **Each project has its budget**, with an alert at 80% and at 100%, and **a tool open to everyone is never cut off**.
- **A client** uses the tool with [an access link and a password](/en/guides/share-app-with-password/), valid for 1, 7 or 30 days.
- **The data** is backed up every day, and your tools are hosted in France by Nextmap. [while's pricing](/en/pricing/) fits on one page.

To compare in detail, read [Netlify or while](/en/comparisons/while-vs-netlify/), [Vercel vs Netlify](/en/comparisons/vercel-vs-netlify/) and [Vercel pricing](/en/comparisons/vercel-pricing/).

## Which Netlify plan to choose

**Choose while if:**

- Your colleagues must sign in with their email account, with no plan on quote.
- A tool must never be paused, and your data must stay in France.

**Stay on Free if:**

- The project is personal, and a pause at the end of the month bothers no one.

**Choose Personal if:**

- You work alone, and your projects go over 300 credits per month.

**Choose Pro if:**

- A team publishes sites or tools, with a password to protect them.

To try while, give this message to your AI. The trial is **free, with no sign-up**, and your tool has its address **in 3 minutes**.

```text titre="The message to give your AI"
Read while.sh/agents and help me get started with while.
```

## How we checked these prices

On November 18, 2026, we read Netlify's pricing page and its documentation on credits and plans, cited as sources. The credits in the example are our calculations from these rates. Netlify sometimes changes its plans: we update this page when they change.

## Sources

1. [Netlify, Pricing](https://www.netlify.com/pricing/), 2026-11-18
2. [Netlify, How credits work](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/), 2026-11-18
3. [Netlify, Credit-based pricing plans](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/), 2026-11-18

## Questions

### How much does Netlify cost per month?

Free costs nothing with 300 credits per month. Personal costs $9 for 1,000 credits and one person. Pro costs $20 for 3,000 credits and the whole team, with tiers up to 20,000 credits. Enterprise is custom (sources 1 and 3).

### How many credits does a publish use on Netlify?

15 credits per production publish. Test versions are free, and a failed publish or a rollback to a previous version uses nothing (source 2).

### What happens when the credit runs out?

The project is paused until the next cycle, and one project going over pauses all projects on the account. Netlify warns you at 50%, 75% and 100%. On paid plans, auto recharge is off by default (source 1).

### Does Netlify charge for each person on the team?

Not on Pro anymore: since April 14, the credit-based Pro plan charges for no seats. Free and Personal are limited to one person (source 1).

### Can you protect a project with a password on Netlify?

Yes, from the Pro plan. Team login with each person's own account and company single sign-on (SAML) require Enterprise (source 1).

### How much does a team tool cost on Netlify?

Often $20 per month. Published 40 times, with 20 GB of transfer, 500,000 requests and 50 GB-hours of compute, it uses about 1,600 credits, within Pro's 3,000 (sources 1 and 2).
