Does this use modern AES-256 encryption?+
No. The current browser implementation uses legacy library encryption. Use a dedicated tool when modern encryption is required.
Will text and forms remain interactive?+
No. This version stores the pages as images in the protected file.
Basic protection with important limits+
This implementation uses the bundled library’s legacy PDF encryption and rebuilds the pages as images. It should not be presented as modern, high-assurance encryption. For confidential material that requires current encryption standards, use a dedicated PDF security tool with an appropriate encryption mode. Do not rely on reader permission flags as strong access control.
Check usability after protecting+
The image-based copy loses original text selection, links and form controls. Choose a password you can retain and test the result before sharing it. Keep an unprotected source in a suitable private location if you will need to edit the content. Reprocessing an already protected input may require unlocking it first.
Legacy encryption and reader-dependent permissions+
Uses basic legacy encryption, not modern high-assurance encryption. Reader permissions can be ignored by software; text and interactive features are lost.
A receiving viewer ignores a permission restriction+
PDF permissions depend on the reader enforcing them. Do not treat copy or print restrictions as reliable protection. Use a reviewed modern security workflow when required.