How to Save a Webpage: 4 Methods (PDF, HTML, Screenshot, Bookmark)

TL;DR

There are really only four ways to save a webpage: as a PDF, as HTML, as a full-page screenshot, or as a bookmark. PDF is best for sharing and archiving because the file is one thing and everyone can open it. HTML preserves the live layout for offline reading. A screenshot is a picture — no text you can copy, but it is impossible to argue with. A bookmark saves nothing at all; it saves a pointer to a page that may not exist tomorrow. If you want the "just make it work" answer, save as PDF with Convert Web to PDF and stop thinking about it.

TL;DR: pick the format for your use case

Most people asking "how do I save a webpage" have already decided what they want to do with it and just do not know which format matches. So here is the short version, one line per use case:

• You want to email it to someone. PDF. It opens on every device without a browser, no missing images, no rearranged layout.
• You want to read it offline on a flight. Single-file HTML (MHTML). Preserves the actual page — links you can hover, text you can select and resize.
• You want proof for a dispute, a refund, an insurance claim, an HR case, a small-claims filing. PDF, and turn on the "print backgrounds" option so nothing that was on the screen goes missing. Screenshot is a fallback if the site is doing something weird that PDF cannot render.
• You want to post the page on social media or drop it in a Slack thread. Full-page screenshot. A PDF preview looks bad in a chat window. A picture works everywhere.
• You want to come back to it later, someday, maybe. Bookmark. This is the only case where a bookmark is the right answer, and even here the correct move is to also save a PDF if the page is one you actually care about.
• You want it in a folder with other documents about the same topic — a school project, a research binder, a lawsuit file. PDF. It is the only format that behaves like the other files in that folder.

There is no format that wins at all six of those. That is the whole reason this article exists — people keep saving webpages in the wrong format and then getting frustrated when the file will not do the thing they need. Pick from the use case, not from the tool. If you are still not sure, default to PDF; it is wrong the least often.

Option 1: Save as PDF (best for sharing)

PDF is the default answer for most people because it is the only format that behaves like a document. Someone can open it in email, on their phone, on Windows, on a Mac, printed on paper, and see the same thing. No file that got separated from its images. No JavaScript that will not run. No rearrangement.

How to do it, native browser: Chrome, Edge, Safari, and Firefox all have "Print" in the browser menu (or Cmd/Ctrl+P), and every one of them offers "Save as PDF" as a fake printer. This works. It is also awkward — headers and footers you did not ask for, cookie banners frozen on top of the page, images that only loaded halfway because the print dialog cut them off, ads captured mid-scroll. On long pages it splits paragraphs across page breaks in the wrong places.

How to do it, extension: an extension made for this (Convert Web to PDF is one; others exist) waits for the whole page to render, scrolls through lazy-loaded images, strips headers and footers, and hands you a file. If you save webpages often, install one and stop thinking about it. If you save them once a year, native print is fine.

Gotchas to know about:

• Pages with infinite scroll (Twitter/X, TikTok, LinkedIn feeds) will not save as a single PDF from print — they only capture what the browser has loaded. Extensions that scroll the page first do better here. See save the full scrolling page for a walkthrough.
• Pages behind logins save fine as long as you are logged in when you save.
• Pages with dark backgrounds sometimes print white. Toggle "background graphics" in the print dialog if the result looks wrong. Chrome native has walkthrough here: save a webpage as PDF in Chrome.
• Pages heavy in web fonts sometimes swap to a generic system font in the PDF. Usually the readable body text is fine and only a stylized headline changes.

If the point is to share the saved page with a human, or file it with other documents, or send it to a printer — PDF. There is no better default.

Option 2: Save as HTML (best for offline reading)

Every browser has "Save Page As... Web Page, Complete" (Ctrl+S on Windows, Cmd+S on Mac). This gives you a .html file plus a folder of assets — CSS, images, fonts. The folder next to the HTML file is not optional; if you move the file without the folder it breaks. The two travel together like a two-piece luggage set.

The upside of HTML is that you have the actual page back. Text is real text you can select, copy, search with browser Find. Links still hover. Layout responds to your window size. It is the closest you get to keeping the page alive.

The downside is fragility. Move the file, delete the folder, share only the HTML — it breaks. Zip it up before sending, or use single-file HTML (see MHTML below) to avoid the folder.

When "Save As HTML" is the right call:

• You are reading long-form articles offline on a flight and want text you can select, resize, and annotate in your browser.
• You are archiving a page to your own hard drive for research and you want to be able to search across it with the same tools you use for the rest of your files.
• You want the page to remain interactive — internal anchor links still jump, tables of contents still work, expandable sections still expand.

