Skip to main content

Why will this email attachment not open?

An email attachment usually will not open because the attachment is an unfamiliar file type, a saved email message, or content that the sending and receiving mail apps handled differently. Start by checking the full filename and extension, then use the relevant path below; for broader file-opening problems, return to PDF and document compatibility. Do not rename the extension or install an unknown attachment viewer until you know what the file contains and trust the sender.

An attachment can fail at the file, message, or mail-app layer

Attachment arrives What is it really?
  • winmail.dat A TNEF wrapper Outlook added around the real files. Extract the files with a TNEF reader, or ask the sender to resend as plain attachments. Problem: the attachment
  • .eml A whole saved email (headers + body + its own attachments). Open in any mail app; drag inner attachments out to save them. Problem: the container
  • .msg A single Outlook message saved as a file. Opens in Outlook; on other apps convert to .eml or export the contents. Problem: the container
  • .docx .pdf … An ordinary file — nothing wrong with it. You just lack an app that opens this type. Install one or convert it. Problem: the receiving app
The attachment is wrapped/altered It is an email container, not a document The file is fine — your app is missing
Follow the attachment to what it really is, and the colour tells you whether the fix is the file, the email wrapper, or the app you open it with.

An attachment is not always a standalone document. It can also be an entire saved email, a package created by Outlook, a cloud-download link, or a file that the receiving service has blocked for security. Identifying which layer failed prevents you from trying to repair a file that is not actually damaged.

A normal document still needs a compatible app

Common attachments such as PDF, DOCX, XLSX, JPG and ZIP files are separate files carried by the email. The mail app downloads or previews them, but another application normally interprets their contents.

A PDF may therefore download correctly but fail to open because no PDF reader is associated with it. A spreadsheet may open in a browser preview but lose features when transferred to an app that does not support its formulas, macros or formatting. An archive may download but remain inaccessible until it is extracted.

In this situation, the email transport has usually done its job. The problem lies with one of these conditions:

  • No suitable app is installed. The device does not have software registered for that extension.
  • The wrong app is selected. The operating system sends the attachment to an application that cannot interpret it.
  • The download is incomplete. The saved file is much smaller than expected, has a temporary name or contains no usable data.
  • The extension is misleading. The filename says one thing, but the file’s internal structure belongs to another format.
  • The document is damaged. The correct app recognizes the type but reports that the content cannot be read.
  • The file requires access or a password. Encryption, rights management or a protected archive prevents ordinary opening.

These failures concern the attachment itself rather than the surrounding email. Saving the file locally and checking its complete name, size and opening application will usually reveal the next step.

An EML or MSG file is an email container

Files ending in .eml or .msg usually represent saved email messages rather than ordinary documents. They may preserve the sender, recipients, subject, message body and attachments as one file.

An EML file follows the structure used for an internet email message. Its content can include message headers, text or HTML body parts and MIME-encoded attachments. Many desktop mail clients can open EML files, although a device may not have one assigned as the default application.

An MSG file is associated more closely with Microsoft Outlook. It stores an Outlook message and its properties in a Microsoft format. A mail app that understands standard EML messages may not necessarily support MSG files.

This distinction matters because the document you want may be nested inside the saved message. Opening the EML or MSG container first can expose another attachment that you can then save separately. Renaming message.msg to message.pdf does not extract or convert anything; it only gives the Outlook message a false filename.

Winmail.dat is an Outlook transport package

A winmail.dat attachment commonly appears when Outlook or Exchange sends information using Transport Neutral Encapsulation Format, or TNEF, and the receiving mail system does not interpret that format.

TNEF can package formatted message content, Outlook-specific properties and the ordinary attachments that the sender added. An Outlook-compatible receiving system may process this package without showing it to the recipient. A different mail client may instead display the package as winmail.dat, win.dat, an ATT file or another generic attachment.

This means the DAT file may not be the document the sender intended you to open. It can be a wrapper around that document. The cleanest resolution is often for the sender to resend the message in HTML or plain-text format with the original files attached normally.

A filename ending in .dat does not always mean TNEF, however. DAT is a generic extension used by many applications for unrelated data. Treat a DAT file as a probable Outlook package only when it arrived by email, especially when the expected Word document, spreadsheet, image or PDF is missing.

The extension and delivery context identify the right opening path

The full filename is the fastest useful clue, but it must be interpreted with the way the attachment arrived. A familiar extension points toward a document app, while EML, MSG and mail-generated DAT files point toward an email container or transport problem.

Check a DAT file for signs of an Outlook packaging problem

A DAT attachment is likely to be winmail.dat or another TNEF package when several of these conditions apply:

  • The sender uses Outlook or an organization that runs Microsoft Exchange.
  • The attachment is named winmail.dat, win.dat or something similar to ATT00001.dat.
  • The sender says that a normal document was attached, but you received only the DAT file.
  • The message has lost formatting, images, meeting information or other Outlook-specific features.
  • Other recipients using Outlook can see the expected attachment, while your mail app cannot.
  • The same sender’s attachments repeatedly arrive this way.

