Save Page WE: How to Save a Web Page as a Single HTML File in Firefox and Chrome
Save Page WE is a free browser extension by DW-dev that saves a complete web page, as it currently looks on screen, into one HTML file. Images, CSS, fonts and other resources are embedded in that file, so there is no extra "_files" folder. Install it from Firefox Add-ons or the Chrome Web Store, click the floppy disk toolbar button or press Alt+A, and the page downloads as a single .html file that opens in any browser.
This guide covers where to get the official extension for Firefox and Chrome, how to save pages with it, what the Basic, Standard and Custom options do, how it compares with the browser's own Save Page As, and when SingleFile is the better pick.

What is Save Page WE?
Save Page WE is a web extension that turns a live web page into a single self-contained HTML file. The developer describes the result as a page saved "as currently displayed", which means content that loaded after scripts ran, such as logos, icons and lazy-loaded images, ends up in the file as well.
The extension is published by DW-dev, the same developer behind Print Edit WE, and the two work together: Save Page WE needs Print Edit WE 26.1 or later for full compatibility if you edit a page before saving it. The Firefox version is licensed under the GNU General Public License v2.0. Neither store listing links to a source code repository or a project homepage, and support runs through an email address on the listing, which explains the many "save page we official website" searches: the official home of the extension is its store pages.
| Store | Latest version | Users and rating |
|---|---|---|
| Chrome Web Store | 33.9 (September 5, 2023), Featured badge | 200,000 users, 4.6 out of 5 |
| Firefox Add-ons | 28.11 (March 31, 2023), Firefox 52 and later | About 20,000 users, 4.4 out of 5 |
Note that the two builds are on different version numbers and neither has received an update since 2023.
How to download Save Page WE for Firefox and Chrome
Save Page WE is only distributed through the official browser stores, so install it from there and avoid third-party download sites that repackage extensions.
- Firefox: open the Save Page WE listing on Firefox Add-ons and click Add to Firefox.
- Chrome: open the Save Page WE listing in the Chrome Web Store and click Add to Chrome. Other Chromium browsers that accept Chrome Web Store extensions, such as Microsoft Edge (after allowing extensions from other stores) and Brave, use the same listing.
- Review the permission prompt. The extension asks to access data for all websites, access tabs and browser activity during navigation, manage downloads and display notifications. It needs these to read the page and write the file, but it is the reason to install only the official listing.
- Pin the blue floppy disk button to the toolbar so it is one click away.
Check the developer name on the listing before installing: it should read DW-dev.
How to save a web page as a single HTML file with Save Page WE
Saving a page with Save Page WE takes one click on the toolbar button or the Alt+A keyboard shortcut.
- Open the page you want to keep and let it load fully. Scroll down once on long pages so lazy-loaded images appear; the extension also has options to load lazy content automatically.
- Click the floppy disk button or press Alt+A. A badge on the button shows progress while resources are packed into the file.
- Choose a location in the download dialog, or let the file save to your downloads folder, depending on the save method set in the options.
- Press Alt+C if you want to cancel a save that is taking too long.
- Open the .html file in any desktop or mobile browser to read it offline.

To save several pages at once, select multiple tabs (Ctrl+click on the tab bar) before clicking the button, or paste a list of URLs into the extension's options. Saved files can be named automatically from fields such as the page title, date, time, host and path, which keeps a large offline archive sorted. An automation mode can also save pages from the command line, closing the browser when the save finishes.
Save Page WE options: Basic, Standard and Custom items
Save Page WE offers three item sets that decide how much of a page goes into the file, picked from the right-click menu of the toolbar button.

