How RFC 5322 email parsing and tracking protection work
Standard .eml files follow the IETF RFC 5322 Internet Message Format specification, storing headers and MIME parts in plain text. Your browser decodes those bytes inside a local Web Worker with 0 bytes uploaded, stripping scripts and remote tracking images before rendering a single pixel.
Blocking remote tracking pixels while keeping inline images
Marketing emails and automated receipts frequently embed invisible 1-pixel https:// images that notify external servers the moment a message is opened. The sanitizer replaces remote image URLs with blocked placeholders so your IP address and reading time stay private.
Inline pictures packaged inside the email file itself remain visible, giving you a clean visual layout without network leaks. Even complex newsletters with nested tables preview safely without executing embedded scripts.
Opening both .eml and Outlook .msg containers
Exporting from Thunderbird, Apple Mail, or Gmail creates .eml files, whereas desktop Microsoft Outlook saves binary OLE2 .msg containers. This viewer opens both formats directly, and if you work primarily with Outlook archives you can bookmark our dedicated Outlook MSG viewer and PDF converter.
Because both formats are parsed in your browser tab, you can inspect multi-year email archives even on computers without an installed desktop mail client. No account sign-in or mail server connection is required.
Extracting attachments and embedding the manifest table
Emails often bundle invoices, signed PDFs, or spreadsheets alongside the message body. You can inspect every attachment right below the header table and export them without installing a desktop mail client.
Saving single files or downloading all attachments as a ZIP
Each attachment row displays its filename, byte size, and a Save button for one-click extraction. When a message contains 2 or more attachments, a Save all as ZIP link bundles every file into a single archive named after your email.
If an attachment is itself a PDF invoice or contract, you can combine saved email PDFs with attachments right after exporting the email body. Keeping the message header page paired with its attached invoice creates a complete audit packet for bookkeeping or legal review.
Inline cid: images versus downloadable file attachments
Under the IETF RFC 2392 Content-ID URL specification, HTML emails embed inline logos or screenshots using cid: references mapped to internal MIME parts. The parser separates inline cid: assets from regular downloadable attachments so logos appear inside the body while real documents stay in the Attachments list.
When a sender attaches a named PDF, spreadsheet, or ZIP file without an inline cid: reference, it appears strictly in the downloadable list with its byte size. Large attachments never bloat the rendered PDF unless you merge them afterward.
Paper size, typography, and audit-ready header options
Converting an email for tax audits, HR documentation, or court discovery requires legible formatting and verifiable header metadata. The right-hand panel exposes 4 focused controls before you click Save as PDF, keeping body text crisp at 10.5 pt.
| Export option | Available choices | Default behavior | Best used for |
|---|---|---|---|
| Page size | A4 or US Letter | Auto-detected from locale | Regional printing and court filings |
| Font | Sans-serif or Serif | Sans-serif at 10.5 pt | Clean reports vs formal correspondence |
| List attachments in PDF | Checked or unchecked | Checked | Appending filename, MIME, and byte manifest |
| Include Message-ID header | Checked or unchecked | Unchecked | Legal discovery and server audit trails |
| Body view toggle | Formatted or Plain text | Formatted when HTML exists | Stripping complex HTML newsletters |
Under the IETF RFC 2045 MIME Format specification, multipart messages often carry both HTML and plain-text alternatives. Choosing Include Message-ID header prints the full server-assigned identifier under the standard header table.
When sharing correspondence externally, you can scrub confidential addresses before court filing once the PDF is generated.
Troubleshooting encoded headers and special characters
Email archives span decades of mail servers, character encodings, and internationalized subjects. Knowing how the parser handles headers and font sets prevents surprises during export.
Why non-Latin glyphs trigger a question mark notice
Encoded subjects and display names are decoded via the IETF RFC 2047 MIME Header Extensions standard, supporting UTF-8, ISO-8859-1, and Windows-1252. When writing the PDF at 10.5 pt using built-in Latin fonts, characters outside that Latin set are replaced with ? and counted on the result screen.
Before exporting, the Formatted preview displays every Unicode character faithfully in your browser, including emojis and non-Latin scripts. Checking the preview lets you verify dates, invoice numbers, and recipient names before generating the final 10.5 pt PDF.
Switching between Formatted and Plain text views
If an HTML newsletter uses complex nested tables or broken CSS, toggle Plain text in the preview header to inspect the raw text alternative. Output filenames are sanitized automatically and capped at 80 characters so operating systems never reject special characters.
Keeping a plain-text fallback alongside the formatted layout ensures you can always read long receipts or server alerts clearly even when an email client omitted clean HTML styling.
If you need to send outbound correspondence instead of archiving received messages, you can generate personalized batch correspondence from a spreadsheet in your browser. Pairing clean outbound mail merges with local .eml archiving gives small teams a complete, server-free paper trail for client billing and compliance records.
Tip: Keep List attachments in PDF enabled for tax and HR records so auditors can verify which files accompanied the original message even when individual attachments are archived separately in another folder.