Convert Outlook email to PDF for discovery
The legal world runs on Outlook, which makes it the most common starting
point for an email production and the most annoying one. Outlook’s desktop
client saves messages in Microsoft’s own .msg format, and almost nothing
outside Outlook reads it.
EML Exhibit converts .eml files, not .msg. That sounds like a
limitation until you find the export path — Outlook on the web downloads
messages as .eml directly, from the same mailbox your desktop client is
connected to, and that is usually the fastest route to a batch you can
convert.
Two Outlooks, two formats
The single fact that unlocks this workflow: the classic Outlook desktop client and Outlook on the web export different formats from the same mailbox.
| Client | Message export | Usable here |
|---|---|---|
| Classic Outlook for Windows | .msg |
Not directly |
| New Outlook for Windows | .eml download |
Yes |
| Outlook on the web / Outlook.com | .eml download |
Yes |
| Apple Mail | .eml via Save As, Raw Message Source |
Yes |
If your firm still runs classic Outlook — many do, deliberately — you do not need to migrate anything. Open the same mailbox in a browser for the length of the export and download the messages there. The mail is identical; only the client differs.
Why not just print to PDF from Outlook
You can, and for one message it is fine. For a production it fails in ways that surface late:
- One at a time. There is no batch print-to-PDF that produces one file per message with usable filenames.
- The header block varies. What Outlook prints at the top of a message depends on the client, the print style and the version. A production set with three different header layouts looks careless because it is.
- Filenames come from the subject line. Which means duplicates, truncation, and characters the filesystem rewrites.
- Attachments are lost. Printing renders the body. The attachment — often the actual evidence — is not in the output at all.
Converting from .eml fixes all four at once, because the conversion is
driven by the file rather than by a print dialog.
Collecting defensibly
Downloading messages by hand from a mailbox is a legitimate collection method
for a small matter, and a fragile one for a large or contested matter. The
things that make it defensible are unglamorous: record who did the collection
and when, collect complete threads rather than individual messages, do not
filter by reading the messages first, and keep the .eml originals unmodified.
If the matter is large enough that a custodian’s whole mailbox is in scope, or if collection method is likely to be challenged, that is the point to bring in a collection tool or a vendor rather than a browser and a download folder. Chain of custody covers what a record of handling needs to contain.
How to do it in EML Exhibit
-
Open the mailbox in Outlook on the web
Sign in to the same Microsoft 365 or Outlook.com mailbox in a browser. This is the same mail, not a copy or an export — you are just using the client that can hand you .eml.
-
Download the messages you need
Open a message, use the overflow menu on the message toolbar, and choose Download. The browser saves an .eml file. Menu wording moves between builds; look for Download or Save as on the individual message rather than on the reading pane.
-
Collect the files into one folder
Put every downloaded .eml for the matter in a single folder. This is also the moment to note where they came from and who pulled them, which is what a chain of custody record is made of.
-
Convert the folder in one batch
Drop up to 100 .eml files into the converter, choose PDF, set a matter prefix and sort by email date. Each message becomes a paginated PDF with the header block above the body.
-
Keep the .eml files alongside the PDFs
The downloaded .eml is the native. Retain it with the production set — the PDF is the readable exhibit, but the .eml carries the full transport headers.
Why does Outlook save .msg when I drag a message to a folder?
Because .msg is Microsoft’s native serialisation for an Outlook item,
and it can carry things the open .eml format cannot — Exchange-specific
properties, calendar and task items, voting buttons. It is a reasonable
format and a closed one. See converting .msg files
for what to do when .eml is not available to you.
Can I export a whole Outlook folder at once?
Outlook’s own export produces a .pst archive, not a folder of
individual messages — see PST to PDF. For a
per-message export, downloading from Outlook on the web is the practical
route. For a large custodian collection, this is the point at which a
collection tool or a vendor earns its fee.
What about the new Outlook for Windows?
The new Outlook client is built on the same web codebase, so the download
behaviour follows Outlook on the web rather than the classic desktop
client. Classic Outlook, still widely deployed in firms, is the one that
gives you .msg.
Will the PDF look like what I see in Outlook?
Close, but it is a render of the message rather than a screenshot of
Outlook. The header block is printed in the standard produced-email form
— From, To, CC, Date, Subject — rather than in Outlook’s
chrome, and the body renders with inline images in place. That is
generally what you want on an exhibit: the message, not the mail client.
Does it handle meeting invitations and calendar items?
Only insofar as they exist as .eml messages. A calendar item saved from
Outlook as an Outlook item is not an email, and the .eml export of an
invitation renders as the message it was sent as rather than as a
calendar entry.