Extract images from EML, on your device. Nothing ever uploads.

Drop up to 20 emails (.eml or .emlx) below — get every embedded photo and image attachment out byte-for-byte, exactly as stored, in the order it appears in the message. Download each image, or all of them as a ZIP.

  • Your file data never leaves the device
  • EML + EMLX, message order
  • Batch up to 20 emails + ZIP
  • Original filenames, sequential ZIP names

Extract images from EML emails

Add your EML emails

Drag & drop EML emails here

or browse your files · you can also paste from clipboard (Ctrl+V)

An EML file is a plain-text RFC 5322 email message — read on this device with a pure-JavaScript MIME parser, images returned in the order they appear in the message, labelled with their original filename, and the text and HTML bodies and other attachments skipped. Every image downloads byte-for-byte, exactly as stored — no re-encoding, no quality loss. EMF, WMF, HEIC and TIFF images cannot be previewed in most browsers, so they show a “preview unavailable” note — they still download byte-for-byte. SVG images are extracted as-is; their preview may not render in some browsers. A nested message (message/rfc822) or nested multipart part is unpacked one level deep; deeper nesting is listed as skipped. Plain HTML files, MHTML saved pages, Outlook .msg files, PDFs and ZIPs renamed .eml are refused with a pointer at the right tool or fix; .emlx files extract the same way as .eml. Images referenced only in CSS (background images) and data: URIs inline in the HTML are not extracted as separate images. A winmail.dat (TNEF) attachment refuses the file with an explanation, and an S/MIME-encrypted message is refused as encrypted.

    No files yet. Everything stays on this device. Downloads start instantly.

    Privacy you can verify, not just trust

    Most online EML tools upload your email to their servers first — and some keep a download link live for 24 hours, or cap free use at a few files a month. This one can't: each image is pulled out of your email entirely in your browser. Your file data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no file fetched after load for the extraction itself. Don't take our word for it:

    New cross-origin requests during use: 0
    1. Press F12 to open developer tools, then the Network tab.
    2. Extract any email above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
    3. Extra credit: disconnect your internet after this page loads — extraction still works.

    How to extract images from an EML file without uploading it

    Every "free" online EML tool you have used uploads your email to a company server, extracts it there, and — in several documented cases — keeps a copy or a live download link for a day, or limits free users to a few files a month. For emails you were sent in confidence, or simply would not post publicly, that is an unnecessary risk. The safer approach is to extract the file where it already is: on your own device.

    This tool does exactly that. When you drop an EML file here, your browser:

    1. Checks the file is really an EML email — by its magic bytes, not its name — so a JPEG renamed .eml is refused with a clear message, a ZIP renamed .eml is refused with a pointer at the Extract Images from CBR tool, a PDF renamed .eml is refused with a pointer at the Extract Images from PDF tool, a Word document, spreadsheet or PowerPoint file renamed .eml is refused with a pointer at the matching Office extractor, an MHTML saved page is refused with a pointer at the Extract Images from MHTML tool, an Outlook .msg file is refused with an explanation that it is a proprietary format, and a plain HTML file is refused with instructions to save the email as .eml from your mail app. A real EML file saved with the wrong extension still extracts, and both .eml and .emlx files are read.
    2. Reads the email’s own structure and pulls the images in message order — the HTML body part lists each inline picture through its cid: references, in document order, so the picture at the top of the message comes before the one at the bottom even when the MIME parts list them the other way round, and every image is labelled with its original filename. Image attachments nothing references are listed last as Unreferenced. The text and HTML bodies and other attachments are skipped, and everything skipped is listed on the email card. The Subject line is shown as the card’s display name.
    3. Hands you the originals — download one image and it keeps its original filename; download the email as a ZIP and every image is renamed image-01, image-02 and so on in message order. Nothing is re-encoded, rasterized or resized at any point: the bytes you download are the bytes that were stored in the email.

    What makes this extractor different

    Most pages that top the results for this search are email viewers, not extractors — they show you the message and make you download each attachment by hand, one at a time — or desktop software you have to install, with demo caps. The free online extractors upload your email to a server first. This page does the simpler job, and does it fully in the browser: no upload, no monthly cap, no account, no 5 MB limit, a batch of 20 emails, EML and EMLX, message order with every image labelled by filename, unreferenced attachments labelled, original filenames on per-image downloads, sequential names in the ZIP, and a live network-request counter so you can verify the privacy claim yourself.

    Honest limitations

    Verbatim means verbatim — no quality recovery

    JPEG throws away detail when it compresses, and extracting cannot put it back. But nothing is lost either: the source bytes download unchanged, in every format. There is no quality setting because there is nothing to re-encode.

    Metadata stays in the files

    Extraction copies the stored bytes, so EXIF and other metadata inside each image is kept — including location data, if the image has any. The email’s own text and HTML bodies and other attachments are skipped, and listed on the card, but the images themselves are untouched. Strip metadata yourself before sharing an image publicly.

    EMF and WMF preview

    EMF and WMF images are extracted as-is, exactly as stored. Most browsers cannot display them, so the page shows a note instead of a broken image in that case, with the format and size shown. The file itself still downloads byte-for-byte and opens in LibreOffice or any viewer that supports the format.

    The message is not re-rendered

    An EML file is a whole email — headers, text and HTML bodies as well as images — and this tool does not render it. Only embedded images come out, byte-for-byte; the message itself stays in the .eml file. To read the whole message, open it in your mail app instead.

    winmail.dat and S/MIME-encrypted messages are refused

    A winmail.dat attachment is a proprietary Outlook (TNEF) container — this tool does not unpack it. Open the message in Outlook and save its attachments from there, or ask the sender to resend without Rich Text format. An S/MIME-encrypted message can only be read with the recipient’s private key, which this tool never asks for — open it in your mail app, where the key lives.

    No text, linked images or data: URIs

    This tool pulls out images only: it does not extract the email’s text, it does not download pictures linked from the web (only embedded images have bytes inside the file), and it does not extract data: URIs as separate images — a data: URI is inline in the HTML itself, not a separate part. Images referenced only in CSS (background images) are styles, not <img> images, so they are not listed either.

    Message order, when the email cooperates

    Message order comes from the HTML body part’s img src and srcset references, in document order. If an email has no HTML body part, the page falls back to part order and says so on the card — the images still come out byte-for-byte.

    Nested messages, one level deep

    A MIME part that is itself a multipart message, or a forwarded message saved inside the email (message/rfc822), is unpacked once; deeper nesting is listed on the card as skipped. Most emails are flat, so nesting is rare in practice — a nested part is usually a forwarded message saved inside the email.

    Frequently asked questions

    Do my emails upload anywhere?

    No. Your EML files are extracted entirely in your browser — your file data never leaves the device, and the only third-party requests are the site’s own analytics, which count page views. You can verify it yourself with the network-request counter in the privacy section below the extractor.

    What is the difference between EML and MHTML?

    An EML file is a single email message (RFC 5322) — headers, a blank line, then the body, usually multipart/mixed or multipart/related. An MHTML file is a saved web page: a multipart/related message whose first part is the page’s HTML and whose later parts are its images. This page reads emails, not saved pages, so an MHTML file is refused here with a pointer at the Extract Images from MHTML tool, which reads saved pages the same way.

    What is the difference between EML and MSG?

    An EML file is a plain-text MIME message any mail app can save, and this page reads it directly in your browser. An MSG file is Outlook’s proprietary binary format (OLE compound document), not plain text, so this page refuses it and explains why. To get your images out of an MSG file, open it in Outlook and save its attachments from there, or ask the sender to resend the message as an .eml.

    What is the difference between an inline image and an attachment?

    An inline image is embedded in the email’s HTML body and shown inside the message — it is an image part the HTML references with a cid: link, and this page lists those first, in the order they appear in the message, labelled with their Content-ID or filename. An attachment is a separate file attached to the message (Content-Disposition: attachment, with a filename); attachments nothing in the body references come last, labelled Unreferenced. Both download byte-for-byte with their original filenames.

    How are the images stored inside an EML file — base64 or quoted-printable?

    Usually base64: each image part carries its bytes as base64 text, and this page decodes it back to the original bytes. Some parts use quoted-printable instead, and those decode the same way. Either way the downloaded image is byte-for-byte the original — nothing is re-encoded, and there is no quality setting because there is nothing to re-encode.

    What is winmail.dat, and why won’t this tool open it?

    winmail.dat is a TNEF attachment — a proprietary Outlook container that holds the message’s images and attachments in a format only Outlook understands. It appears when the sender’s Outlook is set to Rich Text format. This tool does not unpack it, and says so instead of failing silently: open the message in Outlook and save its attachments from there, or ask the sender to resend without Rich Text (Outlook → File → Options → Mail → Message format).

    Why is my S/MIME-encrypted email refused?

    An S/MIME-encrypted email (application/pkcs7-mime) can only be read with the recipient’s private key, which this tool never asks for and never touches — asking for it would break the no-upload promise. The encrypted bytes are unreadable without that key, so the file is refused with a clear message. Open the message in your mail app, where the key lives, and save any images from there.

    Are the images re-encoded, or do I get the originals?

    You get the originals. Every image downloads byte-for-byte exactly as stored in the email — no re-encoding, no rasterization, no quality setting, no quality loss. A JPEG that was compressed when the email was sent stays exactly that JPEG; nothing is lost, and nothing can be recovered either. Per-image downloads keep the original filename; ZIP downloads use sequential names (image-01.jpg, image-02.jpg, …) in message order.

    Does extraction keep metadata like EXIF location data?

    Yes. Extraction is verbatim, so EXIF and other metadata inside each image is kept — including location data, if the image has any. The email’s own text and HTML bodies and other attachments are skipped and listed on the card, but the images themselves are untouched. Strip metadata yourself before sharing an image publicly.