Skip to content

Outlook MSG to PDF converter

MSG to PDF parses Outlook MAPI properties, converts HTML or RTF bodies, and renders calendar invites as readable text.

  • Converted with Mail engine → Document engine · input deleted within 24 h
  • Free: 5 conversions a day · 5 MB each
  • Higher limits →

From real runs

What you get — and what changes

  • Outlook recipients Kept

    From, To, CC, and BCC-like recipient fields are read from MAPI properties when present and rendered with headers enabled.

  • HTML body Changed

    HTML bodies are sanitized before rendering; scripts, unsafe URLs, and tracking pixels are removed.

  • RTF body Changed

    RTF-encoded Outlook bodies are converted to document text and layout before our document engine produce the PDF.

  • Inline images Kept

    CID or MAPI-linked inline images are embedded when the parser can match them to message parts.

  • Attachments Changed

    Attachments are not embedded in the PDF; a manifest table lists filename, size, and detected type.

  • Calendar invites Changed

    Meeting requests and ICS-like invite details render as text; interactive RSVP behavior is not preserved.

  • Threads Lost

    The PDF represents the single MSG file. Outlook conversation grouping and mailbox context are not reconstructed.

Sample conversions

Outlook approval email

Input
310 KB MSG with HTML body, MAPI From/To/CC properties, two inline signature images, one attached XLSX quote, and an Outlook category.
Output
188 KB PDF, headers rendered from MAPI fields, signature images embedded, category not shown, XLSX listed in attachment manifest but not embedded.

RTF meeting request

Input
156 KB MSG, RTF-encoded body, recipients from Exchange properties, calendar invite text, location, and one PDF agenda attachment.
Output
121 KB PDF, RTF text converted, invite fields rendered as ordinary text, recipients listed, agenda attachment listed by name/size/type.

Options and when to change them

includeHeaders
Keep on for Outlook exports where sender, recipients, date, and subject are part of the record.
sanitizeHtml
Leave enabled for messages from outside your organization or any mail with remote HTML content.
attachmentManifest
Use to document attached files without appending or transforming the attachments themselves.

Do it yourself

extract-msg plus Pandoc

bash
python - <<'PY'
import extract_msg
msg = extract_msg.Message('in.msg')
body = msg.htmlBody or msg.rtfBody or msg.body
open('body.html','wb').write(body if isinstance(body, bytes) else body.encode('utf-8'))
PY
pandoc body.html -o out.pdf

Handle RTF conversion, sanitization, CID images, and attachment manifests explicitly for production exports.

Outlook MSG to PDF by API or MCP

The HTTP API and the MCP server run the exact engine this page uses (Mail engine → Document engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=msg&to=pdf.

curl
curl -X POST https://filetypeconverters.com/api/v1/convert \
  -H "Authorization: Bearer $FTC_API_KEY" \
  -F "file=@input.msg" -F "from=msg" -F "to=pdf" \
  --output output.pdf
API reference

When this is the wrong conversion

  • Do not use this when attachments must be appended into the same PDF; they are only listed in the manifest.
  • Use Outlook or e-discovery export when conversation threading, categories, mailbox folders, and retention metadata are required.
  • Keep the original MSG for legal chain-of-custody because PDF cannot preserve every MAPI property.

Outlook MSG to PDF questions

Where do MSG recipients come from?

Recipients are read from Outlook MAPI properties, which is more reliable than scraping visible text from the message body.

Can RTF Outlook messages be converted?

Yes. RTF-encoded bodies are converted before the PDF is generated, though exact Outlook spacing may simplify.

Are MSG attachments embedded in the PDF?

No. As with EML, attachments are not embedded. They appear in a manifest table with name, size, and type.

How are calendar invites shown?

Invite details render as text so the PDF is readable, but RSVP buttons and calendar object behavior are not preserved.