Netlify Drop: Is It Free? Limits and 6 Alternatives

Netlify Drop (app.netlify.com/drop) publishes a dragged project folder or ZIP to a netlify.app URL with no account needed, but the link sits behind a temporary password until you claim it by signing up or logging in. It's free: a claimed project runs on Netlify's Free plan, which has 300 credits a month for deploys, bandwidth and requests, and when an account runs out, every project on it pauses until the next billing cycle (October 2026). If your site changes often, gets steady traffic or needs a password, one of the six alternatives below may fit better.

Updated October 20, 2026: Netlify Drop doesn't need an account, unclaimed drops do expire, GitHub Pages needs a public repo on GitHub Free, and Netlify's credit prices were out of date.

What is Netlify Drop?

Netlify Drop is Netlify's drag-and-drop deploy page. You drop a project folder or a ZIP onto it, and Netlify publishes the files to a netlify.app address. No Git repo. No terminal.

How you use it comes down to one question: are you signed in?

1. Open app.netlify.com/drop.
2. Signed out? Drop the built output folder (dist, build, whatever your tool produces) or a ZIP of it. Signed in? Drop the source and Netlify builds it.
3. Copy the netlify.app URL. If you dropped signed out, claim it next, or visitors hit a password prompt.

The split exists because Netlify only runs a build when you're logged in. Signed in, it detects your framework and builds the project before publishing. Signed out, your files go live exactly as they are, so a Vite or Next.js source folder isn't a working site yet. Netlify's July 2026 Drop changelog says that if you drop a folder whose framework needs a build, it sends you to log in first.

If all you have is one page, I've covered other ways to host a single HTML file separately.

Do you need a Netlify account for Netlify Drop?

No. Netlify Drop works signed out, but the link stays behind a temporary password until you claim it by signing up or logging in.

Until then, anyone you send the link to hits a password prompt. Claiming means logging in or signing up, and it moves the project into your Netlify team. Netlify's post on the history of Drop sums up the deal: "Claim the site if you want to keep it; otherwise, it expires on its own."

How long you get is the fuzzy part. Netlify doesn't publish a current deadline. Its post on Drop's history says that in January 2022 the team "cut the claim window from 24 hours to one" and capped anonymous sites at three per IP address. By early 2025, the post says, a retention policy "suspended unclaimed sites, then deleted them a week later." Claim it right away. Treat claiming as the last step of the deploy, not homework for later.

If you just signed up to claim it, check the project's visibility. Netlify's pricing lists "Private by default until you publish" on Free, and the Drop quickstart says that after you claim, "the outcome depends on your plan." So the link may not open for anyone else until you select Make public under Project configuration > General > Visitor access > Project visibility.

Once it's claimed, the project can take a custom domain and updates, and anything you drop while signed in gets built.

If a throwaway link with no signup is genuinely all you need, Tencent's EdgeOne Pages Drop says a link made without registering lasts 1 hour (pages.edgeone.ai, October 2026).

Is Netlify Drop free?

Yes, Netlify Drop is free: dropping costs nothing, and a claimed project runs on Netlify's Free plan with 300 credits a month (netlify.com/pricing, October 2026). Everything draws from that one balance:

• A production deploy costs 15 credits.
• Each GB of bandwidth costs 20 credits.
• Every 10,000 web requests cost 2 credits.

Here's how fast that goes. Four production deploys (60 credits), 10 GB of bandwidth (200) and 200,000 requests (40) add up to exactly 300. That's the month.

Think of it as a shared health bar. Deploys, traffic and requests all chip away at it. When it hits zero, Netlify pauses every project on the account, not just the busy one, until the next billing cycle or an upgrade. Visitors to a paused project see "Site not available," and a Free team can't buy extra credits or turn on auto recharge, per Netlify's paused projects docs. The same docs say "all deploys will pause, including Deploy Previews and branch deploys," so you can't even push a fix until the cycle resets or you upgrade. The Free plan won't send you a surprise bill. It will take your sites offline, though, and that's the trade.

