How to Upload a Website to Cloudflare Without Git (Direct Upload)

Updated September 23, 2026 · 11 min read

Upload a static HTML site to Cloudflare by drag and drop, without Git. Steps, limits, updates, and the Workers path Cloudflare now recommends.

What Cloudflare Pages Direct Upload is, and who it is for

Cloudflare Pages Direct Upload is a way to publish files that are already finished. You do not connect a GitHub or GitLab repository. You hand Cloudflare a folder, and Cloudflare serves it from its network. Cloudflare’s docs describe it as uploading “prebuilt assets” and recommend it if you want to “upload from your local computer” (developers.cloudflare.com, updated April 21, 2026). Cloudflare introduced Direct Upload on May 10, 2022, as a way to side-step its automatic build pipeline.

That fits a very common case. Imagine a freelance designer who asked Claude for a portfolio site. The result is a folder with index.html, a CSS file and some images. There is nothing to compile. The designer only needs a public address. For the bigger picture of the platform, plans and features, read our pillar guide on what Cloudflare Pages is and how it works. This article stays on one task: getting that folder online without Git.

Direct Upload has two doors: the Cloudflare dashboard, where you drag and drop files in your browser, and Wrangler, Cloudflare’s command-line interface (CLI). Most designers only need the dashboard.

Before you start: Cloudflare now tells new projects to use Workers

Most tutorials skip this. The Cloudflare Pages overview page now opens with a warning box: “Workers supports most Pages use cases and offers a broader feature set. It is Cloudflare’s primary platform for building applications. Start new projects with Workers” (developers.cloudflare.com/pages, updated August 25, 2026).

Cloudflare Pages is not shut down. In April 2025, Cloudflare wrote that Pages “will continue to be supported,” but that all new investment and feature work would go to Workers. So Cloudflare Pages Direct Upload still works, and existing sites keep running. The practical meaning is simple: new features are more likely to land in Workers than in Pages.

For a small static site, Pages Direct Upload is still the most documented browser-based path, with rollbacks and preview links. Cloudflare’s drag-and-drop tool on the Workers side, launched in July 2026, is covered later. Our comparison of Cloudflare Pages vs Workers explains the deeper differences.

Cloudflare Pages Direct Upload limits at a glance

Before you drag anything, check that your site fits. The table below compares the three no-Git ways to put static files on Cloudflare. Figures come from Cloudflare’s docs, checked September 2026.

	Pages Direct Upload (dashboard)	Pages Direct Upload (Wrangler CLI)	Cloudflare Drop (Workers)
How you upload	Drag a folder or ZIP in the browser	Type a command in a terminal	Drag a folder or ZIP in the browser
Account needed to start	Yes	Yes	No (claim within 60 minutes to keep it)
Max files	1,000	20,000 (Free plan site limit)	Not stated in the announcement
Max size per file	25 MiB	25 MiB	Not stated; Workers limit is 25 MiB per asset
ZIP accepted	Yes	No, a single folder only	Yes
Compiles a functions folder	No	Yes	Not applicable (static assets)
Default address	project-name.pages.dev	project-name.pages.dev	A workers.dev address
Can switch to Git later	No	No	Not stated

Two more Cloudflare Pages limits apply to every project on the Free plan. A site can hold up to 20,000 files, and an account can hold up to 100 Pages projects (Pages limits page, updated September 5, 2026). Cloudflare’s product page says all plans include “unlimited sites, seats, requests, and bandwidth,” within those project and file limits.

How to upload a static HTML site with Cloudflare Pages Direct Upload

This section covers the dashboard method, the one a non-developer will use.

Prepare your folder first

A clean folder prevents most upload problems. Check these points before you open the dashboard:

• index.html sits at the top of the folder. It must not be buried inside a subfolder such as my-site/site/index.html.
• Every page has its own HTML file. For example, about/index.html or about.html.
• Links match file names exactly, including capital letters.
• Large files are under 25 MiB. Compress big images or host videos elsewhere.
• Add a 404.html page if your site has several pages. The section on URLs below explains why.

Upload through the dashboard

1. Log in to the Cloudflare dashboard and open the Workers & Pages page.
2. Select Create application, then Get started, then Drag and drop your files. Cloudflare may display a notice recommending Workers; the Pages option is still available.
3. Type a project name. It becomes your address: project-name.pages.dev.
4. Drag your folder or ZIP file into the upload frame. Cloudflare accepts either one on the dashboard.
5. Watch the file list. A red warning symbol next to a file means it was too large and did not upload.
6. Select Deploy site (the docs also mention a Save and Deploy button in this flow).
7. Open the pages.dev link and click through every page, image and link.

That is the whole Cloudflare Pages Direct Upload process. Your static HTML site is now served from Cloudflare’s network. Keep the original folder on your computer. It is your only master copy, because nothing is stored in Git.

