How to open a winmail.dat attachment
A winmail.dat attachment is usually an Outlook message package, not the document the sender intended you to open. The safest fix is to ask the sender to resend the original attachment in an HTML or plain-text email; if that is not practical, a trusted TNEF decoder can extract the files inside. For broader attachment troubleshooting, see the email attachments guide.
Winmail.dat is a wrapper around the original Outlook content
Microsoft Outlook can compose messages in HTML, plain text or Rich Text Format. When Outlook uses Rich Text Format, it can package formatting, message properties and attachments in Microsoft's Transport Neutral Encapsulation Format, usually shortened to TNEF.
Outlook and Exchange understand that package and normally unpack it without showing the wrapper. Some other email apps and servers do not support TNEF. Instead of displaying the original attachment, they expose the package itself as a file named winmail.dat.
Think of winmail.dat as an envelope. The envelope may contain one or more real attachments, such as a PDF, Word document or image, along with Outlook-specific information. Opening the envelope as though it were a document does not reveal the useful content because the receiving app first needs to decode its internal TNEF structure.
A TNEF package can contain:
- The formatted version of the email, including fonts, colors and other Rich Text properties.
- Regular files that the sender attached to the message.
- Embedded pictures or Microsoft Office objects.
- Outlook features such as voting buttons, meeting information, custom forms or task requests.
- Message properties used by Outlook and Exchange.
This explains why double-clicking winmail.dat may produce an “Choose an app” prompt, unreadable symbols or no useful result. A PDF reader cannot open the package merely because the original email may have contained a PDF. The PDF is inside the TNEF wrapper and must be extracted first.
The visible filename can vary. Depending on how the receiving email app or server handles the message, the same problem may appear as:
- winmail.dat
- win.dat
- ATT00001.DAT
- Another numbered .dat attachment
- A plain-text email with the expected attachment missing
The sender may insist that a normal document was attached, and they may be correct. The document can be present inside winmail.dat even though your email app displays only the wrapper.
Winmail.dat is therefore different from an ordinary document that has simply been given the wrong extension. Renaming winmail.dat to document.pdf, photo.jpg or report.docx does not unpack or convert it. Changing a filename changes its label, not the data stored inside it.
Check whether the file is TNEF or another kind of DAT file
Not every file ending in .dat is an Outlook attachment. DAT is a general-purpose filename extension used by many applications for their own data, and there is no single program that can correctly open every DAT file.
Before installing an extractor or trying to convert the file, check where it came from, what it is called and what the sender expected you to receive.
When the attachment is probably a winmail.dat package
The file is likely to be TNEF when several of these details match:
- The exact filename is winmail.dat or win.dat.
- It arrived as an email attachment.
- The sender used Outlook or an organization running Microsoft Exchange.
- The message looks plainer than expected or has lost some formatting.
- A document, image or other attachment mentioned by the sender is missing.
- The file cannot be opened by a normal document, image or archive application.
- Other recipients using Outlook received the message correctly.
- The problem occurs with messages from one sender or organization rather than with every attachment you receive.
The file size can provide a clue, but it cannot prove what is inside. A small package may contain only formatting and message properties. A larger one may contain one or more regular attachments. Do not assume that every winmail.dat file contains a recoverable document.
When a DAT file is probably application data
Treat the file as a generic DAT file rather than winmail.dat when it came from software, a device, a game, a data export or a folder on your computer instead of an email. In that case, the program that created the file is usually more important than the extension.
Use these checks before opening it:
- Confirm the source. Find out which application, device or service created the file.
- Look for companion files. A DAT file may belong to a larger set and may not work when separated from its associated files.
- Check the full filename. On Windows, enable file extensions in File Explorer so that you can distinguish report.dat from a disguised name such as report.dat.exe.
- Ask what the file should contain. Text, video, mapping data, application settings and email packages can all use a .dat suffix.
- Try the originating application first. If the file belongs to installed software, open or import it through that program instead of selecting an unrelated app from the Open with menu.
- Inspect a copy, not the only original. Some application data is not designed for manual editing, and changing it can prevent the originating program from reading it.
Do not save over the original after opening binary data in a text editor. The editor may alter bytes or character encoding, leaving the file unusable in the application that created it.
Check the message before extracting anything
A winmail.dat package does not make an email trustworthy. Treat the files extracted from it with the same care as any other attachment.
Before opening the package or its contents:
- Confirm that you recognize the sender and were expecting the message.
- Check unexpected requests with the sender through a separate communication channel.
- Scan the downloaded file and the extracted attachments with your normal security software.
- Be cautious with executable files, scripts, macro-enabled Office files and password-protected archives.
- Avoid uploading confidential attachments to an unknown online decoding service.
A TNEF extractor reveals what Outlook placed in the package; it does not guarantee that the extracted files are safe or authentic.
Extract the attachment or have the sender resend it
The best action depends on whether you received the file, sent the message or are responsible for an organization's mail settings. Recipient-side extraction can recover an urgent attachment, but correcting the sender's format prevents the problem from recurring.
If you received winmail.dat
Start by asking the sender to resend the actual attachment. Ask them to create a new message in HTML or plain text, attach the original file again and send it without forwarding the broken message.
A newly composed message is preferable because forwarding or replying can preserve the formatting behavior that produced the TNEF package. The sender should also verify that the attachment appears as a normal file before sending.
If you cannot wait for a resend, use a TNEF-compatible extraction tool:
- Save winmail.dat to a known folder without changing its extension.
- Scan the saved file with your device's security software.
- Open it with a trusted application or email add-on that explicitly supports TNEF.
- Review the list of extracted items before opening them.
- Save the required document separately.
- Open the extracted file with the application appropriate to its real format.
For example, an extracted .pdf belongs in a PDF reader, while an extracted .docx belongs in a compatible word processor. If you need a consistent document for sharing or archiving, convert the extracted file only after it has been recovered from the TNEF package.
Some email applications support third-party extensions that decode TNEF and display the original attachments within the message. Check the extension's publisher, permissions, update history and compatibility before installing it. An old add-on may stop working after the email application is updated.
If the extractor finds no document, the package may contain only formatting or Outlook properties. Confirm with the sender that a file was actually attached.
If you sent the winmail.dat attachment
The sender normally controls the lasting fix. In classic Outlook for Windows, Microsoft documents these steps:
- Open File, then Options, then Mail.
- Find Compose messages in this format.
- Select HTML or Plain Text instead of Rich Text.
- Create a new test message.
- Attach a simple file and send it to the affected recipient.
You can also change an individual message through Outlook's Format Text controls before sending it. Exact menu names may differ between Outlook versions, but the goal is the same: send the message without TNEF when the recipient does not need Outlook-specific Rich Text features.
HTML is usually the practical choice because it preserves common formatting and works across widely used email clients. Plain text provides broad compatibility but removes visual formatting. Standard file attachments do not require TNEF.
If changing the default format does not solve the problem, check whether it affects only one recipient. Outlook or the mail system may retain recipient-specific formatting behavior. Remove the saved autocomplete entry, enter the address again and send a newly composed HTML message as a test.
Do not repeatedly resend the same Rich Text message. If the message remains TNEF-encoded, the recipient is likely to receive another winmail.dat package.
If messages from an organization keep producing winmail.dat
When multiple employees send winmail.dat attachments to external recipients, changing one person's compose setting may not be enough. An Exchange or Microsoft 365 administrator may need to control whether TNEF is used for external domains or particular recipients.
Microsoft documents Exchange settings that prevent TNEF from being sent to designated external domains. This converts external messages into a more compatible form before delivery while allowing the organization to retain settings needed for internal Outlook and Exchange communication.
If the attachment is a generic DAT file
For a DAT file that is not an Outlook TNEF package, return to the application or person that created it. Ask for the program name, export instructions or a standard-format copy.
The appropriate action may be to:
- Import the file through its original application.
- Restore it to the folder where its software expects to find it.
- Export the underlying information as PDF, CSV, an image or another documented format.
- Ask the sender to provide the original document instead of an application's internal data file.
- Keep the DAT file unchanged if it is a support, configuration or database component.
A generic converter cannot reliably turn every DAT file into a PDF because the .dat suffix does not define one content structure. First identify or extract the real content. Conversion becomes meaningful only after you know whether the file contains a document, image, table or another supported format.
Source: Outlook message formats, TNEF contents, winmail.dat behavior and sender-side remedies from How message format affects email messages, Microsoft Learn; organization-level external-recipient settings from How to specify the email message format that's used for external recipients to prevent Winmail.dat attachments, Microsoft Learn; and recipient-side TNEF guidance from What is the winmail.dat attachment?, Mozilla Support. Page last checked 2 October 2026.