Vercel Drop is very good at what it's built for: drag a file, a folder, or a ZIP into the browser and it goes straight to production, framework builds included, with no Git and no CLI. For shipping something to the web that's close to the shortest path in existence, and if that's your job there's no reason to look elsewhere. People go looking for an alternative when the job turns out to be delivery instead — the same client, the same piece of work, five revisions over two weeks. Vercel's own documentation notes the constraint plainly: each drop creates a new project, and Drop doesn't redeploy into an existing one. That's a sensible design for one-off ships and an awkward one when somebody has already bookmarked the last URL you sent.
Try it now
Drop a file — get a private link in seconds. No sign-up.
Drop an HTML file or ZIP bundle, or click to choose.
Single file or ZIP. Max 3 MB.
Up to 3 MB, link self-destructs after 7 days. Sign up free to keep links forever, password-protect them, and store more.
Upload the same thing you'd have dropped anywhere else — a single self-contained HTML file, or a ZIP of a built folder with its assets, where the entry page is detected automatically and relative paths keep resolving. You get a link back in seconds. It's a long unguessable string rather than a memorable address, carrying a noindex meta tag and an X-Robots-Tag header, because a deliverable isn't trying to be found.
Set the controls a client-facing link needs, both free on every plan: a password, so a forwarded link still needs the passphrase, and an expiry, so a proposal or a review window closes by itself instead of relying on you to remember. Nothing changes for the person opening it — no account, no install, no platform chrome around your work.
Then send revision two to the same address. Upload a new version and the URL, the password, and the expiry all stay as they were, with each version kept rather than overwritten. That's the whole difference in practice: no 'ignore the last link' email, no bookmark going stale, no wondering which of four URLs the client actually has open. On Studio ($14.99/mo) it runs on your own domain with the miinideck branding removed.
Not for the things it's best at. If you're putting a prototype on the web, shipping a one-off site, or you want a framework project detected and built for you, Drop does that faster than almost anything and it lives in an ecosystem you may already be deep in. The switch makes sense for a narrower case: work going to named people, revised more than once, where the address needs to survive the revision and where being publicly reachable is a liability rather than the point.
That's the specific thing this is built around. A new version replaces the contents at the address you already sent, and the password, expiry, and title carry over untouched, with each upload kept as a numbered version rather than overwriting the last. It matters more than it sounds like it should, because a link you've already handed to a client isn't really a URL any more — it's in their inbox, their bookmarks, and possibly forwarded to two colleagues you've never met.
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 to be built from source, or needs a server, a database, API routes, or authentication, then a platform that runs builds and functions is the correct tool and 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, and it's tier-based. An anonymous upload from the homepage takes a single file up to 3 MB with a link that self-destructs after 7 days — enough to test the flow before deciding anything. With a free account it's 10 MB per file; Solo is $4.99/mo with 25 MB files, 100 MB of storage, and links that never expire; Studio is $14.99/mo with 50 MB files, 500 MB of storage, a custom domain, and white-label.
Neither. They click the link and the page opens in their browser on any device, with 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. The whole point of delivering on a link is that the friction lands on you, once, rather than on the person you're trying to impress.
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 elsewhere. Combined with an unguessable address and no public directory, there's nothing to discover in the first place.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.