SingleFileZ Says the Page Cannot Be Saved: Permissions and Site Access Fixes

Start by checking what kind of page you are trying to save. “This page cannot be saved with SingleFile” can be associated with a browser or domain that blocks an extension’s content script, Firefox Reader View, or a page-specific save bug. If the save succeeds but content is missing, the cause may instead be that the site removed off-screen content from the document before capture.

The evidence available for this error concerns SingleFile. It does not establish whether SingleFileZ is the same project or a separate product, so the SingleFile-specific steps below may not apply to SingleFileZ. Check the extension’s name, publisher, and documentation before changing browser settings.

1. Identify the page and the failure

Before changing a preference, note the browser, extension name and version, page address, and what happened when you tried to save.

• Browser-owned or browser-restricted page: Some browsers prevent extensions from injecting content scripts on certain internal pages or domains they own. A browser restriction can stop an extension from accessing the page at all.
• Firefox Reader View: Reader View is a browser-generated view rather than the ordinary website page. A historical SingleFile issue reports the same error wording in that context, but does not document a confirmed fix.
• Ordinary website with a page-specific failure: Check whether the extension has an update that addresses a known save bug.
• Save completes but the file is incomplete: This points to a different problem. A site may virtualize a long list or conversation, removing off-screen items from the document. An extension cannot save content that is no longer present in the page.

Try the same extension on an ordinary public webpage. If it works there but fails on one browser-owned domain or a browser-generated view, that narrows the problem toward page access or page context. If it fails on ordinary pages too, check the extension version and whether the issue can be reproduced on another site.

2. Firefox: check the specific Mozilla Support restriction

For one report involving support.mozilla.org, the SingleFile maintainer recommended removing that exact domain from Firefox’s extensions.webextensions.restrictedDomains preference. The discussion is a case-specific maintainer response, not a general Mozilla instruction. Another commenter later said changing the preference did not solve a separate problem on addons.mozilla.org; do not assume this setting fixes other domains or current versions of Firefox.

1. In Firefox’s address bar, open about:config.
2. Read the warning and continue only if you are comfortable editing advanced preferences.
3. Search for extensions.webextensions.restrictedDomains.
4. If support.mozilla.org is in the value, remove only that domain from the list and keep the other entries unchanged.
5. Reload the page and try saving again. If the setting is absent, the domain is not listed, or the error remains, restore your previous value if you changed it and use the extension’s current support channel for that exact page and version.

The maintainer’s suggested change was specifically for support.mozilla.org. It does not establish a universal workaround, and it may not apply to SingleFileZ. See the SingleFile maintainer discussion for the original report and the later report where the preference change did not resolve a different Mozilla-domain issue.

3. Firefox Reader View is a separate case

A 2019 issue report describes the same error message when saving Firefox Reader View. It used Firefox Quantum 68.0.1 on Windows 10, so treat it as a historical report, not a statement about current compatibility. The issue does not establish a confirmed fix.

For a practical diagnostic, leave Reader View and try saving the ordinary website page. If that works, the failure is tied to the generated view or its interaction with the extension. If you need a copy of the article, use the website page or another save method that supports the content you need; do not apply the restricted-domain preference change on the assumption that it fixes Reader View. See the Reader View issue report.

4. Update SingleFile when the failure is page-specific

A real extension defect can also affect particular pages. Mozilla’s Firefox Add-ons version history lists SingleFile 1.26.4, released September 23, 2026, with a fix for saving some pages, including Substack home pages. That note is evidence of a specific fix; it does not mean every “cannot be saved” error is caused by an outdated version.

1. Open the extension’s listing in your browser’s official add-on store and check its current version and release notes.
2. Update if a newer version is available, then reload the affected page and retry.
3. If the issue persists, record the page address, browser and version, extension name and version, and whether the problem occurs in an ordinary tab or a browser-generated view.

Version listings change over time. Check the live Firefox Add-ons SingleFile version history rather than relying on a version number in an older troubleshooting post.

5. If the saved page is missing content, check for virtualization

Some sites render only the items currently visible in a scrolling area. As you scroll, the site may remove earlier items from the document and add later ones. In that situation, a saved file can be incomplete even though the extension had permission to access the page. The SingleFile project’s guidance is direct: “The messages that are not in the page cannot be saved.” Read its guide to saving AI chat conversations and virtualized content.

