A viewer lock is not encryption
Several tools offer to “lock” or “protect” a PDF by setting permissions or requiring a code in their own reader. Permissions restrictions and document-open encryption are different mechanisms, and reader behavior can vary.
For confidentiality, use a nonempty document-open password and confirm that the tool applies PDF encryption. Do not treat permissions restrictions alone as equivalent to document-open encryption.
Prefer local processing
Uploading a confidential document to an unknown online converter hands the plaintext to a third party in order to protect it from third parties. Whatever the site's policy says, the file was transmitted and processed.
Where a tool can encrypt on-device, it avoids the document-upload path. It does not remove exposure from the device, temporary files, passwords, or later sharing.
Verify in an independent viewer
Close the creating app and test the result in a fresh independent viewer or session without cached credentials. Inspect the PDF's encryption settings and confirm that a nonempty document-open password is required; no prompt alone does not prove the file is unencrypted.
Use both the settings check and the independent-open test to distinguish document-open encryption from permissions restrictions or cached access.
Doing it properly
- Confirm the tool explicitly states that it encrypts the PDF.
- Create the protected copy locally where possible.
- Close the creating app and reopen the file in an independent viewer.
- Choose a password strong enough to resist offline guessing.
- Remove unprotected source and temporary copies once the protected version is verified.
The two habits that undo it
- Uploading confidential documents to an unknown online converter.
- Sending the file and its password in the same message.
A fictional example
Leo starts with a non-sensitive test: “Confirm the tool states that it encrypts the PDF.” Next, Leo follows the second check: “Test the file after closing the creating app.” This fictional scenario demonstrates the decision process; it is not a report of product testing.
Common mistakes
- Uploading confidential documents to an unknown converter
- Sending file and password in the same message
What this workflow does not change
- Uploading confidential documents to an unknown converter
- Sending file and password in the same message
Questions people ask
Does a PDF password hide the filename?
No. The surrounding file name, size, timestamps, and message context can remain visible.