SingleFile Not Working in Chrome: Extension Troubleshooting Checklist

If SingleFile will not save a page in Chrome, first try the save in an Incognito window. If that does not help, reset SingleFile’s options, restart Chrome, and temporarily disable other extensions to check for a conflict. The right fix depends on whether saving fails on every site, only on a local file, only on one website, or only when the saved copy is missing content.

SingleFile is a browser extension that saves a web page as one HTML file. Its Chrome listing describes saving the current tab, selected content, frames or links, and multiple tabs, with additional options such as auto-save and upload destinations. The listing version changes over time, so compare your installed version with the current Chrome Web Store listing rather than assuming a particular version is installed.

1. Run the recommended checks in order

Try Incognito. Open the affected page in an Incognito window and try saving it with SingleFile. A changed result tells you the browser context matters, but does not identify the cause by itself. If the extension is unavailable there, check Chrome’s extension settings to see whether it is allowed in Incognito.
Reset SingleFile’s options. If Incognito does not change the result, reset the extension options. This can clear a setting that prevents the expected save behavior. Note any custom configuration first if you need to restore it.
Restart Chrome. Close and reopen Chrome, then retry the same page. This is a useful check after changing extension settings or when the extension appears unresponsive.
Check for extension conflicts. Temporarily disable other extensions and retry. If saving starts working, re-enable extensions one at a time to identify a likely conflict.
Record a reproducible failure. If the problem remains, note the page URL, the exact steps, what happened, and whether it affects other pages. The project asks users to report persistent unknown issues with reproduction steps; a failure on one page alone does not establish a confirmed bug.

This sequence follows the SingleFile project’s troubleshooting guidance. Keep the test consistent: use the same page and same save action while changing one condition at a time.

2. Identify where the failure happens

What you see	Likely area to check	Next step
SingleFile fails on ordinary websites	Extension options, Chrome state, or another extension	Follow the Incognito, reset, restart, and conflict checks above.
It fails only on a `file://` page, or the infobar is missing on a saved local page	Chrome’s file URL permission	Enable “Allow access to file URLs” for SingleFile on its Chrome extensions management page.
It fails only on one site, or some images are absent	Site restrictions or resource-loading behavior	Check whether Chrome blocks extension access on that domain; inspect the page’s resource behavior and the Referer setting below.
The page saves, but the name resembles a UUID	A documented Chrome download behavior	Try disabling SingleFile’s “Misc > save pages in background” option.
The save dialog does not appear as expected	SingleFile and Chrome download settings interact	Check both the SingleFile dialog option and Chrome’s “Ask where to save each file before downloading” setting.
The file opens, but differs from the live page or is not interactive	Saved-content settings and offline behavior	Review script removal and content-related options; see section 5.

3. Fix local file and infobar access

Chrome restricts extension access to local filesystem pages by default. If you want SingleFile’s infobar to appear on a saved local page, or want to save a page stored on your filesystem, grant the extension permission to access file URLs:

Open Chrome’s extensions management page.
Find SingleFile and open its details.
Turn on Allow access to file URLs.
Return to the local page and retry.

This permission is specific to file:// pages. It is not a general fix for a save failure on a normal website. The project documents this requirement in its known issues and FAQ.

4. Check the download dialog and filename

The filename looks like a UUID

SingleFile documents a Chrome issue in which the saved filename may look like a UUID. Its suggested workaround is to disable Misc > save pages in background. The project also says reinstalling the browser may fix this behavior. Treat these as project-documented workarounds, not guaranteed fixes; try the setting first and check whether the filename changes.

The “Save as” dialog does not behave as configured

SingleFile’s option File name > open the “Save as” dialog to confirm the file name depends on Chrome’s download preference. The project says disabling that SingleFile option works only when Chrome’s Ask where to save each file before downloading is disabled in chrome://settings/downloads. If the dialog behavior is unexpected, check both settings together and retry.

5. Diagnose missing resources or changed page content

Some images are missing

A website may require a Referer header when serving an image or other cross-origin resource. SingleFile does not pass that header by default for privacy reasons. Its FAQ describes an option to pass it after a cross-origin request error. Consider enabling it only for a site where the missing resource and request error point to this cause; it is a site-specific privacy tradeoff, not a default recommendation.

The page is not interactive offline

SingleFile removes scripts by default because scripts can change how a page renders and may not work offline. If a saved element needs to remain interactive, the FAQ describes unblocking scripts and, optionally, changing settings for hidden elements, unused styles, and raw page content. Those choices can affect what gets saved and how the file behaves. They may address a fidelity or interactivity difference, but do not necessarily fix a failure to start saving.

A site cannot be saved at all

Browsers can block extensions from running on some domains for security reasons, and SingleFile may show a blocked state on its icon. If the issue is isolated to one site, check the extension icon and Chrome’s site access controls. A blocked site is different from an extension-wide malfunction; the project FAQ explains that some pages cannot be saved because of browser restrictions.

6. When to report a persistent problem

After the checks above, prepare a short report that another person can reproduce:

The page URL, if it is safe to share.
The save action used and the steps taken immediately before it.
Whether it fails in Incognito, after resetting options, and with other extensions disabled.
Whether the failure affects all pages, one domain, local files, the download dialog, or only the saved content.
Your installed SingleFile version and Chrome version.
The visible error, blocked indicator, missing resource, or resulting filename.

Use the project’s issue-reporting route linked from the SingleFile repository. Describe the behavior without labeling it a confirmed bug unless it has been reproduced.

Or skip the browser setup

If your goal is a clean screenshot rather than a saved, editable HTML copy, ScreenshotNeo captures a URL with one GET request. Its API returns PNG, JPEG, WebP, or PDF, and its API documentation lists the available options.

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

ScreenshotNeo accepts cookie and consent banners like a visitor, then removes more than 60 known consent platforms, newsletter popups, and chat widgets before the shot; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, with the page verdict and billing status reported in response headers. Its MCP server lets Claude, Cursor, and other MCP clients use take_screenshot, get_page_info, and capture_pdf. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Every feature is on every plan.

Frequently asked questions

Why isn’t the SingleFile infobar displayed on a local page?

Chrome blocks extension access to local files by default. Enable Allow access to file URLs in SingleFile’s extension details.

Why can I save a page but not its images?

The site may require a Referer header for cross-origin resources. SingleFile omits it by default for privacy; only consider the documented option when a specific resource error points to that cause.

Does a saved SingleFile page have to work offline exactly like the live site?

No. Scripts are removed by default, and some page behavior or resources may depend on the original site. Review the script and content settings if offline behavior matters.

Which SingleFile version should I have?

There is no version number that applies to every reader. Check the version installed in Chrome and compare it with the current project or store listing when investigating a version-specific issue.