Technology reviews & practical guides
Netlify review for October 2026: Free, Personal and Pro credit pricing, what one credit buys, the Free plan pause, Pro tiers to $126, limits and legacy plans.

Netlify made Git-based frontend hosting mainstream, and in 2026 it still offers one of the easiest paths from a repository to a live site. Its pricing, however, has been rebuilt around monthly credits and then revised three more times in under a year, so many guides online quote numbers that no longer apply.
This review covers what Netlify costs in October 2026, what a credit actually pays for, what happens when credits run out, the technical limits that matter, and whether a legacy account should switch.
Netlify is still one of the smoothest ways to put a frontend project on the web: connect a Git repository, let it detect the framework, and every push becomes a deploy with a preview URL. What has changed is the bill. Since September 2025 every paid feature draws from a single monthly pool of credits, and the rates behind those credits have been rewritten several times since.
All figures in this review come from Netlify's pricing page, docs and changelog as they read in October 2026. Netlify's own September 2025 launch blog still quotes Pro at 5,000 credits, which is no longer true.
At its core Netlify builds your project from GitHub, GitLab or Bitbucket and serves it from its CDN. You can also deploy without Git by dragging a folder onto the dashboard or using the Netlify CLI. Netlify says it automatically detects and configures your project, and it publishes setup guides for Angular, Astro, Eleventy, Express, Gatsby, Hugo, Hydrogen, Next.js, Nuxt, React Router, Remix, SolidStart, SvelteKit, TanStack Start, Vite and Vue.
Next.js is handled through the open-source OpenNext adapter. Netlify states that it supports all major Next.js features with zero configuration from version 13.5 onward; versions 10 to 13.4 run on a legacy runtime that only receives maintenance.

One recent default worth knowing: since July 28, 2026, new Free, Personal and Pro teams get projects that are private by default.
Every credit-based plan includes a monthly credit allowance. Production deploys, bandwidth, web requests, compute and AI inference all draw from it. Here is what each plan costs in October 2026.
Since July 14, 2026, Pro is sold in five credit tiers. Only the tiers from 5,000 credits upward let unused credits roll over.
The per-credit price barely moves across tiers: about $0.0067 per credit at 3,000 and about $0.0063 at 10,000 or 20,000. The real reason to move up is rollover, not a bulk discount. Rolled-over credits expire at the end of the billing cycle they roll into, so they buffer one busy month rather than accumulating.

We found no annual billing option or annual discount on Netlify's pricing page or billing docs. Treat all plans as month to month.
These are Netlify's published credit rates as of October 2026:
Build minutes are no longer a separate metric on credit plans. You pay per production deploy instead, no matter how long the build runs.

The figures below are our own arithmetic from the published rates, assuming the whole allowance goes to one meter.
Real sites mix all of these. A Pro project with 40 production deploys (600 credits), 80 GB of bandwidth (1,600 credits), 3 million web requests (600 credits) and 20 GB-hours of function compute (200 credits) uses exactly 3,000 credits. Bandwidth is the line that dominates for most sites, so compress images and cache aggressively before you upgrade.
Netlify has changed its pricing four times in about 13 months. If a guide you are reading quotes any of the earlier figures, it is out of date.
The net effect: teams pay less, but traffic and compute cost twice what they did at launch. A small team running a modest site is better off today; a solo developer with a high-traffic site is worse off.
This is the part of Netlify's pricing to understand before you rely on it. Netlify's pricing page states that when a site reaches its monthly usage limits it enters a paused state until the start of the next billing cycle, and that if one project exceeds its limits, all projects on your account will be paused.
If you host several hobby projects on one Free account, a traffic spike on any of them pauses all of them. Keep anything that must stay online on a paid plan, or on a separate account.
Paid plans get extra credits only through auto recharge, which is off by default and can only be enabled by a Team Owner. Personal recharges at $5 per 500 credits and Pro at $10 per 1,500 credits. Credit packs at the same prices can also be bought manually. Credits bought through auto recharge or packs do not expire.
At Pro's recharge rate an extra GB of bandwidth works out to roughly $0.13, and on Personal roughly $0.20. That is our arithmetic from the published prices.

