A WeTransfer alternative for business use
When file transfer stops being personal, three things start to matter that no free tier provides: a data processing agreement naming who is responsible for the data, retention you control rather than one imposed on you, and continuity when the person who sent the file leaves. Transfer size, which is what every comparison leads with, is usually the least important of the four.
This is about what changes when a company rather than a person is sending. If you are a freelancer, the general comparison is the more useful page.
The four questions a business actually has to answer
Who is responsible if this leaks? If the file contains personal data about anyone — a client list, employee records, photographs of identifiable people — you are the controller and the transfer service is your processor. That relationship has to be written down. See what the GDPR actually requires.
Where does the data physically sit, and who can compel access to it? These are two different questions and the second one is the one people forget. A US-owned company storing data in Frankfurt is still subject to US legal process. The CLOUD Act piece covers why.
What happens when the sender leaves? If delivery links belong to a personal account, they leave with the person. This is the failure that costs real money, and it is almost never on anyone's evaluation checklist.
How long do we keep it? Both directions matter. Too short and you cannot re-deliver. Too long and you are holding personal data you have no reason to hold, which is a liability rather than an asset. Retention is a decision, not a default.
What to look for, in order
A DPA you can actually get
Not "we are GDPR compliant" on a marketing page — an actual data processing agreement you can sign or accept, listing sub-processors and where they operate. If a service cannot produce one, it is not usable for business data involving people, whatever its transfer limits are.
Shared ownership, not shared logins
The common workaround is one account with a shared password, which fails an audit and breaks the moment someone changes it. What you want is named people with their own access to the same workspace, so that leaving is a revocation rather than a handover.
Retention you set
The free-tier model is "we delete it in seven days". The business requirement is usually "we keep this for the length of the engagement and then delete it deliberately". Those are opposite defaults.
Delivery that looks like you
A client receiving a deliverable on a page carrying another company's logo and, on some free tiers, another company's advertising, is a small thing that reads as unprofessional. Custom domains solve it properly; branded pages solve it partly.
Where the services stand
I run Yungle, so weigh what follows accordingly. Everything about another company below comes from their own documentation, checked on the date given, and there are no competitor prices anywhere on this site because they move faster than I can keep up with.
WeTransfer (checked 31 July 2026) is ad-supported on the free tier, with a 3 GB ceiling counted across a rolling 30 days, and never-expiring transfers only on the top tier. It is the default because it is the default; for business use the questions above are the ones to put to them directly.
Dropbox Transfer (checked 31 July 2026) has no advertising and 30-day default retention, and inherits Dropbox's business account structure. If the company already runs on Dropbox, this is the path of least resistance and a perfectly reasonable answer.
Filemail (checked 1 August 2026) publishes a Business plan listing transfer size as "Any Size", permanent file availability and 1 TB of storage per user. If your problem is genuinely enormous files moving fast, this is the one in the category built for it.
SwissTransfer (checked 1 August 2026) is free, 50 GB, and excellent — but it is designed for individual sending. Files delete after 15 days, and archives over 10 GB have to be downloaded file by file. It is not a business delivery tool and does not claim to be.
Yungle is built around the delivery case: collections that do not expire on a paid plan, folder structure preserved, client proofing, file request links, workspace members with their own access, and delivery on your own domain on the top plan. Data lives on one server in Germany with backups in the EU, and there is a DPA you can read before signing anything.
One thing to establish before committing: there is no service level agreement, so if guaranteed uptime is a contractual requirement for you, buy from someone who sells one.
The evaluation that actually predicts problems
Skip the feature grid. Ask these five, in writing, of whichever service you are considering:
- Can we have a data processing agreement, and who are your sub-processors?
- Which country do the files sit in, and which country's courts can compel you to produce them?
- When an employee leaves, what happens to the links they created?
- Can we set how long files are kept, in both directions?
- What does the recipient see — our brand, yours, or an advertisement?
Any service worth using can answer all five quickly. The ones that cannot are telling you something useful.
If the answers matter to you and you are comparing on price rather than on these, you are comparing the wrong column. The cost of one badly-handled leak of client data is not in the same order of magnitude as the difference between any two plans in this category.