Vercel Drop turns a dragged file into a live production URL on a major platform. miinideck turns one into a private link for specific people. Both fit 'drag a file, get a URL' — and were built for opposite jobs. When each fits, where the overlap is narrow.
In June 2026 Vercel shipped Vercel Drop — drag an HTML file, a folder, or a zip onto a page and get a live production URL. It's a clean, fast on-ramp, and when a platform that size puts "drop a file, get a link" on its front door, it's worth reading as a signal that delivering work as a live link is becoming normal.
Two tools that both turn a dragged file into a URL. One is designed for public deploy testing; the other for private one-recipient delivery. When each fits, where the overlap is real.
Vercel just shipped drag-a-file-get-a-link. With Netlify, tiiny, and others already here, sharing a built page as a live link is officially the new normal. Here's the whole landscape of tools — and how to pick one — if you're done emailing PDFs.
Two tools that both host an HTML file, designed for different jobs. When tiiny.host fits, when miinideck fits, and where the choice actually matters.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.
It also raises a fair question if you deliver work privately: is Vercel Drop the right tool, or is it built for a different job than yours? Both Vercel Drop and miinideck fit the sentence "drag this file somewhere, get a URL I can share." They diverge on what comes after the URL.
Vercel Drop is designed for a public production deploy on Vercel's platform. You drag a file or folder, pick a team, name a project, and Vercel publishes it straight to production with a live URL — building the project first if it's a framework like Next.js. Vercel's own framing is that "the drop is the starting point for the full platform, not a separate sandbox": it's the no-Git, no-CLI doorway into Vercel's deploy pipeline, branch previews, and edge functions.
miinideck is designed for delivery to specific people. You drop a self-contained HTML file (or a zip), get a private URL with optional password and expiry, and send it to the audience you choose. The link is unguessable and hidden from search by default. The whole workflow assumes "send this to one client; the rest of the internet doesn't need to find it."
Same input shape (drag a file). Same output shape (a URL). Opposite consumption shape on the other side of it — found by many, or opened by a few.
| Vercel Drop | miinideck (Free / No-account) | |
|---|---|---|
| Account to start | Required (pick a team, name a project) | None for a quick anonymous drop; free account for more |
| Visibility default | Public, indexable production URL | Private, noindex |
| URL shape | Project URL on Vercel | Random unguessable slug |
| Build step | Detects and builds frameworks (Next.js, etc.) | None — serves self-contained HTML / zip as-is |
| Re-publish at same URL | No — each drop creates a new project | Yes — replace the file, the link stays the same |
| Password protection | Not part of Drop | Free on every tier |
| Expiry / self-destruct | – (deployments persist until deleted) | 7-day default on Free / No-account; one link can be kept always-on |
| Custom domain | Yes, via the full Vercel platform | Studio tier |
The tables read differently because the products serve different jobs. Vercel Drop defaults to public + production + framework-aware because the design intent is "deploy something, then grow it on Vercel." miinideck defaults to private + ephemeral + serve-as-is because the design intent is "hand a finished page to specific people."
Neither default is wrong for what each is built for; both are wrong if you pick the tool that doesn't match your actual use case.
Vercel's paid plans (Pro, Enterprise) scale into a full deploy platform: Git-based continuous deployment, branch previews, environment variables, edge functions and middleware, build minutes, team workflows, analytics, SSO. The paid path is for projects that grow from "drop the first version" into an ongoing web app with a deploy pipeline and a team around it.
miinideck's paid tiers (Solo $4.99/mo, Studio $14.99/mo) scale into ownership of the private link: permanent links (no self-destruct), no footer, larger files, custom domain at Studio, white-label expiry pages, and per-document searchable opt-in for the rare case a specific link should also be indexable. (Password protection and privacy are free on every tier — the baseline, not the upsell.)
Both ladders are coherent in their own direction. The question isn't "which gives more per dollar" — it's "which axis is the work scaling along": toward a bigger public platform, or toward control over a private delivery.
miinideck pricing — Solo $4.99/mo, Studio $14.99/mo. Privacy and password protection are always free; paid tiers add persistence and ownership, with custom domain and white-label expiry at Studio. Sized for delivery use cases (consultants, agencies, designers, freelancers) rather than for full deploy workflows.
Two cases where both tools handle the same shape of input:
For these, the choice reduces to one question: will this page have one audience, or be discovered by many?
Vercel Drop's design fit (miinideck doesn't try to do this):
For AI product landings that will iterate and grow into a real app, Vercel's full platform (not just the Drop tool) is the right shape.
miinideck's design fit (Vercel Drop isn't built for this):
The pattern that recurs: the page isn't trying to be discovered, and public-by-default is the wrong starting point.
miinideck is narrow on purpose. It doesn't:
For these, Vercel (or Netlify, Cloudflare Pages, a dedicated host) is the right shape. miinideck's narrow scope is what lets it ship default-private without trading against discovery — the same property holds across the vs-Netlify-Drop and vs-tiiny.host comparisons for the same reasons.
Vercel Drop is also narrow on purpose. It doesn't:
For these, miinideck is the right shape. Vercel Drop's narrow scope is what makes it a fast on-ramp to the full Vercel platform; that on-ramp doesn't fit when the goal isn't "deploy and grow on Vercel."
Two questions, in order:
Should this page be findable by people who don't have the link yet?
If "no" to #1, will the project grow into a built, multi-file app with a deploy pipeline?
That's the decision. Both tools are coherent in their own direction; the work is matching the page to the right shape — the same framing that applies in the vs-Netlify-Drop post, with Vercel Drop sitting at the "designed for reach, and for growth into a full platform" end of the axis.