EML vs MSG: email file differences

An EML file is text at the top level. It has headers such as From, To, Subject, and Date, followed by a MIME body. Attachments and HTML alternatives are represented as MIME parts, often base64 encoded.

Because EML follows internet mail conventions, many mail clients and libraries can parse it. You can inspect headers in a text editor, although encoded words, transfer encodings, and multipart boundaries make large messages harder to read by hand.

MSG is Outlook’s saved-message format. It stores a MAPI message inside an OLE compound file, the same structured-storage family used by older Office documents. Message properties, recipients, attachments, and body variants live in streams rather than simple RFC 5322 text.

That structure can preserve Outlook-specific fields better than EML, including some follow-up flags, RTF body data, and MAPI properties. It also makes MSG less portable. Many non-Microsoft tools need a specialized parser before they can extract the message.

Both formats can contain attachments. In EML, attachments are MIME parts with content types and filenames. In MSG, attachments are stored as MAPI attachment objects, and nested messages may appear as embedded MSG attachments.

Email bodies can have plain text, HTML, and sometimes RTF variants. A conversion to PDF normally chooses the HTML body if it exists, then falls back to text. That means hidden plain-text differences or Outlook RTF-only formatting may not appear unless the converter explicitly handles them.

Do not treat an exported email PDF as the only record if headers matter. PDF is useful for reading and sharing, but it may omit transport headers, authentication results, and message IDs unless the conversion includes them. Keep the original EML or MSG when chain of custody or legal review matters.

For quick identification, file -I message.eml may show text, while an MSG file often appears as a generic compound document. The extension is not proof of origin; exported mail can be renamed or wrapped by archiving tools.

Convert EML to PDF when you need a readable copy of a standards-based email. Convert MSG to PDF when the source came from Outlook and the recipient does not have Outlook. Convert MSG to EML only when the target system wants internet-message format and you accept that some MAPI-specific fields may be lost.

If attachments must be included, decide whether they should be embedded, listed, or converted separately. A single PDF of the email body is not the same as a complete evidence package.

For migration projects, decide whether the target needs transport fidelity or user-view fidelity. EML usually represents internet mail exchange well. MSG can preserve Outlook client properties better. A PDF rendition is useful for reading, but it is the least complete option for later mailbox import.

Name exported files with stable fields such as date, sender, and subject only after sanitizing unsafe characters. Message subjects can contain slashes, quotes, emoji, and repeated text. A careless export script can overwrite messages or create paths that work on one operating system but not another.

A final email export policy should state whether duplicate messages are allowed. Mailbox exports can contain the same message in Sent, Inbox, and archive folders, and conversion alone does not identify duplicates reliably.