Best Tools to Export Email to PDF, MBOX or PST (2026)

This guide is for one-off export jobs. A client file that has to leave your inbox and land in a folder someone else can open. A legal request that names a date range and wants everything. A last week at a job, where you are copying out the mail you are allowed to keep. The goal is a portable file, not a restorable backup — the archive is not going to be restored into a mailbox, it is going to sit on a drive or in a case file and be read.

That changes which tool is best. Backup software optimizes for restore. Export software optimizes for fidelity in a fixed format: the folder tree stays intact, the attachments stay attached, the dates stay real, and the format opens in something other than the tool that produced it. Most native exporters do part of this well and part of it badly, and the third-party tools exist to fill the specific gaps.

Below is what actually moves in each format, a pre-export checklist, the exact steps for PDF, MBOX and PST, a table of the failure modes per tool, a rollback plan for when an export goes wrong, and how to run the export against a live mailbox without missing mail that arrives during it. Every capability claim was checked against the vendor's own live page in August 2026 — verify before you rely on it, because this category ships changes quietly.

What actually moves in PDF, MBOX and PST — and what doesn't#

The three formats do different jobs and each one drops a different thing. Pick the format for the reader on the other end, then pick the tool for the format.

MBOX is a flat text file that concatenates every message in a folder, with attachments encoded inside as base64. It is the format Gmail, Apple Mail and Thunderbird all speak. It preserves folder-per-file, dates, headers and attachments — but it is one folder per file, so a nested tree becomes a directory of MBOX files, and no MBOX viewer renders HTML mail as prettily as the original client.

PST is Microsoft's single-file archive. Outlook can open it, Thunderbird cannot. It preserves the folder tree in one file, plus flags, categories and calendar items alongside the mail. Its problem is that almost nothing outside the Microsoft ecosystem writes PST honestly — third-party converters advertise it, but the file they produce is not always readable by every version of Outlook.

PDF is what a non-technical recipient wants. It renders like the original message, it opens in any browser, and it is easy to redact and sign. Its trap is attachments: a PDF made by printing each message loses the attachments entirely unless the tool embeds them, and most one-message-at-a-time PDF exports do not embed anything.

Pre-export checklist — the ten minutes that save the export#

Every failed export we have seen ran into one of five things, and all five are checkable in advance. Do this before you press Export, not after.

• Confirm the destination format. Ask the recipient — PDF, MBOX, PST or EML — and get it in writing. Re-exporting because you produced the wrong format is the most common redo.
• Measure the mailbox. Note the folder count and rough message count in the source. This is what you will compare against afterward to prove the export is complete.
• Check attachment policy. If the export must include attachments, the tool has to embed them; a print-to-PDF loop does not. If attachments are excluded on purpose, say so up front — legal exports often exclude bulky media by policy.
• Set the date range. A folder-wide export is fine for a personal archive; a legal or client file usually has a narrower date range and needs a tool that filters before it writes.
• Verify you have the credentials. Gmail needs an app password or OAuth for third-party tools, Outlook needs the mailbox mounted in desktop Outlook to export PST, iCloud and Fastmail need app-specific passwords for IMAP. Do not discover a locked-out account halfway through.

Exporting a whole folder to PDF with attachments intact#

The naive path — open each message, File → Print → Save as PDF — works for ten messages and fails for a hundred. It also loses every attachment, because print rendering does not embed files. For a folder that has to keep its attachments, use a folder-level converter.

1. 1

   Pick a converter that embeds attachments in the PDF

   Aid4Mail, Mail Backup X and Systools MailXaminer all render one PDF per message with attachments embedded as PDF file annotations you can click open. Thunderbird plus the ImportExportTools NG add-on does the same for free. Confirm the setting is on before you run the batch — every one of these tools has a checkbox that is easy to miss.

2. 2

   Point it at the folder and set the date range

   Load the source mailbox, select the specific folder, and set the exact date range the request asks for. A folder-wide export that includes years the request did not ask for is worse than a short one — you have handed over more than you had to.

3. 3

   Choose one PDF per message or one combined PDF

   One-PDF-per-message is easier to redact and easier to hand to a paralegal. One combined PDF is easier to search and easier to send as a single file. If the recipient did not specify, produce both — the tools support it and the disk cost is small.

4. 4

   Run a five-message dry run before the full folder

   Take five messages that between them cover the ugly cases — a long HTML thread, one with three attachments, a forwarded chain, a message in a non-Latin script, and one with an inline image. Export those five, open the PDFs, confirm the attachments open and the encoding survived. This is where you catch problems while it costs ten minutes, not ten hours.

5. 5

   Batch the full folder and log the count

   Run the full export, then compare the produced file count to the source folder's message count. If they do not match, the tool skipped something — most often a message with a malformed date header or an attachment over its size cap.

Exporting to MBOX from Gmail, IMAP and Apple Mail#

MBOX is the friendliest personal-archive format because every major mail client can still read it a decade from now. There is no third-party tool that beats the native exports here — they already produce clean MBOX.

1. 1

   Gmail — Google Takeout

   Go to takeout.google.com, deselect everything, then select Mail. Choose the labels you actually need (do not export All Mail unless you have to — it is huge). Choose MBOX as the format. Takeout produces one MBOX file per label, downloadable as a ZIP or delivered to a cloud drive. It preserves headers, dates and attachments intact.

