MSG to EML

Use this tool to turn an Outlook .msg file into a standard .eml file that any modern mail client can read. It keeps the original From, To, Subject, Date headers, all attached files, and any inline images so the message appears exactly as it did in Outlook. — only MIME‑compatible content is preserved; Outlook‑only properties such as categories, flags, or voting buttons are omitted.

Headers preserved in the .eml output

All standard email headers from the original Outlook .msg are translated directly into RFC 5322 fields in the resulting .eml. The converter copies From, To, Cc, Bcc, Subject and the original Date header without alteration, preserving the exact timestamps and recipient order so the message threads and sorting behave identically in any mail client.

Any additional MAPI header that corresponds to a standard email field, such as Reply‑To or Message‑ID, is also carried over, ensuring message threading works across platforms. Headers that have no MIME equivalent are omitted, which keeps the .eml compliant while still delivering every piece of information that standard clients can interpret.

Body formats are retained

When a .msg contains both an HTML version of the message body and a plain‑text alternative, the converter creates a multipart/alternative section in the .eml. This preserves both representations, allowing the receiving client to choose the preferred format automatically, so links, tables and styling remain functional for HTML viewers while plain‑text readers get a clean fallback.

If the source message includes only one body type—either HTML or plain‑text—the converter inserts that single part unchanged into the .eml. The HTML preserves its original markup, including embedded styles and clickable hyperlinks, while a pure text body is delivered exactly as written, guaranteeing that no content is lost during the transformation.

Attachments and inline images stay attached

Every attachment stored in the .msg file—PDFs, ZIP archives, Office documents, image files, or any other binary—is added to the .eml as an individual MIME part. The original filename is kept in the Content‑Disposition header, so when the .eml is opened in Thunderbird, Outlook, Apple Mail or any standards‑compliant client the attachment list mirrors the original Outlook message precisely.

Images that were embedded inline in the Outlook message using CID references are retained in a multipart/related block. The converter copies the original Content‑ID values, allowing the HTML part of the .eml to display those images exactly where they appeared in the original message, without requiring separate attachment handling.

Outlook‑specific metadata is excluded

Properties that exist only inside Outlook, such as categories, flag status, follow‑up reminders, voting buttons or custom MAPI fields, have no representation in standard MIME. The converter intentionally leaves these out, focusing on the portable content that any email client can render, which keeps the output file small and universally readable.

If the original .msg contains an RTF body without an accompanying HTML or plain‑text version, the converter extracts a plain‑text rendering of that RTF content and places it in the .eml. Although the rich formatting of the RTF stream is not preserved, the essential message text remains accessible, ensuring that the conversion still delivers a readable message.

Limits and scope

Size & batch scope

Accepts any number of .msg files in a single request as long as the combined upload size stays within the per‑tier limit; each file is processed independently.

Retention

The generated download link remains active for 24 hours after conversion, after which the files are removed from the server.