BASALT · JOURNAL
How to verify a PDF after exporting it
Export is a format change, not proof that a PDF is correct. Fonts can reflow, links can break, hidden content can survive, and a redaction can fail if the editor only placed a visual mark.
Check structure first
Compare page count, order, dimensions, orientation, bookmarks, and required labels with the source. Confirm that the filename and version identify the intended release. For forms, verify that required values remain visible and that no unwanted editable fields survive.
Check content and privacy
Search for removed terms and identifiers in alternate formats. Inspect page images, OCR text, comments, annotations, attachments, metadata, and document properties. Open the file in an independent viewer rather than relying on the same application that created it.
Check the recipient experience
Test links, printing, zoom, accessibility, and password behavior when those features matter. Compare a few pages at high zoom for clipping, blurry scans, or accidental marks. Keep a short verification record for important releases.
Frequently asked questions
Why use a second PDF viewer?
Different viewers expose different layers and behaviors. An independent check can reveal content the authoring application hides.
Is a matching page count enough?
No. A file can retain the same pages while exposing hidden text, attachments, or metadata.
Should I verify every page?
For sensitive releases, yes. At minimum, use a documented sample plus automated searches and targeted visual checks.
Doing it in Basalt
Basalt includes a local verification pass for redactions and document content so you can inspect the exported PDF before sharing it. Download Basalt.
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.