Files never uploaded · processed in your browser

Fake-redaction detector / PDF inspector

See in one second whether text under the black bars is still copyable

Fake-redaction detector / PDF inspector runs locally and is designed for verifiable privacy work: process, export, then confirm the sensitive content is gone before sharing.

Magnified sample PDF showing redaction bars being inspected
Redaction proofLOCAL
ProcessExportVerify
Processed in your browserWorks offlinePre-export self-check

Drag a file here, or click to choose

Processed locally in your browser — never uploaded

Operational notes

What this tool proves

Upload a PDF and this tool renders every page, samples the pixels, and flags any "fake redaction" — areas that look covered by a black box but whose underlying text is still copyable. It also lists identity-leaking hidden metadata (author, creator, timestamps) and tells you whether the file is searchable or scanned. The whole check runs locally; nothing is uploaded. Run it before sharing any "redacted" file.

How to use Fake-redaction detector / PDF inspector

  1. 1Pick the PDF to inspect — analyzed locally, never uploaded
  2. 2Wait a few seconds for the per-page render and sampling
  3. 3Read the report: fake-redaction pages, leaking metadata, searchability
  4. 4If fake redaction is found, jump straight to the true PDF redaction tool

Why this tool

Almost no competitor offers a verifiable "did the redaction actually work" check. We use post-render pixel sampling (far more robust than parsing operator geometry) to catch copyable text under black bars — turning the verifiability nobody else bothers with into your last line of defense.

FAQ

Does it guarantee my file is 100% safe?
No. It is a heuristic that errs toward false negatives. It catches the most common "black box" fake redaction, but PDFs are complex — always combine it with a manual copy-paste check.
Does inspecting change my file?
No. It is read-only analysis; no new file is produced and your original is untouched.

Related tools

State privacy rights

Deletion laws near this workflow

These source-checked rows connect local redaction and PII cleanup to state privacy deletion rights. The cluster is staged noindex until final legal review.

Updated 2026-06-10 · PrivScrub

Sources, review and limits

Last verified

2026-06-17

Author

RedactCat editorial desk

Reviewer

Privacy workflow review

Primary sources

  • Local PDF/image parsing and canvas rendering APIs
  • User-marked redaction regions and export settings
  • OCR helpers where the page explicitly offers OCR

Redaction is high risk. Always inspect the exported file for hidden text, metadata, layers and missed sensitive information before sharing.