Hi, this is Hoda.
On July 8, 2026, Cloudflare rolled out a new service called “Cloudflare Drop.” The pitch is refreshingly simple: drop a folder or a zip file, and your static site goes live — no account needed.
I got curious and tried it myself, so here’s a rundown of how it works and what it’s actually like to use.
I also walk through it in this video, so check that out too:
What is Cloudflare Drop?
Cloudflare Drop lets you deploy a static site without ever creating a Cloudflare account.
You upload a folder or zip file containing your static assets — HTML, CSS, JavaScript, images, fonts — and Cloudflare instantly spins up a temporary live preview. That preview stays live for one hour, which is plenty of time to check that everything works and share the URL with someone.
If you like what you see, you can “Claim” it to turn the temporary deployment into a permanent one.
Pros
- Try it instantly, no Cloudflare account required
- Just drag, drop, and you’re live
- After claiming, it becomes a regular Cloudflare Workers project
- Not sandboxed, so there’s no restriction on calling external APIs
Cons
- If you don’t claim it, it’s automatically deleted after one hour
- Static assets only — no full-stack features like database connections
- Worth checking the content-licensing terms before you upload anything sensitive
Key features
Based on the official site, here’s what stands out about Cloudflare Drop:
- No account needed to start: Open it in your browser and drop a folder or zip — deployment starts immediately.
- One-hour temporary preview: If you don’t claim it, the deployment is automatically deleted an hour later.
- Claim to make it permanent: Attach it to an existing Cloudflare account, or create a new one to keep the deployment. A new account needs email verification.
- Custom domain support: Once claimed, you can connect your own domain.
- Observability: Monitor your site’s traffic and performance.
- Markdown for Agents support: Lets AI agents fetch your site’s content in Markdown format.
- Access control: Make the site private and restrict who can view it.
How to use it
The actual process is very simple.
1. Prepare your static files
Put together a folder — or a zip file — built around index.html, along with your CSS, JS, images, and so on. If you had an AI tool generate the site for you, it’s easiest to just have it output a zip directly.
2. Upload it
Open the Cloudflare Drop homepage, then either use the file picker or just drag your folder or zip straight onto the page. No account creation or sign-in required.
3. Check the preview
Once the upload finishes, you’ll get a temporary URL. Open it and confirm everything looks the way you expect. If something looks broken, it’s usually the folder-path issue from step 1.
4. Claim it if you want to keep it
If it’s a site you want to hang onto, hit the “Claim” button to take ownership. Sign in to an existing Cloudflare account, or create a new one — a new account will need email verification.
Leave it unclaimed, and the site is automatically deleted after one hour. Worth repeating as many times as it takes.
5. After you claim it
Once claimed, the deployment becomes a regular Cloudflare Workers project, which opens up a few more options:
- Connect a custom domain: register a new one or use one you already own. Free DNS, automatic HTTPS, and DDoS protection are all included.
- Turn on observability: gives you insight into your site’s performance and behavior.
- Turn on Markdown for Agents: makes it easier for AI agents to explore your site, and increases how often it shows up in AI conversations.
- Restrict access: control who can reach the Worker. Add authentication, set policies, and manage permissions.
Here’s a live demo: check it out
Watch your zip file’s folder structure
If a zip upload to Cloudflare Drop fails, it’s often not your code — it’s how the files are arranged inside the zip.
Cloudflare Drop expects index.html to sit right at the top level once the zip is opened. If your project folder is nested one level deeper, like this, it won’t publish correctly:
cloudflare-drag-and-drop/
└── color-palette-tool/
├── index.html
├── style.css
└── script.jsThe correct structure has every file visible as soon as you open the zip:
index.html
style.css
script.js
README.mdWhen you create the zip, don’t compress the project folder itself — open the folder and select the files inside it directly.
You can also skip zipping altogether and just drag the project folder (the one containing index.html) straight onto Cloudflare Drop.
It’s worth opening your zip once before uploading, just to confirm index.html is sitting at the top level.
How it compares to similar services
A few other services occupy similar territory to Cloudflare Drop.
Netlify Drop
Netlify beat Cloudflare to this idea with its own “Netlify Drop.” The mechanics are quite similar — including the one-hour window before you need to claim it. If you’re already comfortable with Netlify, Netlify Drop makes sense; if you’d rather stay on Cloudflare’s network and tap into things like Workers and KV, Cloudflare Drop is the better fit.
Tiiny Host
I covered Tiiny Host in an earlier review, and it occupies similar territory: upload a file, get a public URL back.
The big differences: Tiiny Host handles a much wider range of file types beyond HTML and zip — PDF, PHP, images, PowerPoint, Excel — and it’s a paid service starting at $5/month. There’s a free plan, but it caps you at one site and 3 MB, and your link gets deleted if you don’t log in at least once every three months.
Cloudflare Drop, on the other hand, is completely free and doesn’t even require signing up to get started — though it only handles the building blocks of a static site: HTML, CSS, JS, images, and fonts. Tiiny Host already has extras like password protection, analytics, QR code generation, and a built-in code editor, so the split ends up being: Cloudflare Drop wins on simplicity and not needing an account, backed by Cloudflare’s network reliability.
Claude Artifacts and similar AI-tool previews
Some AI tools, like Claude’s Artifacts, have their own built-in preview-publishing feature. It’s hard to beat for convenience, but these previews typically run inside a sandbox, which can restrict calls to external APIs.
Cloudflare Drop runs as standalone hosting, so it doesn’t carry that same restriction — you can publish sites that pull in live, dynamic data without running into sandbox limits. If you want to publish an AI-generated site in something closer to a production-ready form, Cloudflare Drop is often the better fit.
A few things worth knowing before you use it
It disappears after an hour
Worth saying again: unless you claim it, your deployment is deleted after an hour. That’s fine for demos or a quick share with a client, but don’t rely on it for anything you plan to leave up.
About content licensing
Some discussions in online communities raise questions about how broad a license Cloudflare’s terms of service grant it over content you upload. Others point out that this kind of clause is fairly standard across hosting and CDN providers, so opinions on how to read it vary.
Before publishing anything sensitive, or a site you intend to run in production, it’s worth reading the current terms yourself.
Risk of misuse
Lowering the barrier to publishing also raises the risk of things like phishing sites being hosted this way. How well Cloudflare’s review, reporting, and takedown process holds up against that is something to watch as the tool sees wider use.
Wrap-up
Cloudflare Drop is a clean fit for anyone who just wants to get a static site live, fast. In particular, if you’ve been generating static sites with AI tools and haven’t had anywhere obvious to publish them, this fills that gap nicely.
- Quick demos or sharing a preview: works great
- Publishing AI-generated sites: a strong match
- Your main production site: claim it, and read the terms first
- Full-stack needs like database connections: not currently supported
There’s a lot you can try for free, so if you’ve been on the fence about static hosting, it’s worth taking Cloudflare Drop for a spin.
