What Is an MBOX File?

An MBOX file is a plain-text file that stores many email messages one after another, each beginning with a line that starts with From and a space. That is the whole format. It is what Google Takeout gives you when you export Gmail, and what Thunderbird and Apple Mail use to store mail on disk.

If you have one sitting in your Downloads folder and you just want to read it, skip to opening it on Mac or on Windows. If you want to know what you are actually holding, read on.

Why is it just a text file?

Because it was invented in the early 1970s, when a mailbox was a file a program appended to. MBOX — short for mailbox — was never designed; it accumulated. It got a written specification only decades later, in RFC 4155, which describes it mostly to explain how to exchange one over the internet.

Open one in a text editor and you can read your own email with no software at all. That is worth knowing on its own: whatever happens to the app you use today, the archive is not locked to it. Fifty years of tooling can read this format, and that is precisely why services still export to it.

How does it know where one message ends?

By a convention that sounds too fragile to have survived: a line beginning with From marks the start of a new message.

Which raises the obvious problem — what happens when a message body contains a line that starts that way, in a quoted reply or a code sample? The answers to that question are the variants of the format. mboxo puts a > in front of the offending line. mboxrd does the same but also escapes lines that already begin with >From, which makes the change reversible. mboxcl and mboxcl2 skip the escaping and record each message’s length in a Content-Length header instead.

You almost never need to care which one you have. It matters in exactly one situation: when a tool guesses wrong and splits a message in the middle, leaving you with a mailbox that has more messages in it than you ever received.

What is inside a single message?

Everything, encoded as text. A message has headers at the top — From, To, Subject, Date, plus a pile of technical ones — then a blank line, then the body.

If the message has an HTML version, or a photo attached, those are MIME parts inside the same message, and binary files are encoded in base64 so they survive as text. This is why a mailbox with a few hundred photos in it is enormous: base64 makes a file about a third larger than it was, and all of it is sitting in that one .mbox.

Where does an MBOX file come from?

Four sources cover almost everyone:

• Google Takeout. Export your Gmail and you get MBOX — one huge file, or several if the mailbox is very large. Gmail’s labels survive the trip, stored in a header the export writes.
• Thunderbird. Every folder you see in Thunderbird is an MBOX file inside your profile folder, next to a .msf index file that only Thunderbird needs.
• Apple Mail. Exporting a mailbox produces something confusing: a folder named Inbox.mbox containing a file literally called mbox. The folder is packaging; the file inside is standard MBOX.
• Mail servers. Postfix, Dovecot and their relatives have stored mail this way for decades, and old backups are full of it.

So how do you open one?

Not by double-clicking, usually — neither macOS nor Windows ships with anything registered for that extension, so nothing happens, or Apple Mail tries to import it, which is a different thing entirely. Importing copies every message into Mail’s own storage; opening does not touch the file at all.

What you want is a reader that opens the file where it sits and leaves it alone. That is what Mbox Viewer does on Mac and Windows: it streams through the file instead of loading it into memory, so a 50 GB archive of around half a million messages opens in under five minutes and stays below 600 MB of RAM, and it builds an index so every re-open after that takes under a second. It is strictly read-only. Mailboxes up to 1 GB open without buying anything.

Do you need to convert it first?

Almost certainly not, if what you want is to read it. Conversion only matters when some other program needs the mail in a different shape — a case that is rarer than the search results suggest. The conversion people genuinely need is usually the opposite one: getting an Outlook archive into MBOX, which has its own guide.

The short version

It is a text file full of emails, separated by From lines. It is old, it is simple, and that simplicity is why your mail is still readable decades later. The awkward part was never the format — it is that operating systems don’t know what to do with it, and most readers fall over when the file gets big.

---

More definitions in the glossary, starting with MBOX itself.