Open MBOX or EML email archives locally, inspect Gmail Takeout labels, search message bodies, extract attachments, and export PDF, HTML, CSV, JSON, source EML, or a checksum record ZIP.
Gmail Takeout mail is commonly delivered inside a downloaded archive; extract the archive first, then choose the resulting MBOX. Individual EML files can be indexed as a batch.
Email archives often arrive in formats made for transfer rather than review. Gmail Takeout can place years of mail in an MBOX file, while downloaded or saved messages commonly use EML. Email Archive Rescue Studio indexes these sources locally, exposes Gmail labels and archive problems, searches headers immediately, performs an optional deep body scan without retaining every decoded body, opens MIME content on demand, inventories attachments, and creates useful review packages without uploading the mailbox.
OpenFileTools scans MBOX separator lines as a byte stream, indexes each message sequentially, parses MIME headers and bounded bodies in browser memory, preserves Gmail X-Gmail-Labels, estimates attachment inventory without retaining attachment bytes, and re-reads only the selected message when you open it, deep-search its body, download an attachment, or create an export. Derived PDF/HTML/CSV/JSON files and optional ZIP packages are generated locally; original source-message bytes can be copied into separate EML files with a SHA-256 manifest.
| Property | Behavior |
|---|---|
| Processing | Browser local; MBOX/EML content is not uploaded |
| MBOX | 1 GB source / 200,000 messages / streamed boundary scan |
| EML | Up to 2,000 files / 500 MB total / 64 MB per message |
| MIME | Multipart, Base64, quoted-printable, RFC 2047 headers, common RFC 2231 filename parameters |
| Outputs | PDF, HTML, CSV, JSON, attachment ZIP, source EML ZIP, record ZIP + SHA-256 manifest |
A large MBOX is scanned as a byte stream for conservative separator lines. OpenFileTools stores message offsets and compact summaries, then re-reads one message slice when a body, attachment, deep search, or export needs it. That keeps the memory model closer to archive indexing than loading a whole mailbox into one string.
Text and attachments can use Base64, quoted-printable, multipart boundaries, encoded header words, character sets, and filename parameters. The email parser follows those declared MIME layers rather than applying the generic recursive Base64 decoder to arbitrary message content.
Masking email addresses, removing BCC, omitting bodies, and converting to PDF/HTML/CSV/JSON apply only to generated review copies. Source EML ZIP and the source-eml folder inside a record package are raw message-byte copies sliced from the selected MBOX/EML inputs.
That scales poorly for large mailboxes. The normal index stores compact header/snippet data; deep body search re-reads and tests messages sequentially only when requested.
When X-Gmail-Labels is present in the exported message header, the viewer indexes and filters those values.
No. The viewer shows decoded text rather than injecting sender-provided HTML into the page.
No. Source EML exports intentionally preserve the selected raw message bytes. Use PDF/HTML/CSV/JSON for derived masked or BCC-removed copies.