2. 2

   Any IMAP account — Thunderbird plus ImportExportTools NG

   Connect the account to Thunderbird as IMAP, wait for the folders to sync locally, install the ImportExportTools NG add-on, then right-click any folder → ImportExportTools NG → Export folder → MBOX. Runs on Windows, macOS and Linux. Handles Gmail, Outlook, iCloud, Fastmail, Proton (via Bridge) and any generic IMAP host with the same three clicks.

3. 3

   Apple Mail — native mailbox export

   Select the mailbox in the sidebar, then Mailbox → Export Mailbox and pick a destination. Apple Mail writes an .mbox package (which is a folder containing the MBOX file plus indexes). Thunderbird and most viewers open the inner MBOX directly.

4. 4

   Verify the MBOX opens in a second tool

   An MBOX that only opens in the tool that produced it is not portable. Open the exported file in one other client — Thunderbird, mbox-viewer, or your future destination — and confirm the folder loads and the message count matches. This is what separates an archive from a promise.

Exporting to PST — and why native Outlook is the honest answer#

PST is Microsoft's format and Microsoft's tool writes it best. Third-party MBOX-to-PST converters exist and some of them work — but the output can misbehave in specific Outlook versions, and if a legal recipient rejects the file, you have to redo it.

1. 1

   The native path — Outlook desktop → File → Open & Export → Import/Export

   In desktop Outlook (Windows or Mac), File → Open & Export → Import/Export → Export to a file → Outlook Data File (.pst). Pick the folder, choose whether to include subfolders, filter by date if needed, and set a password if the recipient needs one. This is the only PST that every version of Outlook is guaranteed to open.

2. 2

   Mount the source first if it is not already in Outlook

   The native export only works on mailboxes Outlook has mounted. For a Gmail-to-PST job, add the Gmail account to Outlook as IMAP first, wait for the folder you need to sync, then export. Slower than a direct converter, but the file is guaranteed compatible.

3. 3

   For MBOX-to-PST specifically, use Aid4Mail or Systools

   If the source is already an MBOX file and Outlook is not available, Aid4Mail and Systools both convert MBOX to PST. Run a dry-run PST on a small folder first and open it in the exact Outlook version the recipient uses — this is where converter output most often fails.

What breaks in each tool#

This is the field manual — the specific things that go wrong per tool, checked against each vendor's own live documentation in August 2026. Re-verify before you rely on it; this list moves.

Rollback plan when an export goes wrong#

Export failures come in two shapes: the file did not finish, or the file finished but is not what you wanted. Both are recoverable if you did not delete the source, which is the single most important rule of an export job.

1. 1

   Do not touch the source until the export is verified end to end

   Leave every message in place in the source mailbox until you have opened the export file in the recipient's tool and confirmed the folder, counts, attachments and dates. The source is your rollback — an export that never touched the original is a redo, not a disaster.

2. 2

   If the file is incomplete, re-run the export for the missing range only

   Most exporters let you filter by date or by folder. If a batch stopped at 3,200 messages of a 4,000-message folder, re-run for the date range that covers the missing 800 and merge the two files afterward with the tool's combine option or a viewer that opens both.

3. 3

   If the format is wrong, re-run to the requested format from the source

   Do not convert a wrong-format file to the right-format file — every conversion loses fidelity. Go back to the source mailbox and export directly to what was asked for. A PST that was produced from an MBOX that was produced from a Gmail export is three degrees away from the truth.

4. 4

   If attachments are missing, check the embed setting before re-running

   Nine times out of ten a missing-attachment PDF was made with the embed option off. Turn it on, re-run, compare a message with a known attachment before batching. The tenth time is a size cap in the tool — bump it, or exclude oversize items on purpose and document the exclusion.

Doing the export without downtime on a live mailbox#

Most one-off exports run against a mailbox that is still receiving mail. If you run a bulk export and mail arrives during it, some tools include the new mail and some do not — and neither behaviour is what the requester asked for.

Freeze the window instead. Set the date range to end at yesterday 23:59, run the export, then decide separately whether today's mail is in or out of scope. If it is in scope, a second small export the next day catches it cleanly; if it is out of scope, you have not accidentally included it. Either way, the file matches the request instead of matching whenever the batch happened to finish.

For mailboxes on IMAP, one more habit matters: make sure the source client has finished syncing before you export. A local export of an IMAP folder only covers what the client has cached — Thunderbird, Apple Mail and Outlook all default to header-only sync on large folders, and exporting from a half-synced state silently produces a half-full file.

Where AI Emaily fits in an export job#

AI Emaily is not a dedicated exporter and we should not pretend otherwise. If your job is producing a PST for a discovery request or a folder-of-PDFs for a client handover, use a tool from the table above — that is what they are built for, and Aid4Mail in particular has built harder on cross-format fidelity than we have.

What AI Emaily does in this workflow is smaller and more specific. It connects to the Gmail, Outlook, iCloud, Fastmail, Proton or IMAP mailbox you are exporting from, so you can find the folder and the date range in one unified inbox instead of logging into each provider's webmail. It exports its own vendor-side layer — Personal Context, rules, templates and audit log — as a JSON archive during a trial, so nothing we added to your workflow is stuck inside us. And after the export, we are the reading tool for the mailbox that continues; the archive lives elsewhere and the live inbox stays here. We build AI Emaily; there is a 7-day trial with the card required, and pricing is on the pricing page.