Most importantly, this is what page are saved in the format which are accessible for editing. I has turned to SavePageWE because the UnTNT does not work in Firefox v57.

Простое удобное дополнение и очень нужное. Отлично работает.
Thank you for this top tool !

EDIT : Thanks, I give 5 stars back. Webextensions suck :(

Ich verstehe nicht, wieso ich nur einen Stern vergeben hatte. Es sollten 5 Sterne sein!
Es speichert alle Seiten nahezu perfekt. Einen besseren Ersatz für Mozilla Archive Format hätte es nicht geben können!
Bei meinen ca. 60 Add-ons gehört es zu den Top 5 Erweiterungen. (Aktualisiert am Nov. 8, 2018)

thanks, this is a very good addon!!
i have a lot mht format,
i can open it with unmht addon (legacy),
can u help me convert it to "save page we" html format?
until now "save page we" prevent to save mht format to html.
sory for my bad english.
thanks for your effort

Scrapbook is not available, so I'm using this addon.

Thank you for this top tool !

Easy to use to save pages. Feel a little unsatisfied, it's required internet to save(I am using mobile hotspot

I've tried to do something like that. And I know that It's ver hard to do UnMHT analog.
I appreciate this addon.

Great extension. enhance mht format cover to html format is better.

At last! Great 57+ addon for save pages!
Thank You very much!

PS unMHT, Scrapbook, MAFF - all this addons will be discontinued after 14 november 2017. And this Save Page WE addon our last hope for comfort saving pages!)

Simply the best!

I find this tool very neat and useful. It makes saving pages easier, more compact and it can adapt to your needs as well. For example saving a news article resulted in a file somewhat below 700KB, whereas the same page with the Firefox's default save was 5MB overall (plus the additional burden of managing many files). The end results can be hardly distinguished in the browser.

On the other hand with the information I currently possess about this mechanism, I don't think I will be using it as for now, for the following reason:

I'm corcerned as to how other tools (or future tools) that deal with html files will deal with these kinds of giant html files this extension produces, with large binary blobs and scripts embedded (Firefox save produces an html file 700 lines long, this extension: 6700). Encapsulation of data and readability with the classical format may just be too much of an advantage as opposed to the compactness this offers, especially on the long term.
I did a test: I opened the page archived with Save Page and the saved it again but with classic Firefox save. When I reopened that page, aside from the longer opening time, most of the images were lacking and much of the layout was somewhat off. Meaning, even if the visuals can be hardly distinguished, the more can the underlying logic from the perspective of the browser (and most likely from other html parsing tools').

So to sum it up, just as a non-professional in web-dev, I'm having doubts if html format was created for this kind of usage and if it can relatively fairly stand the test of time. For my application this tool, for the aforementioned reasons will not really suffice, nonetheless the engineering is astonishing. In the meanwhile I'm still searching for a tool that focuses its output in one folder and not a folder and a file as Firefox save does.

Perfect for saving web pages and well written.

This addon - very good replacement and alternative for MAFF and UnMHT (still so shame and pity that solutions will be deprecated with ff57). Convinient feature - adding timestamp to file name and other useful information to comments inside created html-file.

Only one wish for future - option for zipping created html.

Firefox's native save format is an html file next to a resource folder. These resource folders clutter the local directory, and make it difficult to move, copy, or delete these saves, because every operation needs a pair operation for the folder. Save Page WE (SPWE) solves all these issues by embedding the resource folder in the HTML file. Historically, two other addons do the same thing, UnMHT and Mozilla Archive Format (MAF). Both have special file formats, .mht and .maff respectively, which cannot be opened unless the addon is installed. Since these other addons are deprecated, their special file formats are no longer acceptable. Save Page WE's pure html file format is a clearly superior engineering solution which does not require addons. This review has shrunk in length significantly from its previous versions, thanks to a number of admirable technical improvements by SPWE.

The other two addons produce the save file dialog before constructing the save. Because of this, MAF has severe problems with silent corruption, and UnMHT must detect failure and alert to re-try. SPWE reverses the order, which solves this issue intrinsically.

UnMHT and SPWE have excellent accuracy in their saves, with small differences going either way. MAF falls behind. Native Firefox saving sometimes fails outright to produce a file.

SPWE saves usually have smaller filesize than UnMHT's. SPWE's saving speed is consistently 40% faster than UnMHT, independently of file size. Some pages take 20 seconds to save, so this helps.

SPWE re-downloads resources at the time of saving. (UnMHT does too.) In practice, this almost never causes any change, only with unusual server configurations and livestream thumbnails.

As a WebExtensions addon, SPWE cannot save Firefox Reader pages, because "Firefox and Chrome do not allow loading of content scripts into [about: pages]." A workaround is to save natively as html+folder, host the save with a local web server, and re-save with SPWE. For the local web server, the addon developer suggests the Google Chrome App called “Web Server for Chrome”. Another option is to install python, run "python -m SimpleHTTPServer 8080" in a console, and then navigate to http://localhost:8080/.

The quotations in this review come from the addon developer.

The following considerations exist, but have caused no problems:
"Save Page WE cannot re-save a “.mht” file because Firefox will not load a content script into a page saved by UnMHT." SPWE cannot re-save local html files with "_files" folders, because "Both Firefox and Chrome do not allow a page to access cross-origin local ‘file:’ resources." Both of these problems can be worked around using the local web server trick.
"The JSFiddle results section (lower right quadrant) is contained in a cross-domain sandboxed iframe. Save Page WE saves the contents of same-domain iframes, but does not save the contents of cross-domain iframes.
I have looked at how UnMHT handles this case and, as far as I can see, UnMHT creates a security risk when the saved page is re-opened. This is because the original cross-domain iframe is in effect loaded as a same-domain iframe when the saved page is re-opened." This applies to Disqus as well.

Simple and effective

With this extension, I can now stop using MAFF and Chrome’s SingleFile!

All-in-one file fully compatible with any web brower on any device without dedicated app nor extension to read it, I've been waiting for this since years. Suddenly makes PDF (of course), MAFF, MHT and every "save page as epub" solutions totally outdated and obsolete.

Already using some of your other extension, all very reliable. But this one is even more useful: now we can locally immortalize our favorite parts of the web without wondering if there will still be a tool to open this file format ten years later. Would deserve to be far more popular!

I use it with 'HackTheWeb' or 'Nuke Anything Enhanced', and I'm very glad of the resulted rendering.

Nice one, but if saved file's name contains space, the file won't open correctly on Chrome (I didn't test IE/Edge), of course will be opened in Firefox without any issue. (I'm using FF beta, just installed your add-on, also tested on latest version of Chrome)

Simple options. Easy to use.
I'm impress with the accuracy of the saved pages. Almost like seeing a screenshot.