Wondering how to get started with Netlify for beginners in 2026? The short answer: create a free account, connect a Git repository, and publish your first site in about ten minutes — the free plan costs nothing, forever. The big update: Netlify replaced its old bandwidth and build-minute limits with a shared 300-credit monthly pool in late 2025, so most older tutorials are now outdated. For a beginner, the free tier is genuinely usable: it’s the easiest way to publish a personal site, and the credit model is predictable once you understand it.
How This Guide Was Built
This guide is based on Netlify’s official pricing page and the official Netlify documentation, cross-checked against community reports. We verified the current free tier, signup flow, deployment steps, and platform availability. This review is based on official documentation, pricing pages, and community reports — we did not run the tool hands-on. Last verified: August 2026.
How do I get started with Netlify for beginners?
Sign up at app.netlify.com/signup with GitHub or Google, click Add new project, Import an existing project, pick GitHub, GitLab, Bitbucket, or Azure DevOps, and authorize access. Netlify auto-detects your publish settings, so you hit Publish and your site goes live at YOUR-PROJECT-NAME.netlify.app — all free, per the official quickstart guide. Every git push redeploys. Compare the Netlify free tier first.
How Netlify’s credit system works
Netlify’s free plan gives you 300 credits per month as a hard limit, per Netlify’s official pricing page. Production deploys cost 15 credits each, bandwidth 20 credits per GB, web requests 2 credits per 10,000, and compute 10 credits per GB-hour, per the official credits documentation. Deploy Previews cost zero credits; credits reset without rolling over, per the billing FAQ.
What the Netlify free plan includes
The free plan bundles 300 monthly credits with unlimited forms, unlimited Deploy Previews, and 500 projects, per Netlify’s official pricing page. Identity and custom domains with SSL are included, and web analytics offers 1-day retention. The table below shows the full breakdown from the credit-based pricing plans documentation.
| Limit | Free plan (Aug 2026) | Source |
|---|---|---|
| Price | $0/month forever; 300 credits/month hard limit; no top-up; never billed | Netlify pricing |
| Monthly credits | 300; reset each cycle; no rollover on Free | how credits work |
| Bandwidth | 20 credits per GB | how credits work |
| Web requests | 2 credits per 10,000 | how credits work |
| Production deploys | 15 credits each; failed deploys and rollbacks = 0 | how credits work |
| Deploy Previews | 0 credits, unlimited | how credits work |
| Concurrent builds | 1 | credit-based pricing plans |
| Projects | 500 per team | credit-based pricing plans |
| Functions compute | 10 credits per GB-hour; default memory 1024 MB | functions usage |
| Forms | Free & unlimited | forms usage |
| Identity | Included, unlimited active users | Identity overview |
| Custom domains & SSL | Included; per-site count NOT documented | credit-based pricing plans |
| Web analytics | 1-day retention | Netlify pricing |
| Netlify Database | 3 databases, 20 active branches, 7-day backups | credit-based pricing plans |
| When credits run out | All projects paused; “Site not available”; alerts at 50/75/100%; resume next cycle or on upgrade | Netlify pricing FAQ |
Sign up and deploy your first Netlify site
To deploy from Git, sign up at app.netlify.com/signup with GitHub or Google, click Add new project, Import an existing project, pick GitHub, GitLab, Bitbucket, or Azure DevOps, and authorize access. Netlify auto-detects your publish settings, so hit Publish and your site goes live at YOUR-PROJECT-NAME.netlify.app, per the official quickstart guide. Every push redeploys; custom domains are added under Domain management.
Two faster alternatives exist: drag-and-drop deploys work best under 50 MB, or you can try the AI site builder “Start with AI agent” at app.netlify.com/start, per the choose-your-path documentation.
Build settings worth knowing
Netlify auto-detects the build command and publish directory for most frameworks — Astro, Next.js, Vite, Hugo, and plain static folders all work out of the box, per the build configuration docs. If auto-detection misses, set them manually under Site configuration → Build & deploy → Continuous deployment: Build command (for example npm run build), Publish directory (like dist or public), and Base directory for monorepos. Store API keys and other secrets under Site configuration → Environment variables; they are injected at build time, per the environment variables docs. Pin your Node version with a .nvmrc file so local and CI builds match, and check Branch settings: only your production branch (usually main) should trigger production deploys, while pull requests build free Deploy Previews for review.
What can you build on the Netlify free plan?
A portfolio or static site is the classic use case, per the how credits work documentation. A landing page with a contact form works well since forms are free and unlimited. A small serverless API is also viable, with ~30 GB-hours of compute in the monthly pool, per the functions usage documentation.
Documentation sites are another strong fit: content lives in Git, reviewers get a free Deploy Preview per pull request, and light doc traffic stays well under the bandwidth cap. Personal blogs work too — at 15 credits per production deploy, a few posts a month barely dents the pool. The one thing to avoid is heavy media: a 1 GB file download costs 20 credits of bandwidth, so a popular page serving big videos can exhaust the pool by itself.
Free plan vs paid plans
Netlify prices paid plans around monthly credit pools rather than a la carte add-ons, per Netlify’s pricing page. The headline differences:
| Feature | Free plan | Paid plans (Pro and up) |
|---|---|---|
| Monthly credits | 300, no top-up | Larger pools, billed per seat + usage |
| Concurrent builds | 1 | More, so build queues clear faster |
| Support | Community forum | Priority email support |
| SAML/SSO | Not included | Included from Pro |
| Web analytics retention | 1 day | Longer retention windows |
| Billing | Never billed | Per-seat + usage |
For most personal sites the free plan is enough — only teams with continuous deployment traffic or strict security requirements need to upgrade, per Netlify’s pricing page.
Netlify vs Vercel vs Cloudflare Pages
Netlify’s single 300-credit pool is the tightest cap of the three — the derived equivalent of only ~15 GB of bandwidth. Vercel Hobby gives 100 GB transfer and 1M invocations but is non-commercial only, per Vercel’s pricing and limits documentation. Cloudflare Pages has no bandwidth charges but no built-in forms, per Cloudflare’s limits documentation.
For the full comparison, see our Vercel free tier guide and our Cloudflare Pages free tier guide.
Common beginner mistakes
The most common beginner errors are dragging a local build instead of connecting Git, spending credits on repeated production deploys, and using Functions when a free form suffices. The full list below covers all six, each with the source that explains the fix.
- Using drag-and-drop instead of Git, which means no auto-deploys, per the choose-your-path documentation.
- Burning credits on repeated production deploys when Deploy Previews are free, per the how credits work documentation.
- Using Functions when a free form suffices, per the forms usage documentation.
- Ignoring the credit meter — the whole account pauses at zero, per the pricing FAQ.
- Skipping deploy notifications, which are available via email, Slack, or webhook, per the deploy notifications documentation.
- Planning around outdated 2024-era limits like “100 GB bandwidth” or “build minutes,” which no longer apply.
Gotchas to plan around
- Deploys are the real cost driver. At 15 credits per production deploy, 300 credits cap you at about 20 deploys a month. Every push to the production branch burns one, so batch your changes and iterate on free Deploy Previews instead.
- Bandwidth is effectively ~15 GB per month. 300 credits ÷ 20 credits per GB. Images and videos dominate; a single 1 GB asset download costs 20 credits alone.
- Custom domain SSL is automatic but not instant. Add the domain under Domain management, point DNS at Netlify, and the certificate provisions within minutes, per the custom domains docs.
- Apex domains trip up some registrars. If your registrar lacks ALIAS/ANAME records, use the
wwwsubdomain instead and redirect to it. - Deploy Previews build on every pull request update. They cost zero credits, but they still queue behind your single concurrent build, so large PRs slow down the pipeline.
FAQ
Is the Netlify free plan really free?
Yes. The free plan costs $0 per month forever, with a hard 300-credit monthly limit, and you are never billed, per Netlify’s pricing FAQ. There is no top-up option on Free, so you cannot accidentally spend money — the only way to get more credits is to upgrade to a paid plan.
What happens when I run out of Netlify credits?
When credits are exhausted, all your projects are paused and visitors see “Site not available,” per Netlify’s pricing FAQ. You get email and in-app alerts at 50%, 75%, and 100% usage, and sites resume next cycle or immediately on upgrade, per the how credits work documentation. Free accounts cannot buy more credits.
How many projects can I have on Netlify’s free plan?
You can have up to 500 projects per team on the free plan, per the credit-based pricing plans documentation. Custom domains with SSL are included, but Netlify does not document a per-site domain cap, so no specific number can be stated.
Do I need a credit card for the free plan?
No. The free plan requires no billing details at signup — you get 300 credits per month and are never billed, per Netlify’s pricing FAQ. Since top-ups are unavailable on Free, there is no accidental-spend path; paid plans are where a card becomes necessary.
How many production deploys fit in 300 credits?
About 20. Each production deploy costs 15 credits (300 ÷ 15), and failed deploys and rollbacks cost zero. Deploy Previews cost nothing, so previewing before pushing to production stretches the pool much further, per the how credits work documentation.
Is a custom domain with SSL really included on free?
Yes. Add your domain under Domain management, and Netlify provisions and renews SSL certificates automatically at no charge, per the custom domains documentation.
Where to go next
The Netlify free plan is an excellent starting point for beginners, provided you monitor your credit meter. Start with a portfolio or landing page, use Git for auto-deploys, and lean on free forms instead of Functions. The free plan cannot top up, so if you hit zero, you wait for the next cycle or upgrade, per Netlify’s official pricing page.