More credits cost money. Personal is $9 a month for 1,000 credits, and Pro is $20 a month for the whole team with 3,000 credits.

Custom domains are included on Free. Once you've claimed a drop, you can point your own domain at it without paying anything.

How do you update a Netlify Drop site?

To update a Netlify Drop site, drag the updated project folder onto the drop area in the project dashboard, under Production deploys. Drop the whole folder again, not just the file you edited, because the new drop becomes the live version of the site.

That update goes straight to production, and each production deploy costs 15 credits. Twenty updates in a month use all 300 Free credits, with nothing left for visitors. If you're polishing a CS project every night before the deadline, batch your edits and drop once.

What are Netlify Drop's limits?

Netlify doesn't publish a hard size cap for Drop, but it says deploys under 50 MB work best and files over 10 MB may get a deploy stuck (October 2026). For anything bigger, it points you to the Netlify CLI.

It also asks for a reliable connection, since network hiccups can stall a deploy, and roughly four times your uncompressed project size in free memory. I write from a rotation of Austin coffee shops, and 50 MB over coffee-shop Wi-Fi is already a big ask.

Privacy is the other limit. A site password needs Netlify Pro, $20 a month, and a freshly claimed project may stay private to your team until you make it public. Our Netlify password protection guide walks through Netlify's options, and there's a host-by-host look at how to password protect a static site.

And the build rule still applies: no login, no build.

Netlify Drop alternatives compared

Here's how six Netlify Drop alternatives line up on accounts, free limits and passwords. If you'd rather compare how many steps each drag-and-drop host takes to a first URL, that's a separate walkthrough.

Prices and limits checked October 2026

Sources: Netlify's Drop quickstart, pricing, post on the history of Drop, project visibility docs and paused projects docs; Vercel's Drop guide, pricing and limits; Cloudflare's Pages overview, direct upload docs, Pages limits and Zero Trust pricing; tiiny.host's comparison page; Surge pricing and SSL docs; GitHub's Pages limits and file upload docs; Hostsmith pricing.

Vercel Drop

Vercel Drop (vercel.com/drop) fits a framework project, say a Next.js or Vite app, that you want built and hosted in one go, as long as you don't mind signing in first. It's the most direct rival to Netlify's page, and Vercel even published its own Vercel Drop vs Netlify Drop guide (updated September 2026).

Sign in, then drop a file, a folder or a ZIP. Vercel detects the framework and builds it. The free Hobby plan allows 100 deployments a day and 100 GB of bandwidth a month, for personal, non-commercial use only. Pro is $20 a month per seat plus usage, and a password costs another $20 a month per protected project.

The trade-off shows up on day two. Every drop creates a brand-new project, so you can't drag a new version over the old one. Updates go through Git or the Vercel CLI. And anything commercial, client work included, belongs on Pro. If it's Vercel's wider platform that's bugging you, I compared other Vercel alternatives too.

Cloudflare Pages

Cloudflare Pages fits anyone who wants a $0 bill on their own domain and expects real traffic. You pay for that with a busier dashboard.

The drag-and-drop lives under Workers & Pages: create an application, then drag and drop your files. One upload takes up to 1,000 files, each up to 25 MiB. Unlike Vercel Drop, you can come back to the same project, select "Create a new deployment" and pick Production to upload a new version, and the project keeps its pages.dev address. A preview gets its own URL instead.

On Free, static asset requests are free, custom domains work, and there's no credit balance to babysit. Cloudflare's limits page lists 500 builds a month. It describes builds as what runs when you push to Git, and it doesn't say whether direct uploads count toward that 500.

Two things to know before you drop. First, Cloudflare's docs are blunt about it: "If you choose Direct Upload, you cannot switch to Git integration later." Pick your workflow up front. Second, Cloudflare's Pages docs now steer new projects toward Workers, so Pages isn't where it sends newcomers anymore. Direct upload still works.

There's no shared password, either. The closest thing is Cloudflare Access, which emails visitors a one-time PIN. It's free for up to 50 users, and you set it up in the separate Zero Trust console. Reasonable for a client or two. A lot of setup for a class project.

