Converting Gmail messages to PDF for court
Gmail will print a message to PDF in two clicks, which is why so many Gmail-sourced exhibits are screenshots of a browser print view with a URL and a date stamp along the bottom edge.
There is a better route that takes about the same effort. Gmail can
download an individual message as a .eml file — the original message,
headers and all — and converting that produces an exhibit that carries the
header block rather than the browser’s print furniture.
The download hiding in the overflow menu
Most people never find it, because Gmail’s interface pushes print and forward
and buries the thing you actually want. Open a message, open the overflow menu
on that message — not the one on the conversation — and there is Download
message. What lands is a .eml: the original internet message, headers,
MIME structure, attachments and all.
That single file is a better artifact than anything the print path produces. It is also the thing you should be retaining regardless of what you produce, because it is the native.
Why the print view makes a weak exhibit
Printing renders what the browser is showing, which is several layers away from the message:
- The header presentation is Gmail’s, not the standard produced-email block.
- The page carries browser print furniture — the print date, sometimes the URL — which is noise on an exhibit and occasionally confusing, because the print date sits near the message date.
- Long threads collapse quoted content behind an ellipsis, and the print view can carry that collapse through, so the exhibit is missing text without saying so.
- Attachments are not included at all.
None of that makes a printed Gmail message inadmissible. It makes it a worse exhibit than one you could have produced with the same effort.
Threads, and deciding what an exhibit is
Gmail’s conversation view groups messages that a court will treat as separate communications. Before exporting, decide what the exhibit is:
Each message its own exhibit — download each one, convert, and let every message be its own PDF. This is right when individual messages are being cited against specific allegations.
The thread as a single exhibit — download every message in the thread, convert with the date sort, and combine into one continuous PDF. This is right when the sequence is the point: who knew what, and when.
Either way, download the messages individually first. Combining is a decision you can make at conversion; un-combining is not.
Attachments and the Drive problem
One Gmail-specific wrinkle worth knowing: a file “attached” from Google Drive is not an attachment. It is a link, and the message carries a URL rather than the file. If the recipient’s access was later revoked, or the document was edited after it was sent, the link no longer points at what the recipient saw.
The conversion cannot fix this, because there is nothing in the message to extract. If a Drive link matters to the case, the document behind it needs to be collected separately, along with its revision history.
How to do it in EML Exhibit
-
Open the message and download it
Open the message in Gmail, use the overflow menu at the top right of the message, and choose Download message. The browser saves a .eml file containing the message exactly as it was received.
-
Download each message in the thread you need
The download applies to the individual message, not the whole conversation. For a thread, expand it and download each message you intend to produce, so each becomes its own exhibit.
-
Convert the batch
Drop the .eml files into the converter, choose PDF, set a matter prefix and sort by email date so the thread reads chronologically.
-
Combine if the thread goes in as one exhibit
The combine option produces a single continuous PDF of the whole batch in date order, which is usually the right shape for a thread that is going in as one exhibit and being stamped in one pass.
-
Keep the .eml files
Retain the downloaded originals with the production. They hold the full header chain, which the PDF does not print and which is what an authentication question would reach for.
What is wrong with printing from Gmail?
Nothing, if the message is uncontested and you only need someone to read it. As an exhibit it is weaker: the print view is the browser’s rendering of Gmail’s rendering of the message, it carries browser print furniture rather than the standard header block, and it drops the attachments. It also silently collapses quoted text in long threads, which means the exhibit may be missing content that is visibly missing.
Can I export a whole Gmail label or the entire mailbox?
Google Takeout exports Gmail as .mbox — one large file containing every
message, not a folder of individual ones. That needs splitting before it
can be converted; see MBOX to PDF. For a handful
of messages, per-message download is faster than a Takeout export.
Does the PDF show the full header chain?
No. The rendered PDF prints the header block from the face of the message
— sender, recipients, CC, date, subject. The full transport chain,
including Received hops, Message-ID, and any SPF or DKIM results,
lives in the .eml and in Gmail’s Show Original view. Keep both; the PDF
is the readable exhibit and the .eml is where an authentication
question gets answered. See
email metadata and admissibility.
What about messages a client forwarded to me?
A forward is a new message that contains the old one. Its headers are the forward’s headers, and the original’s transport chain is inside the body rather than on the envelope. It converts fine and reads fine; just be aware that what you are producing is the forward. If the underlying message is contested, collect it from the mailbox it was sent to.
Do Gmail attachments come through?
Yes. Attachments on the downloaded .eml are extracted byte-for-byte as
their original files beside the message PDF, unmodified and
unwatermarked.