TESTED · PDF WORKFLOWS
Require a password to open a PDF
Try a protected PDF and an encrypted file with an empty open password, then set and check an actual document-opening password.
To make someone enter a password before reading a PDF, set a document-open password, save a separate copy, then close and reopen that saved file to check it. Adobe calls this the “Require a password to open the document” setting. A permissions password serves a different purpose: it addresses actions such as printing or editing after the document opens. Adobe explains the distinction.
Try a protected PDF
Download the protected practice PDF. Its password is TestOpen-2026!, disclosed for this synthetic exercise only. The one-page document contains SYNTHETIC PASSWORD TEST.
A local check of this file found that an empty password and an incorrect password each failed to decrypt it. The practice password succeeded, made the page text readable, and allowed the page to be rendered. You can try the same sequence in your PDF viewer: open the file, enter an incorrect password, then use the practice password and inspect the page.
Run those checks on the saved copy you plan to share. A check on the original file would tell you nothing about whether the new copy saved your chosen settings.
Set the password in Acrobat
Use the unprotected practice PDF if you want to follow along. It has the same synthetic wording as the protected example. It was made later for this exercise and is not the historical input file used to create the protected PDF.
Follow Adobe’s password procedure:
- Open the unprotected PDF. Go to All tools > Protect a PDF > Advanced Options > Encrypt with Password, then select Yes.
- Select Require a password to open the document. Enter
TestOpen-2026!in Document Open Password. - Select OK, retype the password, and select OK again. Acknowledge the security message with OK.
- Save the result as a separate PDF so you retain the unprotected practice file.
Close the saved copy and reopen it. Try an empty password, an incorrect password, and then the one you set. Confirm that the empty and incorrect attempts fail, then that the password you set opens the page. If a PDF is already open and authenticated, start a fresh reader or session for each check. Confirm the file’s name and location, especially if you will send an attachment or downloaded copy; a filename or lock icon alone does not establish how that copy opens.
Use the disclosed password only for these public practice files. Choose a private password for a real document.
What the practice files show
The empty-open-password example is encrypted, yet the local check could read it after supplying an empty password. This makes a useful contrast with the protected file: an “encrypted” indicator by itself does not prove that someone must enter a nonempty password to read the contents.
| Practice file | Encrypted flag | Empty password | Incorrect password | TestOpen-2026! |
Page text when readable |
|---|---|---|---|---|---|
| Unprotected | No | No decryption needed | Not applicable | Not applicable | SYNTHETIC PASSWORD TEST |
| Password to open | Yes | Rejected, result 0 | Rejected, result 0 | Accepted, result 1 | SYNTHETIC PASSWORD TEST |
| Empty open password | Yes | Accepted, result 1 | Rejected, result 0 | Rejected, result 0 | SYNTHETIC PASSWORD TEST |
A rejected result in this table means the supplied candidate did not authenticate. The empty-password file still permits access through its empty password, so rejection of the two nonempty candidates does not make it an opening barrier.
The three files yielded the same page text when readable, but they did not have the same opening behavior. Neither the presence of encryption nor the text visible after access answers the practical question on its own. Test whether an empty attempt fails on the actual file you intend to share.
These examples address opening access. The empty-password file was not configured or tested to enforce printing or editing restrictions.
Check a file locally with Python
If you want a check independent of a viewer’s prompts, the following script opens a fresh pypdf reader for each attempt. It asks for passwords locally through getpass, so you do not need to put a private password in a command or shell history. Install the dependency with python -m pip install "pypdf[crypto]", as described in the pypdf encryption documentation.
Save this as a Python script, run it, and enter the path to one of the downloaded PDFs. For the practice files, enter any incorrect password at the first prompt and TestOpen-2026! at the second. On the empty-password example, that second value is expected to fail.
from getpass import getpass
from pathlib import Path
from pypdf import PdfReader
path = Path(input("PDF path: ").strip().strip('"'))
wrong = getpass("Enter an incorrect password: ")
password_to_check = getpass("Enter the password to check: ")
for label, candidate in (
("Empty password", ""),
("Incorrect password", wrong),
("Password to check", password_to_check),
):
reader = PdfReader(str(path))
if not reader.is_encrypted:
print("File is not encrypted; no password is needed.")
print("Page 1:", reader.pages[0].extract_text())
break
result = reader.decrypt(candidate)
print(f"{label}: {'accepted' if result else 'rejected'} (result {int(result)})")
if result:
print("Page 1:", reader.pages[0].extract_text())
For an encrypted file, a result of 0 means that attempt failed; a positive result means it succeeded. The script prints page text only after a successful attempt. The exact script was run on all three supplied files. The two encrypted files were checked with the empty string, incorrect, and the public practice password; the unprotected file exited after reporting that no password was needed. Its results match the table. For your own check, point it to the final saved or downloaded copy; copies can carry different settings.
If the result is confusing
If the PDF opens but editing is blocked, check which setting you applied. Adobe treats the document-open password and permissions controls as separate choices. Adobe’s password overview describes their different purposes.
If no prompt appears, check the actual file with a fresh reader. The encrypted empty-password example shows that the lack of a prompt does not, by itself, tell you whether a file is unencrypted.
If a password you expect to work fails, first confirm that you opened the intended saved copy and entered the exact password. A failed attempt alone does not establish whether the password is wrong or the file has another problem. If you no longer know the password, ask the document’s creator or use an original copy you can still open. Saving a new protected copy also does not remove access to any unprotected copy you already shared.
Source note: Adobe’s interface steps above are source-based instructions; no Acrobat interface trial was recorded. The file results come from local pypdf checks reviewed October 7, with a separate PyMuPDF render after correct authentication of the protected file. The protected AES-256 output was retained from September 29; the unprotected input and empty-password contrast were created October 7.