SingleFileZ settings for saving pages with embedded images and fonts

To save a SingleFileZ page with its images and fonts, enable image embedding, make sure images and fonts are not blocked under Network, and wait for the page to finish loading before you save it. For maximum retention, keep the image reduction factor at 1 and leave “remove unused fonts” and “remove alternative fonts” off. The result is intended to be one HTML file that also works as a ZIP archive containing page resources. SingleFileZ’s Firefox Add-ons listing describes this format.

The detailed help descriptions below come from the related SingleFile project. They are useful guidance for these settings, but the inspected help does not establish that every SingleFileZ control behaves identically.

1. Set up image retention

Open SingleFileZ’s options and enable the image embedding option, if shown.
Check the Network section and make sure images are not blocked.
Set the image reduction factor to 1 if you want to preserve image dimensions. The related SingleFile help says 1 means no reduction; 2 halves dimensions, and 4 reduces them to one quarter.
Leave “remove alternative images” off if retaining alternate image variants matters more than reducing the saved file size.

The related help says the quality setting applies to resized JPEG and WebP images, ranges from 0 to 1, and defaults to 0.8. It does not affect PNG images or images saved with reduction factor 1. If you increase the reduction factor to shrink the archive, dimensions fall and image quality may also fall. A quality value of 1 saves WebP without loss according to that help text.

2. Set up font retention

In the Network options, confirm that fonts are not blocked.
Leave “remove unused fonts” off when you want to retain fonts even if the tool does not consider them necessary for the captured content.
Leave “remove alternative fonts” off when you want to preserve alternatives as well as the fonts currently used.

These cleanup options are documented as ways to reduce saved-page size. For a font-heavy page or one with visually important typography, save a sample and open it in the browser where you plan to view it offline. Remote font behavior and page-specific CSS can affect the result, and the inspected sources do not promise that every site will render identically offline.

3. Save the page

Open the page and wait for its visible content, images, and web fonts to finish loading.
Click the SingleFileZ toolbar button to start saving.
Wait for processing to complete, then open the saved file offline and check the images and typography that matter to you.

The add-on listing advises waiting until the page has finished loading before clicking the toolbar button. It also says clicking the button again cancels processing. A page that is still loading may not have requested all of its images or fonts when the save begins.

Settings at a glance

Setting	Retention-first choice	Trade-off
Embed images	On	Includes images in the saved page; can increase file size and processing time.
Block images under Network	Off	Blocking prevents image resources from being fetched for retention.
Image reduction factor	1	Higher values reduce dimensions and may reduce quality.
Image quality	Default is 0.8; relevant to resized JPEG/WebP	Lower values can make resized images smaller and less sharp. No effect at reduction factor 1 or on PNG, per related help.
Remove alternative images	Off	Can reduce size by discarding alternate-resolution versions.
Block fonts under Network	Off	Blocked fonts cannot be fetched for the saved page.
Remove unused fonts	Off for maximum retention	May remove font CSS rules the tool judges unused; can reduce output size.
Remove alternative fonts	Off for maximum retention	Can discard fonts treated as alternatives to those in use; can reduce output size.

The option names and controls are visible in the SingleFile options UI. The explanations of individual options are from related SingleFile help text, not a verified SingleFileZ-specific reference.

Completeness versus compactness and speed

Keeping images, fonts, and alternate resources can make a saved page larger and slower to process. The SingleFile FAQ says its defaults optimize for smaller saved pages and that processing can take considerably longer; it also cautions that disabling resource-related handling can leave resources such as images or frames missing. There is no universal file-size or speed result across sites in the cited material.

Choose retention: image reduction factor 1, no image or font blocking, and no removal of alternate or unused fonts when completeness matters most.
Choose a smaller archive: consider image reduction and removal of alternatives or unused fonts, then inspect the output for visual differences.
Choose faster processing: review cleanup and resource options, but check the saved file because reducing resource handling can omit content.

Dynamic pages and scripts

A missing image or font is not always caused by an embedding checkbox. The page may not have loaded the resource yet, or its content may depend on scripts. The SingleFile FAQ says scripts are removed by default because they can change rendering and are not guaranteed to work offline. Script retention involves separate content and Network settings, so do not assume enabling it will make all interactive behavior work offline. Check a saved copy before relying on script-generated content.

Troubleshooting

Symptom	Likely cause	What to try
Images are missing	Image embedding is off, images are blocked, or the page had not finished loading.	Enable embedding, turn off image blocking, wait for the page to finish loading, and save again.
Images look smaller or softer	The reduction factor is greater than 1, or resized JPEG/WebP quality is low.	Set the reduction factor to 1 for original dimensions. If resizing is needed, raise quality and inspect the result.
Some image versions are absent	Alternative-image removal is enabled.	Disable that option when you want to retain alternate-resolution variants.
Typography changed offline	Fonts were blocked or removed, or the page relies on remote font behavior or CSS.	Allow fonts in Network, turn off unused/alternative font removal, and inspect a test copy in the intended offline browser.
Page content or frames are missing	Resources were not loaded before saving, or resource handling was disabled.	Let the page finish loading and restore resource handling options, then save a new copy.
Save seems slow	Embedding and optimization of page resources can take time, especially on resource-heavy pages.	Wait for processing. If you choose to reduce cleanup or resource work, verify that the output still contains what you need.
Processing was cancelled	The toolbar button was clicked again.	Start a new save and avoid clicking the button while it is processing.

Or skip the browser setup

If you need a screenshot image rather than an offline HTML archive, ScreenshotNeo returns a PNG, JPEG, or WebP screenshot or a PDF from one GET request. See the ScreenshotNeo API documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before the shot. Bot checks, blank pages, and failed loads are never billed, and response headers say the page verdict and billing status. Its MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots. ScreenshotNeo captures screenshots and PDFs; it does not produce the SingleFileZ offline HTML archive described above.

FAQ

Does SingleFileZ save a folder of image and font files?

The add-on listing describes a single HTML file that is also a ZIP archive containing page resources, rather than a separate folder per saved page.

Should I use an image reduction factor above 1?

Only when smaller images and a smaller saved file are acceptable. A factor of 1 preserves dimensions according to the related SingleFile help.

Will the saved page preserve every interactive feature?

Not necessarily. Scripts are removed by default in SingleFile according to its FAQ, and script behavior is not guaranteed offline.