Free online converters, and where client email goes
Search for email conversion and the first page of results is free web tools. Most work. Some are genuinely well built. The question worth asking before using one on a matter is narrower than “is it any good” — it is where the file goes, who can read it, and how long it stays there.
We sell a paid tool, so treat this as interested. What follows is the set of questions we think you should ask of any converter, including this one, and our own answers to them.
The questions worth asking
Of any converter, free or paid, ours included:
Where does the conversion happen? In your browser, or on someone’s server? If a tool does not say, assume the file is being uploaded, because browser-based tools almost always advertise it.
How long is the file retained? “Deleted after processing” and “deleted after 24 hours” and nothing at all are three very different answers.
Who is the operator? Some tools identify a company, a jurisdiction and a privacy policy. Some are an anonymous page with advertising.
What else is the file used for? Model training, analytics, quality sampling. This is increasingly the question that matters and increasingly the one left unanswered.
Is there a record? A converter that logs filenames and email addresses is building a record of your matter on someone else’s server.
Where the honest comparison lands
| Typical free web converter | EML Exhibit | |
|---|---|---|
| Cost | Free | Paid, with a free evaluation tier |
| Where files go | Usually uploaded; often unstated | Uploaded, converted, deleted when conversion finishes |
| Retention | Frequently unstated | Output deleted 10 minutes after download; 15 minutes if never downloaded |
| Logging | Unknown | No filenames, recipients or content logged or stored |
| Batch size | Often one file at a time | Up to 100 messages per batch |
| Header block | Varies; often browser print furniture | From, To, CC, Date, Subject above the body |
| Attachments | Frequently dropped or flattened into the PDF | Extracted byte-for-byte, never re-encoded |
| Runs on your own hardware | No | Yes, as a self-hosted Docker image |
Where free tools genuinely win
Cost, obviously, and immediacy — no account, no evaluation, no procurement conversation. For converting a single message that is not confidential, that is a real advantage and we are not going to pretend otherwise.
They also win on breadth. A general-purpose converter handles dozens of
formats. This tool reads .eml and produces PDF or TIFF, and that is the whole
list.
Where the trade turns
Three places, all of which show up at production scale rather than on a single file:
Volume. Converting four hundred messages one at a time through a web form is a day of someone’s time, and the output has inconsistent filenames and pagination that will not stamp cleanly.
Attachments. General converters commonly drop attachments or render them into the body PDF. The first loses evidence; the second changes it, and a re-encoded attachment can no longer be verified by hash. See native production.
The header block. An exhibit needs sender, recipients, date and subject on its face. Print-derived output frequently carries browser furniture instead, which reads as what it is.
The self-hosted answer
If the confidentiality question is the blocking one — and for some firms it correctly is — the version that resolves it entirely is running the converter inside your own network, where discovery material never reaches a third party at all. That is available as a Docker image with no conversion cap and no watermark. It is also, notably, the option that means you do not have to take any of the claims on this page on trust.
Are free converters actually unsafe?
Many are fine. The problem is that “fine” is unverifiable from outside: you cannot tell from the page whether a file was processed in your browser or uploaded, how long it is retained, who has access, or whether it is used for anything else. Some tools state all of this clearly. Most say nothing, and silence is not the same as a good answer.
What is the difference between browser-based and server-side conversion?
A browser-based tool does the work in JavaScript on your machine; the file never leaves it. A server-side tool uploads the file, converts it, and sends back the result. Both are legitimate designs, and only one involves handing client material to a third party. Tools rarely make clear which they are.
Is this really a confidentiality problem or just a technical preference?
Uploading privileged client communications to an unidentified third party is a question about your obligations to the client, not about file formats. What your specific duties require depends on the rules that govern you, and this is not legal advice — but it is worth deciding deliberately rather than by default at 6pm on a filing day.
When is a free converter clearly fine?
When the content is not confidential. Testing a workflow with your own email, converting something already public, or checking output quality before committing a matter — all sensible uses. The line is client material, not the tool.