# Cloudflare Drop: drag a folder, get a live site

> Cloudflare Drop deploys a static site by dragging a folder or zip into the browser. No account, no CLI. How it works and how it ties into temporary accounts.

Author: [Flavio Copes](https://flaviocopes.com/about/) | Published: 2026-07-09 | Topics: [Cloudflare](https://flaviocopes.com/tags/cloudflare/) | Canonical: https://flaviocopes.com/cloudflare-drop/

Deploying a static site keeps getting simpler. Cloudflare just took it to the logical extreme.

[Cloudflare Drop](https://www.cloudflare.com/drop/) is a page where you drag a folder — or a zip — into the browser, and your site is live on Cloudflare's global network. Seconds later you have a URL.

No account. No CLI. No git repo. No build step.

## What is Drop?

Drop is a deployment tool for plain static sites: HTML, CSS, JavaScript, images.

You go to [cloudflare.com/drop](https://www.cloudflare.com/drop/), drop a folder or a zip file, and Cloudflare uploads it and serves it from their edge. You get a live URL you can open and share right away.

That's the entire workflow. There is nothing to configure.

## Why does it exist?

Think about how many times you have a folder with an `index.html` and you just want to show it to someone.

The classic options all have friction. Pages wants a git repo or a CLI upload. A VPS wants ssh and nginx. Even "simple" hosts want a signup first.

Drop removes all of it. The demo you hacked together, the landing page mockup, the CSS experiment — folder in, URL out.

There's a second reason, and it's the more interesting one: this kind of frictionless deploy is built for the AI era. More on that below.

## What about keeping the site?

A site you dropped isn't tied to an account — there's no account. It works like Cloudflare's new **temporary accounts**: the deployment lives on a temporary account, and you get a claim link.

If you claim it, you sign in (or sign up) and the site becomes a normal, permanent deployment in your Cloudflare account. If you don't claim it within the window, it expires and gets deleted on its own.

I like this model a lot. Throwaway by default, permanent by choice.

I wrote a separate post on [temporary Cloudflare accounts](https://flaviocopes.com/cloudflare-temporary-accounts/) — the same mechanism, but for agents deploying Workers from the CLI with `wrangler deploy --temporary`.

## When to use Drop vs the real thing

Drop is for immediacy, not for production.

Use Drop when:

- you want to show someone a static site *right now*
- you're testing how something behaves on a real URL (not `file://`)
- you don't have (or don't want) a Cloudflare account yet

Use [Workers static assets](https://flaviocopes.com/cloudflare-workers-static-assets/) or Pages when:

- the site has a build step (Astro, Vite, anything with `npm run build` — you can still drop the output folder, but you'll want CI eventually)
- you need a custom domain
- you're deploying more than once — at that point `wrangler` or a git-connected project is less work, not more

This site runs on Cloudflare Pages with git-connected builds, and I wouldn't move it to Drop. But for one-off experiments, Drop is now the fastest path to a URL that I know of.

## The bigger picture

Drop and temporary accounts shipped as part of the same push: removing signup as a prerequisite for deploying.

For humans, that's convenience. For AI agents, it's the difference between finishing the job and getting stuck — an agent can't click through an OAuth flow in a dashboard.