SingleFile Not Saving Images: How to Fix Missing Pictures

If SingleFile saves a page without some pictures, first confirm those pictures appear on the live page and wait for the page to finish loading before saving again. If they still disappear, check for deferred images, a site-specific Referer requirement, an extension conflict, browser restrictions, or content drawn into a canvas. The right fix depends on which case applies.

SingleFile is designed to save a web page together with its resources, including images, but it cannot retrieve every resource in every situation. Work through the checks below in order. The official sources are the SingleFile FAQ, known issues, and its Chrome Web Store listing.

1. Check whether the image is missing from the live page

1. Open the original page and check whether each missing picture appears there.
2. Wait for the page to finish loading. If images appear progressively, wait until they are visible before saving.
3. Save the page with SingleFile again and inspect the resulting file.

If an image is already absent on the live page, SingleFile has no displayed image to capture. Resolve the page’s own loading or access problem first. If the live page looks complete but the saved copy does not, continue with the next checks.

2. Load deferred and lazy images before saving

Some pages load images or iframe content only after you scroll, wait, or bring that part of the page into view. SingleFile’s listing describes an option to load deferred images and iframes before saving. In the extension’s options, look for that function; its label or location may differ between releases.

1. Enable the option that loads deferred images and iframes before saving.
2. On the page, scroll through the sections containing missing pictures and allow them to appear.
3. Save again, then check whether the images are present in the saved file.

If scrolling makes the images appear in the live page, deferred loading was likely involved. If they never appear, investigate whether the site blocks image requests or whether the content uses a canvas.

3. Check for a site-specific Referer requirement

A site may refuse image downloads unless the request includes a Referer header. SingleFile’s FAQ describes this for sites such as sspai.com and weibo.com. It documents a Network option to pass the Referer header after a cross-origin request error; the option is off by default for privacy reasons.

1. Look for a cross-origin request error during the save, or note whether the problem happens only on one site.
2. Open SingleFile’s options and find the Network setting for passing the Referer header after a cross-origin request error.
3. Enable it only if this diagnosis fits, then save the page again.

This setting can reveal the source page to the image host as part of the request. Leave it off when you do not need it. If it does not fix the issue, turn it off again and continue diagnosing.

4. Rule out another extension

An extension can interfere with page access or resource loading. For an unexplained issue, SingleFile’s known-issues guidance recommends disabling other extensions to check for a conflict.

1. Temporarily disable other extensions that modify pages, block requests, or manage privacy.
2. Reload the original page, wait for it to finish loading, and save with SingleFile.
3. If the images now save, re-enable extensions one at a time and repeat the save to identify the conflict.

Once you identify the conflicting extension, adjust its settings or leave it disabled on the affected site if appropriate. Restore your usual extension setup after the check.

5. Check browser restrictions and canvas-rendered pictures

Browser-protected pages

Browsers restrict extensions from accessing some domains for security reasons. If SingleFile cannot access the page at all, a missing-image preference may not help: the browser may be blocking extension access. The FAQ does not identify every affected domain or browser version, so check whether the extension can access that specific page rather than assuming all pages of a certain kind are blocked.

Images drawn into a canvas

A picture that looks like an image may have been drawn dynamically into an HTML canvas instead of being available as a conventional image resource. SingleFile documents a security-related limitation that can prevent it from saving the image representation of some canvas elements. If only a canvas-based graphic is missing and the other checks do not help, this may be an inherent limitation rather than a setting you can change.

6. Troubleshooting by symptom

What you see	Likely cause	What to try
The image is also missing on the live page	The page has not loaded it or cannot access it	Wait, reload if appropriate, and confirm it appears before saving.
Images appear after scrolling or waiting	Deferred or lazy loading	Load deferred images and iframes before saving; scroll through the page and save again.
Images fail only on one site, with a cross-origin request error	The site may require a Referer header	Try SingleFile’s Network option to pass Referer after that error.
The extension cannot access the page	Browser security restriction	Check whether the browser permits the extension on that domain.
One graphic remains missing while normal images save	It may be drawn into a canvas	Check whether the page uses canvas; SingleFile documents a security limitation for saving canvas image representations.
The cause is unclear or behavior changes with extensions enabled	Extension conflict	Temporarily disable other extensions and repeat the save, then re-enable them one at a time.

Or skip the browser setup

For a screenshot of the rendered page, ScreenshotNeo offers a one-request website screenshot API. This captures a rendered image rather than creating a self-contained SingleFile page, so use it when a screenshot is what you need. See the ScreenshotNeo API documentation for options and response details.

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 shot = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', shot));

• Cookie banners, popups, and chat widgets are removed before the shot; each step can be turned off.
• Bot checks, blank pages, failed loads, timeouts, and cache hits are never billed; response headers report the page verdict and billing status.
• An MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf.
• 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000. Every feature is on every plan.

Sign up for 1,000 free screenshots a month, with no card required.

Frequently asked questions

Does SingleFile normally save images?

It is designed to save pages with their resources, including images, but individual resources may still be unavailable because of loading, site requirements, browser restrictions, extension conflicts, or canvas limitations.

Should I always enable the Referer option?

No. SingleFile keeps it off by default for privacy. Try it when a site-specific failure and cross-origin request error point to a Referer requirement.

Why is a picture visible on the page but absent from the saved file?

It may have loaded after the save began, required a Referer header, been blocked from extension access, or been drawn into a canvas. Use the symptom table to narrow down which case fits.

Will ScreenshotNeo make a SingleFile archive?

No. ScreenshotNeo returns a screenshot image or PDF of the rendered page. It is an option when you need a visual capture rather than a saved page bundle.