Introduction
What You'll Learn:
- What PST-to-HTML actually means and the main reasons people do it
- Why Outlook's manual method falls apart past a few emails (and the specific reason it makes large archives impossible)
- How to convert a full PST archive to HTML — including the one setting most people miss
- HTML vs. MHTML: they look similar but behave very differently, and picking wrong creates problems
- Six things that go wrong after conversion and what to do about each one
Your PST file is a locked archive. Everything in it — thousands of emails, formatted messages, sender details — is only accessible if you have Outlook running on the same machine.
HTML breaks that lock.
An HTML version of your PST archive opens in any browser, on any device, without Outlook. It's searchable, shareable, and indexable by document review platforms. For compliance work, archiving, and migration, it's often exactly what you need.
Two ways to get there. Outlook has a manual method — it works, but it converts one email at a time and comes with limitations worth knowing before you start. A dedicated converter reads the full PST and processes the entire archive in one job.
This guide covers both. It also covers the HTML vs. MHTML decision — which actually matters more than most people expect.
What Is PST-to-HTML Conversion (And When Do You Actually Need It)?
Think of a PST file as Outlook's private storage format — built by Microsoft, readable by Outlook, and basically nothing else. If you've ever tried to open one on a machine without Outlook installed, you know exactly what I mean.
HTML is the opposite. Drop an HTML file in Chrome, Firefox, Edge, or Safari — it opens, no questions asked. No email client, no special reader. Anyone with a browser gets in.
That's what PST-to-HTML conversion gets you: an Outlook archive that anyone can actually open.
Here's when people reach for HTML output:
- Legal and compliance teams need email records their document review platforms can ingest. Most eDiscovery tools handle HTML natively. PST archives require specialized readers.
- IT administrators archiving email for employees who've left the organization — HTML archives stay readable for years without maintaining an Outlook installation.
- Businesses sharing email records with external parties — auditors, legal counsel, clients — who may not have Outlook.
- Migrations where you need a human-readable backup before switching platforms.
- Intranet email archives where emails need to be accessible via a web interface.
For a legal team I worked with, the requirement was specific: their document review platform could ingest HTML files directly, but not PST archives. The conversion wasn't optional. It was the only way to get the data into their workflow.
Why Outlook's Built-In Method Doesn't Scale
Outlook does have a manual path to HTML. Open an email, File → Open & Export → Save As, change the format dropdown to HTML, click Save.
It works. For one email.
The problems start the moment you need more than that.
One email at a time. No exceptions.
There is no batch option in Outlook's manual export. You open an email, save it, open the next one, save it. I tried the manual method once, on a PST that the client described as "just a small archive." Sat down, opened the first email, File → Save As → HTML, saved it. Opened the next one. Saved it. I remember at one point checking the time and realizing I'd been doing this for almost an hour and had 19 emails. The PST had around 4,800. I closed Outlook, spent maybe ten minutes finding a converter, and had the whole thing done before lunch. Never went back to the manual method for anything at scale after that.
Attachments are not included.
This manual export saves the message body only. Attachments are dropped entirely. If you need attached files alongside the HTML output, the manual method can't deliver.
Multiple dependent files per email.
When you use Outlook's Save As HTML on a single email, it creates a main .html file plus a separate
folder of supporting assets — images, stylesheets, inline resources. The HTML file is not self-contained. Move it
without its asset folder and the formatting breaks. Scale that up to a large archive and you've got hundreds of
folder pairs to manage. It's messy.
Plain text emails are excluded.
The HTML save option only appears for emails composed in HTML or Rich Text format. Plain text messages don't get that option at all.
No folder structure.
The manual method saves individual files with no awareness of where they came from. Inbox, Sent Items, subfolders — none of it carries over. You get a flat pile of HTML files with no organization.
How to Convert PST to HTML (The Fast Method)
For anything at scale, a dedicated converter reads the PST directly and outputs a complete, organized HTML archive without Outlook's single-email limitation.
I've landed on MailExel after trying a few options — it reads the PST directly without needing Outlook on the machine, and on bigger jobs (22 GB recently) it handled it without issue. Folder structure comes through intact on the other end, which matters a lot when you're handing off an archive to someone else.
To follow these steps, you'll need the software installed. Download it below — takes about a minute, then come back and start at Step 1.
Launch the application. Use Add Files to bring in your PST file — or multiple files if you're working with archives from several accounts or time periods. Loading everything together runs more efficiently than separate jobs. Once added, all files appear in the main panel ready for scanning.
Once your files are loaded, the software automatically scans all content in the PST — emails, contacts, calendars, notes, tasks. You don't do anything at this stage. On most archives this completes in a few minutes. Larger PSTs take proportionally longer, but the process runs without any input from you.
Before running the export, check the preview panel. Your folder structure appears with item counts — Inbox, Sent Items, Contacts, and any subfolders. Spend 60 seconds here.
On a compliance project, the client's brief listed three folders to export. The preview showed six. Someone had buried roughly 800 emails in a "Projects" subfolder that nobody on the team had mentioned — or possibly knew about. Checking the preview before I ran the job took about ten seconds. Finding out after delivery would have been a much longer conversation.
In the output settings, choose HTML as the target format. Set a destination folder that's easy to find. If you need self-contained single files rather than the HTML + asset folder structure, check whether your tool offers MHTML output — more on that in the next section.
Start the export. The tool processes all selected folders and writes the HTML output to your destination. A PST with several thousand messages typically finishes in under 10 minutes. Open a few output files in a browser and spot-check formatting before you deliver or import anywhere.
HTML vs. MHTML — Which Output Should You Pick?
Most converters give you a choice at the output step: HTML or MHTML. The formats look similar at a glance but behave very differently, and picking the wrong one creates problems that aren't obvious until you've already done the conversion.
So what's the actual difference?
HTML
creates a main .html file per email plus a separate folder of supporting assets — images, stylesheets,
inline resources. Each HTML file depends on that asset folder to display correctly. Browser-native, editable, but
not self-contained.
MHTML
packages everything — message body and all assets — into one .mhtml file. One file per email, nothing
else needed.
Here's the practical breakdown:
| Output | Best for | Limitation |
|---|---|---|
| HTML | Web display, intranet archives, indexed pages | Multiple files per email — folder pairs must stay together |
| MHTML | Compliance archiving, sharing emails, document platforms | Less editable; some older browsers need a plugin to open |
For most people doing compliance, legal review, or sharing files with external parties — go with MHTML. One file per email, no loose asset folders to manage, and it just works when you send it to someone. If you're building something web-facing that needs to be indexed, HTML is the better fit. But MHTML is the lower-risk default for most archiving jobs.
Worth knowing from testing: if your archive includes emails originally composed in Outlook's Rich Text format, don't assume the HTML output will look right without checking it. I've had layout breaks on those — headers in the wrong place, paragraph spacing completely off. Switch to MHTML and the problem goes away. If you're not sure what format your emails are in, treat any mixed archive as RTF until you verify otherwise.
Common Problems and How to Fix Them
A few issues show up on nearly every PST-to-HTML job. Here's what to watch for.
Inline images are missing or broken.
Almost always the HTML file got separated from its asset
folder — that's just how HTML output works. Each email generates a folder pair, and if you move the
.html file without the accompanying assets folder, the images stop loading. Keep the folder structure
intact when you move files, or just switch to MHTML upfront and you won't have this problem at all.
Email layout looks broken or garbled.
Likely a Rich Text Format source email. Outlook's
proprietary RTF doesn't always translate cleanly to HTML. Switch to MHTML output — it handles RTF emails more
reliably than plain HTML export.
Attachments are missing from the output.
Check your converter settings. Most tools offer a
separate option to export attachments alongside HTML output. If you used Outlook's manual method, attachments are
always excluded — that's a hard limit with no workaround.
Characters appear garbled or show as question marks.
Encoding issue. Make sure your converter
outputs UTF-8. If files look wrong in a browser, check the page encoding (usually under View or the address bar
settings) and force UTF-8.
Fewer emails than expected in the output.
Two things to check. First: was Outlook running when
you exported? A live Outlook instance locks the PST and you'll get incomplete output with zero warning — it just
silently drops records. Close Outlook completely before starting anything. Second: the converter may have only
processed the top-level folder and ignored subfolders. Use the preview panel before running to verify the folder
counts match what you expect.
PST file won't open in Outlook at all.
Before you write it off — try a dedicated converter.
I've seen lightly corrupted PST files that Outlook flat-out refuses to touch get read just fine by a converter. They
access the PST format directly rather than going through Outlook's file handler, so they have more tolerance for
minor damage. Not guaranteed, but worth a ten-minute try before you give up on the archive.
- Close Outlook completely before starting any PST export.
- Work from a copy of the PST, not the live file.
- Check the preview panel and confirm folder and item counts match what you expect.
- Decide HTML or MHTML before running — changing format means re-running the job.
- Open 3-5 output files in a browser and verify formatting before delivering.
- Keep the original PST — the converter writes new files and never modifies the source.
Frequently Asked Questions
Can I convert PST to HTML without Outlook installed?
Yes. A dedicated converter reads the PST file format directly — no Outlook required on the machine. This is one of the main practical advantages over Outlook's manual method. It means you can process archived PST files from old or decommissioned machines without reinstalling Outlook.
Does the HTML output include email attachments?
Outlook's manual Save As → HTML method does not include attachments — they are always dropped. A dedicated converter typically offers an option to export attachments alongside the HTML output; check the output settings before running. For fully self-contained email files with attachments, MHTML format is a better choice.
What is the difference between HTML and MHTML output?
HTML creates a main message file plus a separate folder of supporting assets (images, stylesheets) per email. MHTML packages everything into a single self-contained file. MHTML is generally easier to manage for archiving and sharing. HTML is better suited for web display and scenarios where you need to index or embed the content.
Will the folder structure from my PST be preserved?
Yes, with a dedicated converter. The output folder hierarchy mirrors your PST structure — Inbox, Sent Items, subfolders — so you can navigate the archive the same way you would in Outlook. Outlook's manual one-at-a-time method doesn't preserve folder structure at all.
How long does it take to convert a large PST file to HTML?
A well-optimized converter typically handles several thousand emails in under 10 minutes. A large archive with tens of thousands of messages may take 20–30 minutes. The manual Outlook method has no practical upper bound — it simply never finishes at archive scale.
Wrapping Up
Honestly, PST-to-HTML looks daunting until you've done it once. After that it's just a format decision and a conversion job.
Outlook's manual method is fine for a handful of emails. For anything beyond that — a full mailbox, a compliance archive, a batch of folders — it simply doesn't work at scale. A dedicated converter isn't just more convenient; it's the only way to get the job done in a reasonable amount of time.
Make the HTML vs. MHTML call before you start the job. For archiving and sharing, MHTML is the cleaner choice — one file per email, no folder pairs to track. For web display or indexed archives, go HTML. Get that decision right on the first run and you won't have to do it twice.
Run into a specific problem with your conversion? Drop a question in the comments and I'll help troubleshoot.
