Tried deploying Next.js on Cloudflare with OpenNext but hit caching problems and runtime errors.
79signal
104reviewsi
A score out of 100. Negative and mixed reviews take points off, and so does having only a few reviews, so a handful of glowing reviews can’t beat a product many people like.
77% Positive18% Negative
Generous free tier and fast static hosting, but server-side frameworks sent some back to Vercel.
What customers love, and what they don’tWhat customers noticed
Also mentioned: best for developers1
Customer reviews (104)
Add your reviewShowing 32 reviews mentioning easy to use Show all
Deploying a Next.js app to Cloudflare Pages hit many Edge Runtime incompatibility errors that were only solved by moving to Workers.
Could not get a Lovable site migrated to Cloudflare Pages and found its control panel like operating a space station.
Built their site with Porkbun, Cloudflare and GitHub; Netlify ran out of commits so they moved to Cloudflare, which worked really well.
Deploying a TanStack Start site to Cloudflare Pages was messy until they dropped the plugin and prerendered statically, after which Pages served the output properly.
Moved a Kickstarter landing page from Lightsail WordPress to Cloudflare Pages with Supabase and is very satisfied with the setup.
Deploying Next.js with OpenNext to Cloudflare Workers has been challenging, with missing features and a specific required setup.
Had Claude Code build a static site on free GitHub and Cloudflare, costing about $3.50 a month with domain and Claude.
Came from Netlify to Cloudflare, finds it easier to use and simple to connect a custom domain.
Built a GitHub plus Cloudflare Pages workflow that is straightforward and publishes a site in under 5 minutes at no extra cost per site.
Auto-deployment on Cloudflare Pages started failing on env-var imports after a UI-only change, forcing manual wrangler builds and deploys.
First time using Cloudflare, found deploying a React/Vite fan app to Pages super easy, with only a ~$10 domain as cost.
Has published SvelteKit apps to Cloudflare Pages for years for free without issue: pushes auto deploy and are live within seconds with no config.
Hit the 10ms CPU limit on Cloudflare in a single test todo app and found the configuration obtuse and chaotic.
Runs a SvelteKit app on Cloudflare Pages and found it very straightforward to set up.
Uses Cloudflare Pages with GitHub Actions so pushes to the branch go live within about 30 seconds.
Is a big fan of Cloudflare Pages for Next.js, cheaper and much less of a headache than Vercel.
Gave up on Cloudflare because the Worker runtime could not run their PDF generation, so they containerized the app and hosted it elsewhere.
Found working with Cloudflare Pages insanely frustrating, struggling for weeks to get SvelteKit set up and logging working.
Chose Cloudflare Pages over Vercel and has had a great experience so far.
Found deploying Next.js to Cloudflare pretty straightforward, with a really smooth adapter.
Gave up deploying a Next.js 15 app with dynamic routes to Cloudflare Pages because it was too annoying and used Vercel instead.
Runs a Next.js 15 app with Auth.js and role-based access on Cloudflare without OpenNext.
Fought with next-on-pages on Cloudflare Pages before giving up because of the many limitations they had to build around.
Testing Next.js 13 on Cloudflare Pages gave poor results: every server route must use the Edge Runtime and next/image optimisation is not supported out of the box.
Wanted to go fully Cloudflare for a SvelteKit service but hit Node compatibility issues with Pages and used Vercel instead.
Spent hours failing to deploy a Turborepo Remix monorepo through Cloudflare git deployments, while Netlify and Vercel worked as expected.
Runs their site as Astro SSR on Cloudflare Pages through the framework adapter.
Runs about 10 SvelteKit sites on Cloudflare Pages and finds setup pretty straightforward by following the docs.
Finds Cloudflare Pages pleasant for static sites with better pricing than Vercel and plans to move personal projects there.
Has found Cloudflare Pages completely seamless for deploying dozens of SvelteKit apps and integrating with Workers, Queues, R2 and KV.
Finds SvelteKit great on Cloudflare Pages, praising the ease of deployment and quick prod testing, though the edge needs a different architecture.
Common questions about Cloudflare Pages
What do customers say about Cloudflare Pages?
Customers praise a generous free tier, very fast static hosting and easy deploys from GitHub, often after leaving Vercel or Netlify. The frustrations are mostly with server-side frameworks, especially Next.js, where runtime limits, missing Node features and build failures sent some back to Vercel.
Is Cloudflare Pages worth it?
Of the 66 reviews with a clear verdict, 77% are positive, 5% mixed and 18% negative. The praise mentioned most is good free plan. The most common complaint is poor support.
What do people like about Cloudflare Pages?
The praise reviewers mention most: good free plan (28 reviews), easy to use (24 reviews) and reliable (12 reviews). For example: Calls Cloudflare Pages honestly incredible, costing nothing for a site with over 100,000 monthly active users.
What are the most common complaints about Cloudflare Pages?
The complaints reviewers mention most: poor support (1 review).
What does the signal score of 79 mean?
It's how well reviewed Cloudflare Pages is, out of 100. Negative and mixed reviews take points off, and so does having only a few reviews: a service needs plenty of them, compared with the most-reviewed services here, to reach the high 80s and 90s. It's worked out from reviews only, needs at least 5 of them, and updates as new ones come in.
What are the specs of Cloudflare Pages?
Category: Static & frontend hosting. Free plan: Yes.
Where do these Cloudflare Pages reviews come from?
104 are quotes from Reddit, each linked to the original. Customer reviews are checked for spam before they appear. Every review, written here or quoted, is read as positive, mixed or negative.