100% Client-Side Privacy
Adawaty Pro • adawaty-pro.com
52+ Offline Client-Side Converters & Technical Guides
Home / Tools / MSG & MBOX Email Viewer
Read Technical Guides →

Outlook .MSG & Gmail .MBOX Email Viewer & Converter (PDF / EML / CSV)

Browse Gmail Takeout / Thunderbird .mbox archives and binary Microsoft Outlook .msg OLE2 files in a local split-inbox reader with PDF printing, .eml download, and bulk CSV export.

Drag & drop a Gmail/Thunderbird .mbox archive or Outlook .msg file anywhere inside this box

100% Local Browser RAM Processing — Your files never leave your device.

1. Why Local Browser Parsing Matters for Email Archives

Email archives are the single most sensitive dataset on any corporate or personal machine: password reset links, bank wire confirmations, signed NDAs, attorney-client privilege threads, and employee HR records all sit inside Google Takeout .mbox exports and saved Microsoft Outlook .msg files. Uploading an .mbox or .msg file to a cloud viewer exposes that entire inbox to remote disks and server logs.

Adawaty Pro parses both plain-text .mbox mailboxes and binary OLE2 .msg streams 100% locally inside your browser's isolated RAM via FileReader and Uint8Array. Nothing is transmitted over HTTPS, nothing is logged, and closing the tab clears every message buffer immediately—satisfying strict legal e-discovery, GDPR, and corporate InfoSec policies.

2. Deep Dive into MBOX (RFC 4155) & Outlook OLE2 .MSG Internals

Gmail Takeout & Thunderbird .MBOX Architecture

Originating in Unix mail spools and documented in RFC 4155, an .mbox file concatenates complete RFC 5322 email messages sequentially. Each message starts with an unindented separator line matching ^From <envelope-sender> <ctime-date>. Because a human might write the word "From " at the start of a paragraph inside an email body, modern exporters (mboxrd) prepend a greater-than sign (>From ) to body lines during export; our parser reverses that escaping automatically during rendering.

Inside each message, headers (From:, To:, Date:, Subject:, Content-Transfer-Encoding:) are separated from the body by a blank line (\n\n). Non-ASCII headers use RFC 2047 encoded words (=?UTF-8?B?...?= or =?UTF-8?Q?...?=), while message bodies often use quoted-printable or base64 encoding. Attachment filenames appear inside MIME Content-Disposition: attachment; filename="..." directives.

Binary Microsoft Outlook .MSG (OLE2 / CFBF MAPI Streams)

Unlike plain-text .eml or .mbox, desktop Outlook saves individual emails as binary OLE2 Compound File Binary Format (CFBF) containers opening with the 8-byte magic header D0 CF 11 E0 A1 B1 1A E1. Internally, CFBF acts like a mini FAT filesystem storing MAPI properties inside numbered substorage streams—such as __substg1.0_0037001F (Subject in UTF-16LE), __substg1.0_0C1A001F (Sender Name), and __substg1.0_1000001F (Plain-Text Body). Our binary scanner reads UTF-16LE and ASCII MAPI runs directly from the Uint8Array without requiring Outlook or Windows COM libraries.

# Binary Outlook .MSG OLE2 Header (Offset 0x00):
00000000: D0 CF 11 E0 A1 B1 1A E1 00 00 00 00 00 00 00 00  |................|
# MBOX RFC 4155 Message Boundary:
From billing@atlascloud.io Fri Nov 20 09:12:00 2026
Subject: =?UTF-8?B?UTQgSW52b2ljZSAjNDA5MQ==?=

3. Step-by-Step Split-Inbox Reading & Export Workflow

  1. Load Your Mailbox or Email File: Drag a .mbox archive or Outlook .msg file into the dropzone above (or click a Sample button to preview immediately).
  2. Search & Browse in the Split Inbox: Use the left-pane live search bar to filter messages by sender, subject, or body text, then click any thread to read it in the right pane.
  3. Print Individual Emails to PDF: Click Print Email to PDF to generate a clean, navigation-free A4 PDF of the active message via @media print.
  4. Export Standalone .EML or Bulk .CSV: Download the selected message as a portable .eml file, or click Export All to CSV to audit an entire mailbox in Microsoft Excel with UTF-8 BOM encoding.

4. Technical Format Comparison Table

Format Storage Model Emails per File Primary Ecosystem
.MBOXPlain-text RFC 4155 + MIME1 to 100,000+Google Takeout, Thunderbird, Apple Mail
.MSGBinary OLE2 CFBF (MAPI UTF-16LE)Single emailMicrosoft Outlook Desktop (Windows)
.EMLPlain-text RFC 5322 + MIMESingle emailUniversal (all mail clients & archival systems)

