On this page
Run structural security checks
The output is reopened as an encrypted document and decrypted using the new opening password. The encryption dictionary is examined for the expected key length and revision.
The encoded permission value is compared with the requested printing, copying, editing and annotation choices.
- AES-256 encryption detected.
- Opening password accepted.
- Permission flags match.
- Page count and dimensions preserved.
Understand what permissions can and cannot prove
The PDF contains standard permission flags, but software decides whether to enforce them. A compliant viewer usually honors the restrictions; other software may ignore or remove them.
Permission verification proves that the requested flags were encoded. It cannot prove how every future viewer will behave, and it is not digital rights management.
Perform a recipient-viewer check
Open a copy in the viewer used by the recipient. Test the opening password and permitted actions, then inspect representative pages, bookmarks and form behavior.
Use permanent redaction when information must be removed. Do not rely on copying restrictions to conceal visible content.
Put the workflow into practice
Arrange source documents, select the pages you need, and create one PDF locally in your browser. Review the result before choosing any optional next step.
Try Encrypt PDFFrequently asked questions
Clear answers before you merge
Can permission flags be verified?
Yes. The engine checks that encoded flags match the requested policy.
Does that guarantee every viewer enforces them?
No. Viewer behavior varies, so enforcement is not verified.
Is encryption the same as redaction?
No. Encryption controls access; redaction removes selected content.
