CHECK
Inspect one local document model
Scan a PDF for metadata, hidden content, comments, form data, attachments, external actions and other privacy risks before you share it.
This tool reports checks, findings and limitations. It does not certify that a document contains no private information.
PDF document
Findings
Metadata
Low · Review
Covered text
High · Review
Attachment
Medium · Review
Inspect one local document model
Choose supported cleanup actions
Re-scan the actual output
Embedded files and objects
JavaScript, URLs and submissions
Common sensitive-data patterns
How it works
PDF.js and pdf-lib inspect one in-memory copy.
Each category reports Checked, Partial or Not checked.
Use real Nexynto tools for the specific objects you decide to fix.
A PDF is a container, not just a picture of pages. Metadata, annotations, fields, attachments, active actions, optional layers and extractable text can remain even when they are not obvious during visual review.
Editorial guides
PDF Privacy · 9 min read
Understand visible pages, metadata, review artifacts, embedded objects and active document behavior.
Read guideMetadata · 8 min read
Review document information and XMP fields without confusing normal metadata with confirmed risk.
Read guideRedaction · 8 min read
Learn why a dark rectangle may leave the original searchable text inside the file.
Read guideSanitization · 10 min read
Separate page-content removal from document-wide cleanup of metadata, actions and attachments.
Read guidePrivacy Workflow · 11 min read
Build a practical pre-sharing cleanup and verification workflow using the right tool for each object.
Read guideFAQ
A PDF can contain document metadata, author names, comments, form values, attachments, links, active actions, hidden layers and extractable text beyond what is obvious on the page.
Select a PDF and review the Document identity and Metadata categories. Common document-information fields and accessible XMP properties are listed separately.
Yes. Text can be placed outside the page, rendered very small, stored beneath an overlay or used as an OCR layer. Context determines whether it is a privacy concern.
Yes. Annotation objects can retain reviewer names, comment text, dates and review history.
Yes. A PDF may carry attached files that are not visible in the ordinary page view. The checker reports them without opening or extracting them.
Yes. PDFs can contain document scripts and automatic or form actions. This checker inspects for them but never executes document JavaScript.
The checker looks for selectable text beneath filled rectangles and other suspicious text conditions. Detection is useful but not complete; verify sensitive documents with a proper redaction workflow.
Yes. Current values, default values and field structure can remain inside an AcroForm even when the page looks complete.
No. It reports what was checked, what was found and where coverage is limited. It does not provide a complete privacy guarantee.
No. Command 1 opens and scans the PDF in your browser. OCR and backend scanning are not used, and the selected file is not stored by Nexynto.
Yes. Summary, categories and findings adapt to small screens, while page preview opens as a separate sheet. Large PDFs may work better on a device with more memory.
It can remove supported metadata, comments, form values, attachments and active actions, then re-scan the generated copy. Partial coverage remains clearly identified.
Checking inspects without changing the file. Sanitizing creates a separate rewritten copy with only the fixes you explicitly confirm.
It may. Any rewrite can invalidate an existing cryptographic signature, so signed documents require an explicit acknowledgement before cleaning.
Yes. The cleaned copy is automatically re-scanned using the same inspector, and you can run another review without selecting the file again.
It records the checks performed, coverage, findings and verified changes. It does not guarantee that the document contains no sensitive information.