You cannot un-send a document that went out as an email attachment or a downloaded file, because the recipient already holds their own copy. But you can un-send a document you shared through a platform that keeps the file under your control, by revoking the link so it stops opening. If you are trying to un-send a document, the honest answer depends entirely on how you sent it: an attachment is gone the moment it lands, while a tracked, revocable link can be switched off in one click, even while someone is reading it. This guide explains what is and is not recoverable, and how to share in future so pulling something back is always an option.
The panic is familiar. You sent the wrong version, attached the confidential appendix by mistake, shared a price list with the wrong client, or a deal fell through and you would rather the other side no longer had your financials. What happens next is decided by a choice you made before you hit send: did you hand over a file, or did you share access to one?
Why you can't un-send an email attachment
An email attachment is a copy. When you attach a document and send it, your email client uploads a duplicate of the file, and the recipient's email client downloads that duplicate onto their device. From that instant there are two independent copies, and you control only your own.
This is why the various "recall" features are so unreliable. Message recall in an email client only works within the same email system, only if the recipient has not already opened the message, and often just sends a second email asking the first to be ignored. It does nothing about a file that has been downloaded, forwarded, or saved to a phone. Once an attachment has landed, you have no technical way to reach it. You are relying on goodwill.
The same is true of most shared-drive links once a file has been downloaded. You can disable the link, but the copy already sitting on someone's laptop is untouched. This is one of the core reasons email is the riskiest way to send anything sensitive, a point we make in full in why an email attachment is the riskiest way to send a contract. The lesson is not "be more careful with attachments"; it is "stop sending copies of things you might need to control".
What un-sending actually requires
To genuinely un-send something, the document must never have left your control in the first place. That means sharing access to a file that lives on a platform, rather than sending the file itself. When you share a link to a hosted document:
- The recipient views the document through the platform, they do not receive a permanent copy.
- You can switch that access off at any time.
- Revoking the link means the next time they try to open it, and any time after, it simply does not load.
This is the mechanism behind real revocation. It only works if three things are true: the file is hosted, access is by link rather than download, and downloading is controlled or disabled. Get those right and "un-send" changes from an impossible request to a one-click action. Our guide to one-click revocation covers exactly how this behaves.
Two related controls make the same problem less likely in the first place. Link expiry means a link stops working after a set time whether or not you remember to revoke it, so a document does not stay open forever by default; our piece on how long a share link should stay live covers sensible settings. And version control means that when you spot you sent the wrong version, you can swap the file behind the link so everyone with access sees the correct one, without reissuing anything. Our guide to version control for documents you've already sent walks through it.
The three "oh no" scenarios and what to do
You sent the wrong version. If you shared a copy (email, download), you cannot fix it at source; the best you can do is send a correction and ask them to ignore the first. If you shared a link to a hosted document, swap the file behind the link with version control and the old version disappears for everyone. No awkward follow-up needed.
You shared with the wrong person. If it was an attachment, it is out; assume they have it. If it was a gated, tracked link, revoke it immediately. Because access was tied to a verified identity, you can also see from the analytics whether they actually opened it before you cut access, which tells you how worried to be.
The deal or relationship ended. You do not want a former counterparty holding your financials indefinitely. With copies, you are stuck. With hosted, revocable links, you revoke access to the whole room and the documents stop opening for everyone. This is the single capability that separates controlled sharing from a shared-drive link, and it is the entire subject of the one thing a Dropbox link can't do.
In every case, the difference is set before you send. The tools that let you un-send are the ones where you never sent a copy to begin with.
How 99 Data Rooms handles this
99 Data Rooms is built so that "un-send" is always available, because you never hand over the file. Documents live inside a virtual data room, and you share them as tracked, revocable links rather than attachments. Recipients view the document through the platform after passing a gate (a verified email and a one-time code), so there is no loose copy floating around by default.
If something goes wrong, one-click revocation cuts access immediately, even while someone is mid-scroll: the next load simply fails. If you sent the wrong version, file swap with version history lets you replace the document behind the link so everyone sees the correct file, with no reissue. You can set an expiry so links close on their own, and gating means only verified, invited people ever get in. Because every view is logged, page-by-page analytics show you exactly who opened the document before you pulled it, so you know whether a mistake was actually seen. If you are weighing this against a storage tool, our 99 Data Rooms vs Dropbox comparison shows why a shared-drive link cannot offer the same, and our guide on what a virtual data room is sets out the wider model.
Everything is UK-hosted in London, encrypted at rest and in transit, with a 24-month audit trail. The free tier gives you three rooms and twenty-five active links, forever, no card, which is enough to stop sending risky attachments today. The wider platform is in beta and improving fast, but revocation and version control already work.
Share so you can always un-send, free
The only reliable way to un-send a document is to never send a copy in the first place. The free tier of 99 Data Rooms is a real tier, not a trial: three rooms, twenty-five active links, forever, no card required. Start for free, share your next sensitive document as a revocable link instead of an attachment, and keep the ability to pull it back for good. Upgrade when you want unlimited links, NDA gating and watermarking.
Sources
- Revocation, link expiry and version-control behaviour, and shared-drive comparison points, reflect 99 Data Rooms product facts and the documented behaviour of email recall and shared-drive links: Dropbox https://www.dropbox.com (as at 22 July 2026). No external legal claims are made here.
Can I really un-send a document, or is that a myth?
Both, depending on how you sent it. You cannot un-send a copy: an email attachment or a downloaded file is beyond your reach the moment it lands. You can un-send access to a hosted document shared by a revocable link, because the recipient never held their own copy. The trick is to share the second way, not the first.
Does email recall work?
Rarely, and never for anything already opened, forwarded or downloaded. Recall typically only functions within the same email system and before the message is read, and it does nothing about the attached file itself. Treat it as a last resort, not a safety net.
What happens to someone reading my document when I revoke it?
On a platform with real revocation, access is cut immediately. If they are mid-read, the document stops loading on their next action, and it will not open again. Anything they had not yet seen, they will not see.
Can I fix a wrong version without asking people to delete the old one?
Yes, if you shared a link to a hosted document. File swap with version history replaces the file behind the link, so everyone with access now sees the correct version. There is nothing for them to delete because they never held a copy.
How do I make sure I can always un-send in future?
Stop sending attachments for anything sensitive. Share documents as gated, tracked, revocable links from a data room instead. Set link expiry so access closes on its own, and rely on version control to correct mistakes. Then "un-send" is always a click away.