How to Export Apple Mail to EML: Step-by-Step with Email Converter

Exporting Apple Mail to a portable, standard format is one of those tasks that sounds simple - "just export, right?" - but turns into a multi-hour debugging session the first time you try it. Apple Mail stores messages internally in a proprietary structure under ~/Library/Mail/, exports them as macOS-specific mbox bundles, and breaks attachments out into a separate Attachments/ folder that other clients don't know how to reattach.

The clean output most users actually want: one .eml file per message, attachments embedded inline, folder structure preserved as a directory tree. This is what other clients (Outlook, Thunderbird, Mozilla, archive systems) can read directly. This guide walks through the export step by step using the Email Converter app for macOS.

Step 1: locate Apple Mail's storage

Apple Mail stores messages at ~/Library/Mail/V10/ on macOS Sonoma+ (V9 on older systems). Inside V10 you'll find a UUID-named folder per account (your IMAP / iCloud / Exchange account each gets its own UUID). Inside each account folder is a directory tree mirroring your mailbox structure: INBOX, Sent Messages, Drafts, plus any custom folders.

Each mailbox is a .mbox bundle - but unlike Unix-standard mbox files, Apple's bundles are actually macOS package directories containing a Messages/ subfolder with one .emlx file per email. The .emlx format is Apple-proprietary: it's an EML message wrapped in a property list header.

To browse: open Finder, press Cmd+Shift+G, paste ~/Library/Mail/V10/, hit Enter. You'll see the account UUIDs. Pick one and drill in.

Important: don't edit anything in here directly. Apple Mail rebuilds its envelope index based on these files, and a stray edit can corrupt the index, forcing a reindex on next launch.

Step 2: run Email Converter and preserve structure

Email Converter is a macOS-native app designed for exactly this workflow. Open the app, choose "From Apple Mail" as the source, and point it at the mbox bundle or folder you want to export.

What it does internally:

1. Reads each .emlx file in the source mbox

2. Strips the Apple property list header to recover the underlying EML body

3. Locates any referenced attachments in Apple Mail's Attachments/ subfolder

4. Re-embeds the attachments inline using MIME multipart encoding

5. Writes the result as a standard .eml file

6. Mirrors the folder structure of the source mbox in the output directory

The result: a clean directory tree where each subfolder represents an Apple Mail mailbox, and each .eml inside is a fully self-contained email readable by any standard email client.

Output options:

• One EML per message (default, recommended) - best for archival and import to other clients
• Single mbox file (Unix-standard, concatenated) - useful if importing to Thunderbird
• PDF per message - useful for legal hold or regulatory archives

Email Converter handles the dates correctly (preserves received-date metadata, which many converters strip), keeps the original Message-ID for deduplication, and embeds inline images so the message renders identically to how it appeared in Apple Mail.

Quick comparison

Common pitfalls and how to avoid them

Across every domain this article touches, the same shape of mistake recurs. Practitioners new to the field overweight the most visible piece of the system — the screenshot, the paywall, the exam question, the headline price — and underweight the underlying constraint that actually determines outcomes.

The five most common failure modes:

