Skip to content

drophost

drophost vs WeTransfer

WeTransfer and drophost both move files without stuffing an email inbox.The difference shows up after the send: WeTransfer is built around a transfer that is meant to finish—often with an expiry clock—while drophost is built around a project URL you can leave in a CRM note, Slack pin, or proposal thread and update in place. If your job is a multi-gig archive that should vanish after the download, WeTransfer still fits. If your job is a deck, brief, PDF, or HTML preview that reviewers will reopen for weeks, drophost is the sharper tool.Durable project links versus expiring transfers
  • drophost links stay until you delete the project
  • Replace a file without minting a new URL
  • WeTransfer still wins for huge one-off archives

What each product is optimizing for

WeTransfer’s product language is transfer: pick files, send, notify, download, done. That model is excellent when the artifact is a one-time package—raw footage, a print-ready dump, a zip nobody needs next month. drophost’s model is a project: one signed-in upload becomes a public HTTPS URL on a drophost.space subdomain (or a custom domain on paid plans). Recipients open the link in a browser with no drophost account. The URL stays live until you delete the project. That is a different contract with the people on the other end of the link.

Expiry, bookmarks, and the second review round

Most transfer workflows quietly assume the conversation ends after download. Real client work does not. A proposal gets a legal tweak. A moodboard gains three more frames. A static HTML prototype needs a spacing fix. On drophost you replace the file on the same project and every CRM field, email, and Slack message that already points at that URL keeps working. On WeTransfer you often mint a new transfer, chase the old link out of inboxes, and hope nobody is still on the expired package. If your pain is “the link died again,” durability is the feature—not a larger attachment size.

File types and plan limits that matter in practice

drophost Free covers one project and 2 MB for HTML sites, Word, text, Markdown, CSV, images, and PDFs up to 0.5 MB, plus a browser editor for text and web files. Starter at €5/mo or €50/yr raises you to 8 projects and 100 MB with password protection, custom domains, analytics, branding removal, and full PDF sharing. Pro at €12/mo or €120/yr scales to 30 projects and 500 MB. WeTransfer’s free and paid tiers are tuned for larger single transfers. If you routinely ship multi-gig archives once and forget them, stay on a transfer tool. If your typical file is a deck, brief, export, or site zip under plan limits, drophost’s limits match the job.

Passwords, branding, and how the link feels to a client

Paid drophost plans add a password gate without forcing the recipient through another account signup. That matters for unfinished decks and private proposals. Starter and Pro also remove drophost branding and support custom domains so the URL can look like part of your studio, not a generic transfer bounce page. WeTransfer’s paid tiers add their own brand and transfer controls. Pick based on whether the recipient should feel like they opened your project space or downloaded a package that was mailed to them.

Agents and MCP: publishing without leaving chat

drophost exposes MCP at /api/mcp so Claude, ChatGPT, Cursor, or a script can call publish_file or publish_site with a hashed API key from Settings. Humans can connect with URL-only OAuth. The agent returns a normal browser URL—recipients never need an AI client. WeTransfer is not built as an agent publish surface. If your workflow is “generate the brief in chat, then put a live link in the thread,” drophost is the product that closes that loop without a separate desktop uploader ritual.

When WeTransfer is still the right choice

Choose WeTransfer when the file is enormous, the send is truly one-shot, and expiry is a feature rather than a bug—clearing sensitive dumps after a few days can be desirable. Choose drophost when the same people will reopen the same artifact across review rounds, when you want HTML hosting and document sharing in one place, or when an agent should publish the update. Many teams keep both: WeTransfer for bulk archives, drophost for the living handoff link that sits next to the invoice.

A concrete week-long client handoff on drophost

Monday: upload the PDF proposal on Starter, password it, paste the URL into the kickoff email. Wednesday: legal tweaks the fee table—you replace the PDF, same URL. Friday: they ask for an HTML clickable mock—you switch to Website mode, drop a zip with index.html on a named subdomain, and send that second project link. Nothing expired. Nobody created a drophost account. Nobody hunted for “final_v3_USE_THIS.pdf” in a transfer history. That loop is the reason this comparison page exists.

drophost vs WeTransfer: feature comparison

drophost compared with WeTransfer
FeaturedrophostWeTransfer
Primary modelDurable project URLExpiring transfer
Link lifetimeUntil you deleteOften days/weeks
Replace file, same URLYesUsually a new transfer
Browser uploadYesYes
Static HTML / zip hostingYesNo
PDF sharingFree ≤0.5 MB; full on paidAs a transferred file
Password without recipient accountStarter / ProPaid tiers
Custom domainStarter / ProBrand / paid options
MCP / agent publishYes (/api/mcp)No
Best fitOngoing handoffs & previewsLarge one-off sends

Common questions

Is drophost a WeTransfer alternative?

Yes for durable handoffs. Use drophost when reviewers will reopen the same URL across rounds. Keep WeTransfer when you need a large one-off transfer that is meant to expire.

Do drophost links expire like WeTransfer?

No. drophost project links stay live until you delete the project. Replacing a file keeps the same URL.

Can I send multi-gig archives with drophost?

drophost is built for documents, images, and static sites within plan limits—Free 2 MB, Starter 100 MB, Pro 500 MB. Use a transfer tool for routine multi-gig archives.

Can recipients open a drophost link without an account?

Yes. Recipients open the HTTPS link in a browser. Add a password on Starter or Pro if the file should stay private—still without creating a drophost account.

Can I host an HTML preview as well as send a PDF?

Yes. drophost Website mode hosts a zip with index.html, and file projects share PDFs and Word docs from the same account.

Can an agent publish to drophost instead of using WeTransfer?

Yes. Connect MCP at /api/mcp and use publish_file or publish_site. The agent returns a normal browser URL recipients can open.

Related

Keep the handoff link, not another transfer email

Upload a document or static site on drophost, paste one URL into your thread, and replace the file when the revision lands—recipients keep the same bookmark.