Netlify Pro is now flat $20/month for unlimited team members. Bandwidth credit rate doubled. Form submissions went free. Exact math, by team size.
By Veracity Media Network · Published 2026-04-23
On April 14, 2026, Netlify made three changes to its credit-based Pro plan. Pro is now a flat $20/month for unlimited team members. Form submissions are no longer metered. Credit rates for bandwidth, compute, and web requests all moved.
For a 3-person team, the seat change alone drops the monthly bill from $60 to $20. For a 10-person team, from $200 to $20. The break-even point against Vercel's Pro platform (also $20/month, but with $20 per additional deploying seat) is now at exactly 1 paid seat.
The credit-rate changes cut the other way. Bandwidth went from 10 credits/GB to 20 credits/GB. Compute from 5 credits/GB-hour to 10. Web requests slightly improved, from 3 credits/10,000 to 2. For teams with low seat counts but high traffic, the new pricing is more expensive than the old. For teams with high seat counts and moderate traffic, it is substantially cheaper.
This is the math.
Before April 14, Netlify's credit-based Pro plan charged $20 per seat per month. A 3-person team paid $60. A 10-person team paid $200. Active Git contributors counted as seats, so teams with outside collaborators faced seat creep.
After April 14, 2026, Netlify's Credit Pro plan includes free unlimited team member seats with a monthly subscription of $20 for 3,000 credits to use across a team's projects. The change applies to Credit-based Pro plans only; Legacy Pro plans are not automatically migrated. [1]
All roles (Owner, Developer, Internal Builder, Publisher, Git Contributor, Reviewer) are included at no extra cost.
| Team size | Old monthly (Pro) | New monthly (Pro) | Change |
|---|---|---|---|
| 1 paid seat | $20 | $20 | 0 |
| 3 seats | $60 | $20 | −$40 (−67%) |
| 5 seats | $100 | $20 | −$80 (−80%) |
| 10 seats | $200 | $20 | −$180 (−90%) |
| 20 seats | $400 | $20 | −$380 (−95%) |
| 50 seats | $1,000 | $20 | −$980 (−98%) |
Netlify's stated rationale for the change is that 65% of the 40,000 people signing up for Netlify every day are new to web development, including roles adjacent to engineering such as product managers and marketers. The company framed the seat change as removing friction for onboarding whole teams. [2]
The change applies only to Pro plans on the credit-based billing model introduced in September 2025. Teams on legacy per-seat Pro plans are not automatically migrated and must opt in through Usage & Billing settings.
Vercel's Pro plan is the most common comparison point, and the Pro-tier numbers look similar at a glance. They are not.
Vercel Pro is structured as a $20/month platform fee that includes 1 deploying team seat and $20 in monthly usage credit. Additional deploying seats (Owner or Member roles) are $20/month each. Viewer seats with read-only access are unlimited and free. [3]
So a Vercel Pro team with 3 deploying members pays $20 (platform) + $40 (2 additional seats) = $60/month. A 10-member deploying team pays $20 + $180 = $200/month.
Netlify Pro at the same team sizes pays $20 flat.
| Team size | Netlify Pro | Vercel Pro | Delta |
|---|---|---|---|
| 1 deploying seat | $20 | $20 | 0 |
| 3 deploying seats | $20 | $60 | −$40 |
| 5 deploying seats | $20 | $100 | −$80 |
| 10 deploying seats | $20 | $200 | −$180 |
| 20 deploying seats | $20 | $400 | −$380 |
Both platforms offer unlimited free read-only or viewer access, so teams whose PMs and designers just need to comment on deploy previews were already at parity on that dimension before the change. The difference is strictly on people who deploy.
This compares subscription cost only. Usage-based charges for bandwidth, compute, and function execution are separate on both platforms and are covered next.
The seat change is the headline. The credit changes partly undercut the savings for traffic-heavy sites.
The authoritative rates, from Netlify's April 14 changelog:
| Meter | Previous rate | New rate | Effective change |
|---|---|---|---|
| Bandwidth | 10 credits/GB | 20 credits/GB | +100% cost in credits |
| Compute | 5 credits/GB-hour | 10 credits/GB-hour | +100% cost in credits |
| Web requests | 3 credits/10,000 | 2 credits/10,000 | −33% cost in credits |
| Form submissions | 1 credit each | Free | −100% |
Bandwidth rate doubled as seats went free
The seat change saves teams money at 3+ members. The bandwidth rate change costs teams money at any traffic volume. The two effects cross at different team sizes depending on traffic. A 1-person site with 500 GB/month of bandwidth is net worse off under the new pricing.
Pro plans include 3,000 credits/month. Under the new rates, those 3,000 credits buy:
For a typical team mix, the practical effect depends on traffic. A marketing site serving 200 GB/month of bandwidth will exhaust its Pro credits on bandwidth alone under the new rates. The same site was within the 300 GB bandwidth budget before.
Overages are billed through optional auto-recharge (off by default). Pro's auto-recharge rate is $10 per additional 1,500 credits, which is $0.13 per GB of bandwidth or $0.067 per GB-hour of compute at the new rates. For comparison, Vercel charges $0.15 per GB for bandwidth overages on Pro.
Form submissions going free is the smaller change but worth noting. These previously cost 1 credit each; on a site with 3,000 monthly form submissions, that's equivalent to all of the Pro plan's compute budget going to form processing alone. That cost is now gone.
This is the math; readers can map their own team against it.
Beneficiaries with material savings:
Net worse under the new pricing:
Unchanged:
One question that drives significant search traffic is what the Free plan actually covers after these changes.
Netlify's Free plan includes 300 credits/month as a hard limit (billing stops, site pauses, no charges incur), 1 team owner seat, unlimited Git contributors on public repositories, unlimited deploy previews and branch deploys, Agent Runners and AI Gateway access, custom domains with free SSL via Let's Encrypt, serverless and Edge Functions, and as of April 14 2026, unlimited free form submissions. [4]
Under the new credit rates, the 300 credits buy roughly:
For a personal site, a prototype, or a small SaaS landing page, this is adequate. For anything with meaningful visitor traffic, the bandwidth budget is the constraint. A site that gets 1,000 daily pageviews, each loading 500 KB of assets, burns through 15 GB in a month. The site will pause, not incur a charge.
Worth naming for completeness, because some reporting has treated the April 14 changes as broader than they are: