Cloud storage or a file transfer? They solve different problems
Both let you send someone a file, which is why they get compared. But storage answers "where does this live?" and transfer answers "how does this get there?" — and most of the frustration with either one comes from asking it the other question.
The core difference
| Cloud storage | File transfer | |
|---|---|---|
| Purpose | A place files live | A way files move |
| Lifetime | Until you delete it | Expires on its own |
| Accounts | You need one; often the recipient too | Usually neither side |
| Cost model | You pay for what you keep | You pay for what you move |
| Revocation | Change sharing settings any time | Expiry does it for you |
| Versioning / history | Yes | No |
| The failure mode | Old links nobody revoked | The file is gone when someone wants it again |
Use storage when
- The file has a long life. Contracts, reference material, anything someone will come back to in three months.
- More than one person needs to work on it. Simultaneous editing and version history are the entire point, and no transfer offers them.
- You need an access record. Who opened it, when, from where — required in many professional contexts and simply unavailable from a transfer.
- The same file goes to many people over time. One canonical location beats fifteen copies with divergent edits.
Use a transfer when
- It is a delivery, not a publication. One file, one recipient, one occasion.
- The recipient has no account and should not need one. A client, a print shop, a relative, a stranger on a marketplace. "Create an account to receive this" is a real drop-off point.
- You want it gone afterwards. Expiry is a security control, not a limitation — see how long a shared file should stay downloadable.
- The file is too big for your storage plan and you have no interest in keeping it. Paying for permanent storage to move something once is the wrong shape.
- The content is sensitive enough that you do not want it sitting anywhere indefinitely.
The two failures this prevents
Using storage as a transfer leaves a trail of share links pointing at live files. Every one is a working key for as long as nobody revokes it, and nobody revokes them, because the moment you finish sending is the moment you stop thinking about it. Most accidental disclosures from cloud drives are not breaches — they are a link from two years ago that still works and got forwarded.
Using a transfer as storage means the file expires while the recipient still needs it, and now you are the person who has to find and re-send it. Transfers have no version history, no meaningful audit and no per-person revocation, so a file that matters long-term is in the wrong container.
The combination that actually works
Deliver with a transfer; let the recipient store it wherever it belongs to them. The transfer does the moving and disappears; their drive does the keeping. Neither system is asked the question it is bad at, and expiry costs nothing — by the time the link dies, the file already lives somewhere permanent.
More guides
Six ways to get a file from your phone to a computer — and where each one breaks
Cable, cloud drive, email, messaging apps, local network and transfer services compared: size ceilings, what each one costs you in privacy, and the specific situation where each method falls apart.
Email attachment size limits — and why your file is bigger than you think
The attachment ceiling for Gmail, Outlook, Yahoo, iCloud, Proton and Zoho, why encoding makes your file about 33% larger in transit, and the four ways past the limit.
What end-to-end encryption actually protects — and what it does not
The difference between HTTPS, encryption at rest and true end-to-end encryption, why the key matters more than the cipher, and the four things E2EE will never save you from.
Try SendMyFile
Encrypt a file in your browser and hand it over with a 9-digit code. No account, and it deletes itself.
Try SendMyFile