Reviews for Save Page WE
Save Page WE by DW-dev
307 reviews
- Rated 5 out of 5by Firefox user 13695945, 7 years agoGreat addon which requires a little more attention and it will be the best!
- Rated 5 out of 5by npwski, 7 years ago
- Rated 5 out of 5by Firefox user 13606796, 7 years agogot to give it five stars, because each time i used it so far, it worked. made a nice, single, independent offline html file that includes formatting and images.
why firefox cant do this by default with "save page as..." continues being a mystery to me. but this plugin is great. - Rated 5 out of 5by Firefox user 12456629, 7 years agoWorked great for me. All css images are saved too.
- Rated 5 out of 5by Firefox user 13503988, 7 years ago
- Rated 5 out of 5by Vova, 7 years ago
- Rated 5 out of 5by FF_user, 7 years ago
- Rated 5 out of 5by Firefox user 13503851, 7 years agoMost 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.
- Rated 5 out of 5by keff300, 7 years agoПростое удобное дополнение и очень нужное. Отлично работает.
Thank you for this top tool ! - Rated 5 out of 5by Firefox user 13466531, 7 years ago
- Rated 5 out of 5by Kohcab (Themes developer), 7 years agoEDIT : Thanks, I give 5 stars back. Webextensions suck :(
Developer response
posted 7 years agoSave Page WE uses the new Firefox WebExtensions API's, which are pretty much the same as the Chrome extension API's.
These API's do not allow extensions to perform certain types of operations on a few pages, which are either browser administration pages or web store pages, specifically:
- about:
- moz-extension:
- https://addons.mozilla.org
- chrome:
- chrome-extension:
- https://chrome.google.com/webstore
There is nothing that Save Page WE can about this. - Rated 5 out of 5by Metal_66, 7 years agoIch 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) - Rated 5 out of 5by Firefox user 13394790, 7 years agothanks, 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 effortDeveloper response
posted 7 years agoTo migrate a file saved by UnMHT or Mozilla Archive Format (MAF), please follow these steps:
1. Open the saved ".mht" or “.maff” file in Firefox using UnMHT or MAF respectively.
2. Re-save as an “.htm” file+folder using Firefox’s “Save Page As...” (Web Page, complete).
3. Serve the saved “.htm” file+folder through a local web server and open in Firefox. **
4. Re-save using Save Page WE.
** Suggest using a Google Chrome App called “Web Server for Chrome” from the Chrome Web Store:
https://chrome.google.com/webstore/detail/web-server-for-chrome/ofhbbkphhbklhfoeikjpcbhemlocgigb - Rated 5 out of 5by SENGHUO, 7 years agoEasy to use to save pages. Feel a little unsatisfied, it's required internet to save(I am using mobile hotspot
- Rated 5 out of 5by Siarhei Kuzeyeu, 7 years agoI've tried to do something like that. And I know that It's ver hard to do UnMHT analog.
I appreciate this addon. - 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.