How to send encrypted files, and when encryption isn't the answer
If you want to send encrypted files, the one thing to get right is where the encryption sits. Encrypt the file itself and it stays locked wherever it ends up. Rely on the email or the app to do it and the lock only holds while the file is in their hands.
Most people find this out the wrong way round. They assume "encrypted" is a property of the message, send the attachment, and it turns out the only encryption was the bit nobody was worried about. So here's how to send files encrypted properly, which method suits which job, and the point at which I'd stop encrypting and send something else.
Encryption is three different things
When a tool says it's encrypted, it usually means one of three things, and they protect against different problems.
In transit. The file is scrambled while it travels between servers. Gmail, Outlook and almost every file transfer site do this by default. It stops someone reading the file off the wire, which was never the likely risk.
At rest. The file is scrambled on the provider's disks. Handy if their storage is stolen. But the provider holds the keys, so their systems, and anyone who gets into either account, can still read it.
End to end, or file-level. Only the sender and recipient hold the key. This is the one people picture when they say "encrypted", and it's the only one where the provider can't read your file. It's also the one that takes a bit of effort.
Most "secure" sending is the first two. If your file is genuinely sensitive, you want the third, or you want to control access some other way.
Method one: encrypt the file before you send it
This is the most reliable way to send encrypted files, because the lock travels with the file. It doesn't matter which email provider, cloud drive or messaging app carries it.
For a PDF, set an open password in Acrobat, or in Preview on a Mac. I've written the click-by-click steps in how to encrypt a PDF file for email, and a shorter version for any file in how to password protect a file. Two details matter more than the software:
- Set a password to open the document. A permissions password only restricts things like printing, and on its own doesn't keep anyone out. There's more on the difference in PDF permissions and passwords.
- Send the password by a different route. Text it or ring them. A password in the same email as the file cancels the encryption, and I'd say that's the most common way a protected file stops being protected.
The catch is that you're now managing a password with every recipient. Fine for one accountant. Miserable for fifty prospects. And once the recipient opens it, they can save an unlocked copy and forward it, so the lock only covers the journey and the first opening.
Method two: use a service that encrypts for you
Encrypted email and transfer services take the key handling off your plate. The recipient gets a notification, clicks through, and reads the file in a portal, often after confirming their identity.
This is easier for the recipient than a password, and good services give you an expiry or a way to cut access. But check one thing before you trust the word "encrypted" on the homepage: who holds the keys. If the provider holds them, you're back to encryption in transit and at rest, which is better than nothing and not the same as end to end. Vendors usually say which it is on the security page rather than the front page, and I'd read that page before sending anything you'd hate to see leaked.
For a rundown of what's out there, I compared secure file sharing platforms, and there's a version for people who don't want to pay in secure free file sharing. If it's the business side you're after, secure file sharing for business covers compliance.
Method three: send a link you can switch off
Sometimes the right answer is to stop sending the file at all.
An attachment is a copy. Once it's in someone's inbox you can't reach in and take it back, however well it's encrypted. A link is a pointer, so you can expire it or cut it off. For a proposal, a report or a deck, that's usually the control that matters, because the realistic risk isn't an attacker intercepting the file. It's a perfectly legitimate recipient forwarding it on six months later.
That's what LiveDocument does with a PDF or image: one link, with expiry and revocation, plus a recorded video walkthrough on top and page-level analytics so you can see what got read. To be plain about the limits, it's not encryption of the file in the sense above, it has no watermarking or NDA gating, and it's not a data room. If you need legal-grade confidentiality, encrypt the file or use a proper secure transfer service. If you need the recipient to open, understand and act on a document, and you want to be able to pull it back, a link wins. The mechanics are in sharing a PDF as a link, and the thinking behind it is in secure file access.
Which method for which job
A rough guide, from my own experience of sending a lot of documents:
- One sensitive file to one person you trust to handle a password: encrypt the file, send the password separately.
- Regular exchanges with the same client, where they shouldn't need to fuss: an encrypted service with sign-in.
- A proposal, deck or report to people who might forward it: a link with expiry and revocation.
- Something that has to stay confidential under a contract or regulation: encrypt the file and check the terms, and don't rely on my blog for that part.
Plenty of cases need two. Encrypt the file, then send it through a service that can expire access. Belt and braces isn't overkill when it's a payroll summary.
The mistakes I see most
Putting the password in the same message. Using a weak password because it has to be typed by hand. Encrypting the file and then uploading the unlocked original to a shared drive. Assuming a "secure" label means end to end. And forgetting that a copy the recipient already saved can't be locked again.
When I was running growth at a data company, none of the near misses were somebody cracking encryption. They were the wrong attachment, a stale version, or a file sitting reachable long after the deal was dead.
FAQ
What is the safest way to send encrypted files?
Encrypt the file itself with a strong password and send the password by a different channel, such as a text or a call. Because the lock is on the file, it holds whichever email provider or app carries it.
Can I send files encrypted by email?
Yes. Email travels encrypted between most big providers, but the provider can read it. To send files encrypted properly, protect the attachment before you send it, or use an encrypted email service where the recipient opens the message in a portal. A portal on its own doesn't guarantee end to end encryption, because some services can decrypt the message on their side. If the provider must not be able to read the file, check that the service is end to end encrypted and who holds the keys, or encrypt the attachment yourself before sending. The wider picture is in how to securely send documents via email.
Is a password-protected PDF the same as an encrypted PDF?
An open password does encrypt the contents of a PDF. A permissions-only password doesn't keep anyone out, so set an open password.
Do I need encryption if I send a link instead?
It depends on the threat. A link with expiry and revocation controls who can still open a document, which an attachment can't. If the content is highly confidential, encrypt the file as well.
If you're tired of sending things you can't take back, that's the itch behind LiveDocument. Have a look at the demo or pricing.
About the Author
Cameron JamesCameron is the founder of LiveDocument. He writes about sharing documents, PDFs, decks and contracts, and why pairing a video walkthrough with a document beats sending it cold.