What is a real embedded PDF file?
A PDF can act as a container for attachments. The embedded file is stored as bytes in a file specification and referenced through the document EmbeddedFiles name tree. Recipients with a compatible PDF reader can find the attachment without downloading a separate ZIP file. This differs from placing an image of a spreadsheet into the page or adding a link to a hosted file.
LHTSOFT PDF uses pdf-lib locally to embed small attachments such as CSV, text, images or other document formats. Attachment content is copied as supplied, without conversion, compression promises or code execution. The Convert PDF panel also offers Extract embedded PDF attachments to export supported existing embedded files as a ZIP.
Attach a file safely
- Open a local PDF no larger than 32 MiB and select Convert PDF.
- Expand Embed a file and select a local file between 1 byte and 8 MiB. Filenames may not contain directory separators or control characters.
- Optionally add a short description that helps recipients understand what the file contains.
- Select Attach file to PDF. Use the Embedded files button to list the standard attachment names currently stored in the PDF.
- Download the edited PDF and reopen it in a reader that supports embedded attachments. If needed, use Extract embedded PDF attachments to export a ZIP and compare the contents to the source.
Malware, recipient support and limits
The feature does not scan attachments for malware. Do not automatically open or run attachments received from untrusted sources. Some PDF readers hide or block certain file types; delivery and display depend on the recipient software. For now, only flat standard name trees are supported for adding attachments. PDFs with nested or malformed attachment name trees are rejected instead of being silently modified.
At most 12 attachments are supported by this creation workflow. Duplicate filenames are rejected case-insensitively. The embedded file and PDF are processed in the browser and never uploaded to an LHTSOFT PDF-processing server. Large files can still use significant browser memory, and digital signatures on previously signed documents may be invalidated by edits.