Convert OLM to MBOX — without Outlook for Mac
Move mail out of an Outlook for Mac .olm export and into the open .mbox format that Thunderbird, Apple Mail, and Gmail imports understand. The conversion runs on your own machine — the archive is never uploaded.
How do I convert an OLM file to MBOX for Thunderbird or Apple Mail?
Unpack and reassemble — locally, if the mailbox matters to you. Inside an .olm, every message lives as a separate record of structured fields, so conversion means rewriting each record into a normal RFC 5322 message and stitching the results into mailbox files the destination client accepts; Mailward performs the whole rewrite in your browser, and the export never touches a server. Judge any OLM converter on two specifics. Dates: Outlook for Mac stamps times in UTC with the zone marker omitted, and a converter that fails to pin them back to UTC quietly moves every date in the output — ours pins them. Headers: the records an OLM keeps expose sender, subject, times, bodies, and attachment references, but not the original routing block, so converted messages carry rebuilt headers rather than an authentic Received chain. That is a limit of the source format no converter can honestly escape — keep the original .olm alongside the conversion if provenance ever matters.
Drop the .olm file — Mailward lists every folder, nothing is uploaded.
Convert one folder to MBOX free, or the whole archive with a license.
Download the .mbox file, generated entirely in your browser.
Import it into Thunderbird, Apple Mail, or a Gmail migration tool.
Convert OLM to MBOX — without Outlook for Mac
Use this converter when you are leaving Outlook for Mac — or inheriting an .olm from someone who did — and the mail needs to live in a client that cannot read OLM, which is nearly all of them. The usual options are a paid desktop converter or a website that asks you to upload the whole mailbox; Mailward is the third option.
It unpacks the OLM in a Web Worker in your browser and writes standard MBOX, with attachments re-embedded in each message as MIME parts. Converting a single folder is free; whole-archive export is the one-time paid step.
Attachments can also be saved per message free, or pulled into a single ZIP with Pro. Convert only mailboxes you have the right to access.
What survives the OLM → MBOX conversion, and what does not
An OLM stores each message as an XML document inside a ZIP, with OPF-prefixed elements for the subject, addresses, and body. MBOX wants something quite different: a stream of RFC 5322 messages separated by From_ lines. So the conversion is a genuine rewrite — each message's fields are read out of XML and reassembled into a standards-compliant message, then framed with an mboxrd From_ line and ">From " escaping so the mailbox does not split in the wrong place on import.
Two details are worth stating before you convert rather than after. Timestamps in an OLM are UTC written without a zone suffix, so they have to be interpreted as UTC explicitly or every date in the output shifts — we handle that, but it is the single most common way OLM conversions go quietly wrong.
The second is attachments. Each message is rebuilt as complete MIME — plain text and HTML bodies as alternatives when both exist, attachments re-embedded as base64 parts — so what lands in Thunderbird or Apple Mail carries its files with it. The separate per-message save and the whole-archive attachment ZIP remain available for when you want the files without the mail around them.
Inline images are the detail most converters fumble. An HTML body in an OLM references its embedded images by cid: URI, and each attachment record carries a matching Content-ID attribute alongside its file name and MIME type. Mailward re-embeds every attachment with that Content-ID intact and marks cid-referenced images as inline parts, so a pasted screenshot or signature logo still renders inside the message after import instead of degrading into a detached file. Only images get the inline treatment — any other part keeps a visible attachment disposition, because an inline text part would be swallowed into the body on display.
As for what does not survive: recipient headers in the output are rebuilt from OLM's structured name-and-address attributes, with display names quoted per RFC 5322 where they contain commas — so a contact stored as "Doe, John" arrives as one addressee, not two. A message that exists only as HTML gets its text/plain alternative derived by stripping that HTML, since Outlook for Mac reliably writes the HTML side but not always a plain one. Mailbox-level state — read or unread, flags, Outlook categories — is not carried across, because MBOX frames bare RFC 5322 messages and has no standard field for any of it. And since an OLM keeps no Received chain, the conversion cannot restore one; keep the original .olm alongside the output if provenance ever matters.
- Input
- OLM — ZIP of per-message XML (OPFMessageCopy* elements)
- Output
- mboxrd MBOX, one file per folder
- Timestamps
- OLM's suffix-less UTC read as UTC — dates do not shift
- Attachments in the MBOX
- Re-embedded as base64 MIME parts (separate ZIP extraction with Pro)
- Inline images
- cid: references keep resolving — Content-ID preserved on re-embedded parts
- Recipients
- Rebuilt from structured XML name/address attributes, RFC 5322-quoted
- Not carried
- Read state, flags, categories — MBOX has no standard field for them
- Imports into
- Thunderbird, Apple Mail, Gmail/Workspace migration
Comparing formats? PST, OST, OLM, MBOX & EML explained — what each one is internally, and what is lost converting between them.
Converting this file
Q. Which apps can open the MBOX output?
Thunderbird (via ImportExportTools NG), Apple Mail (File → Import Mailboxes), and most Gmail or Google Workspace migration tools import MBOX directly.
Q. Are attachments included?
Yes — each message is written as complete MIME with its attachments re-embedded as base64 parts, so they arrive in Thunderbird with the mail. You can also save attachments from any message for free, or extract every attachment in the archive to a ZIP with Pro.
Q. Is the conversion free?
Converting a single folder is free. Exporting the whole archive, several folders, or search results is part of the one-time Pro license — no subscription.
Q. Does my mailbox get uploaded?
No. The OLM is unpacked and the MBOX is generated in a Web Worker on your own machine. You can go offline after the page loads and the conversion still works.
Q. Do inline images survive the conversion?
Yes. OLM stores each attachment's Content-ID alongside its file name and MIME type, and Mailward re-embeds attachments with that Content-ID intact, marking cid-referenced images as inline MIME parts. An embedded screenshot or signature image renders inside the message after a Thunderbird or Apple Mail import rather than arriving as a detached file.
Free to open, read, search, and export one message. Batch conversion is a one-time $19 licence — no subscription, no recurring fees.
Other formats & archives
Same local-first engine, every common mail format.