Check a redacted PDF before sharing it
WhatsNew2Day — synthetic-fixture verification checklist

[ ] 1. Keep your original private and unchanged. Practise on the linked synthetic fixture, not an identity document or customer file. Record the exact app, edition, version, operating system and date.

[ ] 2. Use the application’s actual redaction workflow and apply/save the result. Merely placing an annotation over text does not establish removal. Cover both the visible marker and the known white-on-white marker area in our fixture.

[ ] 3. Close the editor and open the newly saved output in a different viewer. Search for both test markers and try selecting and copying the marked areas into a local text editor. Finding a marker is a failure; finding none is only one check.

[ ] 4. Inspect every page visually, including page edges and missed fragments. Extract text locally where possible and check it separately. An empty extraction result does not prove that images or other PDF objects contain no sensitive information.

[ ] 5. Inspect document properties, comments, attachments, form values, layers and previous revisions where supported. Use the tool’s documented sanitization process when needed, then repeat checks on the final saved file.

[ ] 6. Check what was lost: searchable text, form interaction, signatures and accessibility may matter. Verify the output in the recipient’s workflow before sharing. Stop and seek a qualified review if the file is sensitive and you cannot assess its remaining content.

Example markers: W2D-VISIBLE-742913 and W2D-HIDDEN-583201
These checks can expose common failures; they are not a security certification. Do not upload private documents to WhatsNew2Day.
Source and original saved evidence: https://whatsnew2day.com/use-cases/permanently-redact-pdf