How to save email as PDF evidence
that holds up in court.

Most people who need to copy and print email evidence do the obvious thing: open the message in Gmail or Outlook and choose Print → Save as PDF. The result looks like an email. It is not, in any meaningful sense, a record of one. It shows a display name instead of the real sender address, a local-time date with no time zone, no Message-ID, no Received chain, and none of the DKIM or SPF results that let anyone verify the message actually travelled the route it claims to have travelled.

When the other side asks "how do we know this wasn't edited?", a printed screenshot has no answer. A PDF generated from the original .eml or .msg file, with the full headers and a hash of the source file, does. That is the difference between an exhibit that gets argued over and one that gets admitted.

There is no single legal standard for "email evidence PDF", and this page is not legal advice — rules of evidence differ by jurisdiction and your counsel should confirm what your court expects. In practice, though, the same handful of elements come up whenever an email is authenticated:

1. The complete header block. From, To, Cc, Date, Subject, Message-ID, In-Reply-To, and every Received line, in order. This is the routing record that ties the message to real servers at real times.
2. Authentication results. DKIM signatures, SPF and DMARC results as recorded by the receiving server. These are what an expert points to when explaining that the message was not forged.
3. The body, exactly as delivered. Both the plain-text and HTML parts if present, with inline images rendered rather than replaced by broken-image boxes.
4. Attachments, with a manifest. Each attachment listed by filename, size, and a SHA-256 hash, and either appended to the PDF or supplied alongside it.
5. A link back to the source. The hash of the original .eml/.msg file, so anyone can confirm the PDF was produced from that exact file.
6. Page identifiers. Bates numbers if the matter is in discovery, so every page can be cited unambiguously.

MailToPDF's Forensic header mode produces all six by default. The feature overview describes each in more depth.

The workflow is the same whether you have one message or a folder of five hundred. The only part that varies is the export step, which depends on your mail client.

1. Export the original file. Download the message as .eml (or .msg from Outlook). Do not forward it to yourself first — forwarding rewrites the envelope and destroys the original routing headers. The export guide has the exact clicks for Gmail, Outlook, Apple Mail, Thunderbird, ProtonMail, Yahoo, and Fastmail.
2. Open the converter and drop the files in. The MailToPDF converter parses each file in your browser tab. Nothing is transmitted; you can disconnect from the internet after the page loads.
3. Set the header mode to Forensic. This prints the complete raw header block, authentication results, and message IDs above the rendered body.
4. Turn on Bates numbering if you are in discovery. Set the prefix your matter uses (for example SMITH), the padding, and the starting number. Pages are stamped sequentially across the whole batch.
5. Choose how attachments are handled. Append PDF attachments to the message PDF, or export a zip that keeps every attachment in its original form next to a SHA256SUMS.txt manifest.
6. Download, then keep the original. Store the source .eml/.msg files with the PDFs. The PDF is the presentation copy; the original file is what an expert will ask for if authenticity is challenged.

A recurring question is whether converting an email to PDF keeps the timestamps. It depends entirely on what you convert. A printed Gmail page shows one date, rendered in your local time zone, with the seconds dropped. The original message carries several: the sender's Date header (with its UTC offset), plus one timestamp per Received hop, each stamped by a different server as the message passed through.

Those hop timestamps are what make an email's timeline defensible. They cannot be edited by the sender after the fact, they come from independent machines, and they let you show, for example, that a message the sender claims to have sent at 9:00 was not handed to their outgoing server until 11:42. Converting from the .eml with forensic headers preserves every one of them exactly as written, offsets included. Converting from a screen print preserves none.

"Is there a record?" is really two questions: can you show the PDF came from a specific original file, and can you show neither has been altered since? Cryptographic hashes answer both. MailToPDF writes the SHA-256 of the source email file into every PDF it generates, lists every attachment with its own hash in a manifest, and includes a SHA256SUMS.txt in zip exports.

To close the loop, record the hashes at the time of conversion — in a case note, an email to yourself, or your matter management system — with the date and who performed the export. Anyone can later recompute the hash of the original file with a standard command (shasum -a 256 on Mac and Linux, certutil -hashfile on Windows) and confirm it matches. That, plus a short written statement of how the file was obtained, is the chain of custody most courts are looking for from a non-expert.

If you work at a law firm, a clinic, an accounting practice, or anywhere else bound by confidentiality rules, the phrase "free online email to PDF converter" should worry you. Nearly every such service works by uploading your message — privileged content, client names, attachments and all — to a server you do not control, where it is processed, cached, sometimes logged, and occasionally retained under terms nobody read. Whether that breaches your obligations depends on your rules and your engagement terms, but it is a question you do not want to have to answer.

MailToPDF avoids the problem by having no server to upload to. The parsing and PDF generation run as JavaScript inside your browser; the message never leaves your machine. You can verify this yourself: open the browser's network tab, drop a file, and watch no request go out — or load the page and disconnect from the internet before converting. Our privacy architecture page walks through exactly what is and isn't fetched, and how to audit it.

Can I convert Outlook .msg files to evidence PDFs? Yes. The converter reads .msg directly. For the cleanest header block, export from Outlook as .eml where possible — the Outlook section of the export guide shows how.

What about a whole email thread or chain? Export each message in the conversation as its own file and convert them together; the converter can merge them into a single Bates-numbered PDF in date order. See how to convert an email thread to a single PDF.

Does this work for a folder of hundreds of messages? Yes — batch conversion is the normal case. Export the folder (Thunderbird and Fastmail can do this in bulk), drop every file in at once, and choose individual PDFs, one merged PDF, or a hash-verified zip.

Is the PDF admissible? Admissibility is decided by the court, not by software. What the PDF gives you is the metadata, hashes, and unaltered content that authentication typically rests on. Combine it with a documented chain of custody and consult counsel about your jurisdiction's standards.