The native browser saving format is to have an html file and a folder containing all the external resources. A moderate number of these folders will completely obscure the format of the local directory, rendering it into an incomprehensible maze. In addition, the non-locality of the associated resources makes it difficult to handle the files; moving and deleting become tricky. Save Page WE solves this issue by moving the entire resource folder into the HTML file using a combination of tricks. This deserves to be one of the default Firefox save behaviors given its utility.
Historically, there are two other non-WebExtension addons that do the same thing, UnMHT and Mozilla Archive Format (MAF). Both have special file formats, .mht and .maff respectively, which require their addon to open. Firefox has decided that non-WebExtensions addons will be removed, so these two other addons have become unacceptable for backups. Save Page WE's pure html file format is a clearly superior engineering solution. The backups it produces are good forever.
Save Page WE had the foresight to produce the save file dialog after the archive, which solves a major problem by design. MAF, which doesn't do this, struggles with corruption errors. UnMHT has the same problem, but it works around this issue by alerting the user on failed downloads.
UnMHT has been the gold standard for accuracy. MAF has had severe problems with silent corruption throughout its lifetime. Save Page WE approaches UnMHT's accuracy, but WebExtensions has many limitations. It cannot save Firefox reader pages, because "Firefox and Chrome do not allow loading of content scripts into [about: pages]." It 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. A way around this restriction is to serve the local “.htm” file (and resource folder) using a local web server, such as the Google Chrome App called “Web Server for Chrome”." "Save Page WE cannot re-save a “.mht” file because Firefox will not load a content script into a page saved by UnMHT."
These limitations are out of the developer's hands, and every other WebExtensions save addon will have the same issues, but they are still important.
In some cases, I've found that Save Page WE's accuracy is better than UnMHT's. This appears to be because Save Page WE respects my adblocker and UnMHT does not.
Save Current State loses text icons, which can only be discovered after inspecting the saved file. This can be solved, once discovered, by toggling "css fonts" in the extension's settings.
"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.
Testing on several pages, I find that the file size is often 20-30% smaller than UnMHT, but on most pages with user-generated content (reddit, slashdot, forums), the size grows up to 8x times UnMHT. For example, https://www.reddit.com/r/gifs/comments/5x5htw/this_man_is_a_professional/ UnMHT 1.31MB, SPWE 10.4MB. "This happens when a style sheet makes numerous references to an image file that contains a set of sprites." In practice, this increased file size has been a major pain.
Save Page WE's saving speed is consistently about 40% faster than UnMHT. Some pages take 20 seconds to save, so this helps.
Developer turnaround on feedback is very fast and complete, under a day in all cases, even for bugs requiring major reworks. All of the quotes in this review come from the developer.
It works fine in desktop but not in Android. It used to work in Android but do not work anymore. After I click the button then nothing happen in Android. Does anyone know how to get this work in Android now? When this works it is the best that I can find online.
My friend, but when you save, you can choose not only save in .html, but in .maff, your addition has become even more popular, because in .maff, I can unpack it 7 zip and see its content, pictures, and .html, not unpacked
Complete Garbage. For years I used save as mhtml and UNMHT for saving YouTube and it was awesome. Mozilla removed them both when they upgraded and this is nowhere the same. Don't waste your time. Use Google Chrome. They do listen more to what users want. Mozilla is like Microsoft. When something already works great, they change it so it sucks.
It is a LIE that the addonconverts mht files to html, better to use addon "SINGLEFILE" using the "save all tabs" option of the open pages previously converted to html with firefox 56 with the "Mozilla archive format" addon.
I have a lot of TROUBLES with "Save Page WE" I do not recommend it
This extension does not make Firefox into a MHT reader, unfortunately. MHT files still can't be displayed.
We need such a plugin (on Windows) - I have zillions of old MHT files that I won't bother converting, especially since the format isn't dead in Chrome or Android. I keep an old version of Waterfox around just to read MHT (and remember my favorite FF plugins). With SingleFile and Save Page WE around nobody needs to WRITE mht anymore, but it's just lame Firefox is missing the capacity to read them.
Одно из самых полезных дополнени1 Mozilla. Я только ради этого дополнения удалил х64 bit Mozilla версию, и поставил х32 Mozilla One of the most useful add-ons is Mozilla. I just deleted this x64 bit Mozilla version for the sake of this add-on, and put x32 Mozilla
Fantastic addon. Saves current state of the page to a single file, with a high level of compatibility. I've used others that actually save slightly smaller files, but none handle difficult pages as well as Save Page WE does. Very clean and the keyboard shortcut makes it highly unobtrusive (especially once the warning regarding un-saveable elements is disabled). Thanks for your hard work on this addon!