Cloudflare Pages
Cloudflare Pages
Generous free plan; new projects should use Workers per Cloudflare's recommendation.
A service for hosting frontend websites on the Cloudflare network; Cloudflare now recommends new projects use Workers with static assets.
Overview
Cloudflare Pages is a service that builds and hosts frontend websites on Cloudflare's network, within the Workers platform. You can connect a Git repository to build automatically, upload an already-built folder directly, or create a project with the command-line tool.
Something to know before choosing: Cloudflare's official documentation now recommends starting new projects with Workers, because Workers already supports most Pages scenarios and has more features. Workers static assets lets you serve a static website and processing code in a single deployment. Pages still works for existing projects, and Cloudflare has a guide for migrating from Pages to Workers.
This option suits businesses that already manage their domain on Cloudflare and want a fast-loading, low-cost static website. It is not a place to run n8n or Docker; those services need a separate VPS.
Highlights
Runs on Cloudflare's network
The website is delivered through Cloudflare's global infrastructure, convenient if DNS is also on Cloudflare.
Generous free plan
Per the limits documentation, the Free plan allows 500 builds per month and up to 20,000 files per site.
Many ways to deploy
Connect Git, upload a folder directly, or create a project from the command line.
The new direction is Workers
Cloudflare recommends new projects use Workers static assets, so consider it from the start to avoid migrating later.
Combines with the ecosystem
Easy to pair with other Cloudflare services such as storage, databases and security.
What it's for
A company website with the domain on Cloudflare
Bring DNS, SSL and hosting into one place, reducing the number of accounts to manage.
Documentation pages or technical blogs
Build from Markdown with Hugo or Astro and publish automatically on every push.
High-traffic landing pages
Static pages served through Cloudflare's network suit large ad campaigns.
Frontend with a light API
With Workers, you can put the interface and a few form-handling endpoints in the same project.
How to use it
- 1
Create a Cloudflare account
Sign up and, if possible, move the domain's DNS to Cloudflare for centralized management.
- 2
Decide between Pages and Workers
For a new project, read the Pages overview page: Cloudflare recommends starting with Workers.
- 3
Create a project with C3
The sample command in the Workers static assets docs creates a ready-to-deploy React project.
$npm create cloudflare@latest -- my-react-app --framework=react - 4
Or connect Git in the dashboard
Choose a GitHub/GitLab repo and set the build command and output folder so Cloudflare builds on every push.
- 5
Attach a custom domain
In the project's Custom domains section, add the business domain and wait for SSL to be issued.
Video guides
3 Ways to Deploy Static to Cloudflare: Pages, Worker With Assets and R2
Ana's Dev Scribbles
Deploy to Cloudflare Workers & Pages in 10 minutes - Complete overview with a Database & Domain
backpine labs
Real-world example
A small software company in Da Nang already uses Cloudflare to manage DNS for its main domain. When it needs a customer documentation site, the dev team writes content in Markdown, builds a static site and deploys it to Cloudflare using Workers static assets as the documentation recommends. Each time the guides are updated, they just push to GitHub and the site rebuilds itself without any server to manage.
Tips & notes
Choose Workers for new projects
Follow the current recommendation to avoid migrating from Pages later.
Note the build limits
The Free plan runs only 1 build at a time, so avoid configuring rebuilds for every branch unnecessarily.
Check file sizes
Each static file is at most 25 MiB; videos or large files should go on a separate storage service.
Protect your account
Turn on two-factor authentication and create an API token with limited permissions for CI instead of using a full-access key.
FAQ
Is Cloudflare Pages being discontinued?
The documentation does not currently say Pages is ending, but it recommends new projects start with Workers and has a guide for migrating from Pages to Workers.
What does the free plan limit?
Per the Pages limits page: 500 builds per month, 1 concurrent build, 20,000 files per site and each file at most 25 MiB.
Can it run n8n?
No. n8n needs an always-on server; use a VPS such as Hetzner, DigitalOcean or Vultr.
Can a Next.js website run on it?
Possibly, but support depends on the framework and configuration; read the framework guide in Cloudflare's documentation before choosing.
Useful links
Want to apply this in your business?
2dm looks at your workflows, picks the right tools and sets them up with your team. The first call is free.
Same topic
Supabase
4.5
An open-source backend platform on Postgres, with pgvector for storing AI embeddings.
Vercel
4.5
A platform for deploying websites and frontend apps, especially strong with Next.js: push code to Git and you get a live version with a preview link.
Netlify
4.0
A deployment platform for static websites and Jamstack: drag and drop a folder or connect Git to get a live site, with forms, serverless functions and SSL.