When it is the wrong call:

• You want to send the page to anyone else. Send a PDF instead — one file, no fuss, no missing folder.
• You want to file it as evidence or as part of a records-keeping workflow. PDF is what those workflows expect.
• You want to open it on your phone. Mobile browsers do not handle downloaded HTML files gracefully.

There is a subtler gotcha. Pages that render most of their content with JavaScript after load — modern React apps, single-page apps, most social media, most dashboards — save as an empty shell. The HTML file has the skeleton, none of the content. If Save As gives you a page that looks blank when you reopen it, that is why. For those pages, save as PDF instead — the browser renders the page first and then prints, so the content is already there when the PDF gets made.

Option 3: Full-page screenshot (best for social)

A screenshot is a picture of the page. That is it. No selectable text, no clickable links, no live layout — one long PNG or JPG. What you get in return is that a screenshot is impossible to break. There is no dependent folder, no font that could fail to load, no cookie banner that could pop back in later. Whatever you saw, that is what the file has.

Chrome has full-page screenshots built in through DevTools (F12 → Cmd/Ctrl+Shift+P → "full size screenshot"). Firefox has it in the context menu. Safari can do it through the Web Inspector. Extensions like GoFullPage do the same thing without the DevTools detour.

When a screenshot is the right call:

• You are posting to social media. A PDF preview looks terrible in a tweet or a LinkedIn post; an image looks fine.
• You are pasting into a chat — Slack, Discord, iMessage, WhatsApp. Images render inline. PDFs do not.
• The page has some weirdness that neither PDF nor HTML captures correctly — a stylized layout, an animation frozen at a certain moment, a modal that only appears in a specific state. A screenshot captures whatever state you were in.
• You want a fully self-contained thing you can send to anyone without them needing any specific app.

When it is the wrong call:

• You need to copy text out of it later. You can't. Some OS-level OCR can extract text from images now, but it is fragile and not something you want to depend on.
• The page is very long. Full-page screenshots of long pages become giant image files — several megabytes for a typical article, tens of megabytes for a long thread or feed. Email attachments start rejecting.
• You need to send it as evidence. PDFs are legally more familiar as document format than image files.

Screenshot is the format nobody thinks of first but that solves a specific real problem — showing someone what a page looks like right now, in a format that will render inline anywhere you paste it.

Option 4: MHTML single-file archive

MHTML (sometimes MHT) is HTML plus all its assets — images, CSS, fonts — packed into one file. Same idea as "Save As Web Page, Complete" but without the sidecar folder. You get a single file you can email, move, drop into a folder without breaking anything.

Chrome, Edge, and Opera can save and open MHTML natively. Turn it on in Chrome by visiting chrome://flags, searching for "Save Page as MHTML", and enabling it (some versions of Chrome have it on by default). Then Save Page As... and pick "Webpage, Single File" from the format dropdown.

Firefox and Safari do not save MHTML out of the box. Firefox needs an extension. Safari uses a similar-but-different format called Web Archive (.webarchive) that only Safari can open — which is fine if the file will only ever live on Macs, and a problem if you send it anywhere else.

When MHTML is the right call:

• You want the benefits of saved HTML (real text, real layout, live-ish interactivity) but without managing a folder alongside the file.
• You are archiving pages for your own use and you trust that your future self will still have Chrome or Edge to open them.
• You are working inside an organization that has standardized on Edge or Chrome and you want a single-file archive format everyone can open.

When it is the wrong call:

• You need to open the file on iOS, in Firefox, in Safari, or in any environment you do not control. MHTML is not universal. PDF is.
• You need to preserve the page as legal evidence. MHTML is not what courts, insurers, or auditors ask for.
• The page uses heavy JavaScript to render content. Same problem as plain HTML — the saved file captures the shell, not the rendered content.

MHTML is the underrated format. Nobody talks about it, but it solves the exact "HTML but without a folder" problem that trips people up when they try "Save Page Complete." If you are Chrome-only and archiving for yourself, it is genuinely a good option. If your file is going anywhere else, save a PDF.

Comparison table (10 rows)

Read this table with the use case in mind, not top-to-bottom. If your top row is "email to a colleague," you are stopping at PDF. If your top row is "make it show up nicely in a Slack thread," you are stopping at Screenshot. If your top row is "I want the actual page for offline reading and I only use Chrome," you are stopping at MHTML.

Which method for research, receipts, evidence, offline

Rules by use case, since this is where people get most confused:

