MBOX Converter: When You Actually Need One

You need a converter when another program has to receive your mail and cannot read MBOX — moving an archive into Outlook, say. You do not need one to read, search, print or share your own messages. That distinction is worth a few minutes, because conversion is not free: it produces a second copy of everything you own.

The question behind the search

Almost everyone typing “MBOX converter” is holding a Google Takeout export and wants to see what is in it. Converting is the first idea that comes to mind, because the file won’t open and converting sounds like the thing that makes files open.

But conversion does not make a file readable. It makes a different file, in a format some other program prefers, and you still need something to read it in. If the goal is to look at your own email, you can skip the whole step: a reader opens the mailbox where it sits, leaves it untouched, and gets you to the same place without a second 40 GB copy on your disk.

Three good reasons to convert anyway:

1. Another program is the destination. Someone needs the mail in Outlook, or in a system that ingests one specific format.
2. You need individual messages, not a mailbox. A handful of emails to attach to a ticket, a claim, or a filing.
3. You need the data, not the mail. Dates, senders and subjects in a spreadsheet, for an audit or a count.

Cases 2 and 3 are not really conversion; they are export, and any decent reader does them without transforming your archive at all.

What can you turn an MBOX into?

Target	What it’s for	Do you need a converter?
EML	One file per message, opens anywhere, easy to attach	No — export from a reader
PDF	Filing, printing, sending something that will look the same in ten years	No — export or print
HTML	A self-contained copy with images embedded	No — export
CSV	Dates, senders, subjects in a spreadsheet	No — export
A smaller MBOX	Handing over just the messages in scope	No — export a selection
PST	Getting the archive into Outlook	Yes — a real conversion
Maildir	Feeding a mail server or a different client	Yes

Everything in the “no” half of that table, Mbox Viewer does directly: EML, PDF, HTML, CSV, plain text, attachments in bulk, and a new MBOX file containing only the messages you picked. One message at a time is free; batches are Pro.

Going the other way: PST and OLM

The conversion people genuinely need most often is the opposite of what they searched for: they have an Outlook archive — a .pst on Windows, a .olm from Outlook for Mac — and they want it in MBOX, where it can be read without Outlook.

That one is a real conversion and needs a real tool. We keep a step-by-step guide for PST and OLM, because it is the one route we get asked about constantly and the one where the wrong tool can quietly lose your attachments.

What conversion costs you

Worth knowing before you start, whichever direction you go:

• A second copy of everything. Two archives to store, back up and keep track of, and two answers when someone asks what you have.
• Things that don’t survive the trip. Gmail labels are a header in an MBOX file, and most target formats have nowhere to put them. Threading gets rebuilt from headers, sometimes differently. Timestamps can shift with time zones.
• A tool you have to trust with all of it. Many converters are web services: you upload every email you have ever received to a stranger’s server to change a file extension. For a personal archive that is a poor trade; for anything covered by a records request or a legal hold, it is not a trade you are allowed to make.

Whatever you use, keep the original. A conversion you can repeat is an inconvenience; a conversion you cannot is a data loss you haven’t noticed yet.

The rule of thumb

Convert when a destination demands it. Export when a person asks for something. Read when you just want to see your mail — that one needs neither.