You need to send a sensitive PDF to someone. Your bank statement, a contract, a tax document. Two options come to mind: password-protect the PDF itself, or encrypt the email that carries it. Both approaches put a lock on your data, but they protect different things, fail in different ways, and expose your document to different risks. Choosing the wrong one can leave your document more exposed than you think.
The decision comes down to what you are protecting against. PDF passwords protect the file wherever it goes, regardless of how it gets there. Email encryption protects the transmission channel but leaves the file unprotected once it arrives. Understanding the threat model for your specific situation makes the choice clear, and in many cases, the answer is to use both.
What PDF Password Protection Actually Protects
PDF Password protection, properly called PDF encryption, applies security directly to the file. When you set a password on a PDF, the file content gets encrypted using the password as the encryption key. Without the password, the file is mathematically scrambled. A PDF with 256-bit AES encryption, the current standard as of PDF 2.0, is effectively uncrackable by brute force. Even with a supercomputer, breaking a properly implemented AES-256 key would take longer than the age of the universe.
This protection travels with the file. Whether the PDF sits on your hard drive, in a cloud storage folder, attached to an email, or on a USB stick handed to someone in a coffee shop, the encryption remains in place. Anyone who gets their hands on the file needs the password to read it. This is the fundamental advantage of file-level protection over channel-level protection: it secures the data, not just the delivery method.
PDF Security at the file level also supports two distinct types of passwords. An open password, sometimes called a user password, must be entered before the file can be viewed at all. A permissions password, sometimes called an owner password, allows the document to be opened but restricts what can be done with it: no printing, no copying text, no editing. Using both passwords together gives you layered control over who can read the document and what they can do with it after reading.
A key detail that many users overlook is the difference in encryption strength when setting passwords. Modern PDF tools offer AES-256 encryption, which is the strongest widely available standard. Older tools might default to RC4-128 encryption, which is significantly weaker and can be cracked with moderate computing resources. Always verify that your PDF tool uses AES-256 encryption, particularly if you are protecting documents with financial, legal, or personal information.
The PDF encryption standard has evolved over time to stay ahead of advances in computing power. PDF 1.1 used RC4-40, which offered only 40-bit encryption. PDF 1.5 upgraded to RC4-128. The current PDF 2.0 specification mandates AES-256. Each upgrade represented a response to demonstrated weaknesses in the previous standard. Documents encrypted with older standards should be re-encrypted with AES-256 if they are still in active use.
What Email Encryption Actually Protects
Email encryption works on a completely different layer. It encrypts the connection between mail servers or between your email client and the server, depending on the type. Transport Layer Security (TLS) encrypts the connection between mail servers while the message is in transit. End-to-end encryption, as implemented by services like Proton Mail or through S/MIME and PGP, encrypts the message content itself so that only the intended recipient can decrypt it.
Each method solves a different half of the security problem.
A 2025 report by Google's Transparency group found that 95% of emails sent through Gmail are now encrypted in transit via TLS (Google, "Email Encryption in Transit Transparency Report", 2025). This is a massive improvement from a decade ago when the figure was below 50%. However, TLS only protects the message while it moves between servers. Once the email arrives in the recipient's inbox, it sits there unencrypted unless the recipient's email provider applies its own server-side encryption, which most free email services do not do by default.
WukongPDF lets you apply PDF Encryption directly in the browser before the file ever leaves your device. This approach means the file is protected from the moment you set the password, regardless of whether you share it by email, cloud link, messaging app, or physical storage media.
End-to-end encrypted email services like Proton Mail and Tutanota offer a stronger alternative to standard TLS. With these services, the message content and attachments are encrypted on the sender's device and can only be decrypted on the recipient's device. Even the email provider cannot read the message content. The limitation is that both the sender and recipient must use the same secure email service or compatible encryption protocol, which limits the practicality for one-off communications with new contacts.
The Weak Points of Each Approach
PDF password protection has one glaring weak point: the password itself must be shared with the recipient, and the way most people share it undermines the security. If you email the password or text it to the same person you email the PDF to, anyone who intercepts either communication gets both the file and the key. Sending the password through a different channel, calling the recipient with the password or using a secure messaging app, solves this problem but adds friction.
Email encryption has a different weak point: the file sits unencrypted in the recipient's inbox and on their device. If their email account gets compromised, if their device gets stolen, or if they accidentally forward the email to the wrong person, the PDF is exposed. A 2024 Verizon Data Breach Investigations Report found that misdirected email was the most common cause of data exposure, accounting for 27% of all incidents (Verizon, "DBIR 2024", 2024). File-level encryption would have prevented every one of those exposures.
A password on a PDF is only as strong as the password itself. A 256-bit encrypted PDF protected by the password '123456' is trivially broken in seconds through a dictionary attack. A 256-bit encrypted PDF protected by a random 16-character password is effectively uncrackable. The encryption algorithm provides the upper bound on security, but the password quality determines whether you actually get anywhere close to that bound.
Email attachments also face a retention risk that PDF encryption mitigates. Most email services retain sent messages indefinitely, and recipients often keep emails far longer than needed. A password-protected PDF sitting in a five-year-old email thread is still protected by its password. An unprotected PDF in the same thread is fully readable by anyone who gains access to that email account at any point in the future.
Which Approach Fits Which Scenario
For one-time sensitive document transfers, PDF password protection is the stronger choice. Set a strong password, share it through a different channel than the PDF, and the document is protected everywhere it goes. This approach works well for sending tax documents to an accountant, sharing contracts with a business partner, or submitting documents that contain personally identifiable information.
For ongoing communication where convenience matters, email encryption at the transport level provides a baseline of security with zero user effort. If you are emailing documents to the same person regularly, setting up end-to-end encryption through S/MIME or a secure email provider makes more sense than managing a new PDF password for each exchange. The security is not quite as strong as file-level encryption, but the usability is dramatically better for repeated use.
For maximum security, particularly with documents subject to regulatory requirements like HIPAA, GDPR, or financial services regulations, use both. Encrypt the PDF with a strong password, then send it through an encrypted email channel. The layered approach means an attacker would need to compromise both protections to access the document. Many compliance frameworks explicitly recommend defense in depth for sensitive document sharing.
Practical Guidelines for Sending Sensitive PDFs
Three simple rules cover most situations. First, never send the password through the same channel as the PDF. A text message, a phone call, or a secure messaging app are all better choices than including the password in the same email as the attachment. This single rule eliminates the most common failure mode of PDF password protection.
Second, set an expiration date on the shared file when possible. Some PDF tools and secure file-sharing platforms allow you to set documents to expire after a certain date or number of views. This limits the window during which a compromised password can be used to access the document.
Third, use a password manager to generate and share strong passwords. A random 16-character password generated by a password manager is far stronger than any memorable password, and password managers increasingly include secure sharing features that let you send credentials to recipients without exposing them in plain text. For repeated document sharing with the same recipients, consider establishing a shared vault or a secure channel for password exchange rather than inventing a new transmission method each time.
For organizations subject to compliance requirements like SOC 2 or ISO 27001, documenting the specific security measures applied to each category of sensitive document provides auditors with clear evidence of data protection controls.