1. Optimising for the demo, not the durability. A working demo in a controlled environment proves nothing about reliability under real conditions. In iOS development, an in-app purchase flow that works in the Xcode Simulator says nothing about how it behaves in App Store sandbox with network latency and Ask to Buy approvals. In an exam, a 100% score on an untimed quiz tells you nothing about whether you can do 49/50 in 45 minutes with no second guesses. Build for the hardest realistic case from the start.
2. Skipping the first-principles documentation. Every system has a canonical specification. App Review Guidelines for iOS, the official EU regulations for tax deductibility, the CITB question bank for CSCS, the OMIE market rules for Spanish electricity. Reading them takes a few hours but saves weeks of wrong-direction work. Secondary sources (blogs, tutorials, this article included) are useful as orientation but never authoritative.
3. Ignoring the rate limit. Every external system has rate limits — explicit (APNs silent push throttling, RevenueCat API quotas, exam retake fees) or implicit (App Review patience, customer attention spans, your own working memory). Plan around them. A workflow that requires more rate-limited operations than the system allows will fail in production, not on day one but during the first stress event.
4. Underweighting localisation and regional variation. What is true for Germany is not always true for Italy. What is true for English-speaking users is not always true for Japanese ones. What is true for the UK CSCS test is not always true for the Irish equivalent. Always check the local rule before applying a general one.
5. Treating the documentation as static. Apple updates App Review Guidelines. The Bundeslaender change Schonzeiten. OMIE adjusts market clearing algorithms. Set up a periodic review (quarterly is enough for most things) and re-read the canonical sources. Workflows that worked perfectly a year ago can be silently broken today.

None of these are dramatic. The dramatic mistakes (catastrophic bugs, audit findings, exam failures) are the visible tip of a longer-running iceberg of small misses. Catching the small misses is what separates routine outcomes from problematic ones.

Key takeaways

• Locate source — Find mbox. Browse via Cmd+Shift+G.
• Run Converter — Pick source folder. App handles emlx->eml.
• Verify output — Open one EML. Open in Mail or Thunderbird.
• Archive output — Compress to zip. Store on external drive or cloud.

The pattern that runs through every section above: start with the constraint, not the wishlist. In an exam, the constraint is the question bank and the pass mark. In an electricity market, it is the auction clearing rule. In a tax workflow, it is the receipt-retention requirement. In a code architecture, it is the platform's design decision (StoreKit's transaction lifecycle, App Review's guideline, APNs's authentication model). Get the constraint right and the rest follows.

The opposite failure mode — designing for an aesthetic ideal, then trying to retro-fit the constraint — is the most common cause of wasted work in every domain covered here. A beautiful paywall that hangs in sandbox is rejected at App Review. A polished freelancer expense report that lacks receipts is disallowed by the tax office. A study plan that ignores the actual question distribution leaves the candidate stuck below the pass mark.

The practical recommendation: read the official rules of whatever system you are operating in, extract the binding constraints, and treat them as inputs to the design — not afterthoughts. Every section of this article is the application of that principle to a specific domain.

FAQ

Will I lose attachments during export?
No. Email Converter detects attachments in Apple Mail's separate Attachments folder and re-embeds them inline in the output EML files. The result is fully self-contained.

Can I export only one folder, not my whole mailbox?
Yes. Point Email Converter at a specific mbox bundle (e.g. just Sent Messages, or a single project folder) rather than the whole account directory.

Does the export preserve message dates?
Yes. The Date header from the original message is preserved, and the file timestamps match the message receive date so chronological sorting works in any client.

Can I import the resulting EML files into Outlook?
Yes. Outlook reads EML natively - drag and drop into a folder, or use File - Import. Behaviour varies slightly between Outlook for Mac and Windows.

Further reading and references

The references below cover the official sources for the rules cited in this article. Where applicable, they include the canonical documentation, regulatory text, or vendor-provided guides. For each one, prefer the official source over secondary commentary — secondary sources go stale fast and frequently misquote the binding rule.

• Official documentation of the system in question (linked from each app or service's own help centre).
• Apple Developer Documentation for any iOS/macOS reference — the WWDC session videos and the corresponding Human Interface Guidelines pages are the authoritative source.
• For EU regulatory questions (taxation, data protection, energy market structure), consult the relevant national authority — most publish their guidance in English.
• For Spain and Italy energy market data, OMIE and GME both publish full historical price series in CSV format from their public websites — no API key required.
• For UK CSCS prep, the CITB publishes the official question bank book each year — buy a current copy if you want the authoritative source.

If you find a contradiction between this article and an official source, the official source wins. Article rules of thumb are summaries — they have edge cases, exceptions, and regional variations that the source documents specify exactly.