Netlify Drop: How It Works and When to Switch to Git Deploys
Sagar Tayde · · 8 min read
Netlify Drop is the page where you drag a folder into the browser and get a live website a few seconds later. It is how many students and first-time developers in India publish their first site. This guide explains how it works today, what happens if you never claim the site, where drag-and-drop starts to hurt, and how to move the same site to Git-based deploys when you are ready, on Netlify or anywhere else.
Netlify facts here come from Netlify’s own documentation and changelog, checked on 14 November 2026.
What is Netlify Drop?
Drop is Netlify’s drag-and-drop deploy page at app.netlify.com/drop. You drop a folder or a zip file of your site, Netlify uploads it, and you get a URL ending in netlify.app. You do not need a Git repository, and you do not need an account to start. If you are signed in, Netlify can also run your build for you.
It is old and popular. Netlify’s own history post traces it back to a drag-and-drop tool called BitBalloon, first committed in 2013, and says more than 60 percent of people who signed up in June 2026 made their first deploy this way.
How a drag-and-drop deploy works
- Open the Drop page in your browser.
- Drag your project folder, or a zip of it, onto the drop zone. The folder should have an
index.htmlat its top level. - Wait for the upload. Netlify gives you a preview URL ending in netlify.app.
- Sign up or log in to claim the site so it stays online.
- To update it later, open the project’s dashboard and drop the new folder onto the area under Production deploys. The changes publish straight to production.
Signed in versus not signed in
What happens to your files depends on whether you are logged in.
- Not signed in. Netlify publishes the files exactly as they are. Drop a finished output folder, such
as
distorbuild, not your source code. The URL is protected with a temporary password until you claim it. - Signed in. You can drop a project that still needs building. Netlify detects the framework, installs dependencies and runs the build before it publishes. Dropping a pre-built folder still works.
Claiming a dropped site, and what happens if you do not
An unclaimed drop is temporary by design. Netlify’s history post says the claim window was cut from 24 hours to one hour in January 2022, anonymous sites were capped at three per IP address, and unclaimed sites were later suspended and then deleted. For anonymous deploys from its command-line tool, the documentation states the window plainly: you can claim the project within one hour. A reply on Netlify’s forum says one user’s anonymous drop “was automatically deleted because it was not claimed”.
So claim the site the moment it works. Two more things to know:
- Claimed does not always mean public. Teams created on or after 28 July 2026 make new projects private by default, drops included. On the free plan only the team owner can see a private project until you select Make public.
- An unclaimed drop can hold your domain. One forum thread from June 2026 describes a custom domain that could not be added to a new project because an old, unclaimed anonymous drop still had it. The user had to ask Netlify support to release it.
Where drag-and-drop deploys run out
Drop is excellent for a first deploy. It gets harder the second, tenth and fiftieth time.
Size. Netlify says uploads under 50 MB work best, and single files over 10 MB may get the deploy stuck. Your computer also needs free memory of roughly four times the uncompressed project size. For anything larger, Netlify points you to its command-line tool.
Every update is manual. You rebuild on your laptop, find the right folder and drag it again. Nothing records which version of your code is live or who changed it.
One wrong drop replaces a live site. Updates go straight to production. In a July 2026 forum post, a beginner developer at a family-run business described dragging a hobby project’s files “directly on top of my live” business site. Git gives you a commit and a review step before that can happen.
Each update is a production deploy. On Netlify’s credit-based free plan, every successful production deploy costs 15 of the month’s 300 credits, and there is no preview step on a drop. Our guide to Netlify free plan limits and credits shows how fast that adds up.
No collaboration. A teammate cannot propose a change. They send you files, and you drop them.
When to move from drag-and-drop to Git
Move when any of these is true:
- You update the site more than once or twice a month.
- More than one person edits it.
- It is a client or business site that must not break by accident.
- You want to see what changed, and put the last good version back quickly.
- You are tired of rebuilding locally before every update.
Netlify’s guide on how to deploy a site says the same: Git deploys are “the right choice for any project with a repo behind it”. If your site is a one-time event page or a quick demo, Drop is still fine.
Step 1: put the folder in a Git repository
If your project has never been in Git, these commands create a repository and push it to GitHub. Create an empty repository on GitHub first (GitHub explains how in creating a new repository), then run:
cd my-site
git init
git add .
git commit -m "First version of my site"
git branch -M main
git remote add origin https://github.com/your-name/my-site.git
git push -u origin main
The git init reference covers the options if you need them.
Step 2: connect the repository to your host
On Netlify you can do this from the dropped project itself: go to Project configuration, Developer settings, Continuous deployment, Repository, and choose Push to new repository. Netlify creates the repository on GitHub and pushes your files; that path supports GitHub only. After that, every push rebuilds and redeploys the site.
On any other host, you create a new site from the repository. How that works end to end, including what
happens between git push and a live URL, is in our guide to
push-to-deploy from GitHub.
How static sites deploy on Voroa
Voroa does not have a drag-and-drop or upload deploy. Every Voroa site deploys from a Git repository, which is the workflow this article recommends moving to anyway. Here is how a static site works:
- Connect GitHub and pick the repository and branch.
- Set the folder to serve:
/for plain HTML at the top level, or a committed build folder such as/distor/build. - Deploy. You get a live URL with HTTPS.
- Turn on auto-deploy on every push, so each push to that branch publishes a new release.
One difference from a signed-in drop matters: a Voroa static site does not run a build. It serves the files in your repository as they are, just like a drop made without signing in. Commit your built output, or, if you want the build to run on every push, deploy the same repository as a web service, which installs dependencies and builds for you.
If your code is not on GitHub, Voroa can also build from any Git URL over https, public or private with an access token. Those services do not deploy on push by themselves; you deploy from the dashboard or call a deploy hook from your CI.
| What | Drag-and-drop on Netlify | Static site on Voroa |
|---|---|---|
| How you deploy | Drag a folder in the browser | Push to a GitHub branch |
| Account needed | Not at first, claim later | Yes |
| Build step | Only when signed in | None; commit the output, or use a web service |
| Update | Drag the folder again | git push |
| Undo a bad update | Pick an older deploy in the dashboard | Roll back to the previous release |
| Custom domain | Yes, after you claim the site | 2 on the Free plan, with HTTPS |
| Where it runs | Global CDN | Mumbai (IN) |
| Bill when you grow | US dollars | Rupees, with a GST invoice |
Static hosting on Voroa is free and needs no card. Single-page apps need one note: a static site serves
only files that exist, so a visitor who refreshes on a route such as /dashboard gets a 404. Use hash
routing, or deploy the app as a web service.
Publish your static site from GitHub
If you are moving off drag-and-drop, put the folder in a repository, connect it, and every push becomes a deploy you can roll back. See what Voroa static site hosting includes, or follow the step-by-step guide to deploy a static site from a repository.
FAQ
Is Netlify’s drag-and-drop deploy free?
Yes. It works on the free plan. Once the site is claimed, it counts towards the plan’s 300 monthly credits like any other site, and each update you drop is a production deploy.
Can I deploy a React or Vite app by dragging the folder?
If you are signed in, Netlify can detect the framework and build it. If you are not, drop the built
output folder (dist or build), not the source folder.
Why does my dropped site ask for a password?
Anonymous drops are password-protected until you claim them by signing up or logging in.
Can I connect a custom domain to a dropped site?
Yes, after you claim it. If Netlify says another project is already using the domain, an old unclaimed deploy may still hold it, and you need to ask Netlify support to release it.
Does Voroa have a drag-and-drop deploy?
No. Voroa deploys from GitHub, or from any https Git URL. There is no upload page.