SingleFileZ Extension Not Showing in Chrome: How to Fix It

If the SingleFileZ icon is missing from Chrome’s toolbar, open the Extensions menu and pin it if it appears there. If it is absent, open Manage extensions to check whether it is installed, turned off, corrupted, or marked unsupported. If you need SingleFileZ’s self-extracting-file feature, its maintainer says the project has been merged into SingleFile; use SingleFile’s File format setting instead.

1. Check the Extensions menu and pin SingleFileZ

1. In Chrome, select the Extensions puzzle-piece icon near the address bar. If it is not visible, open Chrome’s main menu and find Extensions.
2. Look for SingleFileZ in the list.
3. If it appears, select the pin control next to it. The icon should then appear on the toolbar.

A missing toolbar icon does not necessarily mean the extension was removed: it may simply be unpinned. Chrome notes that some extensions do not offer a pin option. See Google’s official instructions for installing and managing extensions.

2. Check whether Chrome still has the extension

Open Chrome’s More → Extensions → Manage extensions page. You can also enter chrome://extensions in the address bar.

• SingleFileZ is listed and on: return to the Extensions menu and pin it.
• SingleFileZ is listed but off: turn it on if Chrome allows it, then pin it.
• Chrome says it is corrupted: use Chrome’s repair or reinstall option shown on the extension card, then check the toolbar again.
• SingleFileZ is not listed: it is not currently installed in this Chrome profile. Continue to the migration section below if you need its feature.

Extensions belong to a browser profile. If you use multiple Chrome profiles, check the profile where you installed SingleFileZ.

3. Check whether Chrome marked it unsupported

Chrome can disable extensions that do not meet its current requirements. If the extension card says SingleFileZ is unsupported or disabled for this reason, follow the maintainer’s migration path below. Chrome documents temporary re-enablement for some unsupported extensions, but that is time-limited; do not treat it as a lasting fix.

A March 2025 GitHub issue contains a user report that SingleFileZ was unavailable from the Chrome Web Store, quoting a store notice about extension best practices. That is a dated user report, not confirmation of the current store listing or the technical reason for the notice. In particular, it does not establish that a specific manifest version caused the problem. Check Chrome and the maintainer’s current project information rather than relying on that report as a present-day status update.

4. Check whether your organization manages Chrome

On a work or school device, an administrator may block extensions or prevent you from changing their settings. If Chrome says it is managed, or the enable control is unavailable, contact your organization’s administrator. Reinstalling the extension yourself will not override an organization policy.

5. Use SingleFile’s maintained self-extracting-file feature

The SingleFileZ maintainer repository states that “SingleFileZ has been completely merged into SingleFile.” If your goal is to save pages as self-extracting files, install or use SingleFile and choose the relevant option in its File format settings. The maintainer also says existing SingleFileZ settings can be imported. Follow the migration details in the SingleFileZ maintainer repository.

This is the useful route when Chrome no longer offers or enables the standalone extension. If you already have a self-extracting page saved locally and it will not open, that is a separate issue: the maintainer FAQ says the SingleFileZ extension is required to view those files and JavaScript must be enabled. Those requirements concern opening saved files, not restoring a missing toolbar icon.

6. Troubleshoot by symptom

What you see	Likely explanation	What to do
SingleFileZ appears in Extensions but not beside the address bar	It is hidden in the Extensions menu	Open the menu and select Pin.
SingleFileZ appears in Manage extensions and is off	It has been disabled	Turn it on if Chrome permits it; then pin it.
Chrome labels it corrupted	Chrome detected an extension problem	Use Chrome’s repair or reinstall control, then check whether the icon returns.
Chrome says it is unsupported	It does not meet a current Chrome requirement	Use the maintainer’s SingleFile migration for self-extracting files. Any temporary enablement is not a durable solution.
The extension is missing only in one window or profile	You may be using another Chrome profile or a window where the toolbar is configured differently	Check the profile where it was installed and inspect its Extensions menu.
The setting cannot be changed on a work or school computer	An administrator may enforce extension policy	Ask the administrator whether the extension is allowed.
A saved self-extracting page will not open	This concerns viewing the file, not the toolbar icon; the maintainer says the extension and JavaScript are required	Use an environment where the required extension is available, or save with SingleFile’s maintained format and follow its instructions.

7. Choosing the right path

Your situation	Recommended next step
Installed and enabled, icon merely missing	Pin SingleFileZ from Chrome’s Extensions menu.
Installed but turned off or corrupted	Use the controls on Chrome’s Manage extensions page.
Unsupported, unavailable, or you only need self-extracting saves	Move to SingleFile and configure its File format option; consult the maintainer’s migration instructions.
Blocked by organization policy	Contact the administrator.

Or skip the browser setup

If what you need is a screenshot of a web page rather than a saved, self-extracting HTML file, ScreenshotNeo is a website screenshot API and MCP server for developers. A GET request returns a PNG, JPEG, WebP, or PDF. See the ScreenshotNeo API documentation.

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);

Before capture, ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. An MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 shots a month with no card; paid plans start at $5 for 3,000 shots.

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

Frequently asked questions

Does a missing toolbar icon prove SingleFileZ was uninstalled?

No. First check the Extensions menu and pin it. Manage extensions shows whether it is installed in the current profile.

Did Chrome remove SingleFileZ because of Manifest V2?

The supplied research does not establish that. The cited 2025 issue is a user report and guesses at a cause; it is not maintainer confirmation.

Can I keep saving self-extracting pages?

The maintainer says that feature has been merged into SingleFile. Use SingleFile’s File format setting and its migration guidance.

Why does a saved self-extracting file need an extension?

The maintainer FAQ says the SingleFileZ extension is needed to view locally saved self-extracting files, and JavaScript must be enabled. This is separate from whether the extension icon is visible.