Top 5 Static Site Hosting and Jamstack Platforms of 2026: Vercel vs Netlify vs Cloudflare Pages vs Render vs GitHub Pages
Vercel, Netlify, Cloudflare Pages, Render, and GitHub Pages compared on real bandwidth caps, build limits, and function timeouts, not marketing pages.
Quick Comparison
| Platform | Free Bandwidth | Free Build Limit | Function Support (Free) | Paid Tier Starts At |
|---|---|---|---|---|
| Cloudflare Pages | Unmetered for static assets | 500 builds/month, 1 concurrent | Pages Functions on Workers free tier: 100,000 requests/day | $5/month (Workers Paid) |
| Vercel | 100GB (Hobby, non-commercial use only) | 100 deployments/day | 1,000,000 function invocations/month, 300s max duration | $20/seat/month (Pro) |
| Netlify | ~15GB effective (300 credits, 20 credits/GB) | ~20 production deploys/month (15 credits each) | 10s sync function timeout, shared credit pool | $9/month (Personal) |
| Render | 5GB pooled per workspace (Hobby) | Unlimited static builds | None, dynamic logic needs a separate web service | $7/month (Starter web service) |
| GitHub Pages | 100GB/month (soft cap) | 10 builds/hour (soft cap) | None, static files only | N/A, always free |
Cloudflare Pages
- Free Bandwidth
- Unmetered for static assets
- Free Build Limit
- 500 builds/month, 1 concurrent
- Function Support (Free)
- Pages Functions on Workers free tier: 100,000 requests/day
- Paid Tier Starts At
- $5/month (Workers Paid)
Vercel
- Free Bandwidth
- 100GB (Hobby, non-commercial use only)
- Free Build Limit
- 100 deployments/day
- Function Support (Free)
- 1,000,000 function invocations/month, 300s max duration
- Paid Tier Starts At
- $20/seat/month (Pro)
Netlify
- Free Bandwidth
- ~15GB effective (300 credits, 20 credits/GB)
- Free Build Limit
- ~20 production deploys/month (15 credits each)
- Function Support (Free)
- 10s sync function timeout, shared credit pool
- Paid Tier Starts At
- $9/month (Personal)
Render
- Free Bandwidth
- 5GB pooled per workspace (Hobby)
- Free Build Limit
- Unlimited static builds
- Function Support (Free)
- None, dynamic logic needs a separate web service
- Paid Tier Starts At
- $7/month (Starter web service)
GitHub Pages
- Free Bandwidth
- 100GB/month (soft cap)
- Free Build Limit
- 10 builds/hour (soft cap)
- Function Support (Free)
- None, static files only
- Paid Tier Starts At
- N/A, always free
Cloudflare Pages
Best OverallBest for: Static and Jamstack sites that want a genuinely free tier with no bandwidth-overage bill waiting to happen
“Cloudflare Pages is the only platform in this comparison that doesn't meter bandwidth on its free tier, which matters more than any other single number once a site gets real traffic. Add 500 free builds a month, unlimited sites, and Pages Functions that plug straight into Workers, KV, R2, and D1, and it's the safest default for a static or Jamstack site that might actually get popular. The catch is that Cloudflare itself is steering new projects toward Workers with static assets, not Pages.”
Pros
- No published bandwidth cap for standard static assets on the free tier, unlike every other platform here that meters gigabytes and bills overage once a site gets traffic
- 500 builds/month and unlimited sites on the free plan with no credit card required to start
- Pages Functions integrate directly with Workers, KV, R2, and D1 for edge logic without adding a separate vendor or billing relationship
- 100 custom domains included per project on the free tier, well beyond what Render or Netlify include at no cost
Cons
- 500 builds/month works out to about 16 a day, a team with high commit frequency or many contributors triggering CI on every push can hit that ceiling
- Pages Functions share the same 100,000-requests/day quota as the rest of Cloudflare's Workers free tier, so a busy site running edge functions can run out of request budget well before bandwidth becomes a problem
- Preview deployment ergonomics and dashboard polish trail Vercel and Netlify, both of which have invested more directly in the deploy-preview workflow
Unmetered Bandwidth, With Caveats
Every other platform in this comparison eventually charges per gigabyte once a site's traffic exceeds a fixed free allotment: Vercel at $0.15/GB past 1TB on Pro, Render at $0.15/GB past 5GB on Hobby, Netlify by draining its shared credit pool. Cloudflare Pages doesn't meter standard static asset delivery at all on the free tier, which removes the single most common surprise bill in this category. The terms of service do prohibit hosting large binary files like video, so this is a static-site bandwidth deal, not a CDN-for-anything deal.
Workers Integration for Edge Logic
Pages Functions run on the same underlying Workers runtime that powers Cloudflare's standalone Workers product, so a static site can add authentication checks, redirects, or API routes without provisioning a separate serverless platform. Those functions draw from the same 100,000-requests/day free Workers quota as everything else on the account, which is generous for most static-plus-a-little-dynamic sites but is a shared pool, not a bandwidth-style unlimited allowance.
Free: unmetered bandwidth for static assets, 500 builds/month, unlimited sites, 100 custom domains/project. Workers Paid: $5/month, raises Pages Functions request limits and unlocks paid Workers usage for edge logic.
Vercel
FastestBest for: Next.js and framework-heavy Jamstack apps that need first-party rendering support out of the box
“Vercel builds Next.js, and it shows: incremental static regeneration, edge middleware, and streaming server rendering work with zero configuration because the framework and the platform are developed by the same company. The free Hobby plan is genuinely capable, with 1,000,000 function invocations and 100GB of bandwidth included, but its terms of service restrict Hobby to non-commercial use, which forces an upgrade to Pro at $20/seat/month the moment a side project starts charging money.”
Pros
- Deepest first-party integration with Next.js of any host, incremental static regeneration, edge middleware, and streaming rendering work without extra configuration because Vercel builds the framework
- Free Hobby tier includes 1,000,000 function invocations, 4 CPU-hours of active compute, and 100GB of bandwidth, enough headroom for a real side project, not just a demo
- Instant preview deployments on every git push give each pull request its own shareable URL, standard across every plan tier including free
- Function max duration on Hobby is 300 seconds (5 minutes), longer than Netlify's 10-second free-tier sync timeout by a wide margin
Cons
- Hobby plan's terms of service restrict it to non-commercial, personal use; a site running ads, payments, or client work is technically in violation the day Stripe goes live, and Vercel enforces this
- Moving to Pro costs $20 per seat per month, not a flat project fee, so a two-person team pays $40/month just to remove the commercial-use restriction
- Bandwidth overage on Pro is $0.15/GB past the included 1TB, the same metered-overage exposure that makes traffic spikes expensive on any bandwidth-capped host
- 200 projects on Hobby and 100 deployments/day are generous but still fixed ceilings, unlike Cloudflare Pages' unlimited sites
Framework-Native Rendering
Because Vercel and Next.js share an engineering org, features like ISR, partial prerendering, and edge middleware ship on Vercel with no adapter layer or configuration guesswork. Deploying a Next.js app to Vercel is close to zero-config, while deploying the same app's more advanced rendering modes to Netlify or Cloudflare Pages sometimes requires a community adapter that lags a framework release or two behind. For teams standardized on Next.js, this gap is the main reason Vercel remains the default.
The Commercial-Use Catch
The Hobby plan's non-commercial restriction is easy to miss because nothing in the sign-up flow blocks a paid Stripe integration from going live. The distinction only becomes concrete when Vercel's usage or billing team flags an account, at which point the fix is upgrading to Pro at $20/seat/month, not a warning email with a grace period. Any project with a real path to revenue should budget for Pro from the start rather than discovering the restriction after launch.
Free (Hobby, non-commercial use only): 100GB bandwidth, 1,000,000 function invocations, 4 CPU-hours, 300s function timeout. Pro: $20/seat/month, 1TB bandwidth included, then $0.15/GB overage, 6,000 deployments/day.
Netlify
Runner UpBest for: Teams that want the deepest build-plugin ecosystem and are willing to budget for a smaller free tier than Netlify used to offer
“Netlify effectively created the Jamstack build-and-deploy workflow, and its plugin ecosystem, covering everything from Lighthouse budgets to cache warming to sourcemap uploads, is still the deepest of any platform here. What changed is the free tier: the September 2025 move to credit-based pricing replaced separate bandwidth and build-minute quotas with one shared 300-credit pool, and the real free bandwidth for new accounts works out to roughly 15GB, not the 100GB the platform was known for.”
Pros
- Largest build-plugin ecosystem in the category: plugins exist for Lighthouse performance budgets, cache warming, Sentry sourcemap uploads, and dozens of other build-time tasks without custom scripting
- Split testing and branch deploy previews are available on the free plan with no extra configuration
- Netlify Functions and Edge Functions run on the same platform as the CDN and build system, no separate serverless vendor to wire up and bill separately
- Deploy previews on every pull request are unlimited, matching Vercel's workflow rather than gating it behind a paid tier
Cons
- The September 2025 credit-based repricing cut the free tier hard: bandwidth now costs 20 credits per GB against a 300-credit monthly pool, working out to roughly 15GB of real free bandwidth versus the old flat 100GB
- Production deploys cost 15 credits each on the free plan, so frequent CI pushes can burn through the monthly credit pool before bandwidth even becomes the limiting factor
- Function compute is metered from the same shared credit pool as bandwidth and deploys, so a functions-heavy free-tier site competes with its own traffic for the same 300 credits
- Legacy accounts opened before September 2025 keep the old, more generous fixed quotas, meaning two developers comparing notes on Netlify's free tier today may genuinely be describing different products
Build Plugin Ecosystem
Netlify's build plugin system lets a site run Lighthouse performance checks, warm caches, submit sitemaps to search engines, or upload sourcemaps to an error tracker as steps in the same build pipeline that deploys the site, without hand-rolling CI scripts for each task. No other platform in this comparison ships an equivalent marketplace of build-time plugins, and for teams that lean on this ecosystem, it's a real, non-marketing reason to stay on Netlify over a cheaper competitor.
The Credit System Change
Before September 2025, a Netlify free account had two separate, easy-to-reason-about numbers: 100GB of bandwidth and 300 build minutes. The credit system replaced both with one 300-credit pool priced at 20 credits per GB of bandwidth, 15 credits per production deploy, and 10 credits per GB-hour of function compute, meaning a site's actual free capacity now depends on the mix of traffic, deploy frequency, and function usage rather than a single flat number. It's a real repricing, not just a UI change, and it's the single biggest difference between Netlify's current free tier and its long-standing reputation.
Free: 300 credits/month (20 credits/GB bandwidth, 15 credits per production deploy, 10 credits/GB-hour function compute), no auto-recharge. Personal: $9/month. Legacy accounts predating September 2025 retain separate 100GB bandwidth and 300 build-minute quotas.
Render
Honorable MentionBest for: Projects that need a database, background worker, or cron job running alongside the static frontend, not just static files
“Render's static site hosting is genuinely free and unlimited in site count, with CDN, Brotli compression, and managed TLS included by default. Its real differentiator is that the same dashboard can run a Postgres database, Redis instance, background worker, and cron job next to that static site, something none of the pure static hosts in this comparison offer. The trade-off is bandwidth: it's pooled at the workspace level, and the free Hobby workspace only includes 5GB a month before $0.15/GB overage.”
Pros
- Static sites are unlimited in count and free forever, no credit card required, with global CDN, Brotli compression, and HTTP/2 included by default
- The same workspace can host a managed Postgres database, Redis instance, background worker, and cron job alongside the static frontend, useful when a nominally static site needs a small API
- Managed TLS certificates and custom domains are included on the free static tier at no extra charge beyond the domain count limit
- No sleep or cold-start behavior on static sites, unlike Render's free web services, which do spin down after inactivity
Cons
- Outbound bandwidth is pooled at the workspace level, not per site, and the free Hobby workspace includes only 5GB/month before $0.15/GB overage, far below Cloudflare Pages' effectively unlimited bandwidth or even GitHub Pages' 100GB soft cap
- Only 2 custom domains are included per workspace on Hobby; additional domains cost $0.25/month each, a real line item for anyone running several small sites
- No edge functions comparable to Vercel Edge Middleware or Cloudflare Workers; any dynamic logic requires standing up a separate Render web service with its own resource and pricing tier
Full-Stack Beyond Static
Vercel, Netlify, Cloudflare Pages, and GitHub Pages are all fundamentally static-and-functions platforms. Render is a general application host that happens to offer excellent free static hosting as one product among several: managed Postgres, Redis, background workers, cron jobs, and Docker-based web services all live in the same dashboard and billing relationship. For a project that needs more than a static frontend plus the occasional serverless function, that consolidation is a real advantage the pure static hosts don't offer.
The Pooled Bandwidth Limit
Because bandwidth is metered per workspace rather than per service, a workspace running a static marketing site and a backend API shares one 5GB free allotment between them on the Hobby tier. This is a materially different model from Cloudflare Pages, Vercel, or GitHub Pages, where the static site's bandwidth is not competing with anything else on the account. It's worth checking usage per service in the Render dashboard before assuming the static site alone is responsible for hitting the cap.
Static sites: free, unlimited count, CDN included, 2 custom domains included per workspace ($0.25/month each additional). Bandwidth: 5GB/month pooled per workspace on Hobby, then $0.15/GB. Web services (for dynamic backends): from $7/month (Starter).
GitHub Pages
Best Free OptionBest for: Open-source project documentation, personal portfolios, and simple sites that already live in a GitHub repository
“GitHub Pages is free forever with no paid tier, no usage-based billing, and no credit card ever required, but it's a narrower tool than the other four platforms in this comparison. It serves static HTML only, with no functions, no edge logic, and no first-class pull-request preview URLs. For open-source documentation or a personal portfolio already living in a GitHub repo, that's exactly enough. For anything that needs a contact form handler or authenticated content, it isn't.”
Pros
- Completely free with no paid tier, no credit card, and no usage-based billing at all, tied only to a GitHub repository that's likely already free
- Custom domains get free GitHub-managed SSL certificates with no separate certificate authority setup
- Zero additional setup for projects already using GitHub Actions: actions/deploy-pages is a one-file workflow with no third-party account to create
- Jekyll builds are supported natively without a GitHub Actions workflow at all, useful for the simplest documentation sites
Cons
- No serverless or edge functions of any kind; a GitHub Pages site is static HTML only, so anything dynamic (forms, auth, A/B tests) requires bolting on a separate third-party service
- The 100GB/month bandwidth cap and 10-builds/hour limit are both soft limits enforced at GitHub's discretion rather than published hard numbers, meaning GitHub can email a warning and disable the site rather than throttling predictably
- No first-class preview deployment per pull request the way Vercel, Netlify, and Cloudflare Pages all provide out of the box; getting PR previews on GitHub Pages requires custom Actions workflow scripting
What It's Actually For
GitHub Pages is best understood as a free hosting benefit attached to a GitHub repository, not a standalone product competing feature-for-feature with Vercel or Netlify. It has no dashboard, no team billing, no usage analytics beyond what GitHub's repo insights already show, and no roadmap of new platform capabilities the way the other four vendors here actively ship. For its actual use case, docs sites, portfolios, and simple project pages already living on GitHub, that minimalism is a feature, not a gap.
The Soft Limits
GitHub explicitly describes its Pages bandwidth and build-frequency limits as soft: exceeding 100GB/month or 10 builds/hour doesn't trigger an automatic cutoff, GitHub instead reserves the right to contact the owner or disable the site at its discretion. That's a materially different guarantee than a published hard quota with a clear overage price, and it means a GitHub Pages site that unexpectedly goes viral is relying on GitHub's goodwill, not a contractual SLA, to stay up.
Free forever, no paid tier. Soft limits: 100GB/month bandwidth, 10 builds/hour, 1GB recommended repository size. Custom domains and GitHub-managed SSL included at no cost.
Which One Should You Pick?
| Use Case | Our Recommendation |
|---|---|
| Building a Next.js app with server rendering, ISR, or edge middleware and wanting zero-config deploys | Vercel. First-party framework support means Next.js's advanced rendering modes work without adapters or configuration, though budget for Pro at $20/seat/month once the project takes its first payment. |
| Running a static blog or marketing site with unpredictable or growing traffic and wanting no bandwidth-overage surprises | Cloudflare Pages. Unmetered bandwidth for static assets on the free tier removes the single most common surprise bill in this category, and allows commercial use from day one. |
| Needing build-time plugins for Lighthouse budgets, sourcemap uploads, or split testing without hand-rolling CI scripts | Netlify. Its build plugin ecosystem is still the deepest of any platform here, though budget for roughly 15GB of real free bandwidth on a new account, not the 100GB Netlify was historically known for. |
| A static frontend that also needs a small Postgres-backed API, a background worker, or a cron job | Render. The same workspace runs the database, worker, and static site together, though keep an eye on the pooled 5GB/month free bandwidth shared across every service. |
| Publishing open-source project documentation or a personal portfolio already living in a GitHub repository | GitHub Pages. Free forever with zero setup beyond a repo, but plan to move to one of the other four platforms the moment the site needs a form handler, auth, or anything dynamic. |
How we evaluated
Static site hosting is one of the highest-volume developer searches that exists, and most comparisons out there are vendor blog posts restating marketing pages. This one weighs the numbers that actually decide a real project's monthly bill and its ceiling for growth: free-tier bandwidth, build limits, and what a function timeout or a pooled quota actually costs you in production.
Each platform was assessed on the criteria that decide real outcomes, the same dimensions you see in the comparison table above:
- Best fit: which project shape, a pure static site, a framework-rendered app, or a static-plus-backend setup, each platform actually serves well, not the broadest possible audience.
- Free-tier bandwidth: whether the free plan meters gigabytes at all, and what the real effective cap is once credits, pooling, or non-commercial-use restrictions are accounted for.
- Build and deploy limits: builds per month or per hour, and whether those limits are hard, soft, or shared with other account activity.
- Function and edge support: whether serverless or edge functions exist on the free tier, their timeout, and how they're metered.
- Pricing model: free tier limits and what triggers paid upgrade.
What we reviewed
This comparison draws on official documentation and publicly posted pricing, and hands-on evaluation where access was available. It reflects the market as of 2026 and is refreshed as platforms ship and reprice.
Editorial independence: this is a vendor-neutral comparison with no paid placements, sponsorships, or affiliate links. Rankings reflect fit for the stated use cases, not commercial relationships.
Frequently Asked Questions
What's the best free static site host in 2026?
Can I use Vercel's free Hobby plan for a commercial project?
Is Netlify still worth it in 2026?
Which platform is best if I need a database or background jobs, not just static hosting?
Is GitHub Pages good enough for a startup marketing site?
Which platform has the best edge functions?
Related Comparisons
API Testing & Development
Top 5 API Testing and Development Tools of 2026: Postman vs Bruno vs Insomnia and More
5 tools compared
Data Pipeline / ETL
Top 5 Data Pipeline & ETL Tools of 2026: Fivetran vs Airbyte vs dbt vs Airflow vs Dagster
5 tools compared
Feature Flag Management
Top 5 Feature Flag Management Platforms of 2026: LaunchDarkly, GrowthBook, and More
5 tools compared
Test Automation / QA
Top 5 Test Automation / QA Tools for 2026: Playwright vs Cypress vs Selenium vs BrowserStack vs Sauce Labs
5 tools compared