tiiny.host

tiiny.host fits someone who wants one file online with no credit math and no claim step. You make a free account first, then upload, so there's no password-gated waiting period and no balance to watch.

tiiny.host's own comparison page lists the Free plan as 1 active project, uploads up to 3 MB (0.5 MB for PDFs), and 5,000 visits with 5 GB of bandwidth. Paid plans start with Tiny at $5 a month on yearly billing. Custom domains and password protection both start on Solo, at $13 a month on yearly billing.

The limits are the whole story here. Half a megabyte is a tight squeeze for a PDF with images, and one active project means one thing online at a time. The page doesn't say whether free sites expire, so check before you lean on a link for months. If the document is the point, there's more on how to host a PDF online.

Surge

Surge fits front-end developers who already have Node.js installed and would rather type a command than open a browser. There's no web upload at all.

Install it with npm install -g surge, run surge inside your project folder, and the first run sets up your Surge login right in the terminal. The Free plan lists "unlimited publishing," custom domains and Basic SSL (surge.sh/pricing), and Surge's docs say custom domains get free managed certificates, provisioned automatically. HTTPS works on Free; forcing it is paid. The pricing page puts "Force http to https" on Professional, $30 a month, along with your own SSL certificate, password protection and unlimited projects.

It's not abandoned, either. The CLI is still shipping releases, and version 0.46.0 landed on npm on October 19, 2026.

The trade-off is who can use it. Without Node and a terminal, Surge is a non-starter. And if you need a password, that's the $30 plan or nothing.

GitHub Pages

GitHub Pages fits a personal or open-source site whose code can live in a public repo. If your project is already on GitHub, it's probably the shortest path.

There's no drop zone, but files can be dragged into a repo in the browser: up to 100 files at a time, 25 MiB each (docs.github.com). Turn on Pages in the repo's settings and the site goes live at a github.io address. Custom domains are free, bandwidth has a soft limit of 100 GB a month, and a published site can be up to 1 GB.

Read the fine print on two points. On GitHub Free, GitHub's docs say "the repository must be public," so a private repo needs a paid plan. And GitHub's terms bar running an online business on Pages. There's no password protection, either. For hosts that pick up where Pages stops, the GitHub Pages alternatives roundup goes deeper.

Hostsmith

Hostsmith (we build it, so factor that in) has the lowest price on this list for a built-in shared password on one site. From Starter, $5 a month on annual billing ($9 month to month), Private Sites puts a password in front of the site, or lets in only the email addresses you list. Elsewhere, a site password starts on tiiny.host's Solo at $13 a month billed yearly, on Netlify Pro at $20 for the whole team, and on Surge Professional at $30 (October 2026).

The same plans run public sites, too. Starter keeps one site on a hostsmith.link address, and Pro, $15 a month on annual billing ($21 month to month), covers 5 sites on your own domains, private or public. You drag in a ZIP of your folder, or a single HTML file, PDF or image. To update the site, drag in a fresh ZIP at the same URL. There's no charge per update: a new upload only has to fit the plan's storage, 50 MB on Starter and 5 MB on Free.

Which Netlify Drop alternative should you pick?

Most people searching for Netlify Drop should use it and claim the site straight away. Look elsewhere when you hit one of three walls: a password ($20 a month on Netlify Pro), frequent updates (15 credits each), or traffic that burns through 300 credits.

• You need a password. Hostsmith, from Starter at $5 a month on annual billing ($9 monthly), with a shared password or a list of approved emails. tiiny.host's Solo plan has one too, at $13 a month billed yearly. If visitors can sign in with an emailed PIN instead, Cloudflare Access is free for up to 50 users.
• You update often. Cloudflare Pages takes each new upload into the same project, with no credits per deploy. Hostsmith doesn't charge per update either, and its Pro plan runs up to five public or private sites on your own domains.
• Your traffic burns through 300 credits. Cloudflare Pages, where static asset requests are free.

Frequently Asked Questions