How to Save a Webpage with SingleFileZ When Images Are Missing

If images are missing after you save a webpage with SingleFileZ, first check whether deferred images were saved. Keep Images > save deferred images enabled, let the page load, scroll through areas that load images on demand, and save again. Also check whether the site restricts image downloads, whether the missing content is a canvas or video frame, and whether the images were captured but fail to display when you open the saved file.

Important project change: SingleFileZ has been merged into SingleFile. Older SingleFileZ instructions may not match the current interface. The project points users to the SingleFile options page’s File format section for self-extracting files, or to importing existing settings. If you still use a legacy SingleFileZ installation, look for the options it actually provides. SingleFileZ project documentation.

1. Save deferred and lazy-loaded images

Pages often load images only when they are near the visible part of the page. SingleFileZ’s FAQ warns that some images or frames may be missing if deferred-image saving is disabled. When completeness matters, leave Images > save deferred images enabled. Saving deferred resources can take more time and CPU.

1. Open the extension’s options and find the image settings.
2. Enable save deferred images.
3. Open the webpage and wait for its initial content to settle.
4. Scroll through the page, including sections below the fold, to prompt on-demand image loading.
5. Save a new copy and reopen it to check the result.

Scrolling can prompt some sites to load images, but it is not guaranteed to load every resource on every page. If the same images remain absent, continue with the checks below.

2. Check for image-host restrictions

Some image hosts require a Referer HTTP header when a browser requests an image from another origin. The current SingleFile FAQ documents the option Network > pass ‘Referer’ header after a cross-origin request error, including examples such as sspai.com and weibo.com. This is an opt-in option documented for current SingleFile; verify that your installed version exposes it, especially if you are using a legacy SingleFileZ build. Current SingleFile FAQ.

If only images hosted on a particular site are missing, this is a useful avenue to investigate. Enable the documented option if it is available, then save the page again. It will not address every host-side restriction.

3. Identify what kind of image is missing

Not everything that looks like an image is an ordinary image file. SingleFile documents security limitations that can prevent it from saving the image representation of canvas and video elements. If the missing content is generated dynamically in a canvas or is a video frame, changing deferred-image settings may not solve it. SingleFile limitations.

Use the pattern of missing content to narrow the cause:

• Images appear after scrolling but were absent in the saved copy: check deferred-image saving and try saving after the page has loaded them.
• Only images from one host are missing: investigate whether that host requires a Referer header.
• A chart, animation, or video frame is missing: it may be dynamic canvas or video content subject to browser security limitations.
• Most or all images are missing: proceed to isolate extension settings and conflicts.

4. Isolate settings and extension conflicts

For an unexplained issue, the SingleFile project recommends a sequence to identify whether private-browsing behavior, options, the browser, or another extension is involved:

1. Try saving the page in an incognito or private window, with the extension available there.
2. If that does not help, reset SingleFile options and try again.
3. Restart the browser and repeat the save.
4. Disable other extensions to check for a conflict.

Change one condition at a time where practical and compare a fresh save. That makes it easier to tell which change affected the result. The project’s troubleshooting guidance is in the SingleFile FAQ.

5. Make sure the saved file is being viewed correctly

An image can be captured into the saved page yet fail to display because of how the file is opened. SingleFileZ documents that local .zip.html files can be opened in Firefox and Safari only with the documented local-file setting; Chrome requires SingleFileZ to be installed to view these files locally. Check the project instructions for your browser and file format. If only the local copy fails to show an image, distinguish this viewing issue from an image that was never captured.

Quick diagnostic checklist

What you see	What to check
Images below the fold are absent	Enable deferred-image saving; let the page load and scroll through lazy-loaded sections before saving again.
Only images from a particular host are absent	Check whether the host requires a Referer header. Verify the relevant option exists in your installed version.
A canvas, chart, or video image is absent	Consider documented canvas and video security limitations; ordinary image settings may not help.
The saved copy behaves differently from the live page	Check how your browser opens the saved file and any format-specific local-file requirements.
The problem has no clear pattern	Try private browsing, reset options, restart the browser, then check for conflicts with other extensions.

Or skip the browser setup

If you need a screenshot of the rendered page rather than a self-contained HTML archive, ScreenshotNeo can return a PNG, JPEG, WebP, or PDF from one API 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}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed. 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. Sign up and get 1,000 free screenshots a month, with no card.

Troubleshooting common cases

“Images are still missing after I enabled deferred saving.”

Some images may not load until their section is brought into view. Let the page settle, scroll through relevant content, and save again. If the missing items remain, check host restrictions and dynamic content; deferred saving is not a universal fix.

“Only some images are missing.”

Compare the missing images with those that were saved. If the missing ones come from a single host, investigate its request requirements, including Referer handling. If they are charts or video imagery, consider the documented canvas and video limitations.

“The page looks complete live, but the saved copy is not.”

Confirm the images have actually loaded before saving. Then make a new save with deferred-image saving enabled. Also check whether the local viewing method supports the saved file format in your browser.

“The images are missing only in Chrome or only when opening the file locally.”

Check the project’s local-file instructions for the browser and file type. SingleFileZ specifically documents browser requirements for opening local .zip.html files; a display restriction does not prove the capture omitted the images.

“Resetting settings did not fix it.”

Restart the browser and disable other extensions to look for conflicts. If the issue persists, record the browser, extension version, affected page, file format, and which images fail; those details help distinguish a site restriction from a capture or viewing limitation.

Performance, reliability, and file size

Saving deferred images can take additional time and CPU, especially on long pages with many resources. Waiting for the page and scrolling through lazy-loaded sections gives those resources a chance to load before capture, but neither step guarantees that every site will expose every image to the extension. A self-contained save also depends on the browser being allowed to fetch and represent the page’s resources; site restrictions and dynamic-content security limits remain relevant.

Because embedded images become part of the saved page’s data, pages with many or large images can produce larger files. Keep the original live URL alongside the archive when you need a reference to the source page. Cloud storage can preserve a saved file, but it does not repair images that were absent at capture time.

FAQ

Is SingleFileZ still maintained as a separate project?

The project says SingleFileZ has been merged into SingleFile. Consult the current SingleFile options and migration guidance; legacy interface instructions may differ.

Does scrolling always make lazy images save?

No. Scrolling can trigger loading on some pages, but the page may use other loading behavior or restrictions.

Will the Referer option fix every missing image?

No. It addresses a documented class of cross-origin request errors when the option is available. It does not resolve canvas or video limitations, every host policy, or extension conflicts.

Does a missing image in the local file prove it was never captured?

No. Local-file viewing restrictions can make a saved file display differently from the live page. Check the format and browser-specific opening instructions.