How local AES-256 encryption protects PDF streams
Standard PDF encryption scrambles internal content streams and strings inside the document before saving a new binary file. Every step runs inside a local Web Worker in your browser tab, so confidential contracts, tax returns, and passwords never touch a network connection.
Setting an open password inside your browser worker
Type a passphrase of at least 4 characters into Password to open and confirm it in Type it again to require decryption before any viewer can render pages. If you want to verify characters while typing, toggle Show passwords to switch both inputs to plain text.
Once you select Protect PDF, the worker applies 256-bit AES encryption as defined by the NIST FIPS 197 Advanced Encryption Standard. After processing finishes or when you reset the tool, the interface clears all password state from component memory.
Why passphrase length matters for offline brute-force defense
Short four-character passwords satisfy the minimum validation rule but remain vulnerable to fast offline dictionary guesses if someone obtains the file. A longer multi-word passphrase raises the entropy of the derived key and resists automated cracking attempts.
If you need a strong random secret for an important archive, you can generate a high-entropy passphrase before locking your file. Store that secret in a password manager before sharing the locked document with recipients.
What is the difference between open and permissions passwords?
An open password encrypts the document so no viewer can display pages without the secret, whereas a permissions password only locks viewer restriction settings after the file opens. Under the PDF Association ISO 32000-2 PDF 2.0 specification, these two roles map to separate user and owner keys in the encryption dictionary.
When viewers enforce or ignore permission flags
Checking Restrict printing, copying or editing reveals three checkboxes: Allow printing, Allow copying text and images, and Allow editing and comments. Unchecking Allow printing disables printing, while leaving it checked permits high-resolution output.
Unchecking Allow editing and comments blocks page modifications, annotations, form filling, and document assembly in compliant readers. However, PDF viewers are not required to enforce owner flags if the file opens without a user password, so treat permissions as a deterrent rather than hard copy protection.
How the 24-byte random owner password fallback works
You can enter a custom string in Password to change permissions as long as it differs from the open password. If you leave that field blank while restricting at least one permission, the tool generates a random owner secret of 24 bytes (48 hexadecimal characters) so nobody can easily lift the restriction flags later.
When you legitimately need to edit or merge an encrypted file that you already control, you can remove a PDF password when you already know it. Without the matching secret, neither owner permissions nor user encryption can be stripped cleanly.
Permission controls and cryptographic behavior compared
Different combinations of open passwords, owner passwords, and permission checkboxes change how PDF readers handle your file. Comparing each configuration clarifies what stays encrypted at rest and what relies on viewer cooperation.
| Configuration | Open prompt shown | Streams encrypted | Printing and editing behavior | Accessibility flag |
|---|---|---|---|---|
| Open password only | Yes | 256-bit AES | All actions allowed after unlock | Enabled |
| Open password plus restrictions | Yes | 256-bit AES | Blocked per checkboxes in compliant readers | Enabled |
| Restrictions only, custom owner password | No | 256-bit AES with empty user key | Viewers prompt for owner password to change flags | Enabled |
| Restrictions only, blank owner password | No | 256-bit AES with 24-byte random owner key | Flags locked against casual editing in standard readers | Enabled |
| Allow copying unchecked | Depends on open password | 256-bit AES | Copy and paste disabled in compliant viewers | Enabled |
The browser builds the random fallback owner password using the MDN Web Crypto getRandomValues API rather than a predictable math seed. Notice that content accessibility remains enabled across all five configurations so screen readers continue functioning on accessible documents.
If your primary goal is preventing recipients from altering signed form entries rather than encrypting the file, consider permanent form field flattening before distribution. Flattening bakes widget values directly into page graphics instead of relying on viewer permission flags.
Preparing sensitive documents before password locking
Encrypting a PDF protects its contents in transit and at rest, yet pre-existing document structure can still affect how recipients interact with the file. Checking forms, hidden metadata, and delivery packaging beforehand avoids rework after encryption.
Scrubbing hidden metadata and finalizing signatures first
PDF files often retain author names, revision history, or editable annotations that remain visible once an authorized recipient enters the open password. Complete all edits, redactions, and metadata cleanup before applying encryption so you do not have to unlock and re-encrypt the document later.
When choosing a passphrase for long-term storage, follow guidance in the NIST SP 800-63B Digital Identity Guidelines by favoring length over arbitrary symbol substitutions. Memorizable four-word passphrases are both easier to type and harder to guess than short mixed-case strings.
Tip: Send the open password through a separate channel such as an encrypted chat or SMS rather than placing it in the same email as the locked PDF attachment.
Bundling encrypted PDFs for external delivery
Once your PDF is encrypted with 256-bit AES, you can distribute it over standard email, cloud storage, or USB drives without exposing plaintext streams. When sending multiple protected agreements together, you can package encrypted contracts into a single archive to keep filenames and versions organized.
Because encryption runs strictly in local memory, you can lock sensitive files offline once the page has loaded. Double-check your saved password before closing the tab, because no recovery key exists anywhere on the web.