MHTML vs PDF: Which Format Actually Preserves a Webpage?

TL;DR

MHTML preserves the webpage as a webpage — a single file that still contains HTML, CSS, and images, opens in a browser, and lets you copy text out of live DOM. PDF preserves the webpage as a document — a fixed-layout file that looks the same in ten years, opens in almost anything, and stays legible even when the original site is gone. Use MHTML when you need to inspect the source later or keep interactive elements. Use PDF when you need something that will still open, print, and read cleanly in 2036 — and something a lawyer, a manager, or a school portal will actually accept. If you want a fast way to turn any page into a clean archival PDF, Convert Anything to PDF handles it in one click.

What each format is

MHTML stands for MIME HTML. It is a webpage archive format that bundles the HTML, CSS, JavaScript, and inline images of a page into a single MIME-encoded file with a .mhtml or .mht extension. Microsoft introduced it for Internet Explorer in the late 1990s. Chrome, Edge, and Opera still write it today; Firefox and Safari do not.

Open an MHTML file in Chrome and you get something very close to the original page — the layout is preserved, the images are embedded, and the text is still selectable as HTML text. Under the hood it is just a text file with a MIME envelope, the same way an email with attachments is packaged. You can open one in a code editor and see the raw HTML.

PDF stands for Portable Document Format. Adobe created it in 1993 to solve exactly the problem MHTML tries to solve, but from the opposite direction: instead of preserving a webpage as a webpage, PDF preserves it as a printable document. The layout is fixed. Fonts are embedded. Every reader — browser, phone, Kindle, printer, court filing system — renders it the same way.

The trade-off is baked into that difference. MHTML keeps the page alive as a document you can still interact with (scroll infinitely, click anchor links, copy from tables that live in DOM). PDF freezes the page into pages — literal 8.5x11 or A4 sheets — so scrolling feeds, dynamic content, and hover states disappear.

That's the whole distinction. Everything below is a consequence of it.

Head-to-head comparison (10 rows)

Two rows do most of the work in a real decision.

The legal / court acceptance row is why lawyers, HR, and finance almost never touch MHTML. A landlord who wants to submit a Zillow listing as evidence, a plaintiff attaching a scraped Terms of Service page, a compliance officer filing a screenshot — all of them need PDF, not MHTML, because that's what the receiving system is built to accept.

The layout drift row is why archivists have moved toward WARC and PDF/A rather than MHTML. An MHTML file from 2010 that used a since-deprecated CSS property may render broken today. A PDF from 2010 renders identically to how it did on the day it was saved.

Pick MHTML when...

You need to inspect the source later. If you're archiving a page because you might need to look at the HTML — a competitor's markup, a page you scraped, a template you want to reuse — MHTML preserves the machine-readable structure. Open it in a text editor and everything is there.

You need working links inside the page. MHTML preserves internal anchor links, so a table of contents at the top of a long article still jumps to the right section. In a PDF, internal links only survive if the converter explicitly wrote them.

You're archiving for personal reference and you use Chrome. For "I want to look at this later on the same machine," MHTML in Chrome is fine. The file is a single artifact, images are embedded, layout matches the original.

You're preserving a page with interactive elements you want to keep functional. Expand/collapse sections, tabbed content, sortable tables — these still work in MHTML (as long as their JavaScript doesn't depend on external network calls). In PDF, they render frozen in whatever state they were in when the page was saved.

You need to convert to HTML later. MHTML unpacks cleanly back into HTML + assets. If you might want to republish, re-render, or feed the content into a static site generator, MHTML is the friendlier starting point.

The catch: MHTML is a fading format. Safari never supported it. Firefox dropped native support years ago. Chrome still writes it but has quietly deprioritized the feature — the flag to enable saving as MHTML has moved locations several times. Betting a long-term archive on MHTML is betting that Chrome will still write and read it in 2036.

Pick PDF when...

You need someone else to open it. PDF is the closest thing computing has to a universal document format. Anyone with a phone, laptop, or e-reader can open it. No format anxiety, no "sorry, my browser doesn't do that."

You're archiving for evidence, compliance, or records. Courts, insurance companies, tax authorities, HR departments, and school portals all accept PDF and often require it. MHTML is treated as an unknown file type. See our guide on capturing webpages as evidence for the practical constraints.

You need long-term readability. PDF renderers are extraordinarily backward compatible. A PDF from 1994 opens today. An MHTML from 2010 might render broken because a CSS property changed. If you're archiving something you want to open in 2036 or 2046, PDF is the safer bet — and PDF/A (a formal archival subset) is safer still.

You need to print it. PDF is a print-oriented format by design. Page breaks, margins, headers, footers — all handled cleanly. MHTML prints whatever the browser renders, which often includes navigation chrome, ads, and layout artifacts.

You want the file to be searchable across your whole system. Spotlight on macOS, Windows Search, and every document management system indexes PDF text natively. MHTML often isn't indexed at all.