- Basic Items: the HTML, CSS, images and fonts. This is the smallest file and is enough for articles and documentation.
- Standard Items: everything in Basic plus HTML audio, video, objects and embedded files. Use it when media is part of what you want to keep, and expect larger files.
- Custom Items: you pick which resource types to include in the options page.
The options page (Firefox: Add-ons and themes, then the extension's Options; Chrome: right-click the button and choose Options) also sets the default button action, the file name format, the save method and the keyboard shortcuts. Two save methods exist: the old one remembers the last save location but can fail on some pages, while the new one can save all pages but does not remember the location. In the Chrome build, version 33.9 selects between them automatically.

Save Page WE works alongside content blockers such as uBlock Origin, so ads that were blocked on screen are not saved. If you strip clutter first with an element picker, as described in our guide to removing page elements permanently with uBlock Origin, the saved copy is cleaner and smaller. For saved pages, the context menu adds View Saved Page Info and Extract Image/Audio/Video, which pull the embedded media back out of the HTML file.
Save Page WE vs the browser's Save Page As
Save Page WE produces one file that looks like the live page, while the built-in Save Page As in Firefox, Chrome and Edge (Ctrl+S, or Cmd+S on a Mac) usually produces an HTML file plus a folder of resources.
Firefox's own Save Page As has two relevant modes. "Web page, complete" saves pictures and supporting files into a separate folder and may not keep the original link structure. "Web page, HTML only" is a single file but saves the page without pictures.

In ghacks' original 2020 test with a Wikipedia article, Firefox's complete mode produced 17 files (one HTML file plus a folder of 16), and the offline copy was missing the favicon, the Wikipedia logo, the language icon and the user icon. The Save Page WE copy was one file with all of them in place.

| Criterion | Save Page WE | Browser Save Page As (complete) |
|---|---|---|
| Output | One .html file | HTML file plus resource folder |
| Dynamic content | Saved as displayed | Often missing |
| Sharing and renaming | Send or rename one file | Folder must travel with the file |
| Install needed | Yes, extension | No |
Does Save Page WE make files bigger?
Save Page WE files are sometimes smaller and sometimes much larger than the browser's own save, because every resource is embedded inside the HTML as encoded data.
In the 2020 test, the extension beat Firefox's built-in tool by a small margin on one page.

On another, image-heavy page, Save Page WE wrote a 13 MB file while Firefox kept its copy under 3 MB.

To keep files small, use Basic Items instead of Standard, block ads before saving and skip pages dominated by video.
Save Page WE vs SingleFile: which should you use?
SingleFile is the stronger choice for most people today, while Save Page WE remains a solid option if you already use it or rely on Print Edit WE.
Both extensions save a complete page into one HTML file. The difference is maintenance and transparency. SingleFile by Gildas Lormeau is open source on GitHub, has about 700,000 Chrome users and received version 1.31.4 on October 19, 2026. Save Page WE has no public repository and has not been updated since 2023 in either store.
- Pick SingleFile if you want active updates, auditable code and the best chance of handling new site designs. Our SingleFile overview covers its features.
- Pick Save Page WE if you need its Basic, Standard and Custom item sets, its command-line automation mode or its integration with Print Edit WE.
- Use the browser's built-in save if you only need the text of a page and do not want another extension with access to all sites.
For more vetted add-ons, see our lists of the best Firefox add-ons and the best Chrome extensions.
FAQ
Is Save Page WE safe?
Save Page WE has a Featured badge in the Chrome Web Store and about 900 ratings across the two stores, but its code is not published in a public repository. Install it only from the official store listings by DW-dev and remove it if you no longer use it.
Does Save Page WE work on Firefox for Android?
The Firefox Add-ons listing does not state Android support. Treat it as a desktop extension and open the saved HTML files on your phone instead.
Can I change the Alt+A shortcut?
Yes. The save (Alt+A) and cancel (Alt+C) shortcuts can be changed in the extension's options or in the browser's extension shortcut settings.
Does Save Page WE save MHTML files?
No. It saves standard .html files with resources embedded, which open in any browser without MHTML support.
Related: Save any webpage as a single file, Save WebP images as JPG or PNG in Firefox, Best Firefox add-ons
Several replies have mentioned saving as PDF (I find the Opera version the best as it generates a single PDF page that is equivalent size to the HTML page, as opposed to some others which split the PDF into several pages, like a printer would).
However, converting to a PDF can lose content that can be otherwise saved – such as a frame that has scrollable content. Save to PDF only saves the visible portion of the frame (like a screenshot in some ways), whereas the HTML savers retain the scroll-ability of the frame.
Save page WE is very good, but does “lock” up sometimes (a dialog box appears where you can’t cancel and you can’t continue) [Firefox BTW, haven’t tried Chrome]. To escape I have to close the tab. No solution as yet… After reading this site I’m going to try SingleFile.
Hi. I have been using save page we extension and it has been great.It has suddenly stopped working at all on edge. When I click on the icon nothing happens. It still works in my chrome. How do i fix this in edge. Thanks.
There’s a similar extension that saves web pages to your email. It also saves a PDF copy of each web page
https://chrome.google.com/webstore/detail/email-this/lgblkllcjgihfnlefhnnpppndbbjallh
“Warning: I couldn’t find the source code ”
about:support > Profile Folder > “Open Folder” > extensions > [email protected]
Opera browser can do this action for years (HTML only, single page,complete) and also can save as a .pdf. Also has a built-in vpn (by-passes banned access to wikipedia)
its always nice to be able to see the source code (even if i cant understand it fully) but especially when its a browser extension. you really cant be too careful these days. even supposedly reputable companies are now data mining like their life depended on it. that is why i would go with SingleFile over Save Page WE
Where is the supposedly recorded url in the saved page ? Where is the “i” icon ? I can’t see either.
That question is pertaining to Single File.
I’ve found it : you need to enable “Allow access to file URLs” in the extensions permissions. Apparently, it’s not enabled by default. Weird.
Why would you want to use a not recommended extension? Just use SingleFile
Tried them both, prefer SingleFile.
SingleFile FTW. I haven’t come across a single webpage with it that couldn’t be saved exactly as it was rendered without missing out on any images or any elements.
Taking screenshots is much more simple, I think.
Aha, but it depends on your needs.
First, many screenshot tools will copy only the visible part of the Web page. If you need to save the page, most of the time it’s because you want the whole of it.
Then, screenshot tools only result in an image, which means there are no more active links in the page now.
Yeah, for instance I’d like to see the screenshots needed for this page!
Works fine for me on my openSUSE Leap 15.1 system.
This thing is a godsend. It translates characters that don’t save properly in the title using the browser “Save As” tool into characters that do (such as “$” and such), and it completely avoids the “failed” saves the browser loves to do. The latter was a major pain in the butt for me for a long time.
Plus the elimination of numerous folders with their separately saved small files makes copying the saved files so much easier.
It does frequently reports that not all the resources on the page were saved, but I’ve never seen anything significant left out. Most of those are probably ads or something from external servers that are being blocked by NoScript or something.
This is one of the few browser utilities that are worth installing.
I dimly remember using this extension some time ago, with disappointing results.
Note that the AMO page now states: “This is not a Recommended Extension. Make sure you trust it before installing.”
Think I’ll stick with SingleFile until a comprehensive comparison is done.
Saving web pages as a single file has long been important for me.
Internet Explorer had the .mht single-file format, which wasn’t supported in other browsers, and Firefox until support for the original extensions ended had alternative optional extensions that could be used.
The ‘SingleFile’ HTML extension for Chrome and Firefox mentioned above has been invaluable for me since I read about it on Ghacks: not only a single file, but also a file that can opened by any browser and if necessary email easily.
An important practical consideration when saving files is whether links on the saved web page will work if needed: with ‘SingleFile’ an option can be set to save the url of the saved page so that it can be reloaded if needed.
I haven’t tried ‘Save Page WE’ yet but I have certainly noted it, and saved this Ghacks web page as a single HTML file for future reference!
is there a reason firefox avoids a MHT support like any other browser and had only User made Extentions for it? even it own Maff kinda died
I prefer Single File. I find it simpler, which is important.
However, both pale in comparison with the defunct MAFF format, which was what we needed.
What a find Ashwin! Thanks, I love it. Saved files then go on to load perfectly on Android browser, having come from Windows 10 PC. Great.
I use SingleFile. No need for a change
A good alternative is SingleFile
https://addons.mozilla.org/en-US/firefox/addon/single-file/
and a new addon by the same author SingleFileZ
https://addons.mozilla.org/en-US/firefox/addon/singlefilez/
Hello,
What is the difference between SingleFile and SingleFileZ?
Thank you.
The main difference is that SingleFileZ needs JavaScript to be enabled to display pages because it needs to unzip the resources (images, fonts, styles…) of the page. The main advantage is that it produces smaller files which can be unzipped if necessary.
Ok, thank you.
Great extension. Funny enough, it does not work for me since a few days, after using it daily for a long time.
Anyone got a alternative extension for saving in this single file format?
Disclaimer: I am not saying that it is broken in general, only that it does not work anymore on my system. So by no means feel discouraged to test it yourself; It was extremly helpful all this time before. It is such a cool solution, that I even stopped to clip to OneNote and Joplin and used only this extension!
Props to Ashwin for reviewing it!
Perhaps some incompatibility with other extension. In my case – I had to disable “Dark Reader” before save page.
the article has mentioned the alternative, SingleFile
Wikipedia allows to download page as pdf. Left sidebar, under print/export section.
Ghacks reader, thank you for the tip.