EML to PDF renders one email message, not a reconstructed thread, with optional headers at the top and attachments listed rather than embedded.
From real runs
| Element | Result | What happens |
|---|---|---|
| Message headers | Kept | From, To, CC, Date, and Subject render at the top when includeHeaders is enabled. |
| HTML body | Changed | HTML is sanitized before PDF generation; scripts, event handlers, remote tracking pixels, and unsafe URLs are removed. |
| Plain-text body | Kept | Text-only messages render with line breaks and quoted text blocks preserved where the MIME body exposes them. |
| Inline images | Kept | CID-referenced inline images are embedded when the matching MIME part is present in the EML file. |
| Attachments | Changed | Attachments are not embedded in the PDF; they are listed in a manifest table with name, size, and media type. |
| Threads | Lost | A single EML file does not reconstruct mailbox threads or conversation context outside the message body. |
| Remote resources | Lost | Remote images and tracking pixels are blocked instead of fetched, so the PDF is deterministic and does not ping senders. |
From, To, CC, Date, and Subject render at the top when includeHeaders is enabled.
HTML is sanitized before PDF generation; scripts, event handlers, remote tracking pixels, and unsafe URLs are removed.
Text-only messages render with line breaks and quoted text blocks preserved where the MIME body exposes them.
CID-referenced inline images are embedded when the matching MIME part is present in the EML file.
Attachments are not embedded in the PDF; they are listed in a manifest table with name, size, and media type.
A single EML file does not reconstruct mailbox threads or conversation context outside the message body.
Remote images and tracking pixels are blocked instead of fetched, so the PDF is deterministic and does not ping senders.
We converted our EML sample (299 B) with Mail engine → Document engine on 2026-09-11. It took 51 ms and produced a 14 KB PDF file, 48× larger than the input. The engine raised no warnings.
Input · sample.eml · 299 B
299 bytes
Output · sample.pdf · 14 KB
PDF 1.7, 1 page, selectable text (LibertinusSerif-Bold-Identity-H, LibertinusSerif-Bold, LibertinusSerif-Regular-Identity-H, LibertinusSerif-Regular), 0 image objects
Python email module plus Pandoc
python - <<'PY'
from email import policy
from email.parser import BytesParser
msg = BytesParser(policy=policy.default).parse(open('in.eml','rb'))
html = msg.get_body(preferencelist=('html','plain')).get_content()
open('body.html','w',encoding='utf-8').write(html)
PY
pandoc body.html -o out.pdfSanitize untrusted HTML and decide how to inventory attachments; the short script does not embed CID images or create a manifest.
The HTTP API and the MCP server run the exact engine this page uses (Mail engine → Document engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=eml&to=pdf.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.eml" -F "from=eml" -F "to=pdf" \
--output output.pdfNo. Attachments are not embedded. The PDF includes a manifest table with each attachment's name, size, and media type.
No. Remote images and tracking pixels are removed or left unfetched during sanitization so conversion does not contact the sender.
No. EML is one message file. Quoted replies inside the body render, but mailbox thread reconstruction is outside this conversion.
Inline images are embedded when the HTML references a CID and the matching MIME image part is present in the EML.