If the DAT file came from an application, download or storage device rather than an email, it may contain entirely different data. In that case, the application that created it—not Outlook—should determine how it is opened.

Treat EML as a saved internet email

An EML file should be opened with a mail client or another application that explicitly supports saved email messages. New Outlook can open EML files, and other mail applications may support them through a double-click, an Open command, drag and drop or an import function.

After the message opens, inspect it as an email:

  • Confirm the displayed sender and subject.
  • Look for an attachment area inside the opened message.
  • Save the nested document rather than treating the EML file itself as that document.
  • Preserve the original EML file if message headers or other evidence may be important.
  • Be cautious when the saved message contains links or files from an unverified source.

Use Outlook-compatible software for MSG files

An MSG attachment is usually best opened in Outlook or another program that specifically states that it supports the MSG format. New Outlook for Windows and Outlook on the web can open MSG files in supported configurations, including by dragging the file into the reading pane. Microsoft notes that opening MSG files in new Outlook can depend on having a qualifying Microsoft 365 subscription.

If double-clicking an MSG file produces an “unknown file” message, the file may be intact but lack an associated application. Check whether Outlook or an approved MSG-compatible viewer is available before asking the sender to create another copy.

Separate blocked attachments from unsupported formats

A file can be valid and still be unavailable because the mail service considers its type unsafe. Gmail and Outlook block or restrict various executable and script formats that could carry malicious software. Gmail may also reject prohibited file types when they are placed inside archives.

Security blocking is different from an “unsupported format” error:

  • Blocked by the mail service means the provider has refused, removed or disabled access to the attachment.
  • No app can open this file means the attachment reached the device, but no compatible application is available.
  • The file is damaged means a compatible application recognizes the format but cannot read its structure.
  • The attachment is unavailable can indicate a browser, network, account-permission or download problem rather than a file-format problem.
  • A cloud link appears instead can mean the sender’s service replaced an oversized attachment with shared storage.

Do not try to bypass a security warning merely because you recognize the sender’s display name. Confirm unexpected attachments with the sender through a separate trusted channel, particularly when the file contains scripts, executables, macros or password-protected archives.

Open the container first, then save or convert the real document

The safest fix preserves the original attachment while you identify its role. Work on a copy, use trusted applications and avoid changing the extension as a substitute for opening or converting the file.

Save and inspect an ordinary attachment

For a familiar document or image format, use this sequence:

  1. Save the attachment to a known folder instead of repeatedly opening it inside the mail preview.
  2. Display the complete filename, including its extension.
  3. Check whether its size is plausible. A zero-byte file or an unexpectedly tiny download is probably incomplete.
  4. Scan the file with the security tools approved for your device or organization.
  5. Choose an application that explicitly supports the extension.
  6. If the correct app reports damage, download the attachment again or ask the sender to resend the original file.
  7. If the document opens correctly, save a separate copy before converting or editing it.

A preview failure does not prove that the document itself is broken. Mail previews support a limited set of formats and features. The downloaded file may open normally in its native application even when the browser or mail app cannot display it.

Do not repair an unknown attachment by trying random extensions. Changing .dat to .pdf, for example, does not create a PDF structure. Only use a different extension when you have reliable evidence that the file was merely named incorrectly.

Open message containers without discarding their contents

For EML and MSG files, open the email container in compatible software before handling anything inside it. Save nested attachments individually and keep the original message file until you know that all required content has been recovered.

If an EML or MSG file will not open on your current device, the practical options are to use a compatible desktop mail client, try a supported webmail import or opening method, or ask the sender to forward the message normally. The sender can also save the visible email as a PDF when you only need a readable record.

Avoid copying the message body into a document and assuming that nothing was lost. The original container may also hold attachments, message headers, dates and other properties that are not visible in copied text.

Ask the sender to replace a Winmail.dat package

When winmail.dat contains the expected attachment, the most reliable long-term fix happens at the sending side. Ask the sender to attach the original file again and send the message using HTML or plain text rather than Outlook Rich Text or another configuration that applies TNEF to the recipient.

A useful request is specific: explain that you received winmail.dat instead of the named document and ask for the original file as a normal attachment. This is clearer than saying only that “the attachment does not work.”

If resending is impossible, an approved TNEF-compatible application may extract the contents. Use this route only when you trust the sender and the extraction method. Keep the original DAT package until you have confirmed that the recovered files open correctly.

Once the actual document has been extracted, you can convert a copy to PDF when you need a widely readable version. Convert the document itself—not the EML, MSG or DAT wrapper—unless your goal is specifically to preserve the visible email as a PDF. Keep the original file when editable content, message data, formulas, layers, attachments or other format-specific features still matter.

Source: Email body-part and media-type structure from RFC 2045: Multipurpose Internet Mail Extensions Part One, RFC Editor; TNEF and winmail.dat behavior from Content conversion and How Message Format Affects Email Messages, Microsoft Learn; EML and MSG opening guidance from Open .eml, .msg, and .oft files in new Outlook and Outlook on the web, Microsoft Support; and attachment security restrictions from File types blocked in Gmail and Open, save, and edit attachments received in Outlook, Google and Microsoft Support. Page last checked 2 October 2026.