SingleFileZ Fails to Save a Page: Common Causes and Fixes

If SingleFileZ will not save a page, first identify which part failed: the extension may not start, the browser may block access to that page, saving may take too long, the downloaded file may be missing content, or a completed file may not open. These have different causes and fixes. Compare the problem page with an ordinary website, then follow the matching steps below.

SingleFileZ has been merged into SingleFile. For current options and file-format guidance, check the successor project’s documentation as well as the older SingleFileZ FAQ.

1. Check whether the browser blocks the page

Extensions cannot run on some browser-protected domains. If SingleFileZ fails only on an extension store or another protected page, the browser restriction is a likely cause; it does not by itself mean the extension is broken. The maintainer’s FAQ explains that browsers block extensions on certain domains for security. Try saving an ordinary public webpage as a comparison. Do not try to bypass the browser’s protection.

See the SingleFileZ FAQ and SingleFile FAQ for documented examples and details.

2. Check whether the source is a local file

A local page opened from your filesystem is different from a protected website. In Chromium-based browsers, the extension may need permission to access local files:

Open the browser’s extensions management page.
Find SingleFileZ and open its details or settings.
Turn on Allow access to file URLs, if that option is available.
Reload the local page and try the save again.

This permission lets the extension work with local files. It does not grant access to browser-protected domains.

3. Follow the maintainer’s checklist for unexplained failures

If the issue occurs on normal websites and its cause is unclear, try these steps in order. Browser labels differ, and private browsing may not be available or behave identically in every browser.

Try a private or incognito window. If saving works there, a browser profile setting or another extension may be involved. Make sure the browser permits the extension in private browsing if required.
Reset SingleFile options. A changed setting may prevent a successful save or produce an unexpected result.
Restart the browser. Reopen the problem page and try again.
Disable other extensions temporarily. Retry the save, then re-enable extensions one at a time to identify a conflict.
Report a reproducible issue. If it still fails, provide the browser and version, the page type (ordinary website, protected domain, or local file), what you clicked, what happened, and the shortest steps that reproduce it. Consult the project’s known issues and troubleshooting guide before reporting.

4. If saving is slow, reduce expensive processing

SingleFileZ’s defaults aim to reduce the size of saved pages. Some cleanup work can take time and CPU, particularly on complex pages. Its FAQ suggests trying these options if processing is too slow:

Turn off HTML content > remove hidden elements.
Turn off Stylesheets > remove unused styles.

Change one setting at a time and compare the result. Disabling frame removal or deferred-image saving may also affect processing, but can leave some frames or images out. Keep those options enabled when preserving that content matters. Option names may differ in the current SingleFile version; check its documentation.

5. If the file saves but content is missing

A completed download with missing content is a capture limitation or setting issue, not a failure to save the file. Check the symptom before changing options:

Missing images: Some sites require a Referer header for image requests. The SingleFile FAQ documents an option for passing that header after a cross-origin request error. Check the current option label and follow the FAQ before changing it.
Missing frames or deferred images: Review frame removal and deferred-image saving settings. Disabling these features can make content disappear from the saved page.
Blank or unavailable canvas and video snapshots: Browser security restrictions can prevent capturing canvas image representations or video frames.
Maps, carousels, and other interactive features do not work: Scripts are removed by default in the documented SingleFile behavior. A static saved page may therefore preserve appearance without preserving interaction.

These capture details come from the successor project’s FAQ. Check its guidance for the version you use: SingleFile FAQ.

6. If the saved file will not open

First confirm that the download completed. Then identify the selected output format. A self-extracting ZIP-style file has different opening requirements from a regular HTML file.

Self-extracting files need JavaScript enabled to open, according to the SingleFileZ FAQ.
The FAQ describes Chrome as requiring the extension to open these files from the filesystem, unless a command-line switch is used. Use the extension or consult current SingleFile guidance before relying on older version-specific instructions.
The FAQ describes different filesystem behavior in Firefox and Safari. If opening still fails, check the browser-specific current documentation.
Opening the file from a web server avoids the documented local-filesystem restrictions.

SingleFileZ’s repository says the project has been completely merged into SingleFile. For current self-extracting output instructions, look under SingleFile’s File format option; the repository also points users there to import existing settings. See the merger notice and current SingleFile FAQ.

7. A quick diagnosis by symptom

What happens	Likely cause to check	First step
Save action is unavailable on one site	Browser-protected domain	Try an ordinary public webpage for comparison.
It fails on a page opened from disk	Local file access permission is off	Check Allow access to file URLs in extension settings.
It fails on ordinary sites too	Extension setting, browser state, or conflict	Try private browsing, reset options, restart, then isolate other extensions.
The save takes a long time	Page complexity or output-size cleanup	Try disabling hidden-element removal or unused-style removal, one at a time.
The file downloads, but some content is absent	Cross-origin resources, frames, canvas/video limits, or removed scripts	Identify the missing resource type and check the relevant capture option or FAQ.
The file downloads but will not open	Output format or browser-specific filesystem behavior	Check whether it is self-extracting and consult current File format guidance.

Or skip the browser setup

For a clean screenshot instead of a saved, interactive webpage, ScreenshotNeo is a website screenshot API with a single GET request. Its API documentation has the available parameters and formats.

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

ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before the shot. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed; response headers identify the page verdict and billing status. Its MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. 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, with no card required.

FAQ

Is SingleFileZ still a separate project?

The repository says it was merged into SingleFile. Current guidance is under the successor project’s documentation.

Does a successful save preserve a working copy of the website?

Not necessarily. A saved page may be static, and some interactive behavior or browser-restricted resources may not be captured.

Should I disable every optimization to make saving faster?

No. Try the specific expensive options one at a time and check whether the saved output still contains the content you need.

What details help when reporting a failure?

Include the browser and version, whether the page is local or online, whether other sites work, the visible error or outcome, and concise reproduction steps.