Practical guide · verified against the real thing
Render vs Vercel vs Netlify in 2026: the comparison that starts with your project
In one line: Every number here was read off the three platforms' own pricing pages on 15 September 2026 — and the honest answer is a decision tree, not a winner. From a desk whose site actually runs on Render.
Comparisons of these three platforms usually fail in the same way: they recycle last year's free-tier numbers (the numbers have moved a lot), then crown a winner that depends entirely on a project the reader doesn't have. So here are the ground rules for this one: every figure below comes from the platform's own pricing page, checked 15 September 2026; free tiers are compared because that's where the real differences live; and the conclusion is a decision tree, because the right answer genuinely depends on what you're deploying. One more disclosure that matters: this site runs on Render's free tier — the deploy is documented here, including what broke — so our first-hand experience is deepest on that platform, and we've said so wherever it shows.
The 2026 numbers, first-party and dated
Render — Hobby plan, $0/month: up to 25 services, 5 GB of bandwidth included per workspace (then metered), global CDN, custom domains, single-service previews. Pro is $25/month with 25 GB included and unlimited seats. Compute is separate: free web services exist (512 MB RAM, with spin-down after inactivity), paid instances start at $7/month, and managed Postgres/Redis/cron run in the same workspace.
Vercel — Hobby plan, $0/month, positioned for personal, non-commercial projects: 100 GB/month of fast data transfer included, 1M edge requests, 4 hours of Fluid compute, 1M function invocations, unlimited deployments, one developer seat. Pro is $20/month/seat with $20 of included usage credit and the flat-rate CDN. Commercial use on the free tier isn't what the Hobby plan is for — check the terms before putting a business on it.
Netlify — Free plan, $0/month, 300 usage credits per month. The credit math from their own table: a production deploy costs 15 credits, bandwidth costs 20 credits per GB, web requests 2 credits per 10k. So the whole free pool is either about 20 production deploys, or about 15 GB of bandwidth, or a mix — one shared pool for everything. Personal ($9/month) includes 1,000 credits; Pro ($20/month, unlimited members) starts at 3,000.
Notice what changed over the years: Netlify moved from generous separate quotas to the shared credit pool, and Render's free bandwidth tightened from earlier eras. If you read a comparison citing 100 GB free on all three, it's recycling 2024. The numbers above will drift too — that drift is exactly why the free-vs-paid question needs re-checking, and why we date every figure.
What each platform is actually built around
Vercel is built around frontend frameworks — Next.js above all. If your project is a Next.js app, the integration (ISR, image optimisation, edge middleware, preview deploys per pull request) is the deepest of the three, and the free compute allowance is real. The trade: the free tier's seat count, commercial restrictions and the overage-pricing model mean the moment the project grows up, it becomes a paid conversation.
Netlify is built around the Jamstack workflow — deploy previews, branch deploys, forms, functions, instant cache invalidation. The workflow polish is excellent; the credit pool is the discipline. For a site that deploys often and serves moderate traffic, the arithmetic above is the whole story: it's easy to compute exactly when the free tier runs out, which is honest but unforgiving.
Render is built around running everything together: static sites, web services, workers, managed Postgres, Redis and cron in one workspace. The static-site free tier is simple (static sites are free; bandwidth is the 5 GB pool), and the superpower is that the backend your frontend needs is a sibling service, not a separate platform. The trade: free web services spin down after inactivity and take a moment to wake, the free bandwidth pool is the smallest of the three, and the frontend-framework niceties (per-PR preview ecosystems, image pipelines) are leaner than Vercel's.
The decision tree
Pure static site, modest traffic, simple needs? Honestly, all three work — and so do the options we've compared separately: GitHub Pages and Cloudflare Pages, where unmetered static bandwidth can beat all three free tiers at once. Start there if the site is just files.
A Next.js (or heavy React) app? Vercel's framework integration is the reason it exists; the free tier's 100 GB covers a lot of traffic. Have the commercial-use conversation before the project earns money.
A Jamstack site with functions, forms, lots of PR previews? Netlify's workflow is the most polished. Budget the credits: multiply your deploys-per-month by 15, your expected GB by 20, and see whether free is realistic or whether $9 Personal is the honest plan.
A real backend — API server, database, background jobs? Render is the only one of the three where the static frontend and the long-running backend (with managed Postgres and cron) live as first-class siblings. This site's own architecture — static pages served alongside a Node server with security headers and routing — is exactly that shape, and the failures we documented taught us the platform's sharp edges honestly.
Watching bandwidth above all? The 2026 free-tier order for included transfer is Vercel 100 GB > Netlify ~15 GB-equivalent > Render 5 GB. If a static site is your shape and traffic is your constraint, Cloudflare Pages' unmetered static bandwidth changes the question entirely — that's a hosting-costs conversation, not a loyalty one.
The migration tax nobody prices in
Whichever you pick, the cost of switching later is real but survivable: DNS is the piece that takes patience — the order you move records in matters — and the deploy pipeline is usually a re-connect-the-repo afternoon. What doesn't transfer cleanly is platform-specific glue (Netlify function shims, Vercel rewrites, Render's blueprint). Keep the build framework-native and the platform config thin, and you keep the exit cheap. That discipline is why this site could move hosts if the bandwidth math ever demanded it — the build is plain HTML and a Node server, no platform lock-in to speak of.
The honest closing
There is no winner here. There are three well-run platforms with sharply different free-tier shapes: Vercel's is the most generous for non-commercial frontends, Netlify's is the most predictable and the most finite, Render's is the narrowest on bandwidth but the only one that treats your backend as a first-class citizen. Pick by project shape, check the pricing page on the day you decide — not this article, not a forum — and re-check it whenever your traffic changes by an order of magnitude. Checked figures age; the decision tree doesn't.
Official sources (checked 15 September 2026): render.com/pricing · vercel.com/pricing · netlify.com/pricing. Free-tier behaviour (spin-down, credit metering) per each platform's documentation pages.
Sources
Next