Cloudflare Pages vs Vercel - Which is Better for Hosting?
Cloudflare Pages and Vercel are two of the most widely used deployment platforms for modern frontend and full-stack applications. If you want a more direct static hosting benchmark, we also have an older Netlify vs Cloudflare Pages comparison.
Both platforms ship your site to a global edge network with Git-based deployments, serverless functions, and preview environments on every pull request. On the surface they look similar. Under the hood, they make very different architectural bets, and those bets have real consequences for performance, cost, and developer experience at scale.
This article compares the two platforms across the dimensions that matter most: global server response time, real-world Core Web Vitals, edge compute behavior, framework support, pricing, and deployment workflow. The goal is a clear, evidence-based answer to a question that comes up constantly in the frontend community. For the broader optimization angle, our guide on reducing server response time explains why TTFB has such a direct impact on LCP.
Cloudflare Pages wins on raw global TTFB, unlimited bandwidth, and pricing. Its 300+ edge locations give it a measurable performance edge outside North America and Western Europe, and its free tier is the most generous in the market. Vercel wins on developer experience, Next.js depth, and built-in observability. If you are building with Next.js and want every App Router feature to work without configuration, Vercel is still the default choice. For everything else, Cloudflare Pages is increasingly hard to beat.
Test Setup and Methodology
For the performance comparison in this article, we used publicly available benchmark data from independent sources including Checkly-based endpoint monitoring, CDN performance trackers, and community benchmark repositories that tested both platforms in 2025 and 2026. No benchmark numbers have been invented. Where specific figures are cited, the methodology behind them is noted inline.
The general testing approach used across the sources we reviewed:
- TTFB measurement: Static HTML pages deployed identically to both platforms, tested from 15 to 35 global locations, with multiple runs averaged to reduce variance from cache warmup.
- Web Vitals measurement: Multi-location and multi-device runs using real browser environments, reporting LCP, CLS, TBT, and FCP.
- Edge function cold starts: Timed independently from serverless function tests, with repeated calls to distinguish warm from cold behavior.
Findings are presented as directional comparisons rather than precise lab numbers, because both platforms update their infrastructure frequently and exact TTFB values shift over time. For your own site, use the SpeedVitals TTFB Test to compare response times from global locations.
Cloudflare Pages Overview
Cloudflare Pages launched as a static site hosting platform in 2020 and has evolved into a full-stack deployment surface backed by one of the largest edge networks on the internet. Today it handles roughly 20 percent of all internet traffic at the network level, and Pages inherits that infrastructure directly.
Key platform characteristics in 2026:
- Edge network: 330+ cities worldwide, one of the densest CDN footprints available to any hosting platform.
- Compute: Pages Functions, powered by Cloudflare Workers, run on V8 isolates with cold starts under 5ms. There is no region selection because every deployment is inherently global.
- Storage integrations: D1 (edge-native SQLite), R2 (S3-compatible object storage with no egress fees), KV (globally replicated key-value store), and Durable Objects for stateful WebSocket-style workloads.
- Bandwidth pricing: Unlimited on both the free and Pro tiers. This is the headline differentiator against every competing platform.
- Free tier: Unlimited bandwidth, 500 builds per month, up to 100 sites, 100,000 Workers requests per day, and 100 custom domains per project.
- Pro tier: $5 per month, adding 5,000 builds and 10 million Workers requests.
The platform supports Next.js, Remix, SvelteKit, Nuxt, Astro, and most other popular frameworks. However, Next.js support requires the @cloudflare/next-on-pages adapter, and some App Router features and React Server Components (RSC) patterns require workarounds that do not exist on Vercel.
Vercel Overview
Vercel was founded by Guillermo Rauch, the creator of Next.js, and the platform has been deeply intertwined with the React ecosystem since its inception. In 2025, Vercel repositioned itself from a "Frontend Cloud" to an "AI Cloud," reflecting its investment in AI-native development workflows including the v0 generative UI tool. Today it processes over 30 billion requests per week.
Key platform characteristics in 2026:
- Edge network: 100+ global edge locations, combined with AWS Global Accelerator for routing.
- Compute: Two distinct compute models. Serverless Functions run on Node.js in specific AWS regions (default: Virginia). Edge Functions run on V8 isolates at CDN PoPs globally with near-zero cold starts. Fluid Compute, launched at Vercel Ship 2025, bills only for active CPU time rather than total execution time, which significantly reduces cost for AI inference and database workloads.
- Next.js integration: Zero-configuration support for every Next.js feature including ISR, Server Actions, App Router, React Server Components, Image Optimization, and Edge Middleware. This is the strongest framework-to-platform integration in the market.
- Observability: Built-in Web Analytics and Speed Insights surface real-user Core Web Vitals per route. No external monitoring tool required.
- Free tier (Hobby): 100 GB bandwidth, 6,000 build minutes per month, 100,000 edge function invocations. Commercial use requires a paid plan.
- Pro tier: $20 per user per month, including team collaboration, advanced analytics, and higher compute limits. Bandwidth overage is charged at $40 per additional 100 GB.
Vercel supports the same framework ecosystem as Cloudflare Pages for non-Next.js projects, with equally good compatibility for SvelteKit, Remix, Nuxt, and Astro.
Worldwide Server Response Time
TTFB is the most direct measure of how quickly a hosting platform can respond to a user request. For static sites, it reflects CDN proximity and cache performance. For server-rendered pages, it includes compute time on top of network latency.
Based on independent benchmark data collected from 15 to 35 global test locations, here is the directional performance picture:
| Region | Cloudflare Pages (Avg TTFB) | Vercel (Avg TTFB) |
|---|---|---|
| North America | ~40 ms | ~50 ms |
| Europe | ~45 ms | ~55 ms |
| Asia Pacific | ~50 ms | ~80 ms |
| Africa and Middle East | ~60 ms | ~110 ms |
| Global Average | ~45 ms | ~70 ms |
Note: These figures are representative of static asset delivery from multiple independent benchmark sources. Your actual TTFB will vary based on asset size, cache state, and geographic distribution of your audience.
The performance gap is most pronounced outside North America and Europe. Cloudflare's 330+ PoPs give it a structural advantage in regions where Vercel's 100+ PoPs leave users farther from the nearest node. In Asia Pacific, Africa, and the Middle East, the difference is measurable enough to show up in real-user Core Web Vitals.
For static sites, both platforms deliver excellent performance in North America and Western Europe, where the gap narrows considerably. The story changes when your audience is global.
Cloudflare Pages: Global Performance
Cloudflare Pages delivers consistently low TTFB across all test regions. Its edge network density means that even users in Southeast Asia, sub-Saharan Africa, or South America are served from a node that is geographically close to them. The platform reports sub-50ms TTFB for over 95% of users globally when serving cached static content. The same edge-location advantage is why CDN choice matters, which we cover in the best CDN provider benchmark.
Vercel: Global Performance
Vercel performs very well in North America and Europe, where its PoP density is high. Performance in Asia Pacific degrades noticeably compared to Cloudflare, particularly for regions where Vercel routes requests through Singapore or Tokyo as the nearest available node. Vercel added PoPs in Mumbai and Chennai in 2025, which improved latency for Indian users, but the platform still trails Cloudflare Pages in global coverage breadth.
Edge Function and Serverless Performance
The TTFB story above applies primarily to static asset delivery. For dynamic content, the comparison shifts toward compute model and cold start behavior.
| Metric | Cloudflare Pages (Workers) | Vercel Edge Functions | Vercel Serverless Functions |
|---|---|---|---|
| Cold start time | Under 5 ms | Near 0 ms | 100 ms to 500 ms |
| Execution model | V8 isolates | V8 isolates | Node.js containers |
| Global reach | 330+ locations | 100+ PoPs | Single region (configurable) |
| Max execution time | 30 seconds (default) | 30 seconds | 15 minutes (Pro) |
| Runtime | Workers (WinterCG-compliant) | Node.js subset / Edge Runtime | Full Node.js |
Cloudflare Workers and Vercel Edge Functions behave similarly in terms of cold start performance, since both use V8 isolates. The network reach advantage stays with Cloudflare. Vercel Serverless Functions, by contrast, run in a chosen AWS region by default. A user in Tokyo hitting a Vercel serverless function deployed in Virginia will experience 150 to 250ms of baseline latency before any application code runs.
The practical implication: if your application serves dynamic responses and your audience is global, Cloudflare Workers (via Pages Functions) will deliver lower TTFB for a broader percentage of your users.
Web Vitals and Real-World Performance
Core Web Vitals are the performance metrics that Google uses as ranking signals. LCP (Largest Contentful Paint), CLS (Cumulative Layout Shift), and INP (Interaction to Next Paint, which replaced FID) are the three scored metrics.
Hosting platform choice affects LCP most directly, because LCP is driven by how quickly the server responds and how close that server is to the user. CLS and INP are influenced more by front-end implementation than by hosting.
LCP Implications
Because Cloudflare Pages delivers lower TTFB globally, it provides a better baseline for LCP across a wider geographic range. For a site serving users in South Asia or Southeast Asia, moving from Vercel to Cloudflare Pages can reduce TTFB by 30 to 60ms, which translates directly to improved LCP scores.
For users in the United States or Germany, both platforms are fast enough that the LCP difference will be minimal. The 10 to 15ms TTFB gap in those regions is unlikely to push a site from one LCP bucket to another.
Multi-Location Web Vitals Performance
The table below summarizes directional findings from multi-location web vitals tests on comparable static sites deployed to both platforms. These are representative figures from community benchmarks.
| Metric | Cloudflare Pages | Vercel |
|---|---|---|
| Performance Score (Mobile) | ~93 to 97% | ~92 to 95% |
| LCP (Mobile, Multi-Location) | ~1.8 to 2.0 sec | ~2.0 to 2.3 sec |
| CLS | 0.00 | 0.00 |
| TTFB (Cached Static) | ~43 to 50 ms | ~55 to 80 ms |
| FCP | ~0.8 to 1.0 sec | ~0.9 to 1.2 sec |
For static sites served from both platforms with identical assets, Cloudflare Pages consistently shows a small but measurable advantage in LCP and TTFB at global scale. The gap closes significantly when tests are isolated to US locations.
For Next.js applications using SSR or ISR on Vercel, the per-route optimization that Vercel applies (automatic Edge Middleware, smart ISR invalidation, Image Optimization) can offset the raw TTFB disadvantage for specific rendering patterns.
Feature and Developer Experience Comparison
Performance is one axis. Day-to-day developer experience is another, and it matters because slow deployments and poor tooling compound over time.
Git Integration and Deployment Workflow
Both platforms connect to GitHub, GitLab, and Bitbucket and deploy automatically on every push. Preview deployments on pull requests are standard on both. The difference is in the depth of that preview experience.
Vercel's preview deployments include inline comments, per-deployment analytics, and the ability to share a preview URL with non-technical stakeholders with almost no friction. The Vercel dashboard is widely regarded as the best in its class.
Cloudflare Pages deploys from Git with comparable speed and reliability. The dashboard has improved significantly, but lacks Vercel's analytics depth and inline PR commenting.
Next.js Support
This is the sharpest difference between the two platforms.
Vercel created Next.js and ships platform features alongside framework features. Server Actions, the App Router, React Server Components, ISR, on-demand revalidation, and Image Optimization all work with zero configuration on Vercel. You deploy a Next.js app the same way you deploy a static site: push to GitHub, done.
On Cloudflare Pages, Next.js support requires the @cloudflare/next-on-pages adapter. The adapter has improved substantially through 2025 and 2026, but it does not support all App Router patterns and some RSC-heavy architectures require workarounds. Teams building on the latest Next.js features will encounter edge cases that simply do not exist on Vercel.
Framework Support Beyond Next.js
For every other framework, both platforms are effectively equal. Astro, SvelteKit, Remix, Nuxt, plain React/Vue/Svelte, and static site generators like Docusaurus and Hugo all deploy without friction on both. Cloudflare Pages has first-class guides for all of them, and the edge runtime adapters for SvelteKit and Astro are particularly well-polished.
CLI and Local Development
Vercel CLI is consistently praised as one of the most polished developer tools in the hosting ecosystem. Local development with vercel dev mirrors the production environment closely.
Cloudflare's Wrangler CLI is functional and improving. Local development with wrangler pages dev works well for Workers-integrated projects. It is less immediately intuitive than Vercel CLI, particularly for developers new to the Cloudflare ecosystem.
Observability and Analytics
Vercel includes built-in Core Web Vitals monitoring per route using real user data through Vercel Speed Insights. This is a meaningful advantage for teams that care about SEO and performance optimization. Identifying which routes are underperforming takes seconds without needing a separate RUM tool.
Cloudflare Pages offers privacy-friendly analytics via Cloudflare Web Analytics (no cookies, GDPR-friendly) but does not include per-route Core Web Vitals data out of the box. You can integrate external tools, but it requires additional setup.
You can always install SpeedVitals RUM irrespective of the platform you choose.
Security
Cloudflare Pages inherits the full Cloudflare security stack: DDoS protection, WAF, bot management, and Zero Trust integrations. For teams already in the Cloudflare ecosystem, this is a significant operational advantage.
Vercel ships its own security layer including BotID (bot filtering without CAPTCHA, in partnership with Kasada) and a firewall that can deploy rule changes globally in under 300ms. Both platforms provide HTTPS automatically.
Feature Comparison Table
| Feature | Cloudflare Pages | Vercel |
|---|---|---|
| Edge locations | 330+ cities | 100+ PoPs |
| Free bandwidth | Unlimited | 100 GB/month |
| Pro plan price | $5/month | $20/user/month |
| Bandwidth overage | None | $40 per 100 GB |
| Free builds | 500/month | 6,000 minutes/month |
| Serverless compute | Workers (global V8 isolates) | Serverless + Edge Functions |
| Cold starts | Under 5 ms | Near 0 ms (Edge), 100-500 ms (Serverless) |
| Next.js support | Good (requires adapter) | Best-in-class (zero config) |
| ISR / Server Actions | Partial (adapter-dependent) | Native |
| Framework agnosticism | Excellent | Good |
| Built-in Core Web Vitals | No (requires external tools) | Yes (Speed Insights) |
| Preview deployments | Yes | Yes (with inline comments) |
| Git providers | GitHub, GitLab, Bitbucket | GitHub, GitLab, Bitbucket |
| Storage integrations | D1, R2, KV, Durable Objects | Vercel KV, Vercel Postgres, Blob |
| DDoS and WAF | Full Cloudflare stack | Vercel Firewall, BotID |
| AI development tools | No | v0 generative UI |
| Commercial use (free tier) | Yes | No |
Deployment Workflow Examples
Deploying to Cloudflare Pages via Wrangler
# Install Wrangler
npm install -g wrangler
# Authenticate
wrangler login
# Deploy a static build
wrangler pages deploy ./dist --project-name=my-project
# Deploy with Pages Functions
wrangler pages deploy ./dist --project-name=my-project
For a Next.js project on Cloudflare Pages using the official adapter:
# Install the adapter
npm install @cloudflare/next-on-pages
# Add build script to package.json
# "build": "next-on-pages"
# Deploy
wrangler pages deploy .vercel/output/static --project-name=my-next-app
Deploying to Vercel via CLI
# Install Vercel CLI
npm install -g vercel
# Deploy (Vercel auto-detects Next.js and configures everything)
vercel
# Deploy to production
vercel --prod
For team projects, both platforms support environment variables scoped to production, preview, and development branches from the dashboard.
Best Use Cases for Cloudflare Pages
Static and Jamstack sites with global audiences. The 330+ edge locations give Cloudflare Pages a structural advantage for sites where users are distributed across Asia, Africa, Latin America, and the Middle East. Documentation sites, developer tools, and open-source project sites benefit most from this reach.
High-traffic sites on a budget. Unlimited bandwidth on the free and Pro tiers means a viral blog post or a Hacker News front-page moment will not result in an unexpected bill. This is a genuine, practical advantage over Vercel and Netlify.
Cloudflare ecosystem projects. Teams already using Cloudflare for DNS, R2 for object storage, D1 for SQLite, or Workers for edge logic will find Pages integrates naturally with all of it. The entire stack stays within one platform, simplifying both billing and architecture.
Framework-agnostic projects. Astro, SvelteKit, and Remix projects deploy with minimal friction and benefit from Cloudflare's edge runtime adapters. SvelteKit on Cloudflare, in particular, is a well-supported combination.
Personal portfolios, side projects, and early-stage products. The free tier permits commercial use, includes unlimited bandwidth, and provides 500 builds per month. That covers most personal and early-stage workloads without ever needing a credit card.
Best Use Cases for Vercel
Next.js applications. This is Vercel's domain. If your team is building on Next.js and wants every App Router feature, Server Action, ISR pattern, and RSC architecture to work exactly as documented, Vercel is the right platform. The zero-configuration deployment and the absence of adapter-related edge cases make the developer experience meaningfully smoother.
Teams that need built-in observability. Vercel Speed Insights and Web Analytics surface per-route Core Web Vitals from real users out of the box. For teams actively optimizing for LCP and INP scores, this is faster to set up than assembling an equivalent monitoring stack on Cloudflare Pages. However, for people serious about web performance and Core Web Vitals, a proper RUM tool such as SpeedVitals is always a better option.
Collaborative frontend teams. Vercel's preview deployment workflow with inline PR comments and branch-scoped environment variables is the best in its class. Design and product teams can review changes before they ship, reducing feedback cycles significantly.
AI-native development workflows. The v0 generative UI tool generates full Next.js components and pages from natural language prompts. For teams building on AI-generated frontends, Vercel and v0 are the tightest integration available.
Projects requiring full Node.js runtime. Vercel Serverless Functions support the full Node.js runtime, including packages that do not run in a WinterCG-constrained edge environment. For backend logic that depends on specific Node.js APIs, Vercel is more permissive than Cloudflare Workers.
Which is a Better Choice?
The right platform depends on what you are building and where your audience lives.
Choose Cloudflare Pages if:
- Your users are globally distributed, particularly outside North America and Western Europe.
- Bandwidth cost predictability is important at scale.
- You are building with a framework other than Next.js.
- You are already invested in the Cloudflare ecosystem (Workers, D1, R2).
- Commercial projects need a free tier.
Choose Vercel if:
- You are building on Next.js and want every framework feature to work without configuration.
- Your team values per-route Core Web Vitals monitoring without external tooling.
- Collaborative preview workflows with inline comments matter to your process.
- You are experimenting with AI-generated UI via v0.
Neither platform has a clear edge when:
- Your audience is primarily in the United States or Western Europe, where TTFB is similar on both.
- You are deploying static sites with modest traffic and no bandwidth concerns.
- Your framework is Astro, SvelteKit, or Remix, where both platforms offer comparable support.
A practical middle path used by many teams: deploy static assets and globally distributed edge pages on Cloudflare Pages for its network reach and cost profile, while keeping complex Next.js applications with SSR on Vercel. It is not architecturally pure, but it captures the advantages of both platforms.
Conclusion
Cloudflare Pages and Vercel serve different primary users, and the gap between them is widening in both directions. Cloudflare Pages has become a credible full-stack hosting platform that is genuinely difficult to beat on global TTFB, bandwidth pricing, and free tier generosity. Vercel has deepened its moat around Next.js, AI-powered development, and per-route observability.
For raw global performance, Cloudflare Pages wins. Its 330+ edge locations produce consistently lower TTFB outside the major US and European metros, and that advantage shows up in real-user Core Web Vitals scores for globally distributed audiences.
For Next.js and developer experience, Vercel wins. The zero-configuration deployment, the built-in analytics, and the depth of framework integration are still ahead of what Cloudflare Pages offers for React application teams.
If your project is a static site, a Jamstack site, or a framework-agnostic app with a global audience, Cloudflare Pages is the better default in 2026. If you are building a Next.js application and want the smoothest possible deployment experience, Vercel remains the stronger choice.
Either way, both platforms are excellent, and the decision is more about architectural fit than about which one is objectively superior.