How to Save Webpage to Desktop (Step-by-Step)

When a page matters to you — a recipe, a technical reference, a news article — saving it locally means you have it no matter what happens to the original site. Chrome gives you several ways to do this, from a full offline copy to a clean PDF.

Method 1: Save Page As (Ctrl+S)

This is Chrome’s built-in save dialog and the most direct route to a local copy.

1. Navigate to the page you want to save.
2. Press Ctrl+S on Windows/Linux or Cmd+S on Mac. Alternatively, go to the three-dot menu in the top right and choose Save and share > Save page as.
3. Choose a location on your desktop or in a folder.
4. Open the Format (or Save as type) dropdown. You will see several options.

Format options explained

Webpage, Complete — saves the HTML file and a companion folder (named pagename_files/) containing all images, CSS, and JavaScript. The page renders almost exactly as it does online. You must keep the HTML file and the folder together — move one without the other and the layout breaks.

Webpage, HTML Only — saves just the HTML markup, with no images or stylesheets. The page will look unstyled, but the text content is all there. Useful if you only need the text and want a tiny file.

Webpage, Single File — saves everything (HTML, images, styles) bundled into a single .mhtml file. This format is easy to move, email, or store because it is one file. The tradeoff: .mhtml is a Chromium format, so it opens reliably in Chrome, Edge, and other Chromium-based browsers, but not in Firefox without an extension.

For most people saving pages to refer to later, Webpage, Single File is the most convenient — one file, no companion folder to keep track of.

Method 2: Print to PDF (Ctrl+P)

Saving as PDF converts the page into a portable document that any device can open without a browser.

1. Press Ctrl+P (Cmd+P on Mac) to open the Print dialog.
2. In the Destination dropdown, select Save as PDF.
3. Adjust settings if needed:
   • Layout: Portrait or Landscape.
   • Pages: print a range if you only need part of a long article.
   • More settings > Background graphics: toggle this on to include colored backgrounds and CSS-rendered images.
4. Click Save and choose a location.

PDF works well for anything you want to share with someone who does not have Chrome, or for archiving articles in a format that looks clean in any PDF reader. Videos and interactive elements are not preserved — you get a static visual snapshot.

Method 3: Save a Single Image or Asset

If you only want one image from a page rather than the whole thing:

1. Right-click the image.
2. Choose Save image as.
3. Pick a file name and location.

The same right-click menu lets you Save video as for some HTML5 videos embedded directly in the page (though hosted video services like YouTube block this).

Method 4: Extensions for Single-File HTML

Chrome’s native save dialog has one gap: there is no option to save a true standalone .html file (as opposed to .mhtml). Extensions fill this gap.

SingleFile (available on the Chrome Web Store) bundles the entire page — HTML, images, fonts, styles — into a single .html file you can open in any browser. It is open-source and widely used for archival purposes.

Install it, then click the extension icon on any page to save. The resulting .html file is self-contained and does not require Chrome to open.

Local Copy vs. Bookmark: What Is the Difference?

A bookmark stores the URL — nothing more. It is a few bytes of data. When you click it, Chrome fetches the live page from the server. If the page has moved, changed, or gone offline, the bookmark leads you somewhere broken or useless.

A saved local copy stores the actual content at the moment you saved it. It works offline, forever, regardless of what happens to the original site. The tradeoff is size: a fully saved page can be 2–20 MB depending on the amount of images, while a bookmark is negligible.

Which is right depends on your use case:

What Happens When a Bookmarked Page Goes Away

Saving every page locally is practical for a handful of important articles, but most people accumulate hundreds or thousands of bookmarks over years. Going back and saving each one locally is not realistic.

A different approach for existing bookmarks: Bookmend (a free Chrome extension) monitors your bookmark library for dead links using two checks 48 hours apart before flagging anything. When a page does go down, it offers one-click recovery of the closest Wayback Machine snapshot from near the time you first saved the bookmark. This serves the same purpose as a local copy for bookmarked pages — you can recover the content without having had to pre-emptively save each page yourself.