You want to share it in Slack, WhatsApp, or email without the recipient asking "what is this file?" Try attaching an .mhtml to a Gmail message and watch what happens.

If you archive a lot of pages this way, our roundup of the best web-to-PDF Chrome extensions covers the current landscape.

Convert between them

MHTML to PDF. Open the MHTML file in Chrome (drag it onto a tab, or File > Open File). Press Cmd+P / Ctrl+P. Choose "Save as PDF" in the destination dropdown. Save. You now have a PDF of the archived page. The layout will be slightly different — Chrome re-renders the page for print, so navigation, some styling, and any element with a display: none in print CSS will drop out.

PDF to MHTML. There is no clean path. PDF is a fixed-layout format — the source HTML is gone. You can extract text and images from a PDF and rebuild an HTML file, but you're not reconstructing the original MHTML. If you need the source HTML, save the page as MHTML at capture time, not later.

Webpage directly to either. For MHTML in Chrome, enable "Save Page as MHTML" in chrome://flags (or use the built-in File > Save Page As and pick "Webpage, Single File"). For PDF, Chrome's built-in Cmd+P > Save as PDF works, but it often includes ads, cookie banners, and navigation chrome. A dedicated tool like Convert Anything to PDF strips the noise and produces a cleaner archive.

Which conversion to skip. Don't convert MHTML → PDF → back to HTML expecting to recover the original page. Each conversion loses information. If you'll need both formats, capture the page twice at source — once as MHTML, once as PDF — rather than converting between them.

For a broader comparison of archiving approaches, see our guide to the best way to archive webpages.

Frequently asked questions

What is MHTML?

MHTML — MIME HTML — is a webpage archive format that packages a page's HTML, CSS, JavaScript, and inline images into a single MIME-encoded file. Microsoft introduced it in the late 1990s so Internet Explorer users could save a page as one file instead of the messy "webpage folder plus HTML file" that Netscape produced. Today Chrome, Edge, and Opera still support it natively. The file extension is .mhtml or .mht. Open one in a text editor and you'll see it looks a lot like a multipart email — because it uses the same MIME envelope format that email attachments do.

Is MHTML better than PDF for archiving?

For most people, no. MHTML preserves more of the original page (source HTML, interactive elements) but at the cost of universal compatibility and long-term stability. PDF opens on every device, every OS, and every year — the format is so backward compatible that PDFs from the 1990s open cleanly in 2026. If your archive needs to survive browser deprecations, be accepted by legal or compliance systems, or open on a family member's iPhone, PDF wins. If you need the source HTML for technical reasons, MHTML makes sense — but keep a PDF copy alongside it as insurance.

Does Chrome save MHTML by default?

No. Chrome's default "Save Page As" produces two options: "Webpage, Complete" (an HTML file plus a folder of assets) and "Webpage, Single File" (which is MHTML). Most users pick Complete without realizing Single File exists. To make MHTML the default and expose more options, visit chrome://flags and enable "Save Page as MHTML." Even then, Chrome has quietly deprioritized MHTML over the years — the flag has moved locations several times, and it wouldn't be surprising if the feature is removed entirely in a future release.

Can I convert MHTML to PDF?

Yes, easily. Open the .mhtml file in Chrome by dragging it onto a browser tab or using File > Open File. Press Cmd+P (Mac) or Ctrl+P (Windows) to open the print dialog. In the destination dropdown, choose "Save as PDF." Save. The output is a standard PDF that will open anywhere. The layout may shift slightly because Chrome re-renders the page for print — sidebars often drop out, and any styling that uses @media print rules will take effect. For higher-quality conversion that preserves the on-screen layout, use a dedicated tool.

MHTML vs single-file HTML — what's different?

Single-file HTML embeds all assets (images, CSS, fonts) directly into the HTML using base64 data URIs. It's a normal .html file that happens to be self-contained. MHTML uses a different approach: a MIME multipart envelope wraps separate HTML, CSS, and image parts inside one file, similar to how an email packages attachments. The practical difference: single-file HTML opens in every browser (Firefox and Safari included) because it's still just HTML. MHTML only opens natively in Chrome, Edge, and Opera. For portability, single-file HTML is the better modern choice — but Chrome still saves MHTML by default when you pick "Single File" in the save dialog.

Bottom line

MHTML and PDF solve the same problem from opposite directions. MHTML keeps a webpage as a webpage — inspectable, interactive, and readable in Chrome. PDF keeps a webpage as a document — universal, stable, and accepted by every system that handles paperwork. For technical archiving where you might need the source later, MHTML has a niche. For everything else — evidence, compliance, sharing, long-term storage, cross-device readability — PDF is the safer format. If you save a lot of pages, do it in PDF and don't look back. Convert Anything to PDF turns any page into a clean PDF in one click, no format anxiety required.