How to Password-Protect Any File Before You Send It (Free, on Every Platform)

Every file-sharing service makes security claims, and if you read enough of them they start to blur together. Here's the habit that makes most of those claims irrelevant: put the password on the file itself, before it leaves your machine. Do that, and it doesn't matter whether the transfer channel is trustworthy — email, cloud drive, transfer site, USB stick handed to a stranger. The file is unreadable without the password at every point along the way.

Security people call this end-to-end protection you control. It costs nothing, works on every platform, and takes under a minute once you've done it twice. This guide shows the exact steps for each platform and file type — and the one mistake that quietly undoes the whole exercise.

The Principle in One Sentence

Transport encryption (the padlock in your browser) protects a file while it's moving; encrypting the file itself protects it wherever it lands — a mail server, a shared laptop, a forwarded email you never knew about. You're not choosing between them; you're adding the second layer because you don't control what happens after delivery.

Windows: 7-Zip (Free, Two Minutes to Set Up)

Windows can't password-protect a zip natively, but 7-Zip — free and open source, no strings — does it properly:

1. Install 7-Zip, then right-click your file or folder → 7-Zip → Add to archive…
2. Set "Archive format" to zip (opens everywhere) or 7z (stronger, recipient needs 7-Zip or a compatible tool)
3. In the Encryption box, enter a password and set the method to AES-256
4. Using 7z format? Also tick "Encrypt file names" — otherwise anyone can see what's inside the archive even without the password
5. Click OK — the encrypted archive appears next to the original

That file-names detail matters more than it looks: a zip named offer-letter.zip containing a visible salary-negotiation-v3.docx has already leaked something, password or not.

Mac: Built-In Tools, No Install

macOS has two native options. For a quick encrypted zip, Terminal: zip -e archive.zip yourfile.pdf — it prompts for a password. For folders or ongoing use, Disk Utility is friendlier: File → New Image → Image from Folder, then choose 256-bit AES encryption and "read/write" if you'll add files later. Apple documents the disk-image flow in its Disk Utility guide. The result is a .dmg the recipient double-clicks and unlocks with the password — Mac-to-Mac only, so use the zip route for mixed-platform sharing.

PDFs: Password the Document Itself

PDF has password protection built into the format, which is ideal for contracts, statements, and IDs:

• On a Mac: open the PDF in Preview → File → Export → tick "Encrypt"
• LibreOffice (free, all platforms): open or create the document → Export as PDF → Security tab → set an "open" password
• Microsoft Word: when saving as PDF, Options → "Encrypt the document with a password"
• Adobe Acrobat (paid): All Tools → Protect a PDF, per Adobe's guide

One warning about the difference between the two PDF password types: an open password actually encrypts the document; a permissions password (the "can't print/copy" kind) is trivially stripped by free tools and protects nothing. Use the open password.

Office Documents: Built Into Word and Excel

Word, Excel, and PowerPoint encrypt natively: File → Info → Protect Document → Encrypt with Password. Modern versions use AES under the hood, and the file stays a normal .docx/.xlsx the recipient opens with the password. Two caveats: password recovery does not exist — lose it and the document is gone — and files created in very old Office versions (97–2003 format) use weak, crackable protection, so save in the modern format first.

On Your Phone

Phones are the weak spot for this workflow — neither iOS nor Android zips with a password natively. Practical options: on iPhone, the Pages/Numbers apps can set document passwords, and the Shortcuts app has community recipes for encrypted archives; on Android, the free ZArchiver app creates AES-encrypted 7z/zip archives. Honestly though, if the file is sensitive enough to encrypt, it's often easiest to do the encryption step on a computer — or to create the document with its password already set (as with the Office and PDF methods above), so the phone is just carrying an already-locked file.

The Mistake That Undoes Everything

Never send the password through the same channel as the file. An email containing an encrypted attachment and its password is exactly as secure as an unencrypted attachment — anyone who can read that inbox has both. The rule is two channels: file by email, password by text message. File by transfer link, password said out loud on the call. File in a chat, password in a different app. This costs you ten seconds and it's the entire difference between real protection and theater.

While we're at it: "password123" on an AES-256 archive is a vault door with a sticky note. Use a passphrase — four random words beat any clever substitution pattern, per basically every guidance document including NIST's authentication guidelines.

Does This Replace a Secure Transfer Method?

No — it stacks with one. The encrypted file still benefits from a transfer channel that doesn't keep copies lying around: an expiring transfer link, a direct device-to-device tool, anything that isn't "sits in both inboxes forever." We've written about choosing that channel for sensitive documents separately. But the order of operations matters: encrypt first, then send however is convenient. Get the first step right and the second one stops being scary.