Vercel vs Netlify used to be a question about frameworks. It is now a question about arithmetic, because in late 2025 both platforms replaced their pricing models within a fortnight of each other and ended up in structurally different places.
So Vercel vs Netlify is now a pricing-architecture question first. Vercel charges per developer seat and meters usage on top. Netlify charges for a pool of credits and does not charge for seats at all. That single difference decides the answer for most teams before any technical comparison starts, and it flips depending on the ratio between how many people you employ and how much traffic you serve.
The two pricing models, stated plainly
Vercel’s Pro plan is $20 per developer seat per month, with viewer seats free, and each team receives $20 of flexible usage credit. Past that, usage bills on demand. The model changed on September 9, 2025, replacing discrete included allowances across more than twenty products with the credit-plus-on-demand arrangement.
Netlify’s Pro plan starts at $20 for 3,000 credits with unlimited team seats and unlimited team owners. Credits are the single meter: bandwidth, compute, requests, deploys and AI inference all draw from the same balance. New accounts moved to credit pricing on September 4, 2025, and existing accounts stay on legacy plans unless they opt in, which is irreversible.
Since July 14, 2026 Netlify offers five Pro credit tiers, from 3,000 credits at $20 up to 20,000 at $126. Tiers of 5,000 and above roll unused credits into one extra cycle. The base tier does not.
The behavior at the ceiling differs and it matters operationally. Vercel bills you past the credit, with spend management available to alert or pause. Netlify pauses every project on the team and serves an unavailable page once credits hit zero, unless auto-recharge or a credit pack is configured. On Netlify’s free tier you cannot buy credits at all; you wait for the next cycle.
Bandwidth is where the surprise bills come from
This is the number to work out before anything else, and the two platforms are not comparable at a glance because one sells gigabytes and the other sells credits.
Vercel Pro includes 1 TB of fast data transfer plus 10 million edge requests per team. Overage runs $0.15 to $0.35 per gigabyte depending on region, with edge requests at $2.00 to $3.20 per million.
Netlify charges 20 credits per gigabyte. At the Pro top-up rate that works out to about $0.133 per gigabyte, falling to roughly $0.126 at the 20,000 credit tier. So Netlify’s marginal rate is around 13 percent cheaper than Vercel’s United States rate. But 3,000 credits is only about 150 GB if you spend them all on bandwidth, and you will not, because everything else draws from the same pool.
Run the crossover and it turns on headcount. A three-seat team serving 1 TB a month pays $60 on Vercel Pro, where the terabyte is included. The same traffic on Netlify needs the $126 tier. At twelve seats, Vercel is $240 and Netlify is still $126.
Compute, and the sixty-second wall
Vercel’s functions run on Fluid compute, the default for new projects since April 2025. Maximum duration is 300 seconds by default on Pro, with 800 seconds now generally available and 1800 seconds in extended beta, per the function limits documentation. Memory reaches 4 GB with 2 vCPU. Bundles are capped at 250 MB, or 5 GB through the Large Functions beta. Concurrency auto-scales to 30,000.
The billing detail worth knowing is that Vercel charges Active CPU separately from Provisioned Memory, so time spent waiting on input and output bills memory but not CPU. For anything that spends its life waiting on a model or a database, that changes the economics materially.
Netlify’s synchronous functions cap at 60 seconds, and it is not configurable. Background functions run to 15 minutes but are Pro and Enterprise only. Memory is 1024 MB by default, configurable between 1024 and 4096 MB on credit-based paid plans. Edge functions get 50 milliseconds of CPU per request.
That 60 second ceiling is the single hardest technical constraint in this comparison. If you have a route that generates a report, processes an upload or streams a long model response, it either fits or it does not. We worked through how the edge and serverless distinction has largely collapsed on Vercel’s side in our look at Vercel functions, edge versus serverless.
Netlify publishes no cold-start figures anywhere in its documentation, which is worth knowing if that number matters to you.
The Next.js question, settled from Netlify’s own docs
The received wisdom is that Next.js is crippled anywhere except Vercel. On Netlify’s current documentation, that is no longer true.
Netlify supports Next.js 13.5 and above through the open-source OpenNext adapter, updated automatically each build unless you pin it. Its own framework guide lists App and Pages Router, server-side rendering, incremental static regeneration, static generation, React Server Components, Server Actions, streaming, route handlers, middleware, image optimization, on-demand and time-based revalidation, draft mode, Turbopack, cache components, partial pre-rendering and opt-in skew protection as supported.
The genuine caveats are narrower than the reputation. Edge-runtime pages render in your functions region on Node rather than at the edge, which Netlify says costs no functionality but does cost placement. Middleware lacks C++ addons and filesystem access. Headers and redirects evaluate after middleware, which is the opposite of standalone Next.js. Rewrites in next.config cannot target static files in public/. Skew protection needs a manual header on client fetches.
So the gap is placement and that 60 second ceiling, not a feature list. Both pillars are worth reading first if you are new to either platform: our introduction to Vercel and our introduction to Netlify cover what each one is before you compare them.
Builds, previews and the metering underneath
Both platforms give you atomic deploys, immutable artifacts, per-branch previews and one-click rollback. The difference is what gets metered.
Vercel caps builds at 45 minutes on every plan. Elastic build machines, ranging from 4 to 30 vCPU, are now the default for new paid teams and bill at $0.0035 per CPU-minute. So Pro builds are metered in practice even though the plan does not advertise a build allowance. Custom environments beyond local, preview and production are limited to one per project on Pro and twelve on Enterprise.
Netlify does not meter build minutes at all on credit plans. Concurrency is the lever instead: Pro includes three concurrent builds and additional ones are a $40 per month add-on. Deploy previews and branch deploys cost no credits, which is why preview-heavy workflows land differently on the two platforms. Netlify has five deploy contexts configurable in netlify.toml, each with its own environment variables.
Vercel vs Netlify: where each one genuinely wins
Vercel wins when traffic is high relative to headcount, because 1 TB included beats 150 GB. It wins when functions need more than 60 seconds. It wins for AI and agent workloads, where Active CPU billing skips input and output wait. And it wins if you want a ceiling that warns rather than one that stops serving your site.
Netlify wins when the team is large relative to traffic, and this is the biggest single lever in the comparison: unlimited seats at $20 against $20 multiplied by headcount. It wins for agencies running many low-traffic client projects. It wins for preview-heavy workflows, since previews cost nothing while Vercel now meters build compute. And it wins when you would rather forecast one number than twenty-five meters.
Neither wins when bandwidth is your dominant cost, and this is the honest answer to Vercel vs Netlify for a large class of sites. Both are ten to thirty times the price of a raw content delivery network, and if you are serving large static assets at volume you should be pointing a CDN at object storage instead.
Frequently Asked Questions
Is Vercel or Netlify cheaper?
It depends entirely on the ratio of team size to traffic. Netlify charges nothing for seats, so a twelve-person team pays $126 for roughly a terabyte where Vercel would charge $240 in seats alone. Vercel includes 1 TB of bandwidth on Pro against roughly 150 GB of credit-equivalent on base Netlify Pro, so a small team with heavy traffic pays far less on Vercel.
What is the biggest technical difference between them?
Function duration. Netlify’s synchronous functions are capped at 60 seconds and the limit is not configurable, while Vercel supports 300 seconds by default, 800 seconds generally available and 1800 seconds in beta. Anything that generates reports, processes large uploads or streams long model responses either fits inside a minute or rules Netlify out for that route.
Does Next.js work properly on Netlify?
Yes, far better than its reputation suggests. Netlify supports Next.js 13.5 and above through the OpenNext adapter, covering App and Pages Router, server-side rendering, incremental static regeneration, React Server Components, Server Actions, streaming, middleware and image optimization. The real caveats are that edge-runtime pages render in your functions region rather than at the edge, and that headers and redirects evaluate after middleware.
What happens if I run out of credits on Netlify?
Every project on the team is paused and visitors see an unavailable page, unless you have configured auto-recharge or bought a credit pack. On the free tier you cannot buy credits at all and must wait for the next billing cycle. This is a meaningfully different failure mode from Vercel, which bills on demand past your included credit and only pauses if you configure spend management to do so.
How does Netlify’s credit system work?
One pool covers everything. Bandwidth costs 20 credits per gigabyte, compute 10 credits per gigabyte-hour, web requests 2 credits per ten thousand, and each production deploy costs 15 credits. Forms, deploy previews and branch deploys are free. Pro tiers run from 3,000 credits at $20 to 20,000 at $126, and tiers of 5,000 and above roll unused credits forward one cycle.
When did the pricing change?
Both platforms changed within a fortnight in late 2025. Netlify moved new accounts to credit-based pricing on September 4, 2025, and Vercel replaced its per-product allowances with seats plus a flexible usage credit on September 9, 2025. Netlify then made a further change on April 14, 2026, removing per-seat charges but doubling the credit cost of bandwidth and compute.
Which is better for a solo developer or side project?
Vercel’s Hobby tier is free but permits non-commercial use only, so anything earning money needs Pro at $20. Netlify’s free tier allows commercial use but gives only 300 credits, roughly 15 GB of bandwidth, and 20 production deploys will exhaust it. For a small commercial project, Netlify’s $9 Personal tier is often the cheapest legitimate starting point.
Can I move between them later?
Reasonably easily for a standard framework deployment, since both auto-detect common frameworks and both configure through a file in the repository. The friction is in platform-specific pieces: Netlify Forms, Vercel’s storage products, edge middleware behavior and any environment or deploy-context configuration. Note also that Netlify’s migration from legacy to credit-based pricing is irreversible, which is a separate decision from the platform itself.
