Back to Blog
tutorials

Forward Email to PDF: The Zero-Setup Way to Archive Emails Automatically

Daan van Tongeren

PDFen Team

June 24, 2026
Forward Email to PDF: The Zero-Setup Way to Archive Emails Automatically

Forward Email to PDF: The Zero-Setup Way to Archive Emails Automatically

Need to save an email as a PDF — attachments and all — without printing, installing, or configuring anything? Forward it. With a forward-to-convert service you send the email to a special address and get a complete PDF back, ready to file. No browser extension, no Outlook add-in, no Power Automate flow. Here's how it works, what happens under the hood, and how it compares to every other method.

Key Takeaways

  • Forward-to-convert is one step: forward the email, get a PDF back — body, headers, and every attachment converted and included.

  • It works from any device or email client — Outlook, Gmail, Apple Mail, your phone — because forwarding is universal.

  • No extension, no add-in, no flow to build. Print to PDF drops attachments; forwarding keeps them.

  • For compliance archiving (FINRA 6 years, HIPAA 6 years, SOX 3–7 years), a PDF with intact headers is the portable, tamper-evident format auditors accept.

  • You can automate it: set up an Outlook rule or Gmail filter to forward matching emails automatically — hands-free archiving.

Why forwarding beats printing to PDF

The default advice for saving an email as PDF is "File → Print → Microsoft Print to PDF." That works for a body-only snapshot, but it quietly drops every attachment. The new Outlook doesn't even have a native Save as PDF — and its Print to PDF omits the attachments checkbox that classic Outlook still offers.

Forwarding sidesteps the problem entirely. When you forward an email, the email client packages the full MIME message — body, headers, inline images, and every attached file. A forward-to-convert service receives that package and converts all of it into one PDF (or one PDF per email, if you forward a batch).

The result is a PDF that a print-to-PDF can never produce: a document with the email body, the original From/To/Date headers, and every attachment — Word documents, Excel sheets, images, even nested .eml files — rendered as pages inside the PDF.

How forward-to-PDF works (3 steps)

With PDFen, the process is:

  1. Create a free account. PDFen gives you a personal forwarding address — something like convert+abc123@inbound.pdfen.com.

  2. Forward the email. From Outlook, Gmail, Apple Mail, or any client on any device — including your phone. Just forward it to your address.

  3. Download the PDF. PDFen processes the email and notifies you. Download the result: a complete PDF with body, headers, and all attachments converted.

That's it. No software to install, no extension to manage, no workflow to debug. If you can forward an email, you can convert it to PDF.

Close-up of a mail app icon showing unread notification badges — the starting point for a forward-to-PDF workflow.Forward the email from any device — the conversion happens in the cloud.

What happens under the hood

Forwarding an email is deceptively simple on the surface, but a lot happens between "Forward" and "PDF ready." Here's what a proper converter handles:

Attachments

Every attached file — .docx, .xlsx, .pptx, .jpg, .png, plain .pdf — is extracted from the MIME message and converted to PDF pages. The body becomes the first page(s); attachments follow. For a full walkthrough of every conversion method, see our complete Outlook email-to-PDF guide.

Inline images

Emails embed images in two ways: as cid: references (the image is a MIME part) or as external URLs. Both are resolved and embedded in the PDF. This is a known pain point in Power Automate — Microsoft's own documentation notes that native email-to-PDF actions "will not work if email has embedded images". A dedicated converter handles them natively.

Wrapper emails (the forwarding envelope)

When you forward, your email client wraps the original in a new message — the "wrapper email." A naive converter would render the wrapper, giving you a PDF of your own forwarding note instead of the original. PDFen's HybridEmlToPdfService detects wrapper emails, strips the envelope, and extracts the original message(s). If the wrapper contains multiple forwarded emails, each becomes its own PDF — or you can merge them into one document via email merging.

Headers and authentication

The PDF includes the original From, To, Date, Subject, and Message-ID. For compliance-grade output, PDFen can add an evidence page with SPF, DKIM, and DMARC results plus a SHA-256 hash — the kind of proof that holds up when someone asks "was this email actually sent?".

How does forwarding compare to other methods?

Every method has trade-offs. Here's an honest comparison:

Method

Steps

Keeps attachments?

Works on mobile?

Batch?

Setup needed

Print to PDF

4–5

No

No

No

None

Browser extension (e.g. cloudHQ)

3–4

Yes

No

Limited

Install + grant permissions