The one-way door: Direct Upload cannot switch to Git later

Cloudflare’s docs state it in a warning box: “If you choose Direct Upload, you cannot switch to Git integration later. You will have to create a new project with Git integration to use automatic deployments.” This is the single most important rule of Cloudflare Pages Direct Upload.

Why does it matter? A Git-connected project rebuilds your site each time someone pushes code. A Direct Upload project never does. If a developer later wants automatic deployments, they cannot convert it. They must create a second project and move any custom domain to it. The reverse is also restricted: on a Git-connected project, dashboard drag and drop is not available, only manual deploys with Wrangler.

Use this rule to decide before you create the project:

• Choose Direct Upload if you edit files yourself or with an AI tool, and you upload finished folders.
• Choose Git integration if the site lives in a repository, or a developer will maintain it.
• Unsure? Start with Direct Upload for a draft. Creating a second Git project later costs little on a small site.

How to update a Cloudflare Pages Direct Upload site

Updating is where many first-time users get stuck. A Reddit thread titled “Pages: how do I re-upload a file?” ranks on the first page of Google for this topic. The answer is that you never edit one file in place. You publish a new version of the whole site, called a deployment.

Follow these steps each time you change something:

1. Edit the files in your local folder, not online.
2. Open your project in Workers & Pages.
3. Select Create a new deployment.
4. Choose Production to replace the live site, or Preview to test first.
5. If you choose Preview, type a branch name such as “draft.” Cloudflare asks for one, even without Git.
6. Drag the complete folder in again and deploy.

The dashboard does not let you swap a single file. Cloudflare’s troubleshooting section says that if a file fails, “you may choose to delete that asset but you cannot replace it. In order to do so, you must reupload the entire project.” Always upload the full folder, even for a one-word fix.

Preview first, then roll back if needed

Preview deployments are a safety net for client work. A preview gets its own address on your pages.dev domain. Cloudflare adds an “X-Robots-Tag: noindex” header to every preview, which asks search engines not to index it. Previews are public by default, so avoid putting confidential drafts there.

If a production upload goes wrong, use a rollback. Open Deployments, find an earlier production deployment, open its menu and select Rollback to this deployment. Cloudflare’s docs say the change is instant. Preview deployments cannot be rollback targets, only earlier production deployments.

Cloudflare Pages static HTML: how your URLs behave

A plain HTML site behaves slightly differently on Cloudflare Pages than on your computer. Two default rules, documented on Cloudflare’s “Serving Pages” page (updated April 21, 2026), explain most surprises.

First, clean URLs. Cloudflare Pages redirects HTML pages to their extension-less form. A link to /contact.html is redirected to /contact, and /about/index.html becomes /about/. Your links keep working; the address bar just looks shorter.

Second, the 404 rule, which catches many static HTML sites. If your project has no top-level 404.html file, Cloudflare Pages assumes you uploaded a single-page application (SPA), such as a React app. It then answers every unknown address with your home page. A mistyped link shows the home page instead of an error, which hides broken links.

The fix is simple: add a 404.html file at the top of your folder. Cloudflare Pages will then show it for missing pages. It even looks for the closest 404.html first, so /blog/404.html can serve the blog section. Optional _headers and _redirects files add more control, but most small sites never need them.

Direct Upload with the Wrangler CLI

The dashboard stops at 1,000 files. A photo-heavy portfolio or a large documentation site can pass that limit. In that case, Cloudflare Pages Direct Upload through Wrangler raises the ceiling to 20,000 files. It needs Node.js and npm (the Node package manager) installed on your computer.

The commands come from Cloudflare’s Direct Upload docs:

1. Log in with npx wrangler login.
2. Create the project with npx wrangler pages project create. Wrangler asks for a project name and a production branch.
3. Deploy to production with npx wrangler pages deploy <folder>.
4. Deploy a preview with npx wrangler pages deploy <folder> --branch=<name>.

Wrangler takes a single folder; ZIP files are not supported. Wrangler is also the only way to compile a functions folder, which holds server-side code; dashboard drops cannot. Within one Direct Upload project, you can mix both methods. Imagine a small agency where a developer uploads large sites with Wrangler while a designer pushes text fixes by drag and drop.

The Workers path: Cloudflare Drop

Since Cloudflare recommends Workers for new projects, the Workers drag-and-drop option deserves a look. On July 8, 2026, Cloudflare announced Cloudflare Drop, filed under Workers in its changelog. You upload a folder or ZIP of static files at cloudflare.com/drop, with no account needed to start.

Here is how it works, according to Cloudflare’s Drop page and changelog (checked September 2026):

