EML vs MSG, One Holds What Travelled And One Holds More
The format that keeps more is also the one that fewer things can read. That trade is the whole decision.
An EML file carries the .eml extension and an MSG file the .msg. Both hold one message. What separates them is what they are a copy of. An EML records a message as it crossed the network. An MSG records a message as Outlook holds it, which includes a great deal that never crossed anything.
That difference decides everything else, including the one thing worth knowing before you save a folder of either. Moving between them is not symmetrical. Everything in an EML file fits inside an MSG file. Not everything in an MSG file has anywhere to go in an EML file.
EML Files And MSG Files Copy Two Different Things
A message that reaches you crossed a network to get there. Only things that could survive that journey are in it. Headers, a body, attachments turned into characters. Nothing else could have travelled.
Outlook is not restricted that way. It keeps its own properties on every message, whether or not that message ever moved.
Present in Both
- The headers, sender and recipients
- The body, plain and formatted
- Every attachment
- The date the message was sent
Only in an MSG file
- Flags, categories and reminders
- Voting buttons and their responses
- Which Outlook folder it sat in
- Read state, plus who else has seen it
This is why the comparison is not about which is better. One is a faithful record of a message. The other keeps that same record and adds everything Outlook thought about it. Both are complete, at different jobs.
The EML to MSG Asymmetry Nobody Mentions
Because one is a superset of the other, the two directions behave nothing alike.
EML into MSG
Nothing to loseheaders kept
body kept
attachments kept
Outlook bits none to
begin with
Every field has somewhere to go, because the destination holds more than the source ever did.
MSG into EML
Some of it has nowhere to goheaders kept
body kept
attachments kept
flags no field
categories no field
voting no field
The message survives whole. What goes is the layer Outlook added, since no destination field exists to hold it.
Categories are the ones people miss. An archive where somebody colour coded three thousand messages by client loses every one of those labels. The loss shows up months later, when a search that used to work returns nothing. Exporting the category list separately costs a minute and is almost never done.
What an EML File And an MSG File Cost to Open
The second difference matters more day to day. It also runs the opposite way.
| EML | MSG | |
|---|---|---|
| Built on | A published standard, RFC 5322 | A Microsoft container format |
| Opens in Thunderbird or Apple Mail | Yes | No |
| Opens in a text editor | Readable, headers and all | Binary noise |
| Opens in Outlook | Yes | Yes |
| Readable in twenty years | Almost certainly | Depends on Microsoft |
| Needs software written for it | Only outside a mail client | Everywhere outside Outlook |
So the format that holds more is also the format that fewer things can read. That trade is the whole decision. It is not close once you know who opens the file next.
A saved MSG reaching somebody on a Mac is the common failure. They receive a file their mail program cannot open and cannot identify, from a colleague who saw nothing wrong at their end. The sender had Outlook. That was the only reason it looked fine.
How an EML File And an MSG File Store the Same Attachment
Both keep attachments. Neither keeps them the same way, which explains their sizes.
In an EML file
Content-Type: application/pdf
Content-Transfer-Encoding: base64
JVBERi0xLjQKJcfsj6IKNSAwIG9iago...
the file as characters, a third larger
In an MSG file
a stream inside the compound file
the file as bytes, unchanged
named by a property rather than a header
An EML has to encode everything into characters because it was built to cross a channel that only carries text. An MSG never faced that constraint, so it keeps the bytes as they are.
Neither format is reliably smaller. The encoding costs an EML file about a third on its attachments. The container structure costs an MSG file on overhead and on the properties it carries. Which wins depends on the message rather than on the format, so file size tells you nothing useful about which one you are holding.
Read next Why Email Attachments Are Encoded And What It Costs Why one of these two pays a third extra for every file it carries.Which to Save, Decided by Who Opens It
- For yourself, staying in Outlook. MSG. It keeps everything, opens instantly and loses nothing, because the thing that reads it is the thing that wrote it.
- For a colleague, on a machine you cannot see. EML. The chance they have Outlook is not worth the chance they do not.
- For an archive nobody will touch for years. EML. A published standard outlives a vendor container. The reader in ten years is a person you will never meet.
- For a legal or compliance request. Ask them. Where nobody specifies, EML, for the same reason as the archive.
- Where the Outlook layer is the point. MSG, with a word to whoever receives it. If categories and flags are what somebody actually needs, no other single message format holds them.
Why This Question Comes Up at All
Neither format is one anybody chooses in the ordinary way. Both arrive because somebody dragged a message out of a mail program onto a desktop. Which one landed depended entirely on which program it was.
That is why folders of these turn up mixed. It also explains why the question gets asked after the fact rather than before. Somebody inherits four hundred saved messages, half opening cleanly and half not, split along a line nobody drew on purpose.
Mixed folders are the normal case, not the odd one. Sort by extension before deciding anything. The EML half needs no work at all. The MSG half is where every question you have actually applies.
The MSG half needs software that understands the container, which is not the same as software that understands mail. Our file viewers handle it in a browser tab. Where a mixed folder has to become one consistent archive, the converters take it from there.
Structural claims checked against RFC 5322 and the Microsoft MS-OXMSG specification in August 2026.
Questions People Ask
7 questions, answered in full below.Which format should I save messages in?
It depends on who opens them next. Saving for yourself inside Outlook, MSG keeps everything and costs nothing. Saving for somebody else, on a machine nobody can predict, choose EML. It is readable by almost every mail program written since the nineties.
Why can one hold more than the other?
Because they are copies of different things. An EML records what crossed the network. Only things that could cross a network are in it. An MSG records what Outlook holds, which includes items that were never sent anywhere and have no field in ordinary mail.
Is anything lost moving from MSG to EML?
The Outlook specific parts, yes. The message itself survives intact along with its attachments. What goes are the items mail was never built to carry, such as voting responses and the flags and categories somebody applied inside Outlook.
Can I open an MSG file without Outlook?
Not in an ordinary mail program, which will show it as an unrecognised attachment. Software written for the format reads it directly, which is a different kind of tool from a mail client. An EML has no such problem anywhere.
Do both keep attachments?
Both keep them and store them differently. An EML encodes each one into characters, which is why it is larger than the files inside it. An MSG holds them as raw streams, because it never had to survive a mail server.
Which one is better for a legal request?
Ask the requesting side, because the answer is theirs rather than yours. Where nobody specifies, EML is the safer default. It is a published standard that anything can read, which matters more than completeness when a file has to be opened years later by somebody unknown.
Are the two ever the same size?
Rarely. Neither is reliably larger either. An EML pays a third extra for encoding its attachments. An MSG pays for the container structure around its streams. Which comes out bigger depends on what the message was carrying, not on the container.
Sources
Where the figures and behaviour described above were checked.
- Internet Message Format IETF, RFC 5322
- MS-OXMSG, Outlook Item (.msg) File Format Microsoft Open Specifications
- Compound File Binary Format Wikipedia