What Format Does Google Takeout Use for Gmail Exports?
When you request a data download of your Gmail account through Google Takeout, Google compresses your emails into one or more .zip or .tgz archives. Inside the extracted folder hierarchy, your mail is stored in an uncompressed plain-text format:
Takeout/Mail/All mail Including Spam and Trash.mbox
Under RFC 4155, an MBOX file concatenates all email messages sequentially, separated by envelope delimiter lines beginning with From (commonly known as the From_ envelope separator). Each message body following the envelope separator follows standard RFC 5322 (formerly RFC 822) formatting:
From MAILER-DAEMON Fri Oct 10 14:22:00 2026
From: "Alex Johnson" <alex@example.com>
To: "Sarah Miller" <sarah@example.com>
Date: Fri, 10 Oct 2026 14:21:45 +0000
Subject: Project Migration Notes
Content-Type: text/plain; charset=utf-8Attached are the migration checkpoints for the review meeting. ```
Step 1: Extract the Outer ZIP Archive on Your Computer
Before opening your mail in any MBOX reader, extract the Google Takeout ZIP container:
- On Windows: Right-click the downloaded takeout-*.zip file and select Extract All....
- On macOS: Double-click the takeout-*.zip file to expand it with Archive Utility.
Locate the .mbox file inside the Takeout/Mail/ subfolder.
Step 2: Load the .mbox File in Browser Memory
Rather than configuring desktop email clients like Mozilla Thunderbird or uploading confidential personal correspondence to unknown third-party cloud converters:
1. Open the Online MBOX Workspace.
2. Drag and drop your extracted .mbox file into the window.
3. The client-side streaming parser reads the file using chunked byte slicing in asynchronous frames, indexing message headers and attachments directly in your device RAM without transmitting any bytes over the network.
Important Considerations for Giant Gmail Archives
Gmail archives often measure from several hundred megabytes to tens of gigabytes. While 64-bit desktop web browsers (Chrome, Edge, Firefox, Safari) can read large files via streaming byte slices, available physical system RAM and per-tab JavaScript memory limits (typically 2 GB to 4 GB) dictate how many active message structures can be kept simultaneously in memory. For monolithic enterprise archives or automated multi-format conversions, dedicated desktop migration software is recommended.