How To Check a Redacted PDF Someone Sent You
A file arrives with black rectangles on it. You are not the person who drew them, you have never seen the unmarked version, and you have no idea which tool produced it. Every other guide on this site is written for the person doing the redacting, who knows what they covered and can check their own work against the source. Being on the receiving end is a different problem with different limits — and a different set of obligations once you find something.
The asymmetry is the whole point. When you redact your own document you hold two things: the finished file and the source it came from. That second artefact is what makes real verification possible — you can search the output for a string you know is in the original, and a hit is unambiguous proof of failure. A recipient has one artefact and no reference. You cannot search for what you do not know is there, and you cannot tell the difference between a page that was never sensitive and a page that was carefully cleaned.
So a recipient's inspection answers a narrower question than a redactor's does. It is not was this document redacted properly. It is can the content under these marks be recovered by someone with no special access and no unusual skill. That question is answerable, it is worth answering, and people who receive marked-up documents in the course of their work — paralegals taking in a production, journalists handed a leaked file, HR staff receiving records from another employer, anyone reviewing a redacted statement submitted as evidence — almost never ask it, because a black rectangle looks conclusive.
What a received file can and cannot tell you
You can determine: whether the covered text is still present and extractable; whether the black marks are removable objects rather than permanent page content; whether the file carries identifying information in its document properties; whether there is content in the file that is not visible on the page at all, such as comments, bookmarks or embedded attachments.
You cannot determine: whether the scope of the redaction was correct; whether pages were removed before you received it; whether an identifier that was left visible is safe to leave visible; whether the sender kept the original intact. Those questions all require the source document, and you do not have it. Be precise with yourself about this boundary, because the most common recipient error is to run a couple of tests, get clean results, and conclude the document is fine in a much broader sense than the tests support.
An inspection order that does not make things worse
Run these in sequence and stop escalating the moment one of them succeeds. The order matters for a reason that is easy to miss: each step exposes you to more of the protected content than the last, and once you have read something you cannot unread it. If step two hands you the covered text, you have what you need to raise the alarm, and step four would only add to the amount of material you now have to account for.
- Select and copy under a mark. Open the file in an ordinary viewer, drag a selection across a black rectangle, copy, and paste into a plain text editor. If characters appear, the text was never removed and the mark is decoration. This is the single highest-yield test and it takes ten seconds.
- Search for a term you would expect underneath. Use the viewer's find function on a word the context suggests should be there — an account label, a title, a place name. A hit that lands on a blacked-out area is the same finding as above, and sometimes catches cases where selection is awkward because of layout.
- Check whether the mark is an object. Open the file in an editor that shows annotations and try to click the rectangle itself. If it selects, shows handles, or can be moved or deleted, it is an overlay sitting on top of intact page content. Do not actually delete it; you are establishing the category, not extracting the contents.
- Look outside the page. Open the document properties panel and read the title, author and producer fields. Then look for a comments or annotations list, a bookmarks panel, and an attachments panel. Content in these places is not on the page and frequently survives a redaction that handled the visible text correctly.
- Note what the pages are made of. If you cannot select any text anywhere on a page — not just under the marks — the page is an image. That is consistent with a redaction that was flattened properly, and also with a document that was scanned. It is a reassuring signal rather than a proof.
Record what you did and what came back, in a sentence or two per step, at the time you do it. If this turns into a dispute, an account written afterwards from memory is worth considerably less than a contemporaneous note, and the note also protects you by showing that you stopped rather than dug.
When something comes back: what to do next
Stop reading. Once you have established that the redaction failed, further exploration serves no purpose and increases your exposure. You do not need to know the whole of what was leaked in order to report that it leaked.
Do not forward it. Not to a colleague for a second opinion, not as an attachment in the message where you flag the problem. Every copy you make is a copy someone has to account for later. Describe the finding in words; the sender can reproduce it against their own file in seconds.
Tell the sender, promptly and in writing. Say what you found, which page, and how — "text under the marks on page 4 copies out as plain text" is enough. Ask them how they want the copy you hold to be handled.
Check whether a rule governs the rest. In United States federal civil litigation, when a producing party claims that information already produced is privileged or is trial-preparation material, Federal Rule of Civil Procedure 26(b)(5)(B) requires the receiving party, after being notified, to promptly return, sequester or destroy the information and any copies, not to use or disclose it until the claim is resolved, and to take reasonable steps to retrieve it if it was already disclosed onward. Federal Rule of Evidence 502(b) is the companion on the other side: an inadvertent disclosure in a federal proceeding does not operate as a waiver where the holder took reasonable steps to prevent it and promptly took reasonable steps to rectify the error. Between them they explain why prompt notification matters to everybody involved and why quietly retaining the file is the worst available option. If you are a lawyer, a separate professional conduct duty to notify the sender of apparently inadvertent material very likely applies as well; the exact formulation differs by jurisdiction, so read your own rule.
Then make your own copy safe. If you have a legitimate reason to keep working with the document, re-redact the exposed regions in your copy so that the failure does not propagate through your own systems, your own forwards and your own backups.
Common mistakes and misconceptions
Treating a clean copy test as a clean bill of health. It rules out the most common failure. It does not address scope, third-party content, or anything the sender never covered in the first place.
Assuming a failed redaction means the sender was careless. The tools are the problem far more often than the people. A black shape drawn in a general-purpose editor and exported to PDF looks exactly like a burned-in redaction and behaves nothing like one, and there is no visual cue that distinguishes them.
Printing it to "flatten" it before storing it. Printing to paper and re-scanning, or printing to a new PDF, may or may not drop the underlying text depending entirely on the path taken — and either way you have created another copy of a leaking document, and possibly one with a fresh machine-readable text layer generated by the scanner.
Judging the file by whether the boxes look solid. Opacity is a rendering property. A fully opaque rectangle that hides the text perfectly on screen tells you nothing about whether that text is still in the file's content stream.
Forgetting that you are now a custodian. The moment a leaking document lands in your inbox it is in your sent-mail thread, your download folder, your device backup and possibly your organisation's mail archive. Reporting the problem does not clear those. Decide deliberately which copies you keep and where.
Escalating before you look. Raising an alarm about a document that turns out to be correctly redacted costs credibility. Ten seconds of selecting and copying is worth spending first.
Related guides
Explore more ways to redact PDFs privately, or use the redaction tool above:
Frequently asked questions
If I can read the covered text, does that mean the sender did something wrong?
Not deliberately, in almost every case. The overwhelmingly common cause is a tool that draws a black rectangle on top of the page without removing anything underneath it — a highlighter set to black, a drawing annotation, a shape pasted in a word processor before export. On screen the result looks identical to a real redaction, and the person who made it had no way to tell the difference without running the same tests you just ran. Assume inexperience rather than intent. That assumption does not change what you have to do about it, but it does change the tone of the message you send, and a message that treats the sender as having made an ordinary mistake gets a faster and more useful response than one that implies bad faith.
Should I tell the sender, or is it safer for me to say nothing?
Tell them, and do it promptly. Silence leaves a leaking document circulating and leaves you holding material you were never meant to have, which is a worse position than the one you started in. In some settings notification is not merely advisable: in United States federal civil litigation, Federal Rule of Civil Procedure 26(b)(5)(B) sets out what happens once a producing party claims that material was privileged, and the receiving party must then promptly return, sequester or destroy the information and any copies, must not use or disclose it until the claim is resolved, and must take reasonable steps to retrieve it if it was already passed on. Professional conduct rules in many jurisdictions impose a separate duty on lawyers to notify the sender of material that appears to have been sent inadvertently — the wording and the scope vary, so check the rule that actually governs you rather than a general summary. Outside litigation there may be no formal duty at all, and notifying is still the right move.
The document passed every test I know. Can I treat it as safe to forward?
Passing means you could not recover the covered content in a few minutes with ordinary tools. That is genuinely useful, and it is not the same as the document being correctly redacted. Two gaps remain. First, you cannot audit scope: with no original to compare against, you have no way of knowing whether the sender covered everything they should have, and an identifier they left visible because it seemed harmless may still point at a person when combined with the rest of the page. Second, a clean file can still be the wrong file to pass on — a document produced to you under a protective order, an agreement, or a records rule may carry restrictions on onward disclosure regardless of how well it was redacted. Test results tell you about the bytes. They tell you nothing about your permission to share them.
Can I use HidePDF to fix a badly redacted PDF that someone sent me?
You can make your own copy safe, which is a narrower thing than fixing the problem. Open the file here, draw boxes over the exposed regions and download the result: every page is rebuilt as an image with the boxes burned in, so no selectable text survives anywhere in the file you get back, including under the marks. All of that happens inside your browser tab — the document is read by the page's own code on your device, with no upload required and no copy anywhere else. What it cannot do is reach the copy still sitting in the sender's outbox, or the copies that went to whoever else was on the distribution. It also cannot restore the position you were in before you read the covered text. Re-redacting is the right step before you use or store the document; it is a supplement to telling the sender, never a substitute for it.