Looking for a Cloudflare Drop alternative? It usually comes down to when they open it.

Cloudflare's changelog gives the number directly: the temporary live preview stays live for one hour. Within that window you can test the site, share the preview URL, or click Claim to keep it — and claiming means signing in or creating a Cloudflare account, with new accounts needing email verification before the deployment sticks. So the hour isn't a limitation hiding in the small print, it's the deal being offered: total speed and zero signup, in exchange for a preview that's explicitly temporary.

Not for what it's best at, and if you have a Cloudflare account already the calculation is different again. Claim the deployment and you're on one of the fastest networks in existence, with a real project you can attach a domain to and, per Cloudflare's own description, controls to make the site private and choose who can view it. That's a strong place for a site to live. The narrower case this page is about is the one where you don't want a project at all — you want to hand one piece of work to one named person, have it open reliably whenever they get to it, and have it close on your terms afterwards.

Re-upload the same folder somewhere the clock is yours and send the new address once, with an apology you'll only have to make this time. It's worth taking the two minutes to think about which end date you actually want rather than accepting a default: a review window that closes on the 14th, a proposal that stays open until they sign, a reference document that should simply keep working. Deciding that at the moment you send is the difference between a link you control and a link that controls you.

You can do the whole thing without one — an anonymous upload takes a file up to 3 MB and gives you a link that lasts 7 days, which is enough to run the route end to end before deciding anything. An account raises the ceilings and hands you the expiry switch. The person receiving it never needs anything: they click, the page opens in their browser on any device, nothing to install and nobody to sign up as. If you've set a password they're asked for that one passphrase and nothing else.

No, and that's a real difference rather than a modest one. There's no build step here — what you upload is what gets served. If your project needs building from source, or needs a server, a database, API routes, authentication or scheduled work, then a platform that runs builds and functions is the correct tool, and Cloudflare, Vercel or Netlify will serve you far better than we would. What travels well here is the output: a static export, a built folder zipped up, a self-contained page.

Yes, by default, and the mechanism is worth understanding because it's a common trap. The viewing domain lets crawlers in — its robots.txt says Allow — and every document then carries a noindex meta tag plus an X-Robots-Tag header where a crawler will actually read them. Blocking crawlers at robots.txt would look stricter and would in fact be weaker, because a blocked crawler never reads the noindex and can still list a URL it found linked somewhere else. Combined with an unguessable address and no public directory of any kind, there's nothing to discover in the first place.

Yes, over MCP. Connect it once and a tool like Claude Code or Codex can publish the HTML it just wrote and then replace that page in place as it iterates, keeping the same URL the whole way through. That matters for the drag-and-drop crowd more than it sounds like it should: the reason people drop a folder five times in an afternoon is that the work is still moving, and every drop that mints a fresh address is another message explaining which link is the real one.