The short answer
MBOX is a plain-text container format that stores a collection of email messages in a single file. The file extension is .mbox. One .mbox file can hold one message or hundreds of thousands — the format has no upper limit.
If you've just downloaded a Gmail archive via Google Takeout, exported a folder from Apple Mail, or backed up a Thunderbird profile, you've encountered MBOX. It's the lingua franca of email archival.
Where MBOX comes from
MBOX predates most modern file formats. It was introduced in 1975 by the Unix system utility mail, which stored each user's incoming messages as a single concatenated text file in /var/mail/username. That file was called a "mailbox" — hence MBOX.
Because Unix mail was the substrate for most of what became email, MBOX ended up as the de-facto archive format for almost every open-source mail system that followed: sendmail, Postfix, Dovecot, qmail, Mozilla Thunderbird, Apple Mail, and many more. Gmail chose MBOX as the export format for Google Takeout because no other format enjoys the same breadth of client support.
What's actually inside an .mbox file
Plain text. Open a small .mbox file in any text editor and you'll see something like:
From [email protected] Wed Apr 15 09:23:11 2026
Return-Path: <[email protected]>
Delivered-To: [email protected]
Date: Wed, 15 Apr 2026 09:23:11 +0000
From: Alice Smith <[email protected]>
To: Bob Chen <[email protected]>
Subject: Project update
Content-Type: text/plain; charset="UTF-8"
Hi Bob,
Quick status — the migration is on track for Monday.
Alice
From [email protected] Thu Apr 16 14:02:45 2026
Return-Path: <[email protected]>
...The structure breaks down like this:
- From-line delimiter. Every message starts with a line that begins
From(the word "From" followed by a space — no colon). This is how parsers know where one message ends and the next begins. - RFC 5322 headers. After the delimiter comes the standard email header block —
From:,To:,Subject:,Date:,Message-ID:, and so on. These follow the same rules as headers in any individual email. - Empty line. A single blank line separates headers from body.
- Message body. Plain text, HTML, or MIME-encoded multipart content. Attachments are encoded inline using base64 (so a PDF attachment appears as a wall of seemingly random characters).
- Next message. Another
Fromline, and the pattern repeats.
MBOX variants (they exist, but don't worry about them)
There are four recognized MBOX variants — mboxo, mboxrd, mboxcl, and mboxcl2. They differ in two technical areas:
- How the From-line delimiter is escaped inside message bodies. If a user types
From [email protected]as the first word of a new paragraph in their email, that could be mistaken for a message boundary. Different variants escape it differently (mboxrd prepends a>, mboxo ignores the problem). - How Content-Length headers are used. mboxcl and mboxcl2 include a
Content-Lengthheader and use it to locate message boundaries instead of relying on From-line scanning.
In practice, every modern mail tool reads all four variants transparently. You will almost never need to know which variant a given .mbox file uses.
Where you encounter MBOX in 2026
- Gmail via Google Takeout — the most common way consumers run into MBOX. Takeout exports your entire Gmail history as one or more
.mboxfiles. - Apple Mail exports — Mail.app's Mailbox › Export Mailbox produces a bundle containing an
mboxfile. - Thunderbird profile folders — every folder you see in Thunderbird is backed by an
.mboxfile (usually without the extension) inside your profile directory. - Unix mail servers — Postfix, Dovecot, qmail, sendmail, and others either natively store mail as MBOX or export to it for migrations.
- ProtonMail and Fastmail exports — both offer MBOX export for users taking their mail elsewhere.
- Legal discovery productions — when a legal team requests "all emails between X and Y," the producing party often hands over MBOX files because every tool downstream can read them.
MBOX vs EML vs PST — quick comparison
If you have a choice of export format and just want maximum downstream compatibility, pick MBOX. It's the lowest-common-denominator format that every serious email tool can read.
How to open an MBOX file
On Mac
- Convert to PDF with MBOX to PDF for a permanent, searchable archive. Works offline, no email client required. See the full walkthrough.
- Import into Apple Mail via File → Import Mailboxes → Files in mbox format. Good for browsing; not ideal for permanent archival.
- Use Thunderbird + ImportExportTools NG as a free DIY option. More setup friction but zero cost.
On Windows
- Thunderbird with ImportExportTools NG — same workflow as Mac.
- Dedicated converters like Aid4Mail or SysTools handle MBOX on Windows.
On Linux
- mutt, alpine, or claws-mail all read MBOX natively.
- Thunderbird works identically to the Mac/Windows versions.
- Command-line tools like
formailandgrepcan process MBOX files directly because they're plain text.
Why MBOX refuses to die
Despite being 50 years old, MBOX is still the default email archive format in 2026. A few reasons:
- It's human-readable. Open an
.mboxfile in any text editor and you can see the messages. No proprietary reader required. - Universal support. Every serious mail tool reads it. Every serious archive system exports to it.
- No vendor lock-in. MBOX is not owned or controlled by any company. It's a de-facto standard that nobody can take away.
- Works with standard Unix tools. Because it's plain text, you can
grep,awk, andsedyour way through an MBOX file without any specialized software. - Stable for 50 years. An
.mboxfile from 1985 is still readable with 2026 tools. Try opening a 1985 proprietary archive format.
The limitations
MBOX isn't perfect. Things it doesn't do well:
- Metadata beyond headers. Read/unread status, flags, and labels don't cleanly survive an MBOX round-trip. Gmail labels are encoded in a custom
X-Gmail-Labelsheader that only Gmail tools understand. - Concurrent writes. Because everything is one file, you can't have two programs writing to the same MBOX at once without risking corruption. Modern mail servers use Maildir (one file per message) instead.
- Search performance. Finding one email in a 10 GB MBOX requires scanning the whole file. Mail clients build index files alongside to make this fast.
- Attachment bloat. Since attachments are stored inline as base64, a single photo-heavy email might take up more space in the
.mboxthan in the original mailbox's underlying storage.
Frequently asked questions
What is an MBOX file?
A plain-text container that stores many email messages in a single file, separated by From-line delimiters. Used for archives, exports, and server storage since 1975.
What does MBOX stand for?
It's shorthand for "mailbox" — the original Unix concept of a file containing a user's collected mail.
What's inside an MBOX file?
Email messages, one after another. Each includes its full headers (From, To, Subject, Date) and body. Attachments are encoded inline using MIME.
MBOX vs EML — what's the difference?
EML is one email per file. MBOX is many emails per file. Both are plain-text and standards-based.
MBOX vs PST — what's the difference?
PST is Outlook's proprietary binary format; stores email + calendar + contacts. MBOX is an open plain-text format; stores email only. MBOX is universally supported; PST is Outlook-specific.
How do I open an MBOX file?
Fastest path on Mac: MBOX to PDF for document output, or Apple Mail for browsing. On Windows or Linux: Thunderbird. Also see our Gmail Takeout walkthrough.
Are there MBOX variants?
Yes — mboxo, mboxrd, mboxcl, mboxcl2. They differ in small parsing details. Modern tools read all four transparently.
Related reading
- How to convert MBOX to PDF on Mac — step-by-step
- How to open Gmail Takeout MBOX files on Mac
- Best MBOX converter for Mac (2026)