How to Save a Webpage with SingleFileZ When Images Load Lazily

To save a page whose images load as you scroll, use the current SingleFile project: SingleFileZ has been completely merged into SingleFile. Before saving, enable Images > save deferred images. Let the page load, trigger any scroll-based image loading, save it, and inspect the saved copy. This setting can help include deferred resources, but it does not guarantee that every site-specific lazy-loading method will be captured.

1. Use SingleFile instead of the separate SingleFileZ project

SingleFileZ’s official project README says it has been completely merged into SingleFile. Follow the current SingleFile project and its help for installation and current interface details. If you specifically need a self-extracting archive, check SingleFile’s current format options; do not assume the old separate SingleFileZ instructions still apply. SingleFile project

2. Enable deferred-image saving and save the page

1. Open the page in your browser and wait for its initial content to settle.
2. Open SingleFile’s settings and enable Images > save deferred images.
3. If images appear only as you scroll, scroll through the relevant parts of the page first. Some sites create or request images only after scrolling or another interaction.
4. Save the page with SingleFile.
5. Open the resulting file and check the sections where images were deferred. Verify that the images are present and that the page layout is usable.

SingleFile documents that it can download resources present on a page even when they are not displayed or cached. The deferred-image setting is intended for this kind of content. The documentation does not promise that every site’s custom loading behavior will be handled automatically.

3. What the setting changes

Deferred-image saving affects whether SingleFile attempts to save deferred resources. Disabling it may make saving faster, but some resources, including images or frames, may then be missing. For a page that loads images lazily, keep the option enabled while saving and verify the result.

A saved webpage is useful when you need an offline copy of the page. If you need a self-extracting archive, consult the current SingleFile format choices and help rather than relying on an old SingleFileZ walkthrough. Check the project’s current documentation for exact format and browser behavior.

4. Troubleshoot missing images

Symptom	Likely cause	What to try
Images below the fold are absent	The site had not requested or created them when the save began, or deferred-image saving was off.	Enable Images > save deferred images, scroll through the page to trigger loading, save again, and inspect the copy.
Some images remain missing after scrolling	The site may load assets after a different interaction, or may use site-specific behavior that the documented setting does not cover.	Try the site’s relevant interaction, wait for the image to appear in the live page, then save and check again. Do not treat the setting as a guarantee for every implementation.
Images fail with a cross-origin request error	The image host may require an HTTP Referer header.	Only if that error is present, consider enabling Network > pass “Referer” header after a cross-origin request error, then retry. This option is off by default for privacy reasons; sending a Referer can disclose the referring page to the resource host.
Saving takes longer than expected	Saving deferred resources can take more work than skipping them.	Keep the option on when those images matter. Turning it off may speed up saving, but can omit images or frames.
The saved file differs from the live page	Some content may depend on later loading or interaction.	Compare the specific missing sections with the live page, trigger their loading behavior, save again, and verify the new file.

5. Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. A single GET request can return a screenshot image or PDF; see the API documentation for request options. This is a screenshot workflow, rather than a self-contained saved webpage.

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}`);
await Bun.write('shot.webp', res);

ScreenshotNeo removes cookie banners, 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 for 1,000 free screenshots a month, no card required.

6. FAQ

Where is “save deferred images”?

In SingleFile settings under Images > save deferred images.

Does enabling it guarantee every lazy-loaded image is saved?

No. The official guidance describes the capability and setting, not universal support for every site’s loading implementation. Trigger the site’s loading behavior and verify the saved copy.

Why is the Referer option off by default?

SingleFile documents it as disabled by default for privacy reasons. Use it only when a cross-origin request error indicates it may be needed, since the header can reveal the referring page to the resource host.

Is SingleFileZ still a separate project?

The project README says it has been completely merged into SingleFile. Use the current SingleFile project for instructions and format options.