A webpage transfers to a laptop as a file while a crossed-out Wi-Fi symbol signals no internet connection.
Chrome's Ctrl+S feels like a safety net until the day you open the saved page offline and find half of it missing. MakeUseOf writer Afam Onyimadu describes that experience in a new piece. He says he swapped Chrome's built-in page saving for a free extension called SingleFile. Here is what the claim means, what the tool does, and where it stops.

A webpage transfers to a laptop as a file while a crossed-out Wi-Fi symbol signals no internet connection. Why a "complete" save can still come apart​

Chrome's menu path for saving a page is documented in Google's help pages. You choose More, then More Tools, then Save Page As. That is the same dialog Ctrl+S opens.

The weak spot is the "Webpage, Complete" format. Onyimadu explains that Chrome writes one HTML file and drops images, styles and other assets into a companion folder. If the HTML file is moved or emailed without that folder, the references break. This matches Chromium's own design: in Complete HTML mode it saves resources separately, while HTML Only produces just the HTML.

Onyimadu reports two failures of this kind:

  • A recipe page that lost photos partway down when reopened offline.
  • A forum page that lost part of its layout and some images.

Treat these as anecdotes. He gives no browser version, URLs or repeatable test method. He also says Chrome's saving "will work flawlessly most of the time." The structural risk is real, but the frequency of failures is not measured.

What SingleFile does differently​

SingleFile is an open-source extension, with a command-line tool as well. The Chrome Web Store listing says it saves a complete page, including CSS, images, fonts and frames, as one HTML file. The project's GitHub page says it works with Chrome, Firefox, Edge, Safari, Vivaldi, Brave, Opera and other browsers.

You get one portable file instead of a file plus a folder. It opens in any browser, with no extension needed to view it.

How to use it​

  1. Install SingleFile from the Chrome Web Store.
  2. Open the page you want and wait until it has fully loaded.
  3. Click the SingleFile toolbar button. Clicking it again while a page is processing cancels the save.
  4. Find the saved HTML file in your browser's download folder, which is the default destination.
  5. Test the copy with Wi-Fi off before you rely on it.

Onyimadu suggests pinning the icon from Chrome's puzzle-piece menu. That is a convenience, not a requirement.

Useful extras​

  • Right-click menu. It lets you save the current tab, the selected content, the selected frame or selected links.
  • Annotation. "Annotate and save the page..." lets you highlight text, add notes and remove content before saving.
  • Multiple tabs. You can process the selected tabs, the unpinned tabs or all tabs in one click.
  • Shortcut. Ctrl+Shift+Y saves the current or selected tabs, and you can change it at chrome://extensions/shortcuts. Check that page if the shortcut clashes with another command.
  • Upload destinations. The listing says the options page's Destination section supports Google Drive, Dropbox, GitHub and WebDAV. Onyimadu points to Google Drive as a way to keep your Downloads folder from filling with HTML files. Local saving needs none of this.

The author's comparison, and how far to trust it​

Onyimadu compares four approaches: Chrome Complete, Chrome HTML Only, PDF and SingleFile. In his tests, SingleFile gave a single file that opened offline, looked like the original and kept images lower down the page. Chrome Complete and PDF were less consistent. These are his observations on his own pages, not a benchmark.

He also says SingleFile strips scripts by default. As a result, menus and carousels don't work, and you get a static snapshot. The sources I found don't confirm that default for every version or configuration. A 2018 gHacks review noted that the options page lets you enable saving scripts and other resources, so check your installed version's options.

PDF is a separate trade-off. He says it chops long articles into print-sized sheets, while a SingleFile copy stays one long scroll. How good a PDF looks depends on the page and your print settings.

Limits to know before you rely on it​

  • Protected pages. The project's known-issues list says that for security reasons you can't save pages hosted on Chrome's own web store domain and some Mozilla domains. A blocked-page icon appears over the toolbar button when that happens. Onyimadu also warns that extensions don't work on some protected pages.
  • Canvas and video. The project lists known issues. The earlier README also says SingleFile sometimes can't save the image form of canvas elements or snapshots of video elements.
  • Heavy pages. Onyimadu says very heavy pages can take a while on older laptops. He gives no figures.
  • File names. The project says certain characters in page titles, such as colons and question marks, are replaced with underscores.
  • Saved files you open from disk. For viewing and annotating a saved file on your filesystem in Chrome, the project says you must enable "Allow access to file URLs" for the extension.

When saving a page beats bookmarking​

Onyimadu's practical point is that a bookmark stores only an address, and the page behind it can change. He saves copies of:

  • Product pages on the day he buys something expensive.
  • Return policies, which can be reworded without notice.
  • Booking confirmations and boarding passes, in case airport Wi-Fi fails.
  • Recipes, which get redesigned or deleted.

He also warns that a saved HTML file is not proof of what a page said. Anyone can edit it. For a public page where he wants an outside timestamp, he uses the Wayback Machine's Save Page Now. I haven't verified that service's capture behavior here, so treat it as a separate archiving option, not legal evidence.

SingleFile's listing mentions an optional "add proof of existence" setting that links a page's SHA256 hash into a blockchain. That is an extra feature, not a substitute for caution.

Bottom line​

SingleFile fixes a specific problem. It keeps a saved page in one file that is easier to move, email or archive than Chrome's HTML-plus-folder arrangement. The Chrome Web Store listing shows a roughly 4.7 rating across 1.1K ratings. It also shows version 1.31.4, updated in October 2026.

It won't preserve interactivity by default. It won't work on every protected page. A saved copy is not an authoritative record. Test your first few saves offline, especially for pages you can't afford to lose.

 

References

  1. Chrome's Save Page feature isn't enough, but this extension is - MakeUseOf MakeUseOf 2026-10-25T15:00:17+00:00
  2. GitHub - gildas-lormeau/SingleFile: Web Extension for saving a faithful copy of a complete web page in a single HTML file · GitHub github.com
  3. Download a file - Computer - Google Chrome Help support.google.com