On this page
- Are password protected zip files secure?
- ZipCrypto vs AES-256
- How does zip password cracking work?
- What a password protected zip does not hide
- How to create a secure password protected zip
- Is a zipped encrypted email attachment safe?
- When to use a self-destructing link instead
- Frequently asked questions
Are password protected zip files secure?
Sometimes. A password protected zip is only as strong as three things: the encryption method inside it, the password you picked, and the way you delivered the file and the password.
The ZIP format supports more than one kind of encryption. Many tools still default to the oldest one, ZipCrypto (also called traditional PKWARE encryption), which cryptographers broke in the 1990s. The newer AES method, popularised by WinZip, is solid. You usually can't tell which one a file uses just by looking at it.
Short answer: an AES-256 zip with a long, random password, where the password travels by a different channel, is reasonably secure. A ZipCrypto zip with a short password emailed alongside it is not.
ZipCrypto vs AES-256: which encryption does your zip use?
The ZIP specification, published by PKWARE as APPNOTE.TXT, describes the original stream cipher. It was designed long before modern cryptography standards and has a known-plaintext weakness: if an attacker knows roughly 12 bytes of any file in the archive, they can recover the internal keys and decrypt everything, no matter how long the password is.
Known plaintext is easier to get than it sounds. File formats start with predictable headers, and archives often contain a file the attacker can find elsewhere, such as a standard logo or a public PDF. Free, open source tools automate this attack.
| Property | ZipCrypto | WinZip AES (AE-1 / AE-2) |
|---|---|---|
| Cipher | Legacy PKWARE stream cipher | AES-128, AES-192 or AES-256 |
| Known-plaintext attack | Yes, practical and fast | No known practical attack |
| Password to key | Direct, very cheap to test guesses | PBKDF2 with 1,000 iterations |
| Tamper detection | Only a CRC check | HMAC-SHA1 authentication code |
| File names hidden | No | No |
| Opens in older built-in extractors | Almost everywhere | Not always, often needs 7-Zip or WinZip |
What is WinZip AES encryption?
WinZip AES encryption is an extension to the ZIP format that WinZip documents publicly in its AES encryption specification. It runs your password through PBKDF2 to derive an AES key, encrypts each file, and adds an authentication code so tampering is detected. 7-Zip, WinZip and most modern archivers can write and read it.
The catch is compatibility. Because some built-in unzip tools could not open AES archives, many people and many default settings stayed on ZipCrypto so the recipient "can just double-click it". That convenience is exactly what makes the file weak.
How does zip password cracking work?
Once someone has a copy of the file, they can attack it offline. Nothing limits their attempts, nothing locks them out and nothing alerts you. There are two main routes:
- Known-plaintext attack (ZipCrypto only): skip the password and recover the keys directly. Password length does not matter.
- Guessing the password (both methods): tools like hashcat, which has dedicated modes for PKZIP and WinZip archives, run dictionary, rule and brute force attacks on a GPU.
AES slows the guessing down, since each guess costs 1,000 PBKDF2 rounds, but it can't save a weak password. A word plus a year, or a company name followed by an exclamation mark, sits near the top of every cracking wordlist. The same dictionary techniques are covered in our guide to credential stuffing vs brute force.
What makes a zip password hold: 16 or more random characters that a person did not make up. Length does most of the work.
What a password protected zip does not hide
Even with perfect AES-256 and a strong password, a standard ZIP archive leaves a lot in plain view. Anyone holding the file can list it without the password and see:
- every file and folder name, such as salaries-2026.xlsx or passport-scan.jpg
- the size of each file
- modification dates and times
- how many files are inside
File names alone can reveal what matters. If the names are sensitive, put the files inside another container first or use the 7z format with header encryption, shown below.
The copies also stay around. An emailed zip sits in the sender's sent folder, the recipient's inbox, their backups and the mail servers in between. Every copy can be attacked later, including after someone learns or leaks the password.
How to create a secure password protected zip
If you have to send a ZIP, make sure it uses AES. The command line tools make this explicit. Note that the classic zip -e command found on macOS and Linux uses ZipCrypto, so skip it for anything sensitive.
Creates a standard .zip with AES-256 instead of ZipCrypto. 7-Zip prompts for the password.
7z a -tzip -mem=AES256 -p report.zip report.pdfIn the 7-Zip window, choose ZIP as the format and set Encryption method to AES-256. The default for ZIP is ZipCrypto.
The 7z format always uses AES-256, and -mhe=on also encrypts the file names, which ZIP can't do.
7z a -p -mhe=on report.7z report.pdfThe recipient needs 7-Zip or a compatible archiver to open it.
This common command produces a ZipCrypto archive, which is vulnerable to the known-plaintext attack.
zip -e report.zip report.pdfFine for keeping casual eyes out, not for confidential data.
Then treat the password as the real secret: generate it, never reuse it, and send it through a different channel than the file. Our guide on secure password sharing covers how to hand it over safely.
Is a zipped encrypted email attachment safe?
Zipping a file and emailing it is the most common way people send an encrypted email attachment, and it's also where most of the protection gets lost:
- Password in the same thread. "The password follows in a separate email" still lands in the same inbox. Anyone who gets into that mailbox gets both.
- Copies last indefinitely. The encrypted file can be cracked at leisure, months or years later.
- Security filters can't look inside. Mail scanners can't inspect encrypted archives, which is why attackers use password protected zips to deliver malware. Many companies quarantine or block them, so your file may never arrive.
- No control after sending. You can't revoke, expire or see whether it was opened.
When to use a self-destructing link instead
If the goal is to get a file to one person and not leave it lying around, a one-time link fixes most of the problems above. SecretNote's Secret File tool works like this, based on how the page is built:
- Files are encrypted in your browser with AES-256 (AES-GCM) before upload, so the server only stores ciphertext.
- The decryption key sits after the # in the link. Browsers don't send that part of a URL to the server.
- By default, the encrypted files are deleted once the recipient downloads them. You can instead delete them 30 seconds after the link is opened, or keep them until the timer runs out.
- Unopened shares expire after the time you choose, from 1 hour to 30 days.
- Any file type works, and the page shows the file count and total size limits. No account is needed.
One thing to know: the link itself is the key, so whoever opens it first gets the files. Send it only to the intended person. If the link has already been used when they try it, you'll know someone else got there first.

Skip the zip password and the leftover copies
Encrypt files in your browser and share a link that deletes them from the server after download.
Frequently asked questions
Open the archive in 7-Zip and look at the Method column. "ZipCrypto" means the legacy cipher, and "AES-256" means WinZip AES. On the command line, 7z l -slt file.zip prints the method for each entry. If you created it with zip -e or an old built-in tool, assume it's ZipCrypto.
It depends almost entirely on the password and the method. A ZipCrypto archive with known content can be opened without the password at all. A short or dictionary-based password falls quickly on a GPU, even with AES. A long, randomly generated password on an AES-256 archive is out of practical reach.
Neither regulation approves or bans a specific file format. They ask for appropriate protection for the data. A ZipCrypto archive is hard to defend as appropriate given its known weaknesses. AES-256 with a strong password sent separately is a better position, but check your own organisation's policy.
You can see the file names, sizes, dates and number of files, because standard ZIP encryption only protects file contents. To hide names too, wrap the files in another archive first, or use the 7z format with header encryption turned on.
Email security filters can't scan inside encrypted archives, and attackers use them to hide malware. Many mail systems therefore quarantine, strip or reject password protected zips. A one-time encrypted download link avoids the attachment entirely and doesn't leave a copy in either mailbox.


