Will Netlify build my project for me?

Only if you're logged in when you drop it. Logged-in drops get a full build step, so you can hand over source code directly. Logged-out drops publish files as-is with no build, so you need to drop your finished output folder.

Can I update a site after I've already dropped it once?

Yes. Go to the site's Deploys page and drag an updated project folder onto the drop zone there to publish a new version, no need to start a new project or connect Git.

What's the size limit for Netlify Drop?

Deploys under 50MB work best. Individual files larger than 10MB can cause the deploy to get stuck, in which case the CLI is a better option.

Should I unzip a project before dropping it?

Yes. Netlify's guidance is to unzip your archive first and confirm the files sit in a folder with an index.html at the root before dragging it in.

How is Netlify Drop different from Vercel Drop and Cloudflare Drop?

Netlify Drop is the oldest of the three and, like Cloudflare Drop, doesn't require an account to start. Its standout feature is re-deployment: you can repeatedly drag updated folders onto an existing site's Deploys page to publish new versions, something neither Vercel Drop nor Cloudflare Drop is built around in the same way.

Netlify Drop: The Original Drag-and-Drop Deploy Tool

Before Vercel and Cloudflare shipped their own versions of this idea in 2026, Netlify had already been doing it for years. Netlify Drop is the original drag-a-folder-get-a-live-site tool, and it's still one of the simplest ways to get a static site online.

What Netlify Drop is

Netlify Drop lets you deploy a site by dragging a project folder to netlify.com/drop or to the drop zone at the bottom of your team's Projects page. No build step is required on your end, you can drop a project as-is and let Netlify take it from there, or drop an already-built output folder if you'd rather handle the build yourself.

Unlike Vercel Drop, Netlify Drop doesn't require an account to get started. Drop a project while logged out, and Netlify publishes it anonymously with a shareable preview URL. You can claim it later by signing up, similar in spirit to how Cloudflare Drop handles anonymous deploys.

Logged in vs. logged out: two different experiences

This is the detail that matters most with Netlify Drop, what happens depends entirely on whether you're signed in when you drop.

Logged in:

Netlify detects your framework and runs the build for you before publishing
You can drop a project that still needs a build step, source code, not just output
The deploy is tied to your team from the start

Logged out:

There's no build pipeline at all
Files publish exactly as-is
The folder you drag needs to already be your finished build output, commonly named dist, build, or public
The site is anonymous until you claim it by creating or signing into an account

If you're dropping a framework project without being logged in, it won't work the way you expect, Netlify won't build it, it'll just publish whatever raw source files you handed it. Build locally first, or sign in before you drop.

Updating a site you already dropped

This is where Netlify Drop pulls ahead of both Vercel and Cloudflare's versions: it's designed to be re-used. Once a site exists, you can go back to its Deploys page and drag an updated folder onto the drop zone there to publish a new production version. Make your changes locally, rebuild if needed, and drop the updated output folder again. There's no requirement to reconnect Git or start a new project each time, the same site just gets a new deploy.

That turns Netlify Drop from a one-off publishing trick into something closer to a lightweight manual deployment workflow, useful for anyone iterating on a static site without wanting to set up continuous deployment from Git.

Limits worth knowing

Deploys under 50MB work best. Individual files over 10MB can cause a deploy to get stuck.
Zip files are accepted, but Netlify's own guidance is to unzip first and confirm your files sit inside a folder with an index.html at the root before dropping.
Unclaimed sites don't stick around forever. Anonymous deploys are meant to be claimed if you want to keep them long-term.
Large projects should use the CLI instead. Netlify recommends the CLI over drag-and-drop once a project grows past what the browser upload handles comfortably.

AI and CLI options alongside Drop

Netlify Drop isn't the only fast path into the platform. Netlify also offers Agent Runners, letting you build a project with Claude Code, OpenAI Codex, or Google Gemini directly from the dashboard, with every agent change automatically generating a preview deploy. The CLI covers the same ground from the terminal, including netlify deploy --prod for a direct production push and netlify deploy --allow-anonymous for deploying without logging in at all, the CLI equivalent of what Drop does in the browser.

Where it fits

Netlify Drop is built for the same moment Vercel Drop and Cloudflare Drop are aimed at, getting something in front of a browser fast, without Git or CLI setup standing in the way. Where it earns its own place is in ongoing iteration: if you're going to update a static site repeatedly without wiring up Git, Netlify's re-drop workflow on the same Deploys page is a genuinely different capability from either competitor. For projects that outgrow manual re-drops and need a real deployment pipeline, that's the point where our web development and engineering team usually steps in to wire up proper CI/CD from Git instead.

Frequently Asked Questions

No. You can drop a project without logging in and Netlify will publish it anonymously. You'll need to sign up or log in later if you want to claim and keep the site.