Save Webpage as PDF: Why MHTML Beats Print (2026)
"Save webpage as PDF" usually means one thing for most people: Cmd/Ctrl + P → "Save as PDF". That works for simple articles. For modern sites — pricing pages, dashboards, long-scroll documentation, any page with sticky headers or lazy-loaded images — Print to PDF often produces a broken capture: cropped tables, missing images, ad placeholders, weird page breaks. There's a better way for capturing the page exactly as it renders, and it goes through MHTML.
What is MHTML?
MHTML (MIME HTML) is a single-file web archive format. Where a saved
.html file references images and stylesheets externally, an
.mhtml bundles everything — HTML, CSS, images, fonts — into a single
file. Chromium-based browsers (Chrome, Edge, Brave, Arc) save MHTML natively. Safari's
equivalent is the .webarchive format.
Why MHTML → PDF beats Print to PDF
- The full page, not the print view. Many sites have a
@media printstylesheet that strips navigation, ads, and decorative elements. Sometimes that's what you want; often it isn't. MHTML captures the screen view exactly. - Lazy-loaded images survive. Long pages with infinite-scroll or intersection-observer image loading often print as broken-image placeholders. MHTML waits until the page finishes rendering, then snapshots everything.
- Sticky headers don't duplicate on every page. Print to PDF frequently re-renders sticky navigation on each printed page. MHTML → PDF treats the page as one tall canvas.
- Re-convertible later. The MHTML file itself is durable. You can re-export to PDF with different page sizes or margins without re-loading the original site, which may have changed.
Step-by-step: Chrome / Edge / Brave
- Open the page you want to save.
- Wait for it to fully load — scroll to the bottom and back to the top so any lazy-loaded sections render.
- Cmd/Ctrl + S, then in the save dialog choose
Webpage, Single File. The file extension will be
.mhtml. - Open to-pdf.com/mhtml-to-pdf and drop the file in.
- Click Convert PDF. The page is reconstructed in your browser and exported with proper pagination.
The MHTML → PDF conversion happens in your browser, not on a server. The archive never leaves your device.
Step-by-step: Firefox
Firefox doesn't ship native MHTML save. Two options:
- Install the Save Page WE extension, which exports MHTML.
- Or save the page as a single HTML file (right-click → "Save Page As" → "Web Page, complete"), then drop that into the HTML to PDF tool. You'll lose some image assets if they're loaded from cross-origin URLs, but text and layout will preserve cleanly.
Step-by-step: Safari
Safari saves .webarchive by default, which is its own format. To use
the MHTML pipeline:
- Open the page in Safari.
- File → Save As → choose Web Archive.
- To convert .webarchive to MHTML, the easiest path is to re-open the page in Chrome and save MHTML there. Most users find this faster than installing a Mac conversion tool.
When Print to PDF is actually the right call
Print to PDF still wins for two cases:
- Articles and blog posts. Reader-mode style content where the publisher's print stylesheet is good — newspapers, news magazines, well-designed blogs.
- You need text-selectable output. Browser print produces real PDF text. The MHTML → PDF tool rasterizes for fidelity, so the result is image-based. If searchability matters more than layout fidelity, Print to PDF wins.
Privacy notes
Many "URL to PDF" services (PDFmyURL, html-pdf-node, Browserless, etc.) work by spinning up a headless browser on their servers and visiting your URL on your behalf. That works, but the URL — and any auth cookies you'd need to share to capture a logged-in page — go through someone else's infrastructure. Saving MHTML locally and converting it in your browser keeps both the URL and the page contents private.