BASALT · JOURNAL
The redaction mistakes that happen with good software
Documented redaction failures are rarely caused by bad software. They are caused by competent people using capable tools under time pressure and missing a step.
Listing the recurring ones is more useful than comparing feature tables.
Using an annotation instead of a redaction
Drawing a black rectangle with a markup tool, or in Preview, produces a page that renders exactly like a redacted one. The content underneath is untouched and recoverable by selecting the region or deleting the annotation.
Caught by: extracting text from the output and searching it.
Redacting but not sanitising
The marked content is removed and the metadata, attachments, hidden layers and earlier revisions are not. In tools where these are separate commands, the second is easy to skip.
Caught by: exiftool for metadata, pdfdetach -list for attachments, counting %%EOF markers for revisions.
Saving incrementally
An incremental save appends changes rather than rewriting the file, so the previous revision, containing the unredacted page, remains in the bytes.
Caught by: more than one %%EOF marker in the output.
Missing the OCR layer
On a scanned document, destroying pixels without removing the corresponding invisible text leaves the words machine readable under a blacked out image.
Caught by: extracting text from the finished file and searching it.
Redacting the image but not the thumbnail
Some documents carry embedded page thumbnails generated before the redaction. The page is clean and the thumbnail is not.
Caught by: structural inspection of the output.
Trusting the page
The single common thread. Every failure above renders identically to a correct redaction, which is why checking by looking is the one method guaranteed to tell you nothing.
The countermeasure
Verify the output rather than the appearance, and verify with something other than the tool that produced it. That habit catches every item on this list and does not depend on which application you chose.
Frequently asked questions
What is the most common redaction mistake?
Using an annotation or markup tool to draw a black rectangle instead of a redaction tool that removes content. The page renders identically to a correct redaction while the material underneath remains recoverable.
Why do redactions fail even with good software?
Because most failures are missed steps rather than tool defects: sanitisation skipped, an incremental save leaving an earlier revision, an invisible OCR layer left intact, or an embedded thumbnail generated before the redaction.
How do I know if my redaction worked?
Extract the text from the finished file with a different tool and search for what you removed, read the metadata, list attachments, and count %%EOF markers. Checking the appearance of the page tells you nothing, because every failure renders identically to success.
What does more than one %%EOF marker mean?
That the file contains multiple revisions from incremental saves, and earlier bytes are still present. A redacted document should be written as a single generation, because an earlier revision can contain the unredacted page.
Doing it in Basalt
Basalt is a native macOS PDF toolkit with eighteen tools in one window: merge, split, compress, OCR, Bates numbering, privilege logs, forms, signing, watermarks, comparison and more. Redaction destroys content rather than covering it, and an independent verifier re-opens every written file and proves the material is gone before the file is saved. If it cannot prove it, nothing is written. A one time $29 licence covers up to three Macs, it is free for the first 24 hours, there is no account, and the engine holds no network entitlement at all, which macOS enforces at the code-signature level. Download it at basaltformac.com.
Redaction that proves itself
Basalt destroys the content you mark, then re-opens the file it wrote and proves the content is gone before it saves anything. Your documents never leave your Mac.