Netlify Drop vs Birta: What an Anonymous Drop Actually Gives You

The short answer

Both get a page to a live address in one gesture. For a single HTML file, Birta's Publish HTML matches Drop: drop the file, get a link anyone opens without an account. A folder goes up through Birta's own agent, where you attach the files in its chat, or through the agent that already reads your files. The difference shows up the week after. Netlify's quickstart says an anonymous drop stays password-protected until you claim it, and its agent connector hands an agent no deploy history, no way to put an earlier version back, and no domain. The sections below are the evidence.

What you get when you drop without signing in

The deploy works. Your files go up unchanged. Netlify's create-deploys documentation says it plainly: "If you drop a project without being logged in, Netlify publishes the files as-is."

"As-is" matters. Framework detection and the build run only when you are signed in. Drop an unbuilt project anonymously and you get the unbuilt project.

The address needs a password from you. For a "here, look at this" moment, that password is the friction you were avoiding.

Claiming it is a fork rather than a finish line. Netlify's Drop quickstart, under the heading "Is your project public?", is where the password rule is written down: "If you drop without signing in, your project URL is protected with a temporary password until you claim it." It continues: "After you claim it by logging in or signing up, the outcome depends on your plan." On Credit-based plans with private by default switched on, the project stays private until you make it public, and whether that default is on "depends on when your team was created". On a Legacy plan it goes public once claimed. Which branch you land on turns on your own team, not on anything you can check from outside.

One ceiling before you drag something large: Netlify's troubleshooting notes say deploys under 50 MB work best, and files over 10 MB may get stuck.

How the same folder goes up on Birta

One file needs no account. Paste the HTML or drop one .html file into Publish HTML: your own browser draws the preview, and nothing leaves it until you press "Get a link to send". The link opens for anyone for 24 hours, search engines are told not to list it, and the same document keeps the same address while it lives. The limit is one document up to 1 MB. Inline CSS and JavaScript run; images in a folder beside the file do not travel with it, and a ZIP or several files are refused. "Keep it in my account" signs you in and turns the page into a site with a permanent address, where everything below applies.

A folder goes through an agent: attach the files in Birta's chat, or tell the agent you already use "publish this folder to Birta". The agent opens a draft, writes the files in, confirms index.html sits at the root, and publishes. Birta converts no formats. Which files reach the site, and what to do when a folder is not a website yet, is in the folder-publishing guide.

What each agent connection reaches

Netlify has an agent connector, so "an assistant can publish here" separates nothing. It documents the server at netlify-mcp.netlify.app/mcp, publishes a Claude setup guide, and has built a destination into Claude Design that needs a connected account.

Where it stops is written in their own tool source. Its map ticks off finished work and leaves the rest blank: deploy rollback is blank, choosing which deploy goes live is blank, domains are blank. The tools matched the map.

Rollback itself is real on Netlify. It sits in the dashboard, so the undo belongs to you and not to the agent that published the site.

Of the hosts this site compares Birta with, none hands an agent a version list and a rollback. Netlify is the clearest case because it marks the work unfinished in public.

What Drop keeps, honestly

A whole folder, zero setup, no account. That is Drop's real advantage. Birta matches it only for a single HTML file; a folder wants an account first, then its chat or a connected agent. For a multi-file site somebody asked to see in two minutes, that cost is the whole story.

One more row goes to Netlify on the free plan. Birta puts a mark in the corner of every page on its Free plan, and only the Team plan removes it. Netlify badges new free projects too, from 19 August 2026, but theirs is a per-project switch you can flip. A custom domain is not on this list: both connect one for free.

One more row is not a free-plan quirk. Netlify versions every deploy, lets you browse any deploy you have made, and puts an earlier one live from a Publish Deploy button with no rebuild. Their documentation calls rollbacks instantaneous. The catch is retention: Netlify deletes deploys after 30 days on Free and Standard, 90 on paid. Birta keeps the last 10 versions with no clock.

Those rows stay real. None of them covers who makes the next change.

Showing it to someone, then changing it

The two products charge opposite people. Drop is free to publish and charges the viewer a password. Birta charges the viewer nothing, and you an account once the page has to outlive a day.

What the table row below does not say is how the remarks behave. Each thread returns a number, the element it points at, whether it is open, and every message with author and time. Numbers are permanent, so "number four is still open" means something next week. After the fix the agent replies in the thread and closes it. Everyone with access gets an email digest roughly 15 minutes after the first remark. No plan gates any of it, and the walkthrough is in the versions and remarks guide.

Netlify's Drawer is the richer surface: comments, annotated screenshots, video, synced to the pull request and to Jira or Linear, with a free Reviewer seat. It is off this route for two documented reasons. Reviewers "must be approved and log in to Netlify through the Netlify Drawer", and the Drawer runs only on a Deploy Preview or branch deploy, which needs a repository or an agent run. A dragged folder has neither.

Compare the work after the first upload

Netlify takes the entry gesture, the build, the badge, deploy retention on paid plans, and any app whose addresses have to stay regular paths. The domain is a tie. Birta takes the rows where one agent has to carry the work: the version the agent can put back, the remark a stranger leaves without an account.

Use Netlify Drop when...

• The page need not outlive the moment. A one-off handoff, a demo you throw away on Friday, a file somebody asked to see.
• You want Netlify to build it. Sign in, drop an unbuilt project, and it detects the framework and builds. Birta has no build step at all.
• You are already on Netlify. One more folder in the same dashboard beats a second account for no gain.
• The site belongs in a repository. That route unlocks Deploy Previews and the Drawer, which reviews better than we do.
• The site needs what a static host cannot serve: functions, a platform-handled form, or the rewrite rule that keeps a single-page app on regular paths.

Weighing the wider platform rather than the drop box is a different comparison: Netlify alternatives covers what the credit-based free plan does when the credits run out.

Birta fits better when...

• The folder is not the end of it. Three changes, then two more, then the pricing next month. On Drop each is a rebuild and a drag; here it is a sentence to the agent that has the source.
• Somebody else has to look first. They open an address with no account and mark what is wrong where it is wrong.
• A bad publish has to be reversible by whoever caused it. Netlify's undo is a dashboard button, and the thing that broke the site is an agent that cannot reach it.
• The page has to collect something from its readers. The agent declares the fields; submissions land in the Forms tab.
• The site should stay up free without a card, on your own domain.

The trade: an account instead of a drag for anything past one HTML file, a mark on free pages that only Team removes, no build step, and no way yet to take a payment from your visitors.

If you're moving a dropped site over

A static site is your own files, and neither side holds them.

1. Step 1Get the folder backUse the local folder you dropped. If you've lost it, download the deploy from the project's Deploys page in Netlify.
2. Step 2Hand it to an agentAttach the files in Birta's chat, or point the agent you already use at the folder, and have it create a project and publish.
3. Step 3Check every page, then move the domainWalk the internal links and any form on the new address before repointing DNS. Repoint last, once the copy passes.

One thing will not travel: anything relying on Netlify's platform features, such as its forms, functions or redirect rules. Those need rebuilding against what Birta offers, and for a form that means letting the agent declare it rather than porting the markup.

The decision

One question resolves most of this: does the thing you are publishing need to be alive next month?

If not, drop it. The password is a small tax on something you were throwing away, and a single HTML file skips it in Publish HTML. Weighing hosts in general instead, the wider list is here, and the drag-and-drop comparison that is really about maintenance covers what this page skips.

If it does, weigh the week after the gesture: who makes the next change, whether they can undo it, and whether the person you sent the link to has to ask you for anything. The middle one is the row nobody in this category has closed, and Netlify says so in its own repository.

Frequently asked questions