Post-sanitization verification examines the PDF created by a sanitization operation and checks whether it satisfies the removal requirements that were actually applied. It provides a technical assessment of the output rather than relying solely on the appearance of the document in a PDF viewer.
Automatic verification is enabled by default in every PDFSanitize edition. You can disable it in Sanitization Options and perform verification manually afterward when that better suits your workflow.
Verification and the selected settings
Every sanitization operation has an associated set of options describing which types of information were selected for removal. PDFSanitize uses those settings when verifying the resulting PDF, even if you subsequently change the active profile in the interface.
For example, suppose you sanitize a report with External Sharing and then change the selected profile to Strict Privacy. Verification of the existing output still follows the External Sharing requirements used when that file was created.
This distinction matters because different profiles permit different features to remain. A document can pass Metadata Only verification while still containing hyperlinks or attachments, since those features are not targeted by that profile.
Structural integrity and page count
Verification begins by checking whether the sanitized output can be opened and its PDF structure validated. If this check fails, the result is marked Failed and the remaining content-specific checks do not continue.
When structural validation succeeds, PDFSanitize also compares the number of pages in the original and sanitized documents. An unexpected difference causes the page-count check to fail, since sanitization is not intended to change the number of pages.
A matching page count does not establish that every visual detail is unchanged. When pages have been reconstructed or the original contains complex graphics, opening the sanitized file for a visual comparison remains important.
Checking the removal requirements
Depending on the sanitization settings used, PDFSanitize can check document information metadata, XMP metadata, PDF identifiers, previous revisions, annotations, interactive forms, embedded files, JavaScript, document actions, hyperlinks, bookmarks, optional-content structures, and detected hidden or off-page text.
The applicable checks correspond to the selected removal options. For example, a profile that preserves hyperlinks does not require all link annotations to disappear, while a profile that removes them includes checks for hyperlink annotations and supported external navigation actions.
Verification also accounts for distinctions between annotations, form widgets, and hyperlinks. A form or link annotation that the selected policy intentionally permits is not automatically treated as a failure merely because ordinary annotations were selected for removal.
Automatic verification
When automatic verification is enabled, PDFSanitize verifies each successfully sanitized document after creating its output. The results are associated with the document and can be reviewed in the Verification tab.
For a batch, each successfully processed PDF receives its own verification result. A successful result for one file does not indicate that every document in the batch passed.
After processing, inspect the individual results and pay attention to warnings or failures before exporting reports or distributing the files.
Manual verification
You can use Verify Output when automatic verification was disabled or when you want to repeat the checks for an existing sanitized result.
- Highlight the relevant document in the PDF list.
- Confirm that it has a completed sanitization result in the current session.
- Click Verify Output.
- Allow verification to finish and open the Verification tab.
- Review the overall result and individual checks.
Manual verification requires an existing sanitization result for the selected document in the current session. It is not intended as a general command for verifying arbitrary PDFs that were created outside the current PDFSanitize workflow.
SHA-256 fingerprints
Verification records SHA-256 fingerprints for the original and sanitized files. If these values were not already calculated during sanitization, PDFSanitize calculates them when verification runs.
Fingerprints are useful when you need to identify an exact file, particularly if several sanitized outputs have similar names. They can also be included in exported reports and Enterprise certificates.
Verification should be followed by reviewing the actual PDF when appearance, readability, or document functionality matters. The technical checks establish the selected conditions, while visual review helps confirm that the final document is suitable for its intended recipients.
