Save Email as PDF for HR or Court: What Survives and What Gets Lost
HR wants the email as a PDF. So does your lawyer, or the tribunal portal. A PDF is fine for reading, but it drops the parts of an email that prove where it came from. Here's what an EML file holds, what a converted PDF keeps and loses, and how to hand over both without weakening your case.
Someone has asked you for "the email, as a PDF." Maybe it's HR running a grievance. Maybe it's a solicitor, an employment tribunal portal, a small claims form, or an insurer. They want something they can open, print and attach to a file.
Fair enough. The trouble is that the PDF version of an email is a picture of the message, and the parts that prove the message is genuine aren't in the picture.
That doesn't mean don't send the PDF. It means know what you're handing over, and keep the thing that backs it up. If the other side ever says an email "was never sent in that form," a PDF can't settle the argument. The original file can.
Why you'd save email as PDF in the first place
Three reasons, and they're all practical.
- Nobody on the receiving end wants to install an email program to read your evidence. A PDF opens anywhere.
- Case bundles and HR files are page-numbered documents. You can't put page 14 of a bundle inside an .eml file.
- Upload portals are picky. Many accept PDF, Word and images and nothing else.
So the PDF is the reading copy. Treat it that way and most of the problems below stop mattering.
What an email file actually contains
When you download a message from Gmail or save it from Thunderbird, you get an .eml file. It's plain text in the format set out in RFC 5322, with MIME sections (RFC 2045 onward) for HTML, images and attachments. Open one in Notepad and you'll see it.
The top of the file is the header block. You know the obvious lines: From, To, Cc, Date, Subject. But there are usually dozens more, and a few of them carry real weight:
| Header | What it tells you |
|---|---|
| Received | One line added by each mail server the message passed through, with that server's own timestamp. Read bottom to top, it's the route. |
| Message-ID | A unique ID the sending system gives the message. The sender's mail system can often find the matching copy by it. |
| DKIM-Signature | A cryptographic signature from the sending domain (RFC 6376). If the body or key headers were edited later, the signature stops matching. |
| Authentication-Results | What your provider concluded when it checked SPF, DKIM and DMARC on arrival (RFC 8601). |
| Return-Path | Where bounces go. Often differs from the From address, which is normal for newsletters and worth a look for anything else. |
None of these show up in your inbox view. All of them are what an expert would look at if authenticity was ever challenged.
Save email as PDF: what the PDF keeps
Take the EML to PDF converter on this site as a worked example, because I've read the code and can tell you exactly what it does rather than guessing. Other converters differ in detail, but they make the same kind of choices.
- Five headers go in a table at the top: From, To, Cc, Date and Subject, each only if the email has it.
- The body. If the message has an HTML version it uses that, otherwise the plain text version. Scripts, style blocks, iframes and embedded objects are stripped out before layout.
- An attachment list. Every attachment is named with its size in KB, under a line that reads "Attachments (not included)".
- Page size is A4 with half-inch margins.
If the HTML can't be laid out, or would run past 500 pages, it falls back to the five headers and the body as plain text. You get the words, but tables and formatting are gone, and so is the attachment list. If even the plain version runs past 500 pages, the conversion stops with an error telling you to trim the quoted reply history. The fallback is sensible, and it's also a reason to check the PDF against the original before sending it anywhere important.
What gets lost when you save an email as PDF
This is the part that matters for evidence.
The routing headers
Received, Message-ID, DKIM-Signature, Authentication-Results: none of them make it into the PDF. That's normal. Gmail's print view leaves them out too, and so does Outlook's. A PDF can't carry a DKIM signature that means anything, because the PDF isn't the signed content.
Images
The converter replaces every image in the body with the text [image]. That covers remote images (tracking pixels, logos hosted on the sender's server) and inline ones embedded in the message. If a screenshot inside the email is the actual evidence, a converted PDF won't show it. Save that image separately.
Attachments
Listed by name and size, not included. Inline images embedded in the message usually show up in this list too, since they're stored as separate parts. A contract sent as an attachment needs its own PDF. If you want one file, convert each attachment and then combine the email and its attachments into one PDF, with the email first so the attachment list on page one works as an index.
Bcc and anything outside the five
Bcc isn't printed. If you're the sender and your Sent copy records a Bcc, it won't appear. Reply-To, Sender and every other header are left out as well.
The Date line is the sender's clock, not a fact
The Date header is written by the sender's mail program from the sender's computer clock, time zone and all. The PDF prints it with the sender's offset intact, for example "Tue, 03 Mar 2026 16:42:10 -0800", and doesn't convert it to your local time.
Two consequences. First, if you're matching an email against a timeline written in UK time, do the conversion yourself and say you did. Second, a wrong PC clock produces a wrong Date header. The Received lines are stamped by mail servers, which are far less likely to be off, and that's one more reason the original file matters.
How to export the original .eml
Do this before anything else, and do it from the mailbox that received the message, not a forwarded copy. Forwarding rewrites the message: new headers, new Date, the old ones gone or pasted into the body as text.
- Gmail: open the message, click the three dots, choose "Download message". Or "Show original", which displays the full headers and has a "Download Original" link.
- Outlook on the web and the new Outlook: open the message, three dots, "Save as". You get an .eml file.
- Classic Outlook for Windows: File, Save As saves a .msg file by default. That's Outlook's own format, not .eml. Keep it, it's still the original, but know that a lot of tools won't read it.
- Apple Mail: drag the message to a Finder window and it becomes an .eml file. Or File, Save As, with the format set to Raw Message Source.
- Thunderbird: File, Save As, File. It saves as .eml.
Name the files so they sort sensibly: 2026-03-03_from-jsmith_re-rota-change.eml beats "Re: Re: FW: rota.eml" every time.
Is a PDF of an email accepted as evidence?
Usually, yes, as a copy. Courts and tribunals see printed emails constantly and most of the time nobody disputes them. I'm not a lawyer and rules differ by country, so treat this section as orientation, not advice.
In US federal courts, Federal Rule of Evidence 901 says the party offering an item has to show it is what they claim it is. Testimony from the recipient often does that for an email. Rule 902(14), added in 2017, lets data copied from an electronic file be self-authenticating when a qualified person certifies it was checked by a process of digital identification, which in practice usually means a hash value, and the other side gets advance notice. That's the modern answer to "prove this copy matches the original," and it works on the .eml, not on a PDF you made from it.
In practice, the PDF usually gets read. The original gets examined when someone says it's fake.
Fingerprint the original with a hash
A hash is a short fingerprint of a file. Change one character and it changes completely. Taking one on the day you export the email gives you a simple way to show later that the file hasn't been touched.
- Windows (Command Prompt): certutil -hashfile message.eml SHA256
- Windows (PowerShell): Get-FileHash message.eml (SHA-256 is the default)
- macOS: shasum -a 256 message.eml
- Linux: sha256sum message.eml
Paste the result into a short text note with the date and where the file came from. It costs a minute and it's the kind of detail that makes an HR investigator or an opposing solicitor take the rest of your material seriously.
A checklist before you send it
- Export the .eml (or .msg) from the original mailbox. Don't forward first.
- Hash it and note the date.
- Make the PDF from that file, not from a screenshot.
- Open the PDF and compare it with the email on screen. Check the body is complete and the Date line reads correctly.
- Save any important inline images and every attachment separately, and convert them if the recipient needs PDFs.
- Send the PDF as asked. Say in your covering note that you hold the original message files and can provide them.
- Keep the originals somewhere that isn't the mailbox. Accounts get closed, especially work ones, and usually right when a dispute starts.
That last point is the one people miss. If the dispute is with your employer, your work mailbox can disappear the day you leave. Export what you're entitled to keep, check your company policy on that first, and do it early.
When a PDF on its own is enough
Plenty of times. A receipt for a returned item, a confirmation of a booking, a landlord's agreement to fix the boiler: nobody's going to challenge the headers on those, and a clean PDF is exactly what the other side wants. Save the .eml anyway. It's a few kilobytes and it takes ten seconds.
Where I'd never rely on the PDF alone is anything where the other side has a reason to say the email was altered, never sent, or sent at a different time. Harassment complaints, disciplinary cases, contract disputes, anything involving money changing hands on the strength of an email. In those, the PDF is the copy people read. The .eml is your evidence.
