Convert TNEF to JSON
Turn TNEF emails into JSON. One object with the subject, date, headers, the plain and HTML bodies, and the name, type and size of each attached file, read from the winmail.dat as a standard email.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop TNEF files on the dialor turn it to pick what to do
A winmail.dat turned into JSON data.The message details come out as one JSON file. The attachments stay behind.
What you get
One JSON file made from the TNEF file. TNEF is Outlook's winmail.dat wrapper, which hides the real attachments inside it, and the JSON holds the message data from that wrapper.
A body that Outlook kept only as rich text becomes plain text in the JSON.
What changes or is left out
The contents of the attachments are left out. The JSON does not carry the files that were wrapped inside the TNEF file.
The sender and recipients appear only when Outlook also put them inside the file. If Outlook did not, those details are not in the JSON.
Options and related pages
This conversion has no options to set. You pick the file and get one JSON file back.
To see other ways to start from this format, go to every TNEF conversion. To work with the result, go to every JSON conversion.
TNEF and JSON.What each format is.
The formats
TNEF
Outlook's winmail.dat attachment wrapper that hides the real attachments inside.
- Extensions
- .tnef
- MIME type
- application
/vnd .ms -tnef - Kind
JSON
JSON, the data format of every API.
- Extensions
- .json
- MIME type
- application
/json - Kind
- Text and data
In your code.The same TNEF to JSON conversion through the API, for your app or your agent.
$ cv convert report.tnef report.json$ cv convert report.tnef report.jsonQuestions.What people ask about TNEF to JSON.
No. The contents of the attachments are left out. Only the message data is in the JSON.
Only when Outlook also put them inside the file. Otherwise they are not there.
A body kept only as rich text becomes plain text in the JSON.
One file. The result is a single JSON file.