• Expose more content before saving: Scroll through the page so the site loads the items you need, where the site retains them in the document.
• Increase the capture height: The SingleFile wiki describes making the browser window tall enough, including zooming out in the extension, to expose more content at once. A height that is too small can still omit items.
• Use the documented user-script approach where applicable: The project describes an approach for supported embedded scroll areas. Follow the current project instructions for the site and extension version; this is not a universal method for every virtualized page.
• Inspect the saved file: Confirm the first and last expected items and some items in between. A successful save does not prove that every message or row was present.

The wiki gives one author-reported example, not a general benchmark: on one X thread with 252 replies, the author saved 19 at the default window height, 141 at 4,000 pixels, 249 at 8,000 pixels, and all 252 at 16,000 pixels. The author reports a 7.6 MB file at 8,000 pixels. Results depend on the specific page and setup.

6. Quick decision table

What you observe	Likely direction	What to try
Fails only on a browser-owned domain	Extension content script may be restricted	Check the browser and domain. For the reported Firefox support.mozilla.org case, see the limited preference guidance above.
Fails in Firefox Reader View, but not on the ordinary page	Browser-generated view interaction	Save the ordinary page or use another method; the historical issue does not confirm a fix.
Fails on one ordinary site	Possible page-specific bug or site behavior	Check current extension updates and release notes; report reproducible details if unresolved.
File saves, but scrolling content is absent	Virtualized content was not present at capture time	Expose the content, adjust capture height, or follow the project’s supported embedded-scroll guidance.
Product is labeled SingleFileZ	Product identity is unverified by the available evidence	Confirm its publisher and documentation; do not assume SingleFile instructions apply.

Or skip the browser setup

If your goal is a screenshot of the website rather than a self-contained saved HTML page, ScreenshotNeo offers a website screenshot API and MCP server. It is an alternative capture workflow, not a fix for SingleFile permissions or Reader View.

For a quick screenshot, replace the example URL with the page you want to capture. See the ScreenshotNeo API documentation for the available parameters and response behavior.

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 accepts cookie and consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, with the page verdict and billing status in response headers. Its MCP server includes take_screenshot, get_page_info, and capture_pdf for AI agents. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.

Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.

Common errors and fixes

The domain preference change had no effect

Cause: The maintainer’s answer covered one support.mozilla.org report, and a later report says the change did not solve a separate addons.mozilla.org issue. Fix: Do not remove additional domains based on that report. Restore unintended changes, identify the exact page context, and check current extension guidance.

The error appears only in Reader View

Cause: Reader View is a browser-generated presentation, and a historical issue reports this failure there. Fix: Retry on the ordinary website page. The report does not document a reliable Reader View fix.

The capture is successful but long-page content is absent

Cause: The site may have removed off-screen content from the document. Fix: Load or expose the needed content before saving and use the project’s guidance for capture height or supported embedded scroll areas.

Updating did not fix the message

Cause: Release notes address particular bugs, while domain restrictions and browser-generated views are different causes. Fix: Classify the page context first, then check whether the extension publisher has a report for that specific page and version.

The instructions do not match SingleFileZ

Cause: The available research does not verify that SingleFileZ and SingleFile are the same product. Fix: Verify the extension listing and publisher. Apply SingleFile-specific settings only if the product’s own documentation confirms they apply.

Reliability, performance, and cost considerations

For browser-extension saves, reliability depends on the page being accessible to the extension and the content being present when capture occurs. A permission workaround for one domain does not guarantee access elsewhere. Virtualized content may require extra preparation and can make captures larger; the SingleFile wiki’s 7.6 MB example applies only to its reported X thread and setup.

For an API screenshot workflow, check the provider’s current documentation for supported output and options before integrating it. ScreenshotNeo’s stated billing behavior excludes bot checks, blank pages, timeouts, failed loads, and cache hits; its response headers identify the page verdict and billed status. Its free and paid plan limits are listed above and may change, so consult the product site for current plan details.

FAQ

Is SingleFileZ the same extension as SingleFile?

The available research does not establish that. Verify the exact listing and publisher before following product-specific instructions.

Does the Firefox preference fix every restricted website?

No. The cited maintainer guidance concerns one support.mozilla.org report, and a later commenter said it did not fix another Mozilla-domain problem.

Can a screenshot API save a SingleFile HTML archive?

A screenshot API returns an image or PDF capture, not the self-contained HTML archive that a browser-saving extension is intended to create.

Why is the saved file incomplete if saving did not show an error?

The site may have removed off-screen items before the extension captured the page. Check whether the content was loaded and present in the document at save time.