Redacting a PDF: cover-up, flattening and what to verify
Redaction is not drawing a dark rectangle over a sentence. A rectangle can leave the original text in the file and make it recoverable by copying, searching or inspecting the PDF objects. The safe question is not “does it look hidden?” but “what can still be extracted from the exported copy?”
A practical workflow
- 1
Work on a copy
Keep the source in a controlled location. Make a list of the values that must not appear in the released file, including repeated headers, footers, attachments and metadata.
- 2
Mark every occurrence
LittleKit’s flattened workflow asks you to mark visible areas yourself. Review every page, zoom in on small text and look for repeated or partially obscured values.
- 3
Export a new image-only copy
The flattened operation rebuilds each page from pixels and does not copy the original PDF text/object layer. This is deliberately destructive: forms, links, annotations, signatures and selectable text do not survive.
- 4
Try to disprove the redaction
Reopen the output, search for the removed value, select and copy text, and inspect the page visually. If the value is still visible or can be recovered, do not share the file.
Three different operations
A whiteout or filled rectangle is a visual annotation. It can be useful for a draft, but it is not a security boundary. Standard metadata removal clears common document fields, but it does not remove visible names or hidden text. Flattening rebuilds the visible page as an image, which is stronger against source-object extraction but also removes useful document features.
Some professional workflows require native, text-preserving redaction with audit records and a controlled review process. If the document is part of litigation, a regulated disclosure or a signed workflow, use the process required by your organisation rather than treating a free browser tool as a legal guarantee.
Do not forget the surrounding file
A redacted page can still reveal a person through context, a unique date, a filename or an attachment. Review the filename you download, document metadata and any companion files before publishing. Never paste the source into a support message just to ask whether the redaction worked.