Why a PDF can contain hidden additional files
A PDF is more than a visible sequence of pages. Depending on how it was prepared, it can contain embedded source files, a spreadsheet used to make a chart, exported data, or a file attached to a report. These embedded files may be unrelated to text that the PDF viewer displays. A normal page screenshot therefore cannot reveal everything stored inside the document.
LHTSOFT PDF uses the browser's PDF.js parser to request supported attachment metadata and then fetch the decoded file bytes. This operation is read-only: it does not change, flatten or remove anything from your open PDF. It never opens an extracted attachment automatically, and the original PDF and Undo history are unchanged.
What you receive in the ZIP archive
Every ZIP member carrying attachment bytes receives a generic name such as attachment-001.bin rather than using the name supplied by the PDF. This helps prevent filename-based path traversal, overwriting unrelated files or accidentally double-clicking an executable. Original PDF-supplied names are included only as informational strings in manifest.json.
- Open the PDF in your browser. If the PDF is damaged or password protected, open or unlock it through a supported local workflow first.
- Choose Convert PDF and click Export embedded PDF attachments (ZIP). The browser prepares the files locally, then initiates a ZIP download.
- Open manifest.json inside the ZIP with a text editor to see the attachment names, descriptions, archive names and byte counts.
- Treat the numbered attachment-NNN.bin files as unknown until you have verified their origins. Do not rename and execute untrusted scripts or software simply because they were found inside a PDF.
Limits that protect the editing session
The beta export accepts PDF files no larger than 32 MiB, at most 25 embedded attachments, up to 15 MiB for any one decoded attachment and 40 MiB of combined decoded attachment data. Empty or unsupported attachment values and oversized results are rejected. If there are no attachments, the tool reports that rather than producing an empty archive.
These limits are not a guarantee that every malicious PDF will use little memory. The PDF.js decoder must allocate decoded attachment bytes before the tool can measure their size, so extreme compression or parser-specific inputs can still pressure browser memory. Do not open suspicious PDFs on a device that handles sensitive work.
Security and preservation: what this tool does not do
PDF attachment extraction is not malware scanning or file-type verification, and it does not prove a PDF is clean. It also does not remove attachments from the source file. The exported ZIP is for user-directed inspection and recovery, not an automatically trusted package for sharing.
Your PDF stays local during this workflow. Ordinary requests for website code and advertising resources are separate from document processing; optional cloud operations are only initiated when you choose a cloud provider. Review the archive and the original document independently before transmitting any attachment to someone else.