The thread that proves it: converting an .eml to a PDF that will still open in 2036

Convert a saved email to PDF in your browser: headers typeset, inline images kept, attachments listed, remote trackers never loaded — all on your device.

UnboundPDF is a free suite of 48 PDF and image tools that run entirely in your browser — merge, split, compress, edit text, OCR in 126 languages, redact, sign, convert and archive to PDF/A. Your document is read and written by the page on your own device; there is no document-upload endpoint in the core tools, no account, no watermark and no daily cap. Every result can be checked — with the Network tab, or with the Document Passport the Workspace writes for a chain of steps.

Diagram comparing in-browser local processing, where a document never leaves the device, to an upload-based tool that sends the document to a server and back

Quick start. Export the message as .eml (drag it out of your mail client, or Save As), open Email to PDF, add the file, download. Header block, body, inline images, attachment manifest — one clean, paginated record.

Mailboxes are not archives

The message that proves the deadline was extended lives in an account that can be closed, migrated, quota-purged or simply searched badly under pressure. The moment a thread starts mattering — a deposit, a promise, a dispute — it deserves a fixed form in your own files. That is a PDF with the headers visible, not a screenshot with a suspicious crop.

What the conversion preserves, and refuses

Preserved: From, To, Cc, Date and Subject typeset at the top, the body as sent (HTML rendered, inline images included), and an honest manifest of attachments by name and size. Refused: remote content — the tracking pixels and remote images that would tell a server you opened the message are never fetched, marked in place instead. Outlook's binary .msg is refused by name with the .eml export route explained, which beats a parser that half-reads it.

Filing like you mean it

Name it for retrieval — 2026-08-28-landlord-deposit-agreement.pdf — and file the saved attachments beside it. If the record set grows into a production, the law-office checklist pattern applies; if it feeds a signing chain, the contract flow is next door. Run the pre-send routine before the record itself travels onward.

Troubleshooting

My client only gives me .msg. The tool names the refusal and the fix: export as .eml (most clients can) or forward to a client that does. An image shows as a placeholder. It lived on a server, not in the email — that is the privacy stance working. The thread is fifty messages. Export the ones that matter individually; a curated record reads better than a haystack.

Diagram comparing in-browser local processing, where a document never leaves the device, to an upload-based tool that sends the document to a server and back

Frequently asked questions

Why not just screenshot the email?

A screenshot is a picture with no selectable text, no full headers, and obvious crop marks where context should be. The PDF carries the typed record.

Will anyone see that I converted it?

Nothing is announced to anyone — remote content is never loaded, so even the sender's tracking pixel stays silent.

What about the attachments?

Listed by name and size at the end of the PDF, not embedded. Save them beside it — a record plus its exhibits.

Try it yourself

Free, private, no account. Runs entirely in your browser.

Related articles