Cloudflare Pages

VPS & hostingEdgeLevel: IntermediateFree plan
Logo Cloudflare Pages

Cloudflare Pages

4.0/5OPCAIOS rating

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.

What is Cloudflare Pages and who is it for?

The OPCAIOS tools library files Cloudflare Pages under VPS & hosting: it is a VPS and hosting service. Short label: Edge. A service for hosting frontend websites on the Cloudflare network; Cloudflare now recommends new projects use Workers with static assets. 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. Best suited to: Businesses already using Cloudflare, dev teams building static websites and documentation. According to OPCAIOS, the editorial score of Cloudflare Pages is 4.0 out of 5: generous free plan; new projects should use Workers per Cloudflare's recommendation.

  • Platform: Web dashboard, CLI (Wrangler, C3), Git integration.
  • Difficulty to get started: intermediate.

Is Cloudflare Pages free, and what does it cost?

Cloudflare Pages is a service with a free plan, and its paid plans add limits and features. Free plan (500 builds/month) and paid plans by usage — see the official pricing page. Additionally, prices are set by the provider and can change, so compare with the official Cloudflare Pages site before you pay. To compare costs, the VPS & hosting group of the library also includes Supabase (free plan), Vercel (free plan), and Netlify (free plan).

What are the main features of Cloudflare Pages?

According to OPCAIOS, the standout strengths of Cloudflare Pages are runs on Cloudflare's network, generous free plan, and many ways to deploy, among others. Additionally, the list below explains each of the 5 recorded features.

  1. Runs on Cloudflare's network: The website is delivered through Cloudflare's global infrastructure, convenient if DNS is also on Cloudflare.
  2. Generous free plan: Per the limits documentation, the Free plan allows 500 builds per month and up to 20,000 files per site.
  3. Many ways to deploy: Connect Git, upload a folder directly, or create a project from the command line.
  4. The new direction is Workers: Cloudflare recommends new projects use Workers static assets, so consider it from the start to avoid migrating later.
  5. Combines with the ecosystem: Easy to pair with other Cloudflare services such as storage, databases and security.

When should you use Cloudflare Pages?

Cloudflare Pages is used for 4 kinds of work. When using Cloudflare Pages, the most typical case is A company website with the domain on Cloudflare. Additionally, the main audience is businesses already using Cloudflare, dev teams building static websites and documentation.

  1. A company website with the domain on Cloudflare: Bring DNS, SSL and hosting into one place, reducing the number of accounts to manage.
  2. Documentation pages or technical blogs: Build from Markdown with Hugo or Astro and publish automatically on every push.
  3. High-traffic landing pages: Static pages served through Cloudflare's network suit large ad campaigns.
  4. Frontend with a light API: With Workers, you can put the interface and a few form-handling endpoints in the same project.

How do you get started with Cloudflare Pages?

When using Cloudflare Pages for the first time, you go through 5 steps, which OPCAIOS rates as intermediate difficulty. The first step is to create a Cloudflare account, and the last is to attach a custom domain. The steps are listed in order below.

  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.
  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.

What is Cloudflare Pages?

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.

How much does Cloudflare Pages cost?

Free plan (500 builds/month) and paid plans by usage — see the official pricing page

Prices are set by the provider and can change; check the official site for the latest.

Key features of Cloudflare Pages

01

Runs on Cloudflare's network

The website is delivered through Cloudflare's global infrastructure, convenient if DNS is also on Cloudflare.

02

Generous free plan

Per the limits documentation, the Free plan allows 500 builds per month and up to 20,000 files per site.

03

Many ways to deploy

Connect Git, upload a folder directly, or create a project from the command line.

04

The new direction is Workers

Cloudflare recommends new projects use Workers static assets, so consider it from the start to avoid migrating later.

05

Combines with the ecosystem

Easy to pair with other Cloudflare services such as storage, databases and security.

What is Cloudflare Pages used 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 Cloudflare Pages

  1. 1

    Create a Cloudflare account

    Sign up and, if possible, move the domain's DNS to Cloudflare for centralized management.

  2. 2

    Decide between Pages and Workers

    For a new project, read the Pages overview page: Cloudflare recommends starting with Workers.

  3. 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. 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. 5

    Attach a custom domain

    In the project's Custom domains section, add the business domain and wait for SSL to be issued.

Cloudflare Pages 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: Cloudflare Pages

Illustrative scenario

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 for using Cloudflare Pages

  • 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.

Cloudflare Pages: frequently asked questions

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

Articles about this tool

Want to apply this in your business?

OPCAIOS looks at your workflows, picks the right tools and sets them up with your team. The first call is free.

Book a call