Cloudflare Drop: drag a folder, get a live site

Cloudflare made deploying a static site as quick as dropping a folder into a browser.

Cloudflare Drop is a page where you drag a folder or a zip into the browser. Seconds later, your site is live on Cloudflare’s global network and you have a URL.

You don’t need an account, CLI, git repo, or build step.

What is Drop?

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

You go to 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, with nothing else 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. You can upload a demo you hacked together, a landing page mockup, or a CSS experiment and get a URL.

This kind of frictionless deploy also works well for AI agents.

What about keeping the site?

A site you dropped isn’t tied to your account. It uses 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 because the site can stay temporary unless you decide to keep it.

I wrote a separate post on temporary Cloudflare accounts. They use the same mechanism for agents deploying Workers from the CLI with wrangler deploy --temporary.

When to use Drop vs the real thing

Drop works best for quick, temporary deployments rather than production sites.

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 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, because wrangler or a git-connected project then becomes less work

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.

Why this helps AI agents

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

This is convenient for us. It also lets an AI agent finish a deployment without clicking through an OAuth flow in a dashboard.

Want me to talk about your product? You can sponsor this site.