Vercel Drop: Deploy a Live Site by Dragging a Folder Into Your Browser

There's a specific kind of friction every developer knows: you have a finished folder of files sitting on your local machine, and getting them onto a real URL still requires a Git push, a CLI login, or navigating a dashboard full of CI/CD settings you don't actually need for a five-minute demo.

Vercel built a feature specifically to eliminate that gap.

What Vercel Drop is

Vercel Drop lets you deploy a file, folder, or .zip archive by dragging it directly into your browser at vercel.com/drop. There's no Git repository to link, no CLI to install, and no local build setup required. You select a team, name the project, and hit Deploy. Vercel uploads the files and publishes them straight to production with a live, shareable URL in seconds.

The one strict requirement, unlike some competing tools, is an active Vercel account. You must be signed in with a designated team before you can drop anything. There's no anonymous, no-signup path. The trade-off is that the output is immediately real and permanent, rather than a temporary preview waiting to expire.

How it actually handles your files

Drop isn't limited to static HTML. Vercel inspects the payload and treats two cases very differently:

• Framework projects. If Vercel detects a known framework, Next.js being the obvious example, it runs the required build steps automatically. This is the exact pipeline used by exports from AI coding agents like Bolt.new, which output raw framework source code rather than flat compiled files.
• Static sites. Files with no framework architecture are deployed exactly as-is, bypassing the build step entirely. This covers plain HTML/CSS/JS bundles as well as direct exports from AI design environments like Claude Design and Google Stitch.

In either scenario, there's no vercel.json to write, no environment variables to string together, and no build commands to configure before the first deployment. Vercel infers the project type and serves it using sensible defaults.

The root routing detail: if your uploaded folder lacks an index.html at the top level, Vercel prompts you to select which page should load at the site root. Choose no root page, and visiting / returns a 404, while every other file still serves cleanly at its own path.

The post-drop lifecycle

Every drop creates a brand-new Vercel project. It isn't wired to Git by default, meaning a subsequent push to a repository won't automatically trigger a new deployment. This is a one-off publishing mechanism, not a continuous integration pipeline.

If you need that pipeline later, connecting a Git repository after the fact instantly converts the drop into a standard Vercel project, complete with automatic deployments on every push.

Because the deployment hits production the moment the upload completes, there's no separate "claim" step and no countdown clock before the site disappears. The URL is live, public, and permanent from the first second.

Where it fits in the workflow

Drop is aimed squarely at the moment before a project needs a repository, a team convention, or a reason to exist as long-term infrastructure:

• Frictionless previews — sharing a working prototype with a client or teammate without provisioning infrastructure first
• AI tool handoffs — publishing a static or framework export directly from an AI-generation tool to evaluate it in a real browser
• High-speed demos — a live link in under a minute during a hackathon, technical interview, or stakeholder meeting
• Build verification — a quick sanity check on local build output before wiring up a full CI/CD pipeline

It's not engineered for applications that need a database, server-side authentication, or ongoing team collaboration from day one, that's exactly what a Git-connected project and the broader Vercel platform are for. Drop is the on-ramp, not the final destination. For teams that outgrow the drag-and-drop phase quickly, that's the exact gap where our web development and engineering work usually begins: taking an asset that was fast to prototype and architecting the real, scalable infrastructure underneath it.

The bigger picture

Vercel Drop, announced in June 2026, made a specific architectural bet: remove absolutely every step between "I have files" and "I have a URL," even if that means enforcing the one step, an account login, that guarantees your published asset isn't going anywhere unless you delete it yourself. No expiry, no claiming ritual, just an instant production deployment.

That bet is worth keeping in mind, because it's not the only version of this idea on the market. Cloudflare shipped its own take on drag-and-drop deployment in July 2026, and it made the opposite trade-off on almost every point: no account required to start, but a strict one-hour clock on how long your site stays alive. We'll break down exactly how Cloudflare's approach compares, and when to use it, in our Cloudflare Drop breakdown.

Frequently Asked Questions