Can you search inside a password-protected PDF?
Last reviewed: September 2, 2026 · Markdown version
No — not while it is locked. If a PDF asks for a password before it will open, the words inside it are encrypted, and nothing can search them: not your reader, not a desktop suite, not a website, not DocFind. The useful question is therefore not "which app can get in" but "what is the safe way round", and there is one: unlock the file where it was made, search the unlocked copy, and put the protection back.
Why a password stops search dead
A PDF keeps its text in internal streams — instructions that say draw this character here. Encrypting the document scrambles those streams. The outside of the file stays legible, which is why a reader can still tell you it has twelve pages, but the bytes that spell the words are ciphertext until the password derives the key that unscrambles them.
So there is no clever tool that reads a locked PDF anyway. That is not a gap in the software; it is the entire point of the password. If you do not have it, the honest answer is that the document cannot be searched, and any product implying otherwise is describing something else.
What to do instead
- Open the file with its password in an app that can open it — usually the one that produced it, or any reader you already use.
- Save an unprotected copy. This is normally a "save a copy" or export step, or a security setting where you clear the password. The wording differs per app; the operation is the same everywhere.
- Index and search the copy.
- Re-apply the password afterwards if the protection was there for a reason — and mind where the unprotected copy sits in the meantime. An unlocked bank statement sitting in a shared folder is a bigger exposure than anything the search was ever going to cause.
If you do not have the password, stop here. Nothing on this page, and no app, changes that.
The wrinkle: some "protected" PDFs open without a password
PDF actually has two kinds of password, and they behave very differently:
- An open password is required before the file will open at all. This is the case above — the contents are unreadable without it.
- A permissions password restricts things like printing or copying, but the file still opens for anyone who double-clicks it. Files like this are encrypted in a technical sense, yet their text can be read and indexed perfectly normally.
That distinction explains a result people find confusing. The free "is your PDF searchable?" checker on this site reports any encrypted file as “Encrypted — it may still be searchable”, because from the outside it cannot safely tell the two apart: separating them means attempting the decryption itself, which is more than a web page should do with your document. So it reports the ambiguity and hands you the test you can run yourself. What DocFind declines is the narrower case: the file that will not open without a password.
Why "no results" is the worse answer
Imagine a search tool that tries an encrypted file, reads nothing, and reports zero matches alongside everything else. Nothing on screen is technically false, and yet the result is useless: an empty result list is indistinguishable from "the word is not in your documents". You would conclude the clause is not in the contract, when in fact the contract was never read.
This is the same failure as a scanned page that nobody OCR'd — the "the word is right there and search can't find it" problem — and it has the same remedy: a tool should tell you what it could not read, so a gap looks like a gap instead of an answer.
Where DocFind fits
DocFind refuses PDFs that will not open without a password, and tells you so. If a file can't be opened, hasn't been read yet, or has changed since it was indexed, it names which ones and why — "password-protected" being one of the named causes — rather than folding the file quietly into a zero-result search. One locked document does not stop the run either: the rest of the library indexes as usual and the locked file is reported at the end.
One thing that is not a limit, because it is a deliberate decision in both apps: a PDF carrying only a permissions password — restrictions on printing or copying — exports like any other file. Neither app checks those permission bits. The iPhone code says why in its own comment: refusing such a file would “drop pages that were there for the taking”. Only a file that will not open is omitted, and every export lists what was searched and anything that was skipped, so you are never handed a document with pages silently missing.
Check a file before you go looking
If you are not sure which kind of file you have, the checker answers it in one step: it reports whether the file has a text layer, looks like a scan, or is encrypted — and it says so when it cannot tell. It runs in your browser and the file is never uploaded.
Related: PDF search not finding words that are there? · Search PDFs without uploading them anywhere · Make a scanned PDF searchable · Search many PDFs at once