Cloudflare Drop: Deploy a Static Site Without an Account, for One Hour

Vercel proved last month that dragging a folder into a browser could replace an entire deployment workflow. Cloudflare just answered with the opposite trade-off: instead of requiring an account and giving you a permanent URL, it asks for nothing upfront and gives you an hour.

What Cloudflare Drop is

Cloudflare Drop lets you deploy a static site without needing a Cloudflare account to get started. Upload a folder or .zip file of static assets, HTML, CSS, JavaScript, images, and fonts, and you get a temporary live preview served from Cloudflare's edge network.

That preview stays live for 60 minutes. During that window you can test the site, share the preview URL with someone else, or decide to keep it permanently.

Claiming a deployment

If you want the site to survive past the hour, you claim it. Claiming means signing in to an existing Cloudflare account or creating a new one, and the claim link itself runs on a visible countdown before it expires. If you're creating a brand-new account in the process, you'll need to verify your email address before the claim finishes.

Once claimed, the deployment stops being a temporary preview and becomes a real project tied to your account, at which point several options open up:

• Add a domain. Connect an existing domain or purchase a new one for the site.
• Enable observability. Monitor the site's performance and usage the way you would any other Cloudflare-hosted project.
• Enable Markdown for Agents. Lets AI agents read the site's content in Markdown rather than parsing raw HTML.
• Control access. Make the site private and decide who's allowed to view it.

What it deliberately doesn't do

Cloudflare Drop is explicitly scoped to static assets. It isn't running a build step for you, and it isn't trying to be a full deployment platform on day one, it's meant to be the fastest possible path from "I have files" to "someone can look at this," with the account requirement pushed to the moment you've actually decided you want to keep it.

That scoping shows up in a few specific gaps worth knowing before you rely on it:

• No single-file drop. You need a folder or zip, dropping one HTML file on its own isn't supported yet, though it's been requested.
• No API. There's no programmatic way to drop or update a deployment at launch, everything goes through the browser.
• Public by default. Anything you drop is publicly reachable at its preview URL the moment it uploads. Don't drop secrets, .env files, or anything you wouldn't want briefly exposed on the open internet.
• Static only. No server logic, no auth, no database. Anything beyond flat files needs Cloudflare Pages or Workers.

Where it's actually useful

The one-hour window isn't a limitation so much as the whole point. It's built for moments where you need a real URL for a short amount of time and don't want an account standing between you and that URL:

• Interview take-homes and hallway demos — hand someone a working link on the spot, no setup conversation required
• Internal stakeholder previews — show a layout or prototype before committing to a full Pages project
• Agent-generated static output — let an AI agent's build get eyeballed by a human before anyone decides it's worth keeping
• Quick proof of concept— settle "does this actually work" before investing in real infrastructure

For anything meant to survive the weekend, claim it immediately or skip straight to Cloudflare Pages' free tier. Drop is a front door, not a place to live. That's the same line we draw with clients doing performance marketing and paid ads landing page tests, prove the concept fast and cheap, then move whatever wins into real, owned infrastructure rather than leaving it on a tool built for disposability.

Vercel Drop did this first, Cloudflare took the opposite bet

Vercel Drop launched in June 2026 with a simple premise: remove every step between a folder and a live URL, except the one step, an account, that guarantees the result is permanent. No expiry, no claiming ritual, deploy straight to production. We covered the full mechanics of that approach in our Vercel Drop breakdown.

Cloudflare Drop arrived a month later solving the same problem from the other direction. No account needed to start, but nothing sticks around unless you actively claim it within the hour. Same drag-and-drop instinct, opposite philosophy on what should be free and what should require commitment.

Neither is wrong, they're solving for different moments. If you want zero friction to test something disposable, Cloudflare's hour-long window with no signup wins. If you want zero friction to ship something you already intend to keep, including a full framework build, Vercel's permanent-by-default approach wins. We'll go deeper on when to reach for which in the full comparison.

Frequently Asked Questions