Netlify Free 300 credits: when indies should buy Personal

After an indie drops a marketing or docs site on Netlify, the search quickly becomes how many free credits you get each month, how much a production deploy costs, and how bandwidth is metered. This page does not re-teach Netlify Forms and does not reopen Netlify versus Vercel. It freezes the Free 300-credit wall and when to consider Personal at $9/month or Pro at $20/month using netlify.com/pricing as of 2026-10-01. Re-open the page before you pay; metering can change.

How to read Free and credit units

Pricing labels Free as $0 forever with a 300 credit limit per month. The same page explains example usage costs: production deploys at 15 credits each, compute at 10 credits per GB-hour, bandwidth at 20 credits per GB, and web requests at 2 credits per 10k. Substituting your own release cadence into those units is closer to a real bill than reading “deploy free forever.” Free is also limited to one free member, while Git contributors on public repos can remain free and unlimited—usually fine for solo work, early pain for a second Netlify seat.

Three hundred credits are not abstract points. Multiple weekly production deploys at 15 credits each can consume most of the month before traffic; real visitors then add bandwidth and request burn. On new credit-based accounts, projects may start private until you follow the live docs to make them public—operate from today’s docs, not old tutorials.

What Personal and Pro each unlock

Personal is $9/month, described as everything in Free plus 1,000 credits/month, smart secret detection, 1-day observability, and priority email support. For most indies this is the first paid door: credits jump from 300 to 1,000 with more serious observability and support. Pro is $20/month with unlimited members, private organization repos, shared env variables, 3+ concurrent builds, 30-day analytics, and credit tiers starting at 3,000/month. If your pain is seats and concurrency, evaluate Pro; if the pain is solo credit headroom, Personal usually fits better.

Do not treat Pro’s professional optics as the default upgrade. Ask whether the blocker is credits, members, or concurrency/private-org features. When only credits hurt, prefer Personal.

How to spend 300 credits without drama

Treat production deploys as budgeted events. Prefer preview deploys for doc tweaks; batch production publishes. Put heavy images and downloads on purpose-built object storage or a cheaper CDN path so site bandwidth is not a file locker. Keep builds cacheable and incremental to reduce compute credits. Review the usage panel weekly: deploys, bandwidth, or requests—which line dominates.

If you host many toy sites, merge or retire cold projects. Free fits validation and light sites; burst campaign pages may belong on a plan or host chosen for spikes. Track credits per typical release for two weeks so you have your own baseline instead of deciding from someone else’s screenshot.

When to buy Personal or Pro

Buy Personal if for two consecutive weeks 300 credits still tip after preview batching and asset offload, or you need the card’s secret detection / shorter observability window to debug. Look at Pro if you need additional Netlify member seats, private org repos, shared env vars, or higher concurrency, and credit need clearly exceeds Personal’s 1,000. You can also upgrade before a commercial campaign and treat credits as campaign budget instead of firefighting mid-event.

Stay on Free if previews dominate, production publishes are few per week, bandwidth is docs-scale, and one member is enough. In week one after paying, reconcile the invoice shape against expectations and delete useless automatic production deploys. Re-check Personal $9 and Pro $20 plus the Pro credit tier you actually select.

Keep this separate from Forms and host comparisons

Toolvori already covers Netlify Forms and Vercel versus Netlify. Those answer form workflows and host choice. This tutorial answers credit quotas only. Pin 300/1000 and unit costs in your ops handbook with a date. When someone says “Netlify free is always enough,” ask monthly production deploy count and bandwidth before accepting forever-free slogans.

Write upgrade triggers as a checklist: credits block mainline publishes, cleanup discipline is exhausted, and Personal or Pro maps to the exact blocker (credits versus seats/concurrency). Wire usage review into Friday ops so the subscription does not become shelfware.