What does this PDF checker inspect?
It searches readable PDF names such as /JavaScript, /OpenAction, /Launch and /EmbeddedFiles, along with encryption, object-stream and metadata signals. A match identifies a pattern, not execution or the safety of the whole document.
How to use the check
- Choose a PDF and read both the result and inspection coverage.
- Open the priority findings. Keep the original closed if its source is unknown or active patterns appear.
- Intentionally confirm an available preview. Use page-image export only when its complete scope is shown.
Exact limits
Compressed or encrypted content may remain inaccessible. Native preview and page-image export require input no larger than 16 MiB. Limits are 4 million pixels per page, 8 million overall and 8,192 pixels per edge. Complete export also requires at most twelve pages; exceeding a budget blocks export rather than producing a partial copy.
Reproducible synthetic example
This PDF contains /JavaScript only in an inert comment, with no script action. It still triggers pdf.token.JavaScript. This demonstrates a possible raw-pattern false positive, not proof of executable code.
The findings come from an actual local scan of this test file. Download it and choose it in the scanner. No real personal data or malware.
Download test file: pattern-demo.pdfExample inspection coverage: partial.
Interpret the result
Risk and inspection coverage are separate statements. complete means analyzed within the defined inspection scope. Green does not establish the absence of malware. partial, unavailable or failed mean inspection is limited, unsupported or unsuccessful.
- Check a PDF before opening: JavaScript, actions and limits
- Inspection method and next steps
- More guides
Responsible operator: Tom Silas Helmke, operator of ScanBeforeOpen. Content revised: .