Research (building a library of pages on a topic): Save as PDF. Put them in a folder named after the topic. This works because PDFs behave like other documents in the folder — same search, same preview, same file operations — and because most PDF viewers highlight and annotate. If the pages are long and rich, consider saving as HTML instead so you can pull structured data out later, but PDF is the default for research where the point is reading and referencing, not reprocessing. Related: save research papers from the web as PDF.

Receipts (orders, transactions, subscriptions, invoices): Save as PDF. Always PDF. Every accounting workflow, every tax preparer, every finance department expects a PDF. Screenshots are also acceptable but harder to file. HTML is worse than either. Guide: save online receipts as PDF.

Evidence (disputes, HR cases, small-claims filings, insurance claims, warranty complaints): Save as PDF with backgrounds enabled, and take a full-page screenshot as backup. The PDF is the file you send; the screenshot is proof of what the page looked like if anyone questions the PDF. Include the URL and the date/time in the file — most save-to-PDF tools do this automatically in the footer. Related: capture a webpage as evidence, honestly.

Offline reading: Save as HTML or MHTML if you want the actual page. Save as PDF if you want something that looks the same everywhere and reads well on a Kindle, e-reader, or tablet. For a flight, most people are better served by PDF because it renders more reliably in the reader apps preinstalled on tablets and phones.

Sharing on social / posting in chat: Full-page screenshot. This is what feels right when you actually try it in a chat window.

Bookmarks: Save as bookmark if the page is likely to remain the same for the next few years and you just want a shortcut back. Save the page (any of the above) if the page might change, might disappear, or might get updated behind you. Websites change. Whole sites go dark. If it matters, do not trust that it will still be there tomorrow. See the best way to archive webpages for how to think about this.

Frequently asked questions

What's the best format to save a webpage in?

For most people, most of the time: PDF. PDF is one file, opens everywhere, preserves layout, and is what every professional workflow expects. The exception is when you are posting to social media or dropping the page into a chat window, in which case a full-page screenshot is better because it renders inline. HTML and MHTML are useful for offline reading on your own devices when you want the actual live page, but they do not travel well to other people.

How do I save a webpage as HTML?

In any desktop browser, press Ctrl+S (Windows) or Cmd+S (Mac). You will see a dialog with a "Save As" or format dropdown. Pick "Webpage, Complete" for HTML plus a folder of assets, or "Webpage, Single File" in Chrome/Edge for MHTML. Save both the HTML file and the folder next to each other — moving one without the other breaks the page. If the page uses heavy JavaScript to render content, "Save As HTML" will capture only the empty shell, so save as PDF instead in that case.

How do I save a webpage as a screenshot?

In Chrome, press F12 to open DevTools, then Cmd/Ctrl+Shift+P and type "full size screenshot" — pick it from the menu. In Firefox, right-click anywhere on the page and choose "Take Screenshot," then click "Save full page." In Safari, use Develop → Show Web Inspector, then right-click the top HTML element and pick "Capture Screenshot." Or install a dedicated extension like GoFullPage that scrolls the page automatically and hands you a single PNG.

How do I save a webpage for offline reading?

Two good options. PDF is more portable — it will open on any device without a browser, renders reliably in e-readers and tablet reader apps, and travels between devices without breaking. Save-as-HTML or MHTML gives you the live page — selectable text at any size, working internal links, responsive layout — but only on desktops with a browser and only if you keep the file's folder alongside it. Choose PDF for a flight or a Kindle; choose HTML for browsing your own archive on a laptop.

What is MHTML and should I use it?

MHTML is HTML packaged into a single file — all the CSS, images, and fonts bundled inside one archive with a .mhtml extension. Chrome and Edge open MHTML files natively; Firefox and Safari do not. Use it if you save a lot of webpages, you only use Chrome or Edge, and you dislike managing folders. Do not use it if you need to share the file with anyone outside your own devices, or if you need long-term archival — MHTML is not a widely supported archival format, and there is no guarantee Chrome will open it in ten years. For anything you might share or need to keep permanently, use PDF.

Bottom line

Four formats, four use cases. PDF for sharing, filing, and evidence. HTML for offline reading of live pages on your own devices. MHTML for the same thing without the folder if you live in Chrome or Edge. Full-page screenshot for social posts and chat threads where the file needs to render inline as a picture. Bookmark for nothing except a shortcut back to a page you trust will still exist.

Default to PDF when you are not sure. It is the format that is wrong the least often. If you save webpages more than once a month, install Convert Web to PDF or the convert-web-to-pdf tool — it does the boring parts (waiting for lazy images, stripping headers and footers, handling long scrolling pages) so you do not have to think about them.