What is an OLM file, and why almost nothing opens it

An OLM file is an archive that Outlook for Mac writes when somebody exports a mailbox. Underneath the extension it is a ZIP container holding XML files and encoded attachments. It is neither a live mailbox nor a database. No version of Outlook for Windows will import it.

Most people meet this format at an awkward moment. A Mac is being replaced. A mailbox has to move. Or a file has turned up that nothing will open. The quickest way through is to understand what the file is for, because almost every problem with it comes from expecting it to be something it is not.

What is actually inside an OLM file

Rename a copy in Finder so it ends .zip and macOS opens it like any other archive. That single fact tells you most of what you need to know about the format.

Inside sit folders of XML. Each message is a record rather than a file you can double click. Header fields, body and parent folder are written out as markup and addresses appear as their own elements rather than as a header line. Attachments travel alongside as base64 data, referenced from the message that owned them. A converter has to rebuild proper MIME around all of it before another mail application will accept the result.

The top level is unremarkable once you see it.

• Ziparchive.olmRename a copy to .zip and this is what opens
• FileCategories.xmlColour categories applied to items
• FolderAccountsOne folder per account the export covered
• FolderLocalThe mail, in the folder tree it came from
• Xmlmessage recordsHeaders, body and addresses as elements, not as a mail file
• Dataattachment dataEncoded. Referenced by the message that owned it

Two consequences follow. They explain almost every complaint about the format.

• It is readable in principle and useless in practice. XML is text, so a determined person can pull one message out by hand. Nobody is doing that across a mailbox of forty thousand.
• The parts depend on each other. A message record points at its attachment data and at its place in the folder tree. Extract pieces on their own and you get orphans. That is why unpacking an archive by hand and repacking it tends to break it.

A bag of documents with a manifest, in other words. That is a reasonable way to build an archive and a poor way to run a mailbox, which is exactly how the format is used.

An OLM file is an archive, not live storage

Search for this format and you are told repeatedly that OLM is the master repository for Outlook for Mac local data. That claim appears on several vendor pages and it is wrong.

Outlook for Mac keeps your working mailbox in a profile, which it maintains continuously as mail arrives. Inside that profile the messages sit as .olk15 items, a running store the application writes to as mail lands. That is the live copy. An OLM exists only when a person chooses to export one. No OLM is created on install and none is created on a schedule. Deleting one takes nothing away from the running application.

The practical test is simple. If you have never used Export, you have no OLM file anywhere on the machine.

The format arrived with Outlook 2011 for Mac, the release that replaced Microsoft Entourage. It has been the export format ever since. It has never been the storage format.

Why the distinction matters. People go looking for an OLM to back up their mail and find nothing, then assume something is broken. Others copy an OLM onto a new Mac and expect Outlook to pick it up on launch. Neither works, because an archive is a snapshot somebody took, not the thing the application reads.

What an OLM file carries and what it leaves behind

Microsoft is specific about the item types. An archive holds email messages, contacts, calendar items, tasks and notes, along with the folder structure they sat in.

Microsoft describes a profile as the whole set of data Outlook holds. That list includes accounts, rules and signatures. The archive format covers the first half of it. Mail that lives on a Microsoft 365 server is a separate matter again, because that copy is not on the Mac to export in the first place. Restore an OLM and your mail comes back while your setup does not. That surprises anyone who treated the export as a full backup.

Cloud attachments are not really attachments. A file physically attached to a message is embedded in the archive. A OneDrive or SharePoint link is not, because there was never a file on the Mac to embed. The message keeps the link and the link keeps pointing at a server, so an archive of link heavy mail is far less self contained than its size suggests.

OLM vs PST vs OST: what each file is for

Three Outlook file extensions get confused with each other. The difference is not really about platform. It is about what each file is for.

The row that matters is Role. A PST can be somebody's working mailbox for years. Reading one on a Mac takes a PST converter for Mac. An OST cannot leave the account that made it. An OLM is neither, which is why treating it like a PST leads people wrong.

Why Outlook for Windows will not open an OLM file

This is the question the format is best known for. The answer is duller than people expect. Windows Outlook reads PST and OST. There is no OLM importer in the product and Microsoft ships no conversion utility for it.

Notice which way the door swings.

Windows Outlook
PST file → Outlook for Mac Works. Microsoft documents the import steps.

Outlook for Mac
OLM file ✗ Windows Outlook No importer and no first party conversion utility.

Either the mail goes up to a server and comes back down on the other side or the archive gets converted into something Windows Outlook accepts.

Why the new Outlook for Mac will not import an OLM either

The newer Outlook for Mac has no OLM import at all. Microsoft's documentation on moving items in and out covers the older client only. People find this out after switching, having already made the archive they were told to make.

So an archive made today is readable by a client that is being retired and by nothing else Microsoft makes. That is worth knowing before you decide an OLM export is your backup. The October 2026 deadline is what puts a clock on it.

The 2GB OLM file size limit that is not a limit

Somewhere along the way, two gigabytes became the accepted ceiling for an OLM. It is quoted constantly. No Microsoft documentation states it.

The figure looks inherited from the older Outlook for Mac identity, which did struggle at that size. It has been copied forward ever since as though it were a property of the archive format. Large archives do fail more, because a single long write has more chances to be interrupted. That is a reason to verify a big export, not a ceiling to design around.

Treat the number as folklore. Verify the archive instead.

How to open an OLM file without Outlook

Four routes exist and they are not equivalent.

• Import it back into legacy Outlook for Mac. The official route. Everything lands under On My Computer rather than back in the account it came from, so it arrives as local mail. It needs the legacy client, which limits how long it stays available.
• Unpack the ZIP by hand. Free and fine for finding one message. Hopeless for a mailbox and easy to corrupt.
• Use an open source converter. Free tools exist that read the archive with a zip library and write each message out as EML or HTML. Worth knowing about. They tend to cover mail and skip contacts, calendars and tasks. Support depends on whoever is still maintaining them.
• Use a maintained converter. Parses the XML, rebuilds the messages and writes them out as something ordinary, including the item types the free tools leave behind.

One limit applies to every route. Microsoft states that iCloud and Google calendars and contacts cannot be imported into Outlook for Mac at all, so anything that arrived from those services is outside this picture entirely.

The last two are the only routes that end with the contents in a format with a future. Conversion lifts the contents out of a container only one retiring application understands. Messages land as MBOX, PST, EML, EMLX, MSG or PDF. Contacts leave as CSV or vCard. Calendars leave as ICS. An OLM converter for Mac handles the parsing locally, without Outlook present anywhere.

Whichever route you take, check the result rather than the file size. A truncated archive opens perfectly well, lists its folders and simply comes up short inside them.