drophost
drophost vs SwissTransfer
- drophost: durable URLs
- SwissTransfer: large temporary sends
- drophost: sites and MCP too
Expiry is the product on transfer tools
Temporary transfer is a feature when you do not want stale links floating around. It is a bug when a client reviews next week. drophost projects stay until you delete them—you control end-of-life explicitly. Large temporary packages and living review links can both be right—just not for the same file. Free remains useful to validate the loop at 2 MB before you pay.
Size versus artifact type
SwissTransfer aims at large packages. drophost aims at documents, images, and site zips inside Free 2 MB, Starter 100 MB, or Pro 500 MB. Match tool to payload. Large temporary packages and living review links can both be right—just not for the same file. Starter at €5/mo is the usual upgrade when passwords or domains appear.
Sites and passwords
HTML hosting and Starter passwords are drophost-native. Transfer tools send blobs; they do not host clickable prototypes. Large temporary packages and living review links can both be right—just not for the same file. Pro at €12/mo fits teams that keep many parallel links online.
MCP
Agent publish exists on drophost, not on SwissTransfer. Chat-native updates need durability. Large temporary packages and living review links can both be right—just not for the same file.
Regional / brand preferences
Some teams pick SwissTransfer for brand and jurisdiction reasons. That can matter more than features—honor it, and still use drophost for durable web previews. Large temporary packages and living review links can both be right—just not for the same file.
Decision rule
Bulky expiring send → SwissTransfer. Ongoing document/site handoff → drophost. Large temporary packages and living review links can both be right—just not for the same file.
European transfer brands versus project URLs
Brand and jurisdiction can decide the transfer tool. They should not decide how you host an HTML prototype. Keep SwissTransfer for bulky packages; keep drophost for living web previews and docs. Large temporary packages and living review links can both be right—just not for the same file.
Deleting on purpose
Durable does not mean forever. Delete drophost projects after the engagement. Explicit deletion is clearer than hoping an expiry email was noticed. Large temporary packages and living review links can both be right—just not for the same file.
Review calendars versus transfer calendars
Transfer expiry is calibrated to download completion. Review calendars are calibrated to humans being busy. A board member opens the deck nine days later. If the transfer died on day seven, you resend and look disorganized. If the drophost project is still there, you look prepared. Choose the calendar that matches the relationship, not the default of the upload widget you used last year. Large temporary packages and living review links can both be right—just not for the same file.
HTML is not a transfer attachment
Shipping a zip of a site through a transfer tool forces download-and-unzip theater. Hosting it on drophost lets stakeholders click. When the artifact is interactive, durability and hosting beat parcel shipping—even if SwissTransfer remains perfect for the raw footage dump that accompanies the project. Large temporary packages and living review links can both be right—just not for the same file. Prefer SwissTransfer for bulky expiring packages; prefer drophost for decks and sites that must survive a slow review calendar. Delete drophost projects deliberately when the engagement ends.
Creative production versus client presentation
Creative teams move huge plates through transfer tools. Client presentation of the selected stills or the HTML lookbook should not inherit that expiry. Use SwissTransfer on the way in; use drophost on the way out to the client.
Notification habits
Transfer tools email download notifications. Project links live in CRM fields. If your process is CRM-shaped, drophost matches it; if your process is inbox-shaped one-shots, SwissTransfer matches it.
drophost vs SwissTransfer: feature comparison
| Feature | drophost | SwissTransfer |
|---|---|---|
| Link expiry | Until you delete | Temporary |
| Static sites | Yes | No |
| Large multi-GB transfers | Plan limited | Yes |
| Password protection | Starter / Pro | Available |
| Agent publish | MCP | No |
| Best fit | Ongoing handoffs | Large one-offs |
Common questions
Is drophost a SwissTransfer alternative?
For durable handoffs within plan limits, yes. For large temporary transfers, SwissTransfer remains a better fit.
Do drophost links expire automatically?
No. They stay until you delete the project.
Can drophost send multi-gig packages?
Stay within Free 2 MB, Starter 100 MB, or Pro 500 MB. Use a transfer tool for huge one-offs.
Can SwissTransfer host a static site?
No. drophost can.
Can agents publish to drophost?
Yes via MCP. SwissTransfer is not an agent publish surface.
Related
When expiry would break the review cycle
Use drophost for living handoffs under plan limits. Keep SwissTransfer for bulky one-off packages that should disappear.