Convert MSG to PDF
Attaching an Outlook message to a claim, a case file or a ticket almost always means turning it into a PDF first, and doing that through an online converter means handing over correspondence that is usually the reason the PDF is needed at all.
This page reads the .msg properly — the Compound File container, the MAPI property streams, the compressed RTF body when there is no HTML property — and lays the message out as a paginated PDF with the header fields you choose and an appendix listing every attachment with its type, size and SHA-256 hash. Where a field is not in the file, the PDF says so instead of leaving a convincing blank.
The file is read by code running in this tab. It is not uploaded, not queued on a server and not seen by anyone but you — which also means there is no size limit imposed from outside, only what your own device can hold.
- 1.Drop one or more .msg files, or a folder of them.
- 2.Choose the header fields, page size, and whether to include the attachment index and hashes.
- 3.Convert, then download the PDFs individually or as a ZIP with a manifest.
Drop email files here
Built for .msg. Nothing is uploaded — the file is read by code running in this tab.
What this page cannot do
- As with EML to PDF, the page carries the message's text rather than a rendering of its HTML. See that page's limits — they apply identically here.
- A .msg with no stored transport headers has no Date header to print; the PDF uses the submit or delivery time from the MAPI properties instead and labels which.
- CJK, Arabic, Hebrew, Thai and Indic characters are outside the embedded font and are drawn as ▯, with a count reported. For a Chinese or Japanese .msg, open it in the viewer and print from the browser instead.
- Embedded messages are indexed in the attachment appendix but are not laid out as pages of their own.
If it did not work
- The PDF has a body but Outlook showed a formatted one.
- Why: Formatting is not reproduced; only the text within it is.
- Try: Open the message in the MSG viewer and use your browser's Print to PDF for a visual copy.
- The Date field says the message has none.
- Why: The .msg stored neither transport headers nor a submit time.
- Try: Add the source-file field to the printed headers so the output can still be tied back to a specific file.
Questions
Is my email actually uploaded anywhere?
No. There is no server here that accepts a file. The page's Content-Security-Policy sets connect-src to 'self', so the browser itself refuses any request to another origin, and form-action is 'none' so nothing can be submitted anywhere. The only network requests this site makes are for its own JavaScript, its own font files, and the Vercel page-view counter — which records that a page was viewed and nothing about what you opened. You can confirm all of it in your browser's network panel with the page open.
Do I need Outlook installed?
No. The .msg is fully self-contained and everything needed to read it is implemented here. This works on macOS, Linux, ChromeOS and phones as well as on Windows.
Can I convert a folder of .msg files into one PDF?
Not into one file from the batch queue — each input produces its own PDF so that a failure isolates cleanly. Open a mailbox in the viewer and select messages if you want several in a single document.
Are the attachment hashes trustworthy?
They are the SHA-256 of the exact attachment bytes as stored in the file, computed by your own browser's WebCrypto. You can verify one with shasum -a 256 on the extracted file and get the same value.
Related
- Open Outlook MSG files — Open .msg files from Outlook in your browser: body, HTML, recipients, dates, attachments and embedded messages, read from the real Compound File structure. Nothing is uploaded.
- Convert MSG to EML — Convert Outlook .msg files to standard .eml messages that open in Thunderbird, Apple Mail and anything else. Attachments and inline images are preserved. Nothing is uploaded.
- Convert EML to PDF — Convert .eml email files to PDF without uploading them. Headers, body text, reply chains and a full attachment index with SHA-256 hashes, laid out on real pages — entirely in your browser.