NOTICES
Conversion of Mozilla Archive Format and UnMHT files (.maff & .mht)
Please see the section near the bottom of this page for a description of how to convert Mozilla Archive Format and UnMHT files (.maff & .mht) into Save Page WE (.html) files.
CHANGES
Versions 13.8
• New option to always show browser 'Save As' dialog box (overrides browser downloads setting).
• Saved file name option now accepts path relative to downloads folder before file name (e.g. "abc/def/%TITLE%").
OVERVIEW
Save Page WE provides a simple facility to save a web page (as currently displayed) as a single HTML file that can be opened in any browser. The saved page is a highly accurate representation of the original page.
Save Page WE is implemented using the new WebExtensions API and is available for both Firefox and Chrome with identical functions and user interfaces.
OPTIONS PAGE
The Save Page WE Options page can be accessed as follows:
• Firefox - On the menu bar select Tools > Add-ons (or press Ctrl+Shift+A), select the Extensions tab, and then click on the Options button.
• Chrome - Right-click on the toolbar button, and then select Options.
TOOLBAR BUTTON
After installation of Save Page WE, there will be a new blue 'floppy-disk' button on the main toolbar.
To save a web page as an HTML file, just click on the Save Page WE toolbar button.
There is an option to set the button action as:
• Save Basic Items
• Save Standard Items
• Save Custom Items
There is an option to prompt the user to enter comments when saving the file.
There is are options to specify the format of the saved file name. See the 'Saved File Name' section below.
In order to be prompted for the save location, the Firefox 'Downloads' option must be set to 'Always ask you where to save files'.
By default the saved HTML file will have a '.html' extension.
CONTEXT MENU & BUTTON MENU
To save a web page as an HTML file, or to perform operations on a previously saved page, right-click on the page contents to open the context menu, select the 'Save Page WE' sub-menu, and then select one of the menu items:
• Save Basic Items
• Save Standard Items
• Save Custom Items
• View Saved Page Info
• Remove Page Loader
• Extract Image/Audio/Video
Alternatively, right-click on the Save Page WE toolbar button to open the button menu, and then select one of the menu items.
There is an option to show/hide the Save Page WE submenu item on the context menu.
Note, the 'Extract Image/Audio/Video' menu item is always shown on the context menu when viewing saved pages.
KEYBOARD SHORTCUTS
To save a web page as an HTML file, using the configured button action, press Alt+A. This shortcut can be reconfigured in the Shortcuts tab of the Save Page WE Options page.
SAVED ITEMS
Save Basic Items - saves these items:
• HTML elements
• HTML image files (currently displayed)
• CSS style sheets
• CSS image files (currently displayed)
• CSS font files (used by this browser)
Save Standard Items - saves the Basic Items and these items:
• HTML image files (all)
• HTML audio & video files
• HTML object & embed files
• CSS font files (woff for any browser)
Save Custom Items - saves the Basic Items and the items selected from this list:
• HTML image files (all)
• HTML audio & video files
• HTML object & embed files
• CSS image files (all)
• CSS font files (woff for any browser)
• CSS font files (all)
• Scripts (in same-origin frames)
Note, scripts in cross-origin frames are never saved.
There is an option to retain cross-origin iframes and frames when saving the page. Note, cross-origin iframes often contain adverts or visitor comments.
There is an option to include an information bar at the top of the saved page.
There is an option to include metrics and resource summary in the saved file.
There is an option to set the maximum depth of saved nested frames/iframes.
There is an option to purge elements that have been hidden by the page itself, or by page editors (e.g Print Edit WE), or by content blockers (e.g. uBlock Origin).
SAVED FILE NAME
There is an option to specify the format of the saved file name.
This format is used when saving the complete page and when extracting a resource (Image/Audio/Video).
The saved file name may contain a path relative to the downloads folder before the file name (e.g. "abc/def/%TITLE%").
The saved file name may contain the following predefined fields:
• %TITLE% - (saving a page) the document title or if this is empty the same as %FILE%
• %TITLE% - (extracting a resource) the same as %FILE%
• %DATE% - the current date in YYYY-MM-DD format
• %TIME% - the current time in HH-MM-SS format
• %HOST% - the host name in the page or resource URL
• %PATH% - the path in the page or resource URL without the final file extension
• %FILE% - the file in the last segment of the path without the final file extension
There are options to replace spaces in the saved file name with a user-defined character and to set the maximum length of the saved file name.
There is an option to always show the browser 'Save As' dialog box, which overrides the browser downloads setting. This is especially useful if using Vivaldi or Firefox 52-57, where the browser downloads setting does not work correctly.
PAGE LOADER
There is an option to use a page loader to reduce the saved file size.
The page loader runs immediately after opening a saved page and completes the loading of the resources from the saved file.
When a saved page is opened, if it has a page loader then it cannot be immediately re-saved using Save Page WE or another application. Before this can be done, the page loader must be removed using the Remove Page Loader menu item.
LOADING RESOURCES
There is an option to set the maximum size allowed for large or repeatedly referenced resources.
There is an option to set the maximum time allowed for loading individual resources.
There is an option to force lazy loading of images before saving the page.
There is an option to allow loading of passive mixed content (image,audio,video).
There is an option to send a referer header when requesting a resource. The options are: do not send a refer header, send a referer header with origin only, or send a referer header with origin and path (origin only in private browsing).
UNSAVED RESOURCES
There is an option to show a warning if any resources cannot be saved.
There is an option to show a list of all resources that cannot be saved.
There is an option to remove URLs of unsaved resources, which avoids unsaved resources being loaded from the internet when the saved page is opened.
SAVED FILE FORMAT
The HTML elements (as currently displayed) 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, binary resources (images, fonts, audios, videos, etc) in same-origin frames 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. Binary resources in cross-origin frames are still stored as Base64 data URIs.
Note that not all cross-origin frames can be saved. A cross-origin frame will be saved only if all of its cross-origin ancestor frames can run content scripts. Scripts in cross-origin frames are not saved.
There is an option to format the HTML source code in the saved file.
CONVERSION OF MAF AND UnMHT FILES (.maff & .mht)
It is not possible for Save Page WE to do an automatic conversion of a Mozilla Archive Format (.maff or .mht) file or an UnMHT (.mht) file into a Save Page WE (.html) file. Firefox WebExtensions add-ons, such as Save Page WE, are not allowed to read local files.
It is recommended to convert .maff/.mht files as follows:
• Open the saved .maff/.mht file in Firefox.
• Re-save as .htm file (+ resources folder) using Firefox’s “Save Page As...” (Web Page, complete).
• Serve the saved .htm file (+ resources folder) through a local web server and open in Firefox.
• Re-save using Save Page WE.
With regards to a local web server, it is suggested using a Google Chrome App called “Web Server for Chrome” available from the Chrome Web Store: https://chrome.google.com/webstore/detail/web-server-for-chrome/ofhbbkphhbklhfoeikjpcbhemlocgigb
Note that, using Firefox 56 and Mozilla Archive Format 5.2.0, it is possible to do a bulk conversion of .maff/.mht files to .htm files (+ resources folders), as described here: http://maf.mozdev.org/index.html.
SUPPORT
Please e-mail: dw-dev@gmx.com
LICENSE
Distributed under the GNU General Public License version 2.
See LICENCE.txt file and http://www.gnu.org/licenses/
Conversion of Mozilla Archive Format and UnMHT files (.maff & .mht)
Please see the section near the bottom of this page for a description of how to convert Mozilla Archive Format and UnMHT files (.maff & .mht) into Save Page WE (.html) files.
CHANGES
Versions 13.8
• New option to always show browser 'Save As' dialog box (overrides browser downloads setting).
• Saved file name option now accepts path relative to downloads folder before file name (e.g. "abc/def/%TITLE%").
OVERVIEW
Save Page WE provides a simple facility to save a web page (as currently displayed) as a single HTML file that can be opened in any browser. The saved page is a highly accurate representation of the original page.
Save Page WE is implemented using the new WebExtensions API and is available for both Firefox and Chrome with identical functions and user interfaces.
OPTIONS PAGE
The Save Page WE Options page can be accessed as follows:
• Firefox - On the menu bar select Tools > Add-ons (or press Ctrl+Shift+A), select the Extensions tab, and then click on the Options button.
• Chrome - Right-click on the toolbar button, and then select Options.
TOOLBAR BUTTON
After installation of Save Page WE, there will be a new blue 'floppy-disk' button on the main toolbar.
To save a web page as an HTML file, just click on the Save Page WE toolbar button.
There is an option to set the button action as:
• Save Basic Items
• Save Standard Items
• Save Custom Items
There is an option to prompt the user to enter comments when saving the file.
There is are options to specify the format of the saved file name. See the 'Saved File Name' section below.
In order to be prompted for the save location, the Firefox 'Downloads' option must be set to 'Always ask you where to save files'.
By default the saved HTML file will have a '.html' extension.
CONTEXT MENU & BUTTON MENU
To save a web page as an HTML file, or to perform operations on a previously saved page, right-click on the page contents to open the context menu, select the 'Save Page WE' sub-menu, and then select one of the menu items:
• Save Basic Items
• Save Standard Items
• Save Custom Items
• View Saved Page Info
• Remove Page Loader
• Extract Image/Audio/Video
Alternatively, right-click on the Save Page WE toolbar button to open the button menu, and then select one of the menu items.
There is an option to show/hide the Save Page WE submenu item on the context menu.
Note, the 'Extract Image/Audio/Video' menu item is always shown on the context menu when viewing saved pages.
KEYBOARD SHORTCUTS
To save a web page as an HTML file, using the configured button action, press Alt+A. This shortcut can be reconfigured in the Shortcuts tab of the Save Page WE Options page.
SAVED ITEMS
Save Basic Items - saves these items:
• HTML elements
• HTML image files (currently displayed)
• CSS style sheets
• CSS image files (currently displayed)
• CSS font files (used by this browser)
Save Standard Items - saves the Basic Items and these items:
• HTML image files (all)
• HTML audio & video files
• HTML object & embed files
• CSS font files (woff for any browser)
Save Custom Items - saves the Basic Items and the items selected from this list:
• HTML image files (all)
• HTML audio & video files
• HTML object & embed files
• CSS image files (all)
• CSS font files (woff for any browser)
• CSS font files (all)
• Scripts (in same-origin frames)
Note, scripts in cross-origin frames are never saved.
There is an option to retain cross-origin iframes and frames when saving the page. Note, cross-origin iframes often contain adverts or visitor comments.
There is an option to include an information bar at the top of the saved page.
There is an option to include metrics and resource summary in the saved file.
There is an option to set the maximum depth of saved nested frames/iframes.
There is an option to purge elements that have been hidden by the page itself, or by page editors (e.g Print Edit WE), or by content blockers (e.g. uBlock Origin).
SAVED FILE NAME
There is an option to specify the format of the saved file name.
This format is used when saving the complete page and when extracting a resource (Image/Audio/Video).
The saved file name may contain a path relative to the downloads folder before the file name (e.g. "abc/def/%TITLE%").
The saved file name may contain the following predefined fields:
• %TITLE% - (saving a page) the document title or if this is empty the same as %FILE%
• %TITLE% - (extracting a resource) the same as %FILE%
• %DATE% - the current date in YYYY-MM-DD format
• %TIME% - the current time in HH-MM-SS format
• %HOST% - the host name in the page or resource URL
• %PATH% - the path in the page or resource URL without the final file extension
• %FILE% - the file in the last segment of the path without the final file extension
There are options to replace spaces in the saved file name with a user-defined character and to set the maximum length of the saved file name.
There is an option to always show the browser 'Save As' dialog box, which overrides the browser downloads setting. This is especially useful if using Vivaldi or Firefox 52-57, where the browser downloads setting does not work correctly.
PAGE LOADER
There is an option to use a page loader to reduce the saved file size.
The page loader runs immediately after opening a saved page and completes the loading of the resources from the saved file.
When a saved page is opened, if it has a page loader then it cannot be immediately re-saved using Save Page WE or another application. Before this can be done, the page loader must be removed using the Remove Page Loader menu item.
LOADING RESOURCES
There is an option to set the maximum size allowed for large or repeatedly referenced resources.
There is an option to set the maximum time allowed for loading individual resources.
There is an option to force lazy loading of images before saving the page.
There is an option to allow loading of passive mixed content (image,audio,video).
There is an option to send a referer header when requesting a resource. The options are: do not send a refer header, send a referer header with origin only, or send a referer header with origin and path (origin only in private browsing).
UNSAVED RESOURCES
There is an option to show a warning if any resources cannot be saved.
There is an option to show a list of all resources that cannot be saved.
There is an option to remove URLs of unsaved resources, which avoids unsaved resources being loaded from the internet when the saved page is opened.
SAVED FILE FORMAT
The HTML elements (as currently displayed) 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, binary resources (images, fonts, audios, videos, etc) in same-origin frames 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. Binary resources in cross-origin frames are still stored as Base64 data URIs.
Note that not all cross-origin frames can be saved. A cross-origin frame will be saved only if all of its cross-origin ancestor frames can run content scripts. Scripts in cross-origin frames are not saved.
There is an option to format the HTML source code in the saved file.
CONVERSION OF MAF AND UnMHT FILES (.maff & .mht)
It is not possible for Save Page WE to do an automatic conversion of a Mozilla Archive Format (.maff or .mht) file or an UnMHT (.mht) file into a Save Page WE (.html) file. Firefox WebExtensions add-ons, such as Save Page WE, are not allowed to read local files.
It is recommended to convert .maff/.mht files as follows:
• Open the saved .maff/.mht file in Firefox.
• Re-save as .htm file (+ resources folder) using Firefox’s “Save Page As...” (Web Page, complete).
• Serve the saved .htm file (+ resources folder) through a local web server and open in Firefox.
• Re-save using Save Page WE.
With regards to a local web server, it is suggested using a Google Chrome App called “Web Server for Chrome” available from the Chrome Web Store: https://chrome.google.com/webstore/detail/web-server-for-chrome/ofhbbkphhbklhfoeikjpcbhemlocgigb
Note that, using Firefox 56 and Mozilla Archive Format 5.2.0, it is possible to do a bulk conversion of .maff/.mht files to .htm files (+ resources folders), as described here: http://maf.mozdev.org/index.html.
SUPPORT
Please e-mail: dw-dev@gmx.com
LICENSE
Distributed under the GNU General Public License version 2.
See LICENCE.txt file and http://www.gnu.org/licenses/
