# How to Deploy a Static HTML Site on Cloudflare Pages with One-Click Publishing from GitHub
Static websites are fast, secure, and easy to maintain. If you’re looking for a free, high-performance hosting solution that integrates seamlessly with your GitHub workflow, **Cloudflare Pages static site deployment** is the way to go. In this guide, we’ll walk through everything you need to know to set up a static HTML site on Cloudflare Pages, enable one-click publishing from GitHub, and even compare it to other quick-start options like HTMLPUT for instant deployments.
## Why Cloudflare Pages for Static Sites?
Cloudflare Pages is a JAMstack platform that offers global CDN distribution, automatic SSL, and generous free tier limits. It’s built for developers who want to deploy static assets (HTML, CSS, JavaScript) with minimal configuration. The platform integrates directly with GitHub repositories, allowing you to trigger a new build every time you push code.
The magic of **Cloudflare Pages static site deployment** lies in its simplicity: you connect your GitHub repo, choose a branch, and Cloudflare handles the rest — builds, deploys, and serves your site on its edge network. No server management, no complex CI/CD pipelines.
## Prerequisites
Before we dive into the deployment steps, make sure you have:
– A GitHub account (free tier works fine)
– A Git repository containing your static HTML site (index.html, CSS, JS, assets)
– Basic familiarity with Git commands (or a GUI tool)
– (Optional) A custom domain if you want to use your own URL
## Step-by-Step Guide to Deploying a Static HTML Site on Cloudflare Pages
### 1. Prepare Your GitHub Repository
Your static site should have an `index.html` at the root. Cloudflare Pages supports any framework (or no framework), but for a plain HTML site, just push your files to a GitHub repository. For example:
“`
my-static-site/
├── index.html
├── css/
│ └── style.css
├── js/
│ └── app.js
└── images/
└── logo.png
“`
Commit and push to a branch (usually `main` or `master`).
### 2. Log into the Cloudflare Dashboard
Go to [dash.cloudflare.com](https://dash.cloudflare.com) and sign in. If you don’t have an account, create one (free). Navigate to **Pages** from the left sidebar.
### 3. Connect Your GitHub Account
Click **Create a project** → **Connect to Git**. You’ll be asked to authorize Cloudflare Pages to access your GitHub repositories. Grant the necessary permissions (read-only for public repos, or full access for private repos).
### 4. Select Your Repository and Branch
After authorization, you’ll see a list of your repositories. Choose the one containing your static HTML site. Then select the branch you want to deploy (e.g., `main`). Cloudflare Pages will automatically detect that it’s a static HTML project.
### 5. Configure Build Settings
For a plain HTML site, you don’t need a build command or output directory. Cloudflare Pages will use the default: **Build command:** (leave empty) and **Build output directory:** `/`. However, if you have a framework like Hugo or Jekyll, you’d specify the appropriate command.
Once you click **Save and Deploy**, Cloudflare will clone your repo, run the build (if any), and deploy the output. You’ll see a progress log.
### 6. Enjoy One-Click Publishing from GitHub
After the first deployment, every time you push new commits to the connected branch, Cloudflare will automatically rebuild and redeploy your site. This is the **one-click publishing** experience — you only need to click “push” on GitHub, and Cloudflare handles the rest.
You can also trigger a manual redeploy from the Cloudflare Pages dashboard if needed.
### 7. Assign a Custom Domain (Optional)
By default, Cloudflare Pages assigns a `.pages.dev` subdomain (e.g., `your-site.pages.dev`). To use your own domain:
– Go to your project page in Cloudflare Pages.
– Click **Custom domains**.
– Enter your domain (e.g., `www.example.com`).
– Follow the DNS instructions — Cloudflare can manage your DNS if your domain is already on Cloudflare, or you can add a CNAME record at your registrar.
## What About Static Site Generators?
If your static site is generated by a tool like Hugo, Jekyll, Next.js (static export), or Eleventy, Cloudflare Pages can still deploy it with zero configuration. For example, for a Hugo site, you’d set the build command to `hugo` and the output directory to `public`. Cloudflare Pages supports Node.js, Python, Go, and many other runtimes.
## Auto-Deploy with One-Click Publishing
The phrase “one-click publishing” is the hallmark of Cloudflare Pages: once your repo is connected, every `git push` is a deploy. No need to log into any dashboard. This is ideal for teams working on documentation sites, personal blogs, or marketing landing pages.
But what if you want an even simpler solution that doesn’t require a GitHub account at all? That’s where platforms like HTMLPUT come in.
## Alternative: Deploy Static HTML Instantly with HTMLPUT
While **Cloudflare Pages static site deployment** is powerful and free, it does require a Git workflow. Sometimes you just need to throw a single HTML page online in seconds — no repositories, no commands.
HTMLPUT is a free web hosting platform that lets you deploy static HTML pages instantly. With one-click deployment and Cloudflare CDN out of the box, it’s ideal for quick prototypes, single-page landing pages, or sharing HTML snippets. You can even password-protect your pages or generate HTML using AI assistance.
If you’re already comfortable with Cloudflare Pages, you can also use [HTMLPUT](https://htmlput.com) as a complementary tool for those “I need a quick URL” moments. Check out the [HTMLPUT blog](https://blog.htmlput.com) for tips on combining static hosting approaches.
## Troubleshooting Common Deployment Issues
### Error: “Build failed with no output”
If you’re deploying a plain HTML site and you left the build fields empty, this shouldn’t happen. But if you accidentally set a build command, Cloudflare will try to execute it. Make sure your site files are in the root of the repository, and the build output directory is either empty or set to the root (`/`).
### Error: “404 Not Found”
This usually occurs when your `index.html` is not in the root or your build output directory is misconfigured. Double-check that your repo has an `index.html` at the top level.
### Custom domain not resolving
If you’re using a domain on Cloudflare, make sure the DNS record is a CNAME to your `pages.dev` domain. If the domain is external, you may need to wait for DNS propagation (up to 24 hours, but usually minutes).
## Best Practices for Cloudflare Pages Static Site Deployment
– **Use environment variables** for any API keys or configurations — Cloudflare Pages supports them.
– **Leverage preview deployments** for staging branches — every branch you push gets a unique URL.
– **Enable automatic HTTPS** (it’s on by default) for all custom domains.
– **Use the Cloudflare Pages dashboard** to view deployment logs and rollback to previous versions.
– **Combine with Cloudflare Workers** if you need serverless functions alongside your static site.
## Why Cloudflare Pages is a Top Choice for Static Hosting
Cloudflare Pages offers everything a developer needs for **static site hosting**:
– Global edge network with 250+ data centers
– Free tier includes unlimited bandwidth and 500 builds per month
– Instant cache invalidation on new deploys
– Automatic SSL/TLS certificates
– Support for popular static site generators
Compared to other free hosts like GitHub Pages or Netlify, Cloudflare Pages often delivers faster response times due to its massive CDN. And because it’s integrated with Cloudflare’s DNS, performance optimizations are seamless.
## Conclusion
Deploying a static HTML site on Cloudflare Pages with one-click publishing from GitHub is one of the most efficient ways to go from code to live website. The entire process — from connecting your repository to seeing your site live on a global CDN — takes less than five minutes. For team projects, blogs, or portfolio sites, this workflow is hard to beat.
And if you ever need to deploy a single HTML file without a Git repo, remember that HTMLPUT offers an even quicker alternative for those on‑the‑go publishing needs. Whether you choose Cloudflare Pages or HTMLPUT, you’re getting fast, reliable, and free static hosting.
Now go ahead and push your next static site — you already know the steps.