Extract PDF Attachments
Inspect standard embedded files and download a safe ZIP
About this tool
The scanner follows the catalog Names/EmbeddedFiles name tree and validates nested nodes, cycles and file specifications. It retains original display names, duplicate entries and valid zero-byte files, then assigns safe unique filenames for one explicitly downloaded ZIP. It supports unfiltered streams and plain FlateDecode without predictors; malformed entries or unsupported filters stop the entire scan rather than disappearing. Page FileAttachment annotations, AF associated files, external links and portfolio structure are outside this scan. Decompression is streamed and cancelled when its decoded-byte budget is reached. Limits: 20 MiB PDF input, 200 pages, 100 attachments, 16 MiB per decoded file and 64 MiB total. Downloaded attachments are never opened automatically.
Scenario Recipes
Export an attachment and an empty file
Goal: Inspect standard embedded files and download a safe ZIP
- Load the example with notes.txt and empty.txt.
- Inspect the count and decoded sizes before downloading.
- Download ZIP and confirm empty.txt remains a zero-byte file.
Result: Two entries remain separate and no attachment is opened automatically.
Failure Clinic (Common Pitfalls)
Why can a PDF viewer show an attachment that is absent here?
Cause: This scan is limited to standard catalog EmbeddedFiles. A viewer may also expose page attachment annotations, AF associations or portfolio features.
Fix: Check the PDF viewerβs attachment source and use a tool supporting page annotations or AF when that is where the file is stored.
What happens to duplicate or unsafe names?
Cause: Entries remain separate. Paths and unsafe characters are replaced, and case-insensitive collisions receive deterministic numeric suffixes in the ZIP.
Fix: Use the JSON originalName/downloadName mapping to identify each ZIP entry; do not merge entries by original name.
Production Snippets
Export an attachment and an empty file
text
notes.txt -> Sample attachment\n
empty.txt -> 0 bytes
Catalog scope: Names/EmbeddedFilesFrequently Asked Questions
Why can a PDF viewer show an attachment that is absent here?
This scan is limited to standard catalog EmbeddedFiles. A viewer may also expose page attachment annotations, AF associations or portfolio features.
What happens to duplicate or unsafe names?
Entries remain separate. Paths and unsafe characters are replaced, and case-insensitive collisions receive deterministic numeric suffixes in the ZIP.
Is an empty attachment an error?
No. A valid zero-byte stream remains an empty file. Missing or corrupt streams are errors.
Keep browsing