EML / EMLX Viewer
Read a saved email, inspect its headers and download individual attachments locally.
Choose an .eml or .emlx file, drag it into the box, or paste raw email source. Parsing runs locally in this browser; message content is not uploaded by this viewer.
Up to 5 MB. Message parsing stays in this browser.
Paste raw email source instead
Recorded authentication and Received chain
Quoted from the file, including its reporting server identifier. These headers can be forged and are not independently verified.
Enabling this contacts the sender’s servers and may reveal that you opened the message, your IP address and browser information.
Attachments
Files are never opened automatically. Download only attachments you trust.
How to use EML / EMLX Viewer
- Export or save the original message as
.eml, or use an Apple Mail.emlxfile. Your mail client’s original-message or source view can also provide raw email text. - Choose or drop one file, or expand Paste raw email source instead, paste the headers and body with the blank line between them, and select Open email. Files and pasted source are limited to 5 MB.
- Try the synthetic source below by pasting it as a complete message. It uses example addresses and contains no attachments or remote images.
- Inspect Rendered, Plain text, Headers and Raw source. Loading remote images is optional and off by default. An empty pasted source cannot be parsed; choose a file or paste a complete message first.
From: Alex <alex@example.com> To: Sam <sam@example.net> Subject: Safe viewer example MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 This is a synthetic message for local inspection.
What this tool checks
Parsing runs in your browser. The viewer reads the supplied bytes; it does not ask your mail provider for the message or perform a DNS authentication test.
- EML headers and body structure, or the byte-length prefix in an EMLX file before parsing its contained message.
- MIME parts: the message sections that hold text, HTML and attachments. It decodes supported base64 and quoted-printable content, encoded headers and attachment names, with limits of 200 parts and nesting depth 20.
- Recorded sender, recipients, subject, date, Message-ID, Authentication-Results and Received headers. These are values from the file, not independently authenticated facts.
- A restricted HTML preview in a sandboxed frame. Active content is removed, remote images are blocked by default, and supported embedded images can be shown. Attachment bytes can be downloaded individually.
The viewer does not verify SPF, DKIM or DMARC, decrypt encrypted messages, scan attachments for malware or reproduce every mail client’s layout. It can reject an unsupported or damaged structure even if another mail client opens it.
Understanding your results
External images are blocked until you explicitly enable them. Authentication-Results are quoted from the file, can be forged and are not independently verified. Website analytics still measures page visits; it does not receive the file content.
| Finding | Meaning & likely cause | Next action |
|---|---|---|
| Ready · MIME parts inspected locally | The file or source was parsed, and available views and attachments are displayed. | Use Headers and Raw source for diagnosis; Ready is not a security or authenticity verdict. |
| No subject / Not present / No attachments found | The corresponding field, text view or attachment was not found in the parsed content. The original may simply omit it. | Compare the other views and original source before assuming data has been lost. |
| No Authentication-Results / No Received chain | The file contains no such recorded header. An export can omit them, or they may never have been added. | Obtain the full original from the receiving mailbox when transport or authentication context is needed. |
| Malformed header / missing closing boundary warning | A header line was skipped or a multipart message lacks its final delimiter. The message may be truncated. | Compare with the original export and export again; the preview may be incomplete. |
| Unable to read this message | A separator, multipart boundary, EMLX length or encoding is invalid, or a MIME safety limit was reached. | Use a complete original EML/EMLX export. Keep the exact error when asking the exporting client or provider for help. |
| Wrong file type / size / file-read error | The file is not .eml/.emlx, exceeds the configured limit, or could not be read locally. | Choose the correct export format and size. Renaming a .msg or PDF file does not convert it to EML. |
| Missing images or simplified rendering | Remote images are blocked by default and unsupported HTML is removed from the preview. | Use Plain text or Raw source. Enable remote images only if you want to contact the image servers. |
To locate a published signing key, take d= and s= from the original DKIM-Signature and use the DKIM checker. A quoted Authentication-Results header is not a substitute for signature verification.
What is an EML or EMLX file and why does it matter?
An EML file stores an email’s source: headers describing the message, followed by a body that may contain multiple MIME sections. MIME, or Multipurpose Internet Mail Extensions, allows text, HTML and attachments to travel in the same message. EMLX is an Apple Mail format with a byte-length prefix around the message data.
Use this viewer to read a saved email, compare the text and HTML, find a selector, inspect the recorded delivery chain or extract an attachment. It shows evidence contained in a file; it does not establish who created those bytes or whether a receiving server trusted them.
For a walkthrough of locating d= and s= in the Headers view, read How to Find Your DKIM Selector.
Frequently asked questions
Can I paste just the email body or use an Outlook MSG file?
Paste the original source with headers, a blank line and the body. Body text alone is not a complete email source for this parser. The file picker accepts .eml and .emlx; .msg, PDF and screenshots are not supported formats.
Is my email uploaded when I open it?
Message bytes are parsed in the browser and are not included in the viewer’s usage request. A successful parse sends a usage event; the application records tool usage with the visitor IP and time. Website analytics can also measure visits. The optional remote-image setting permits HTTPS images and contacts their hosts; HTTP images remain blocked. See the privacy policy for service-wide information.
Why does the HTML look different from my email client?
The preview deliberately permits only a subset of HTML and styles. Scripts, active features and unsupported content are removed, and external resources are restricted. Use the raw and plain-text views when you need to distinguish source content from preview formatting.
Does Authentication-Results prove that this file passed SPF or DKIM?
No. The header is quoted from the supplied file and can be forged or changed. The viewer does not rerun authentication. Use the receiving system’s trusted original and its logs when investigating an authentication result.
Can I safely open every downloaded attachment?
The viewer never opens attachments automatically and does not scan their contents for malware. Download only files you trust and apply your normal attachment handling checks. A successful MIME parse says nothing about an attachment’s safety.
Does Copy link share my opened email, and will a reload keep it?
Copy link copies the viewer’s page URL without the message. Copy report copies parsed metadata, header findings, warnings and attachment information to your clipboard. Reloading starts a fresh viewer; select the source again to inspect an updated export, and check copied report contents before sharing.