1. Drop a folder or .zip file with your HTML, CSS, JavaScript, images and fonts.
2. Get a live workers.dev address and a temporary preview.
3. Test and share the preview. It stays live for one hour.
4. Select Claim within 60 minutes to sign in or create a Cloudflare account. New accounts must verify their email first.
5. After claiming, add a domain, turn on monitoring or restrict access.

Cloudflare’s Workers pricing page says “Requests to static assets are free and unlimited.” Each Workers version on the Free plan can hold up to 20,000 files, with 25 MiB per file.

Cloudflare Drop has gaps for client work today. The announcement does not describe how to push a new version by drag and drop after claiming. Treat Drop as the quickest test, and check Cloudflare’s docs on updates before relying on it for a client. For a similar tool at another host, see our guide on how to use Netlify Drop.

Which no-Git path should you pick?

Answer these questions in order and stop at the first “yes”:

1. Do you only want to test a site for a few minutes, without an account? Yes → Cloudflare Drop. Claim it within 60 minutes if you want to keep it.
2. Does your site have more than 1,000 files, or a functions folder? Yes → Pages Direct Upload with Wrangler, or Workers with Wrangler.
3. Will a developer maintain the site with Git soon? Yes → skip Direct Upload and create a Git-connected project from day one.
4. Do you want browser-only updates with previews and rollbacks? Yes → Cloudflare Pages Direct Upload through the dashboard.
5. Would you rather skip Cloudflare accounts and project settings? Yes → a dedicated drag-and-drop host, as explained in our guide to static site hosting.

Custom domains work on both Pages and Workers. A free Cloudflare Pages project accepts up to 100 custom domains (Pages limits page, checked September 2026). The DNS (Domain Name System) steps are covered in our guide to adding a custom domain to Cloudflare Pages.

Common Direct Upload mistakes and quick fixes

Most failed uploads come from a handful of causes, and each has a fast fix.

Symptom	Likely cause	Fix
Blank page or “not found” at the pages.dev address	index.html is inside a subfolder	Upload the folder that directly contains index.html
Red warning next to a file	File larger than 25 MiB	Compress it, then reupload the whole project
Upload refused	More than 1,000 files on the dashboard	Remove unused files, or use Wrangler
Broken link shows the home page	No 404.html, so SPA mode is on	Add a 404.html file at the top level
Image missing online, fine on your computer	File name case does not match the link	Rename the file or fix the link exactly
Old version still showing	New deployment went to Preview	Create a new deployment and choose Production
Want to connect GitHub later	Project was created with Direct Upload	Create a new Git-connected project

Where sofast fits

sofast hosts static HTML sites by drag-and-drop upload: no Git, no command line, automatic SSL (the certificate behind HTTPS), and a free plan with 50 MB and a sofast subdomain, not listed on Google. It is built on Cloudflare’s global network, but it is a separate service. sofast does not run on Cloudflare Pages.

Compared with Cloudflare Pages Direct Upload, sofast removes the project settings, branch names and deployment menus. You drag a folder or ZIP in, and sofast says a typical upload is live in about 15 seconds. Commercial use is allowed on the Free plan.

Cloudflare wins on several points, and you should know them. Pages offers preview deployments, instant rollbacks, up to 20,000 files and custom domains on its free plan. sofast has no Git workflow, no server-side functions and no build step. The free plan is limited to one site and 50 MB, and a custom domain needs Starter at $5 a month, billed annually. sofast also returns a real 404 for unknown paths, so single-page apps with client-side routes need one HTML file per page. sofast is a new, pre-launch service. The sofast pricing page lists every plan.

Frequently asked questions

Sources

• Cloudflare Docs — Pages Direct Upload (updated April 21, 2026)
• Cloudflare Docs — Cloudflare Pages overview, “Start new projects with Workers” (updated August 25, 2026)
• Cloudflare Docs — Pages limits (updated September 5, 2026)
• Cloudflare Docs — Serving Pages (route matching, 404 and SPA behavior) (updated April 21, 2026)
• Cloudflare Docs — Pages rollbacks (updated April 21, 2026)
• Cloudflare Docs — Pages preview deployments (noindex header, public by default)
• Cloudflare Blog — Introducing Direct Uploads for Cloudflare Pages (May 10, 2022)
• Cloudflare Blog — Full-stack development on Cloudflare Workers (April 8, 2025)
• Cloudflare Changelog — Cloudflare Drop (July 8, 2026)
• Cloudflare — Cloudflare Drop page (checked September 23, 2026)
• Cloudflare Docs — Claim deployments (temporary accounts) (updated July 14, 2026)
• Cloudflare Docs — Workers pricing (static asset requests free and unlimited) (updated August 28, 2026)
• Cloudflare Docs — Workers limits (files per version, size per asset)
• Cloudflare — Pages product page (“unlimited sites, seats, requests, and bandwidth”)
• sofast — Pricing

Written by the sofast team.