Netlify's position is simple: the Free plan has hard monthly limits that cannot be exceeded or incur any costs, and on paid plans keeping auto recharge off works as the spend cap. There is a separate AI credit usage limit for Agent Runners. The trade-off is that a cap means downtime: with auto recharge off, hitting the limit pauses your sites instead of billing you.

Observability history is the one area where Netlify contradicts itself. The pricing page, the Pro plan card and a December 2025 changelog entry give different retention windows per plan, so check your own dashboard rather than relying on a single number.
Netlify's self-serve subscription agreement also says the Free tier runs on a common build environment with no service level commitments, and that Netlify may shut down Free projects without notice. That document is dated 2020, but it is the one linked from the pricing page.
If you created a Netlify account on a Free, Starter or Pro plan before September 4, 2025, you are on a legacy plan. Netlify says no action is required, and legacy plans keep their old limits: 100 GB of bandwidth and 300 build minutes on Free and Starter, and 1 TB of bandwidth (then $55 per 100 GB) and 25,000 build minutes (then $7 per 500) on legacy Pro, where seats cost $19 per member per month.
Our view: a legacy Pro team with several members and moderate traffic will usually save money by switching, because seats are now free. A one-person legacy account serving hundreds of GB a month should stay put, since the same bandwidth on credits would cost far more.
If you are weighing Netlify against Vercel, read our Vercel review alongside this one: both now meter usage, but they draw the line between included and paid usage differently.
Free is $0 with 300 credits, Personal is $9 per month with 1,000 credits, and Pro starts at $20 per month with 3,000 credits and unlimited members. Pro tiers go up to $126 per month for 20,000 credits, and Enterprise is priced on request.
Every project on the account is paused until the next billing cycle. Visitors see a Site not available page and deploys stop. Free cannot buy extra credits, so the only options are upgrading or waiting.
Only on Pro tiers with 5,000 or more monthly credits, and rolled-over credits expire at the end of the next cycle. Credits bought through auto recharge or credit packs do not expire.
No, not on credit-based Pro. Since April 14, 2026, Pro has charged for no seats. Free and Personal allow only one member, and legacy Pro still bills $19 per member.
Generally no. The subscription agreement says fees are non-cancelable and non-refundable, and the terms of use say credits have no cash value and are forfeited if the account is closed. The documented exception is a prorated refund of the previous plan when you upgrade between Pro tiers. Downgrades take effect at renewal.
Not as a separate metric on credit plans. Each production deploy costs 15 credits regardless of build length, while deploy previews, branch deploys, failed deploys and rollbacks are free.
Yes. Next.js 13.5 and later runs with zero configuration through the open-source OpenNext adapter, with all major features supported. Versions 10 to 13.4 run on a legacy runtime that only gets maintenance fixes.
Only after you check your bandwidth. The switch cannot be undone and cancels any Analytics subscription without refund. Teams with several members usually save money; solo accounts with heavy traffic usually pay more.
Self-serve plans accept credit cards, Apple Pay and Google Pay. ACH and wire transfer are reserved for Enterprise.
More in Cloud Computing
Browse Cloud ComputingSeats used to be the expensive part of Pro. Before April 14, 2026, credit-based Pro charged $20 per seat, including active Git contributors. Netlify now states that credit-based Pro plans no longer charge for any seat, which makes Pro far cheaper for teams. Free and Personal still cannot add team member seats.
For comparison, the legacy Pro plan included 1 TB of bandwidth. On today's rates 1 TB alone would cost 20,000 credits, the size of the top $126 Pro tier. Image-heavy or download-heavy sites should do this math before moving off a legacy plan.
Function memory matters too. The default allocation is 1024 MB; credit-based Pro and Enterprise can raise it to 4096 MB, and the GB-hour cost rises in proportion, so a function at 4 GB costs four times as much per second of runtime.
Two caveats from Netlify's community forum, which are user reports and statements rather than written policy. Between July and September 2026 several users reported projects paused despite credits remaining, which they tied to a credit migration issue. And in October 2024 a Netlify representative wrote that charges related to DDoS attacks are waived. Neither appears in Netlify's billing docs.