# What is Cloudflare Pages? Deploy websites from Git, free plan limits and switching to Workers

URL: https://opcaios.org/en/blog/cloudflare-pages-la-gi
Date: 2026-11-05
Author: Lê Quốc Nghĩa

What is [Cloudflare Pages](/tien-ich/cloudflare-pages)? Cloudflare Pages is Cloudflare's platform for deploying web applications to their global network: you connect a Git repository (GitHub or GitLab), upload a pre-built artifact directly (Direct Upload), or use a command-line tool, and Pages automatically builds, deploys, and creates preview versions for each branch; server-side code runs via Pages Functions. Pages is available on all plans; the Free plan, according to Cloudflare (as of 10/24/2026), offers 500 builds per month, free static file requirements, and unlimited bandwidth. However, the documentation also recommends **new projects should start with Workers**, and provides a guide for migrating from Pages to Workers.

This post covers: 1) how to deploy from Git; 2) plan-based limits; 3) how Functions pricing works; 4) when to choose Pages or Workers; 5) OPCAIOS's experience. For example, a static blog exported from Next.js or Hugo can run on Pages with almost no distribution costs.

![Cloudflare Pages diagram: Git repository, build, preview, production, Functions priced like Workers, Free plan limits, and recommendation to start new projects with Workers](https://opcaios.org/images/blog/cloudflare-pages-la-gi/so-do.webp)
*Pages deploys from Git and serves static files for free; new projects are recommended to start with Workers. Diagram: OPCAIOS.*

## What is Cloudflare Pages?

Cloudflare Pages is a platform for deploying full-stack applications to Cloudflare's global network, available on all plans, according to Cloudflare (as of 10/24/2026). There are three deployment methods: 1) connect a Git provider; 2) upload a pre-built artifact using Direct Upload; 3) use the C3 command-line tool. Server-side code runs via Pages Functions, requires no separate server, and you can instantly rollback to a previous production version. Cloudflare's documentation provides guides for frameworks like React, Hugo, and Next.js with static export. For example, a business introduction page written in Hugo is pushed to GitHub, then Pages builds it automatically, and finally deploys it each time there's a new commit on the production branch. Pages sits within Cloudflare's ecosystem; if you're new to the company, first read [What is Cloudflare?](/blog/cloudflare-la-gi). For new projects, the documentation recommends starting with Workers, so the comparison between Pages and Workers below is important.

## How does Git deployment work?

Git deployment is how Pages automatically builds and deploys each time you push code, and according to Cloudflare (as of 10/24/2026) consists of four steps.
- Step 1: go to Workers & Pages in the dashboard, choose to create a Pages application, then connect Git.
- Step 2: choose GitHub or GitLab, sign in, select a repository (public or private), then install and grant permissions.
- Step 3: set the project name (determines hostname), production branch (usually `main` or `master`), build command and output directory (pre-configured by framework), root directory for monorepos, and environment variables.
- Step 4: click save and deploy; the build log shows progress.

After connecting, pushing code to the production branch deploys the production version, while other branches create preview versions and pull requests get updated preview links. You can limit who views preview versions using Access policies. For example, the `feature-banner` branch has its own preview link for teammates to review before merging into `main`. For more on code repositories see [What is GitHub?](/blog/github-la-gi).

## What are Cloudflare Pages limits by plan?

Cloudflare Pages limits are ceiling levels that vary by Free, Pro, and Business plans, according to Cloudflare (as of 10/24/2026).
- Free plan: 500 builds per month, 1 concurrent build, 100 custom domains per project, 20,000 files per site.
- Pro plan: 5,000 builds, 5 concurrent builds, 250 domains, 100,000 files.
- Business plan: 20,000 builds, 20 concurrent builds, 500 domains, 100,000 files.
- Common limits: maximum build time of 20 minutes; each asset file maximum 25 MiB; 100 projects per account; new projects are restricted for the first 48 hours.

For example, a site with 30,000 files exceeds the Free plan limit and needs a paid plan. An important restriction: a project with integrated Git cannot switch to Direct Upload later. Files larger than 25 MiB should be stored in R2. Finally, paid plans require setting the environment variable `PAGES_WRANGLER_MAJOR_VERSION=4` to have higher file limits.

## How Does Pages Functions Charge?

Pages Functions is the server-side code part of Pages, and it charges like Workers, according to Cloudflare (read on 24/10/2026), through three rules.
- First, on the Free plan, Functions fall within the Workers Free limit of 100,000 requests per day, reset at midnight UTC.
- Next, on paid plans, Functions count toward the Workers Paid limit, including calls to KV or Durable Objects.
- Finally, **static file requests are free and unlimited** on both plans; a request is counted as static when it does not call Functions.

So static sites like landing pages, documentation, or static blogs cost almost nothing to distribute, and each request to Functions counts as one Workers request. For example, a static blog getting thousands of views per day still only creates static file requests, while a form calling Functions counts toward the 100,000 request limit. OPCAIOS has not read the detailed Workers Paid pricing, so I do not mention overage rates.

## Pages or Workers: Which Should You Choose?

Workers is the Cloudflare-recommended platform for new projects, according to Cloudflare (read on 24/10/2026), because Workers supports most Pages use cases and has a broader feature set. Pages still works and has official migration guides. The selection suggestions include three branches. First, if your site is running well on Pages and does not need new features, you can keep it. Next, new projects should start with Workers. Finally, if you need a domain outside Cloudflare, review the limits before switching, because Workers only supports domains with nameservers managed by Cloudflare. Cost is similar: static files are free on both, Functions charge at Workers rates. For example, a site needing Cron Triggers or Gradual Deployments must use Workers, because Pages has neither Cron Triggers nor Gradual Deployments. The migration steps include creating a Wrangler config file, replacing `pages_build_output_dir` with an assets directory, and converting `functions/` or `_worker.js` to a Worker.

### Key Differences Between Workers and Pages

The Pages documentation states outright that Workers supports most Pages use cases and has a broader feature set, and recommends starting new projects with Workers. According to the official migration guide, some key differences:

| Feature | Workers | Pages |
|---|---|---|
| Gradual Deployments | Yes | No |
| Cloudflare Vite Plugin | Yes | No |
| Workers Logs, Logpush, Tail Workers | Yes | No |
| Cron Triggers | Yes | No |
| Durable Objects | Yes | Requires separate Worker |
| Domains outside Cloudflare | No | Yes |
| File-based routing | Requires framework or build step | Yes |
| Branch deployment control | Partial | Yes |

The migration steps also include setting up 404 error handling for single-page applications and setting `run_worker_first` if you need to run the Worker before assets (for example, login checks). The `_headers` and `_redirects` files still work.

## Compared to Vercel and Self-Hosted on VPS

| Criteria | Cloudflare Pages | [Vercel](/tien-ich/vercel) | Self-Hosted VPS |
|---|---|---|---|
| Deploy from Git, preview builds | Yes | Yes | Build your own process |
| Static files | Free, unlimited | By plan and usage tier | By machine resources |
| Server-side code | Functions (charges like Workers) | Functions | Run separate process |
| Infrastructure control | Low | Low | Full control |

See also [What is Vercel?](/blog/vercel-la-gi), [What is VPS?](/blog/vps-la-gi), and [What is Nginx?](/blog/nginx-la-gi). The comparison table is a general description based on each platform's documentation, not measurement.

## OPCAIOS Experience

OPCAIOS uses Cloudflare as a distribution and protection layer in front of a private server, while the main website runs Next.js on a VPS behind nginx. To our current knowledge, we have no production projects running on Cloudflare Pages, so this post is based on official documentation rather than our actual measurements; we also have not tried the Pages-to-Workers migration process. From our experience placing Cloudflare in front of nginx, one general note: if you use Pages for a static site and VPS for your API, clearly separate subdomains and check the caching policy for each part.

Read more: [6 best website deployment platforms 2026 for non-specialists](/blog/nen-tang-deploy-website-tot-nhat).

## Frequently Asked Questions

### What is Cloudflare Pages?
It's Cloudflare's platform for deploying websites and web applications from Git, Direct Upload, or the command line, with preview for each branch and Functions for server-side code.

### Is Cloudflare Pages free?
Yes, on the Free plan: 500 builds per month, unlimited static file requests, and free; Functions count toward the 100,000 requests per day limit of Workers Free.

### Should new projects use Pages or Workers?
According to the official documentation, you should start new projects with Workers; Pages still works and has guides for migrating to Workers.

### Can I switch a Git project to Direct Upload?
No. A project already integrated with Git cannot be switched to Direct Upload; you can disable automatic deployment and use Wrangler instead.

### What is the file size limit?

Cloudflare Pages' file size limit is 25 MiB per asset file, according to Cloudflare (as read on 24/10/2026). Larger files should be placed on R2, Cloudflare's object storage service. Beyond size, there are three other limits to remember. First, the number of files per site is 20,000 on the Free plan and 100,000 on paid plans. Next, the maximum build time is 20 minutes. Finally, the `_headers` file has a maximum of 100 rules, while `_redirects` allows a maximum of 2,000 static redirects and 100 dynamic redirects. For example, a 200 MiB video cannot be placed directly as a site asset but needs to be on R2 and then embedded via a link. Limits can change, so check the official page again. To learn how to deploy websites and automate safely, see OPCAIOS's [AI application training course](/services/dao-tao-ung-dung-ai).

*Source: developers.cloudflare.com (Pages overview, Git integration, Limits, Functions pricing, guide to migrating from Pages to Workers), read directly on 24/10/2026. Limits and recommendations change over time; we have not reviewed Workers Paid pricing in detail. Experience is from OPCAIOS.*
