Reviews for Save Page WE
Save Page WE by DW-dev
443 reviews
- Rated 5 out of 5by gejiod, 7 years agoGreat extension. enhance mht format cover to html format is better.
- Rated 5 out of 5by Firefox user 13312103, 7 years ago
- Rated 5 out of 5by Procenko, 7 years agoAt 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!) - Rated 5 out of 5by Firefox user 13282130, 7 years agoI 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.Developer response
posted 7 years agoIn reply to a couple of the points raised:
1) With regards to the saved file format:
The page source (HTML) and all of the referenced resources are saved in a single file (.html).
External CSS style sheets are converted to internal CSS style sheets. All other textual resources (scripts & frames) are stored as UTF-8 data URIs.
If the page loader is not used, all binary resources (images, fonts, audios, videos, etc) are stored as Base64 data URIs. In this case, if a binary resource is referenced multiple times, a Base64 data URL will be stored for each reference.
If the page loader is used, all binary resources (images, fonts, audios, videos, etc) are stored as Base64 strings in the page loader script, and are converted to blob URLs when the save page is opened. In this case, if a binary resource is referenced multiple times, its Base 64 string will be stored only once, resulting in much smaller saved files.
2) "When I reopened that page ... most of the images were lacking and much of the layout was somewhat off."
The reason for this discrepancy is that, when you saved the page with Save Page WE, you had the 'Use page loader to reduce file size' option enabled, which means all of the binary resources are represented as blobs.
Before using the Firefox 'Save Page As', you need to use the 'Remove Page Loader' menu item that is built into Save Page WE. Alternatively, you could disable the 'Use page loader to reduce file size' option before saving the page with Save Page WE. Either way, you should find that the re-saved page is pretty much identical to the original page. - Rated 2 out of 5by Firefox user 13268994, 7 years agoI just installed this addon - on click on button - it says: Saving... it takes very long, browser freezes, CPU jumps and browser should be killed; next time the same.... I was not able to test beyond that.... ff 57 nightly...
Developer response
posted 7 years agoAs suspected, this issue was caused by a bug in Nightly 57, not by a bug in Save Page WE.
Mozilla have fixed this bug in Nightly 57.0a1 (2017-09-08). - Rated 5 out of 5by Vik, 7 years agoThis 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. - Rated 5 out of 5by Firefox user 12552652, 7 years agoFirefox'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. - Rated 4 out of 5by Firefox user 13218075, 7 years agoThis addon is a great replacement for Mozilla Archive Format. Its only downside is that it doesn't work on Android.
- Rated 3 out of 5by 我是一只来自北方的狼,在自由的荒野上尽情奔跑, 7 years agoHey, guy, can you make this html pages into the file like MHT, MAFF format? I'd like to read these files in my laptop. Thanks anyway.
Developer response
posted 7 years agoThe HTML file save by Save Page WE contains all of the resources required by the web page, including the images, fonts, style sheets and scripts. This is exactly the same information that is saved in an MHT or MAFF file.
However, the big difference is that the file saved by Save Page WE can be opened in any browser without any add-ons being required, and is therefore furure-proof.
Whereas, an MHT or MAFF file can only be opened in Firefox using an add-on such as UnMHT or MAF, both of which are legacy add-ons that do not work with multi-process (e10s) Firefox. - Rated 4 out of 5by me, 8 years agoIt should save from cache, but this addon re-downloads all the files and makes the size bigger. I used current state and did not enable any media. Whereas MAFF save for the same page was 6 times less.
- Rated 5 out of 5by Rommel Martinez, 8 years agoWith this extension, I can now stop using MAFF and Chrome’s SingleFile!
- Rated 5 out of 5by FenyX, 8 years agoAll-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. - Rated 5 out of 5by Mehdi, 8 years agoNice 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)
Developer response
posted 8 years agoCannot reproduce this problem. Which operating system are you using?
Please can you send a link to a web page that causes this problem to: dw-dev@gmx.com
Opening a saved file with spaces in its name should work fine, and has been tested on Windows 10 with Firefox, Chrome, Opera, Vivaldi, Safari and Internet Explorer. - Rated 5 out of 5by dLeon, 8 years agoSimple options. Easy to use.
I'm impress with the accuracy of the saved pages. Almost like seeing a screenshot. - Rated 4 out of 5by Firefox user 12302018, 8 years agoSorry, I was wrong. But you should not write that your addon saves page as "Complete file". Because without js it is not complete page.
Developer response
posted 8 years agoSave Page WE 2.0 now has options to:
- Save Current State
- Save Chosen Items
- Save Complete Page
It is possible to save the following items:
- HTML elements (all)
- Style sheets (all)
- HTML images (all or currently displayed)
- CSS images (all or currently displayed)
- Custom fonts (all)
- Scripts (all)