5. Troubleshooting Common MBOX & MSG Parsing Issues

  • Splitting Multi-Gigabyte Gmail Takeout .MBOX Archives: Google Takeout's "All Mail" export can easily reach 5–20 GB. In Google Takeout, click All Mail data included and select only the specific Gmail label you need (such as Invoices-2026), keeping the .mbox under 150 MB for instant browser loading.
  • Compressed RTF Bodies Inside Older Outlook .MSG Files: Legacy Exchange emails sometimes store their body inside an LZFu-compressed RTF stream (0x10090102) rather than plain UTF-16LE (0x1000001F). In those cases, our scanner still recovers Subject, sender/recipient addresses, and readable metadata cleanly.
  • Base64 & Quoted-Printable Corruption: Never open and re-save an .mbox file in Windows WordPad or Microsoft Word—re-saving converts line endings and breaks Base64 padding. Always upload the untouched original archive.
  • Arabic & French Characters in Exported CSV: Our CSV exporter prepends the UTF-8 BOM (0xEF 0xBB 0xBF) automatically so international subjects and sender names open crisply in Windows Excel.

Understanding MBOX Variants (mboxo, mboxrd, mboxcl, mboxcl2)

Although every archive shares the .mbox extension, Unix and desktop mail clients historically wrote four subtly different dialects. mboxo replaces any body line starting with From with >From irreversibly; mboxrd (used by modern Thunderbird and Google Takeout) prefixes an extra > onto any line matching ^>*From so decoding cleanly strips exactly one leading >; and mboxcl / mboxcl2 rely on a Content-Length: header byte count to skip over body lines without escaping them. Our boundary splitter anchors on full RFC 4155 envelope lines (^From [^\n]+\n) and unescapes >From cleanly so message paragraphs read exactly as originally composed.

Splitting Oversized Google Takeout .MBOX Archives Locally via CLI

If your full Gmail Takeout archive exceeds 500 MB—which can exhaust browser tab RAM—split it locally into manageable 50 MB chunks using standard Linux/macOS csplit or Python before opening individual chunks in this browser reader:

# Split a large Gmail Takeout .mbox into individual messages on Linux/macOS:
csplit -z -f mail_ -b "%04d.eml" AllMail.mbox '/^From /' '{*}'

Once split, you can inspect individual messages here, print privileged threads straight to clean A4 PDFs for legal counsel, or export structured sender/recipient/subject/body logs to UTF-8 BOM CSV for rapid Excel filtering. Because zero bytes ever leave your local machine, sensitive merger discussions, HR investigations, and client tax records remain strictly under your physical control.

Frequently Asked Questions

How does an .MBOX file store thousands of Gmail Takeout or Thunderbird emails in one file?

MBOX concatenates individual RFC 5322 emails back-to-back inside a single plain-text file, separating each message with an unindented 'From ' boundary line. Any literal line inside an email body starting with 'From ' is escaped as '>From ' (mboxrd convention) so parsers never split a message in half.

Why is a Microsoft Outlook .MSG file unreadable in Notepad unlike .EML or .MBOX?

Outlook .MSG uses Microsoft's binary OLE2 Compound File Binary Format (CFBF, starting with hex bytes D0 CF 11 E0 A1 B1 1A E1), packing MAPI properties (Subject 0x0037, Body 0x1000, Sender 0x0C1A) inside UTF-16LE binary substorage streams.

How does this viewer decode Quoted-Printable (=C3=A9) and RFC 2047 (=?UTF-8?B?...?=) headers?

Our client-side MIME decoder unfolds soft '=\n' line breaks, converts hex '=XX' escapes back to raw bytes via TextDecoder('utf-8'), and decodes Base64/Q-encoded Subject and From headers so French accents and Arabic subjects read cleanly.

Can I open a 4 GB Google Takeout .mbox file directly in a web browser?

Browsers cap single-tab JavaScript ArrayBuffer allocations well below 4 GB (typically 150–500 MB depending on RAM). For multi-gigabyte Gmail Takeout archives, split the .mbox by date or label first—or export a specific Gmail label in Google Takeout—before opening it here.

Can I save a single email from a multi-message .MBOX archive as a standalone .EML file?

Yes. Select any email in the left inbox pane and click 'Download .EML' to save that exact RFC 5322 message for import into Apple Mail, Thunderbird, or Outlook.

How do I export every email's sender, subject, date, and body into Excel for legal e-discovery?

Click 'Export All to CSV' to download a UTF-8 BOM spreadsheet containing Index, Date, From, To, Subject, Attachments, and Body columns ready for Excel filtering.

Are my private Gmail Takeout archives or Outlook .MSG files ever uploaded to a server?

Never. All MBOX splitting, MIME decoding, OLE2 binary scanning, and CSV/EML/PDF generation execute strictly inside local browser RAM.