SingleFile Stuck Saving a Large Webpage: Fixes for Chrome and Firefox

When SingleFile takes a long time to save a large webpage, first wait until the source page has fully loaded. Then follow its troubleshooting sequence: try a private window, reset SingleFile options, restart the browser, and temporarily disable other extensions to check for a conflict. If the save completes but is slow, test the performance options below. SingleFile’s documentation does not specify a universal page-size limit or a time after which a save is definitely frozen.

SingleFile is a browser extension that saves a complete webpage as one HTML file. Its default settings aim to make that file small, and some of the processing can take considerable time and CPU. A slow save and a failed download are different symptoms, so first note whether the extension is still processing, a save dialog is open, or no file appears.

1. Check whether the page or save is still progressing

Wait for the source page to finish loading. SingleFile’s getting-started guidance says to wait until the page is fully loaded before saving. This is a first check, not a guarantee that every lazy-loaded image or dynamically added section has appeared.
Give the save a chance to finish. The official documentation does not define a reliable timeout for declaring a save hung. Avoid treating a particular number of minutes as proof of failure.
Check for a download prompt. If the browser is waiting for a filename or save location, the extension may have finished processing while the download awaits your input.
Cancel only if you want to stop. Click the SingleFile button again to interrupt processing. The documentation does not promise that cancellation produces a usable partial archive.

2. Follow SingleFile’s troubleshooting sequence

Use these steps in order. Retry the same page after each step so you can tell whether the result changes.

Try a private or incognito window. If your browser requires it, allow SingleFile to run in private browsing. If the save works there, the cause may involve the regular browser profile or one of its extensions; the private-window test alone does not identify which one.
Reset SingleFile’s options. Do this if the private-window test does not help. A reset can change customized settings, so note any options you rely on before resetting.
Restart the browser. Retry the page after the browser has reopened.
Temporarily disable other extensions. If the save now works, re-enable extensions in groups or one at a time to identify a conflict. The project documentation does not name a particular extension as the cause.
Report a repeatable issue. If the problem persists, record a short reproduction description and report it through the SingleFile project issue tracker, as its README recommends.

3. Reduce processing time while preserving the content you need

SingleFile’s FAQ explains that defaults optimized for smaller saved pages can slow saving and use more CPU. Test the following settings one at a time, checking both save time and whether the resulting file still contains the content you need.

Setting	What to test	Tradeoff
HTML content > remove hidden elements	Disable it and retry the save.	May reduce processing work; the documentation does not quantify the speed change.
Stylesheets > remove unused styles	Disable it and retry the save.	May reduce processing work; the documentation does not quantify the speed change.
HTML content > remove frames	Test disabling it only if frame content matters less than reducing work.	Frames may be missing from the saved page.
Images > save deferred images	Test disabling it only if deferred images are not needed.	Some images may be missing.

Start with the hidden-element and unused-style options, which the FAQ identifies as time- and CPU-saving options to try. Disabling frame removal or deferred-image saving changes what can be included, so use those settings only when that loss is acceptable. No documented setting guarantees a fix for every large page.

4. Check browser-specific symptoms

SingleFile documents some Chrome/Chromium and Firefox issues. They are symptom-specific checks, not general fixes for a slow capture.

Chrome and Chromium

The file has a UUID-like name: SingleFile’s known-issues guidance says to try disabling Misc > save pages in background. It also notes a possible conflict with another downloader extension.
You are saving a local file or want the infobar on one: enable Allow access to file URLs in the extension settings. This is not a remedy for a slow save of a regular website.
The Save as dialog does not appear as expected: SingleFile’s File name > open the “Save as” dialog to confirm the file name option works only when Chrome’s Ask where to save each file before downloading setting is disabled.

Firefox

A filename prompt or conflict-resolution option behaves unexpectedly: the documented filename-conflict-resolution setting does not work when set to prompt for a name.
Content inside a sandboxed iframe is missing: SingleFile may fail to save that content. The documentation does not describe a general setting that makes sandboxed iframe contents capturable.

If none of these symptoms matches what you see, return to the general troubleshooting steps instead of changing unrelated browser settings.

5. Tell a slow save from a different failure

Processing continues, then a file appears: the save was slow. Try the documented processing options and verify the saved page for missing content.
A dialog is waiting: check the browser’s download behavior and the relevant Chrome setting above.
The save works only in private browsing or with other extensions off: investigate profile settings or extension conflicts.
A particular frame or image is absent: check the frame and deferred-image tradeoffs, along with Firefox’s sandboxed-iframe limitation where applicable.
Nothing changes after the documented checks: make a concise reproduction description and report the issue to the project. The documentation does not establish a universal size ceiling, memory threshold, or Chrome-versus-Firefox cure.

Or skip the browser setup

If your goal is a screenshot or PDF rather than a self-contained HTML archive, ScreenshotNeo captures a page through one API request. The browser-extension steps above are for diagnosing SingleFile; this API is an alternative when you need an image or PDF output. See the ScreenshotNeo API docs.

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(`ScreenshotNeo returned HTTP ${res.status}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', bytes));

Replace YOUR_API_KEY with your key and change the target URL as needed. The request returns a screenshot; it does not create SingleFile’s one-file HTML archive. ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, and failed loads are never billed. It also offers an MCP server so AI agents can take screenshots. The free plan includes 1,000 screenshots per 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.

Frequently asked questions

Does SingleFile have a maximum page size?

The reviewed official documentation does not publish a universal maximum size or memory threshold.

How long should a large save take?

There is no documented time threshold for deciding that a save is hung. Check whether processing or a download prompt is still active, then use the troubleshooting sequence.

Will disabling image or frame handling keep the page complete?

No. The FAQ warns that frames or deferred images may be missing when you disable the corresponding handling.

Is Chrome or Firefox better for large SingleFile saves?

The documentation describes certain browser-specific quirks, but does not establish a universal advantage or fix for large saves.