Printing from Outlook vs converting
Printing an email to PDF is free, requires nothing new, and works. For a single message going into a letter it is the right tool and there is no argument to make against it.
This page is about where that stops being true, which is earlier than most people expect — and about four failures that are specific rather than general, because “it’s unprofessional” is not a reason and these are.
The four specific failures
1. Attachments are not in the output. Printing renders the message body. The attachment — very often the actual evidence, the letter or the spreadsheet the case turns on — is not included at all. It is not degraded or reduced; it is absent, and the resulting PDF looks complete.
2. The header block is the client’s, not the standard one. What Outlook
prints at the top of a message varies by version, by print style and by whether
you printed from the reading pane or an open message. A produced email is
expected to carry From, To, CC, Date and Subject in a consistent
block. A set assembled by three people over two weeks carries three layouts.
3. Filenames come from the subject line. Which means duplicates when a
thread has twenty replies all named RE: Q1 forecast, truncation on long
subjects, and characters the filesystem rewrites. Collating those against a
document store afterwards is manual work that scales linearly with the set.
4. Pagination is inconsistent, and stamping exposes it. Page counts depend on the client, the print style and the paper size. Inconsistent page counts are tolerable right up until the set is Bates numbered, at which point the numbers in the production do not reconcile against the log — see how to Bates stamp emails.
Side by side
| Print to PDF from Outlook | Convert from .eml |
|
|---|---|---|
| Cost | Free | Paid, free evaluation tier |
| Setup | None | Export messages as .eml first |
| Volume | One message at a time | Up to 100 per batch |
| Header block | Varies by client and print style | Consistent From/To/CC/Date/Subject |
| Attachments | Not included | Extracted byte-for-byte as originals |
| Filenames | From the subject line | Matter prefix, sequential |
| Ordering | Whatever you printed in | Filename or email date |
| Combined document | Manual merge afterwards | One continuous PDF, in sort order |
| Pagination consistency | Varies | Single pipeline across the set |
Where printing genuinely wins
One message. Attaching a single email to a letter or a declaration. The export-and-convert round trip is more work than pressing print, and the result is the same.
Nothing is contested. Where both sides know the correspondence is real and nobody is going to question it, the additional information a native carries has no job to do.
No attachments. If the message is the evidence and it carried nothing, the largest failure above does not apply.
You need it in thirty seconds. Sometimes that is the whole requirement, and it is a legitimate one.
The threshold
Roughly, the point where printing stops being reasonable is where any of these becomes true:
- More than about twenty messages.
- Any attachment matters.
- The set is going to be Bates stamped as a production rather than attached as individual exhibits.
- More than one person is preparing it.
- The messages might be contested, so the natives need retaining anyway.
That last one is worth a note on its own. If you are going to retain the .eml
files regardless — and you should — then you already have the input to a
conversion, and the marginal cost of converting properly rather than printing
is close to zero. See
how to export email as EML.
Is a printed email inadmissible?
No, and it is worth being clear about that. Printed emails go into evidence routinely and most are never challenged. The argument here is not about admissibility — it is that a printout carries less information, and by the time you discover you needed that information the native may be gone. See email metadata and admissibility.
What about the print-to-PDF built into Windows and macOS?
Same thing. The virtual printer is fine; the limitation is what the mail client hands it. The client decides the header layout, the pagination and whether quoted content is expanded, and none of those are print settings.
Can I batch print from Outlook?
Outlook can print multiple selected messages, but to one continuous print job rather than to one file per message with usable filenames. For a production you need per-message files that can be named, ordered and stamped individually.
Is this really worth paying for?
For under about twenty messages, probably not — print them. The calculation changes with volume, with whether attachments matter, and with whether the set is going to be Bates stamped, because that is where inconsistent pagination becomes an actual problem rather than an aesthetic one.