For pages that are not yet bookmarked and that you know you will need forever, a local save is still the right choice. For the bookmarks you already have, a tool that watches for rot and retrieves archived copies handles the problem at scale.

Troubleshooting Saved Pages That Look Broken

Saved pages sometimes look wrong when opened locally. Here is what typically causes each problem:

Images are missing. You saved using “Webpage, HTML Only”, which strips images. Re-save using “Webpage, Complete” or “Webpage, Single File”.

The HTML file loads but looks unstyled. You moved the .html file without moving its companion _files folder. Both must be in the same directory. Move the folder next to the HTML file and reload.

The .mhtml file opens with a warning. Some browsers or operating systems flag .mhtml files from downloads. In Chrome, the file should still open — click through the warning if one appears. If Chrome refuses, try opening via File > Open File (Ctrl+O) rather than double-clicking.

The page says “This is not available offline.” Some web apps (Gmail, Google Docs, interactive tools) actively resist local saves. Their content is dynamically generated from a server and cannot be fully captured with Ctrl+S. For those pages, PDF is more reliable than an HTML save.

The saved page is from the wrong time. If you saved a page previously and want to update the local copy to reflect the current version, you need to re-save. Chrome’s save overwrites the existing file if you save to the same location and use the same file name.

Choosing a Format: A Decision Guide

The right format depends on what you plan to do with the saved file.

If you need to open it in any browser, on any device: Save as PDF. It is the most universally readable format and does not depend on a specific browser engine.

If you need to open it only in Chrome/Edge and want full fidelity: Use “Webpage, Single File” (.mhtml). One file, no companion folder, full visual accuracy in Chromium browsers.

If you want a standalone HTML file any browser can open: Use the SingleFile extension. The resulting .html file is larger than .mhtml but has no browser compatibility issues.

If you only need the text content: Use “Webpage, HTML Only”. The smallest file, loads fastest, but will look unstyled without CSS.

If you want to share or print: PDF is the right choice. It looks the same for everyone regardless of browser.

Saving Pages with Dynamic Content

Some pages do not render correctly when saved because they load content dynamically from external servers. Examples include:

• Pages that require login (the saved version may show a login screen or truncated content)
• Real-time dashboards with live data
• Web apps where the “page” is actually a shell that loads content via APIs
• Pages with heavy JavaScript rendering that runs after initial load

For these, the best approach is usually a PDF saved at the moment the page is fully loaded. Press Ctrl+P immediately after the page finishes loading and all dynamic content is visible. The PDF captures the visual state at that moment.

If you need to capture the full interactive state of a web app, neither Ctrl+S nor Ctrl+P will fully capture it. Browser automation tools like Puppeteer can take more complete snapshots of dynamically rendered pages, but that is a developer-level workflow.

When to Use Third-Party Archiving Instead

For pages you want to preserve long-term without managing local files, web archiving services offer an alternative. Services like the Wayback Machine (web.archive.org) or archive.today save public pages to their own servers and give you a permanent URL pointing to that snapshot.

This approach has advantages over a local save for some use cases:

• The archive is accessible from any device without transferring a file
• It persists even if your hard drive fails
• You can share the archived URL with others

The limitation is that these services work best with public pages — they cannot archive pages behind logins, and some pages opt out of archiving.

Summary

• Ctrl+S > Webpage, Single File — best for a portable local snapshot you open in Chrome or Edge.
• Ctrl+P > Save as PDF — best for cross-platform sharing, printing, and universal compatibility.
• SingleFile extension — best for a standalone .html file that opens in any browser.
• Right-click > Save image as — for individual assets only.
• archive.today / Wayback Machine — for public pages you want to preserve without managing local files.
• Bookmend — for monitoring and recovering pages you have already bookmarked rather than saving them all locally upfront.