File Encryption

How to Encrypt Files Before Sending Them by Email

8 min read
By
How to Encrypt Files Before Sending Them by Email

Photo by Tima Miroshnichenko from Pexels

Think about the last sensitive file you emailed. A tax return. A contract. A medical record. Now think about the path that attachment took from your outbox to the recipient's inbox.

It passed through your email provider's SMTP server. Then it hopped to one or more intermediate mail servers. Then it landed on the recipient's provider's server. Finally, it downloaded to their device. At every hop, the file sat on a server you've never heard of, operated by people you've never met, for a duration you can't control.

If you used TLS — and most email providers do by default — the connection between servers was encrypted. But the file itself was not. It existed in readable form on every server it touched, in every backup of those servers, and in every log that recorded its passage.

Why Email Encryption Is Not Enough

TLS protects email in transit. It does not protect email at rest. Once your attachment arrives at a mail server, it's stored as a regular file. If that server is compromised, your attachment is readable. If that server is backed up to cloud storage (and they all are), your attachment lives in that backup indefinitely. If that server is in a jurisdiction where the government can demand data access, your attachment is subject to that jurisdiction.

Gmail, Outlook, ProtonMail — they all handle this differently. ProtonMail offers end-to-end encryption between ProtonMail users, but if you're sending to a Gmail user, the encryption drops to TLS. Gmail encrypts at rest, but Google holds the keys. Outlook is similar.

The only way to guarantee your attachment is private end-to-end is to encrypt the file before you attach it.

The Pre-Attachment Encryption Workflow

Here's the process I use for every sensitive file I email:

1. Open a browser-based file encryption tool. 2. Select the file I want to send — a PDF, a Word doc, a ZIP, anything. 3. Enter a password. This password is separate from my email password, separate from my computer password, unique to this file or this recipient. 4. Download the encrypted file. 5. Attach the encrypted file to my email. 6. Send the password through a different channel — a phone call, a text message, a Signal message.

That last step is the one most people skip, and it's the most important. If you send the encrypted file and the password in the same email, the encryption is pointless. Anyone who intercepts the email gets both the locked file and the key to open it.

What the Recipient Experiences

When the recipient gets your email, they see an attachment with an unfamiliar extension — .enc, .encrypted, or something similar. They download it. They open the same encryption tool you used, select the file, enter the password you shared with them, and download the decrypted original.

This takes about 20 seconds. In my experience, most people figure it out without instructions, especially if you include a brief note in the email: "I've encrypted this attachment for security. I'll text you the password separately."

The few people who get confused are usually the ones who've never received an encrypted file before. A one-sentence explanation resolves it: "Download the file, go to this website, upload it, enter the password I texted you, and download the original."

Password Protecting Email Attachments: Common Mistakes

I've seen every mistake in the book. Here are the ones that make me wince:

**Sending the password in the same email.** This is the most common mistake. It completely defeats the purpose. If someone gains access to the recipient's email account — which is more common than you'd think — they have both the encrypted file and the password.

**Using the same password for every file.** If one password leaks, every file you've ever sent is compromised. Use a password manager to generate a unique password for each file or each recipient.

**Using a weak password.** "Password123" encrypts a file just as easily as "7K$mP9#nLx2QrB8w." But the first one can be guessed in seconds. The second one can't be guessed before the heat death of the universe. Use at least 16 characters.

**Forgetting to tell the recipient the password.** I've done this. It's embarrassing. The recipient emails back saying "I can't open this," and you have to send the password anyway, which means you're now sending it over the same channel you were trying to protect. Set a reminder to share the password immediately after sending the email.

Secure File Transfer via Email: When Email Isn't the Right Tool

Sometimes email isn't the right delivery method. If you're sending a file larger than 25 MB, most email providers will reject it. If you're sending something extraordinarily sensitive — classified business documents, legal evidence, personal health records — you might want to use a dedicated secure file transfer service instead.

But for the 90% case — sending a contract, a tax form, a financial statement, a medical record — encrypting the file before attaching it to an email is the right balance of security and convenience. The recipient doesn't need special software. They don't need an account. They just need a browser and the password you shared with them.

For more on the broader practice of protecting sensitive files, our guide on encrypting sensitive documents covers the specific considerations for tax, medical, legal, and financial files.

A Real Example

Last month, I needed to send a signed lease agreement to my landlord's property manager. The document contained my full name, address, Social Security number, and bank account details. I encrypted it with a browser-based tool, attached the encrypted file to a Gmail message, and texted the password to the property manager.

She emailed back: "That was easy. Can I use this for my other tenants?" Now she encrypts every lease she sends. Not because I told her to. Because she tried it once and realized it took 20 extra seconds and gave her something she didn't have before: certainty that her tenants' personal information was actually private.

That's the whole pitch. Twenty seconds of extra effort for actual privacy instead of assumed privacy. The difference matters.,

Frequently Asked Questions

Should I send the password in the same email as the encrypted file?

No. Never send the password through the same channel as the encrypted file. If someone intercepts the email or accesses the recipient's account, they'd have both the file and the key. Use a phone call, text, or messaging app.

What if my recipient doesn't know how to open an encrypted file?

Send them a one-line instruction: download the file, open the same browser-based encryption tool you used, upload the file, enter the password you shared separately, and download the decrypted original. It takes about 20 seconds.

Is email encryption built into Gmail or Outlook enough?

Gmail and Outlook encrypt connections between servers (TLS) and encrypt data at rest, but they hold the encryption keys. This protects against network interception but not against account breaches, server compromises, or legal data requests.

Explore the File Encryptor Tool: Try it now

Try NovelCrypt Tools

Experience military-grade encryption for your sensitive data. Create self-destructing messages, encrypt files, or explore our experimental lab tools.

Explore NovelCrypt