Power Automate / Zapier

8+ setup

Partial

Yes (after setup)

Yes

Flow builder + connector license

Outlook add-in

2–3

Yes

No

Yes

Install (often Windows-only)

Forward to PDFen

1

Yes

Yes

Yes (ZIP/PST upload)

Free account

Print to PDF is built in and works for a simple body snapshot. But the moment you need attachments, mobile access, or compliance-grade output, forwarding is the lowest-friction path.

When you need compliance-grade email archiving

Around 60% of business-critical data lives exclusively in email (IDC). That makes email archiving not a nice-to-have but a regulatory requirement across industries. The retention periods are specific:

  • FINRA Rule 4511: 6 years for broker-dealer correspondence (smarsh.com).

  • SEC Rule 17a-4: 3 years minimum for securities-related communications.

  • HIPAA: 6 years for compliance documentation (hipaajournal.com).

  • Sarbanes-Oxley (SOX): 3–7 years; indefinite for certain executive records.

  • IRS: 7 years for financial transaction records.

A professional working at a laptop — the kind of email archiving work that compliance regulations require.Compliance-driven email archiving means every email needs a portable, tamper-evident copy — and PDF is the universal format.

PDF is the format auditors and courts accept because it's portable, self-contained, and doesn't require the original email client to view. A forward-to-PDF service with an evidence page adds the authentication proof (SPF/DKIM/DMARC) and cryptographic hash that elevate it from "saved copy" to "verifiable record."

Setting up automated email-to-PDF forwarding

The real power of forward-to-PDF is that you can automate it with rules you already have:

Outlook rules

In Outlook (classic or new), create a rule: "When a message arrives from [client/domain], forward it to convert+abc123@inbound.pdfen.com." Every matching email is automatically archived as a PDF — no manual step. One user on Microsoft's forum put the frustration plainly: "It is required that I print outgoing mail for hardcopy filing. Additionally, I am required to save all in and outgoing mail as a PDF for digital filing" (Microsoft Q&A). A forwarding rule solves both needs.

Gmail filters

In Gmail, create a filter: "From: [address] → Forward to [your PDFen address]." Same automation, same result — every matching email becomes a PDF without you touching it.

Bulk archives

For existing mailboxes, export to .pst (Outlook) or .mbox (Thunderbird/Apple Mail), then upload the archive to PDFen's email converter. The service extracts every message and converts them in a single run — one PDF per email, or merged into a single document for case files.

Frequently asked questions

Does forwarding preserve the original email headers?

Standard forwarding (inline) strips most headers and only passes the body. Forward as attachment wraps the entire original as a .eml file, preserving all headers. PDFen handles both: forwarded-inline emails get the visible headers (From, To, Date, Subject); forward-as-attachment emails get the full RFC 822 headers including Message-ID and Received chain.

Can I forward emails from my phone?

Yes — that's the point. Forwarding works from any email client on any device. Tap Forward, paste your PDFen address, and send. The conversion happens in the cloud; your phone doesn't need to do any processing.

What if the email has attachments larger than 25 MB?

Most email providers cap attachments at 25 MB. If the forwarded email exceeds that limit, the provider may strip the attachment. For large emails, export the message as .eml or .msg and upload it directly instead of forwarding.

Can I forward S/MIME encrypted emails?

No. S/MIME encryption requires the recipient's private key to decrypt the message body. When you forward an encrypted email, the forwarding service cannot decrypt it — it doesn't have your key. For encrypted emails, see our guide to converting encrypted email to PDF.

How is this different from a browser extension like cloudHQ?

A browser extension works inside one email client (usually Gmail on Chrome) and requires installation + browser permissions. Forward-to-PDF works from any email client on any device — Outlook, Gmail, Apple Mail, Thunderbird, mobile — because it uses email itself as the transport layer. No extension to install, no browser dependency, no permissions to grant.

Can I convert hundreds of emails at once?

Yes. Export your mailbox as a .pst or .mbox archive, or zip a folder of .eml/.msg files, and upload the archive to PDFen. Every email in the archive is extracted and converted. For merging them into a single document, use email merging.

Start archiving emails in one forward

Print to PDF is fine for a quick body-only copy, but it leaves your attachments behind and doesn't work from your phone. Forward-to-PDF gives you the complete email — body, headers, and every attachment — with nothing to install and nothing to configure. Try it free on PDFen: create an account, get your forwarding address, and send your first email.

Related reading: