drophost
drophost vs Netlify Drop
- drophost: files and sites
- Netlify Drop: static folders
- drophost: MCP for agents
The overlap is real
Both let you drag finished static files and get a URL without git. That is the whole appeal. Competition is honest here—pick on adjacent features and habit. Site-only drops are fine until tomorrow’s artifact is a PDF; plan for the week, not the widget. Free remains useful to validate the loop at 2 MB before you pay.
Documents Drop does not host
Netlify Drop is site-only. drophost Free includes Word, text, Markdown, CSV, images, small PDFs, and HTML. Starter expands PDF and adds passwords. If your week mixes prototypes and proposals, one product reduces tool switching. Site-only drops are fine until tomorrow’s artifact is a PDF; plan for the week, not the widget. Starter at €5/mo is the usual upgrade when passwords or domains appear.
Platform gravity
Drop can be an on-ramp into broader Netlify (forms, functions, git). That is great if you want the platform. drophost stays focused on project URLs—intentionally narrower. Site-only drops are fine until tomorrow’s artifact is a PDF; plan for the week, not the widget. Pro at €12/mo fits teams that keep many parallel links online.
Passwords and domains
drophost Starter bundles password + custom domain + branding removal at €5/mo. Map that against whatever Netlify features you would enable after a Drop. Site-only drops are fine until tomorrow’s artifact is a PDF; plan for the week, not the widget.
Agents
MCP publish_site is native on drophost. Drop is a human browser flow. Agent-produced HTML lands more naturally on drophost. Site-only drops are fine until tomorrow’s artifact is a PDF; plan for the week, not the widget.
Decision rule
Already in Netlify and site-only → Drop. Mixed files + sites + agents → drophost. Production later → graduate to full Netlify from git. Site-only drops are fine until tomorrow’s artifact is a PDF; plan for the week, not the widget.
Habit formation across artifact types
Teams that only Drop sites invent a second tool for PDFs. Teams on drophost reuse one drop zone. Habit beats micro-optimizing the site-only path. Site-only drops are fine until tomorrow’s artifact is a PDF; plan for the week, not the widget.
Graduation path
Start on drophost. If the preview becomes a marketed property with forms and git, graduate to full Netlify. You did not waste a repo on day one. Site-only drops are fine until tomorrow’s artifact is a PDF; plan for the week, not the widget.
Support burden of two drop habits
Design uses Drop. Sales uses a file host. Someone always uploads to the wrong place. Standardize on drophost for all outbound artifacts under plan limits, and reserve Netlify for production git deploys. Fewer “where did you put it?” messages. Site-only drops are fine until tomorrow’s artifact is a PDF; plan for the week, not the widget.
Password before the client forwards freely
Drops are easy to forward. Starter passwords on drophost slow casual leaks of unfinished work without requiring Netlify identity setup. Turn the password off when the work is public. Site-only drops are fine until tomorrow’s artifact is a PDF; plan for the week, not the widget. Prefer Drop when you are already standardized on Netlify and the artifact is only a site; prefer drophost when the week mixes PDFs, Word, and HTML. Agents publishing via MCP also point to drophost.
End-of-week cleanup
Friday cleanup is easier when previews are drophost projects you can delete in a list—not Netlify sites entangled with team permissions. Use Drop when you are intentionally entering the Netlify platform; use drophost when you are intentionally leaving a temporary URL.
drophost vs Netlify Drop: feature comparison
| Feature | drophost | Netlify Drop |
|---|---|---|
| Drag-and-drop site | Yes | Yes |
| PDF / Word sharing | Yes | No |
| Password protection | Starter / Pro | Platform features |
| MCP | Yes | No |
| On-ramp to full platform | Focused project URLs | Yes (Netlify) |
| Best fit | Handoffs + previews | Site drops into Netlify |
Common questions
How is drophost different from Netlify Drop?
Both drag-and-drop static sites. drophost also shares PDFs, Word, images, and Markdown, and supports MCP agent publish.
Should I use Netlify Drop if I already pay for Netlify?
If you only need a site and want platform gravity into Netlify, Drop is fine. If tomorrow’s handoff might be a PDF, drophost is broader.
Can I password a Drop-style preview on drophost?
Yes on Starter and Pro.
Can an agent publish to drophost like a Drop?
Yes with publish_site through MCP.
Does drophost lead into a bigger hosting platform?
drophost stays focused on project URLs. Netlify Drop can on-ramp into forms, functions, and git deploys.
Related
When the next handoff might not be HTML
Use drophost when today’s zip preview and tomorrow’s PDF proposal should live in the same simple workflow.