Netlify Legacy plans are the Free, Starter and Pro pricing plans, and the earlier Enterprise arrangements, held by Netlify accounts created before September 4, 2025. Netlify explains: “If you’ve created your Netlify account with a Free, Starter, or Pro plan before September 4, 2025, then your pricing plan is now considered a Legacy pricing plan. There is no action required for you.”[2] The pricing page makes the same point to existing customers: they can keep their current plan.[3] Legacy plans matter to software asset managers because a single organisation may hold teams on both plan generations, with different metrics, seat rules and AI feature access.
Editions
The documented Legacy plans are compared below.[1]
| Feature | Free and Starter | Pro (Legacy) | Enterprise |
|---|---|---|---|
| Members | 1 free member; free Git Contributors | $19 per month per member, including active Git Contributors | Custom |
| Bandwidth | 100 GB per month (Free hard limit; Starter $55 per 100 GB over) | 1 TB per month, then $55 per 100 GB | Custom |
| Build minutes | 300 per month (Free hard limit; Starter $7 per 500 over) | 25,000 per month, then $7 per 500 | Custom |
| Serverless Functions | 125,000 invocations per site per month | 125,000 per site per month | Custom |
| Edge Functions | 1 million invocations per month | 2 million per month, then $2 per million | Custom |
| Form submissions | 100 per site per month | 100 per site per month, then $19 and up | Custom |
| Concurrent builds | 1 | 3, then $40 each | Custom |
| Web Analytics | $9 per site per month add-on | $9 per site per month add-on | Included |
| Maximum sites | 500 | 500 | Unlimited |
| Preview Servers | Not available | Included, then $15 each | Included |
| SLA | None | None | 99.99% |
Catalog: Legacy Pro plan; Legacy bandwidth; Legacy build minute; Legacy pricing plans; Earlier Free, Starter and Pro accounts are Legacy plans.
Other differences in the table include log retention (functions logs 7-day history on Legacy Pro and full history on Enterprise), Real User Monitoring (7-day on Legacy Pro), audit log history (7-day on Legacy Pro, full on Enterprise), and SSO, SCIM, log drains and organization management available only to Enterprise.[1]
Metrics
Bandwidth
Netlify tracks outgoing bandwidth at the team level. Each team plan includes a monthly allotment, and usage above it is charged in extra usage packages.[4] Metered usage covers all outgoing data on the team’s sites, including pages, files and responses served on production sites, branch deploys or Deploy Previews, and outgoing data in proxied API requests including requests to Netlify Functions.[4] Bandwidth metering excludes data transferred as part of a site build or deploy, and form submissions or other incoming data.[4] Catalog: Legacy bandwidth.
Build minutes
Legacy plans meter build minutes, with allowances of 300 on Free and Starter and 25,000 on Pro.[1] Build minutes are not a separate metric on credit-based plans; a credit-based team pays 15 credits per production deploy instead, and extra concurrent builds remain an add-on at $40.[5] Catalog: Legacy build minute; Build minutes are not metered on credit plans.
Members
The Team Owner is billed on the number of active members, the plan’s member limit and usage; Reviewers are not charged.[4] Team Owners and Developers are paid roles on Legacy plans, and Git Contributors are billed if they triggered a deploy during the billing period.[6][4] Legacy Pro charges $19 per member per month.[5] Catalog: Legacy Pro bills $19 per team member; Team Owners are paid members on Legacy plans; Legacy plans bill only active Git Contributors.
Counting and floors
How Legacy billing is timed
The Legacy billing FAQ lists three payment patterns.[4]
| Pattern | Applies to | Detail |
|---|---|---|
| Charged annually | Domain registrations | Charged immediately on purchase or renewal |
| Charged monthly, in advance | Team plans, team member seats, extra concurrent builds, Web Analytics | Combined payment on the billing date; first-month fees prorated by days remaining |
| Charged once per purchase | Extra usage packages for bandwidth, build minutes and edge functions, and project add-ons | Applied to a running balance and paid at the end of the billing cycle; not prorated |
For teams not linked to an organization, billing runs on a monthly cycle starting on the day the team was created.[4] Team plan, extra capacity and add-on level fees are prorated by days when a plan changes or when a member seat or concurrent build is added or removed. Extra usage packages are neither prorated nor carried to the next billing cycle.[4] A downgrade of a metered add-on level is not possible if current usage is above the lower level’s limits, and usage-triggered upgrades persist at the higher level at the start of the next cycle.[4]
Organization usage
Organization Owners on Enterprise can check bandwidth and build minute usage across linked teams. Each team has its own allocation, and any usage above the allotment is charged at the organization level and invoiced monthly with a breakdown by team.[4]
The self-serve agreement states the contractual basis: if usage exceeds the capacity of the selected Paid Plan, “Customer will incur and agrees to pay additional fees that reflect actual usage”, and fee changes apply only to new Services and to renewal terms after notice.[7]
Virtualization and partitioning
Not applicable. The team is the billing unit, and an organization on Enterprise can contain multiple teams, each with its own usage allocation.[4]
Cloud and BYOL
No bring-your-own-licence rights apply. AI features differ by plan generation: Legacy plans can use Ask Netlify AI and the “Why did it fail?” troubleshooting feature, whereas AI Gateway and Agent Runners are available only on credit-based plans.[4]
Programs
Migrating to credit-based plans
A Legacy team may switch to a credit-based plan. A Team Owner goes to Usage & billing, Plan details and chooses Change team plan.[5] Key consequences documented by Netlify:
- Irreversible. “You cannot revert to a Legacy plan from a Credit-based plan.” Projects cannot be transferred from a credit-based team to a Legacy team.[1][5] Catalog: Switching to credit-based plans is irreversible.
- Analytics. An Analytics subscription is terminated immediately on transfer, without refund; analytics then follows the plan’s lookback period.[5]
- Functions. Function usage consumes credits based on compute (GB-hours), tracked at the team level, and “There is no longer a free tier.”[5] Catalog: Moving a project from Legacy to credit plans changes billing.
- Forms. Form usage becomes free and unlimited, with no submission limits.[5]
- Seats. Credit Pro seats are free and unlimited, and for existing credit-based Pro teams seat charges ended on the next billing cycle after April 14, 2026.[5]
- Project transfers. Projects can be transferred between teams on credit-based plans, but a feature that needs a higher plan generally must be removed or turned off first.[5]
Catalog: New accounts use credit-based plans from 2025-09-04.
Audits and compliance
For Legacy plans the practical compliance evidence is the Account usage insights dashboard, which shows projects, bandwidth, web requests, builds, compute, image transformations and members.[4] Owners and Billing Admins can see the team’s bandwidth usage and allowance, and Enterprise teams can export top bandwidth usage to CSV.[4] The agreements contain no software audit clause.
Out of scope
- Legacy plans older than the table above, which Netlify says may differ.
- Legacy Enterprise Order Form values.
- The credit-based meters, covered in Netlify credit-based plans and credit metering.
- Netlify Domains and third-party extension pricing.