How to install SingleFileZ in Chrome and save your first page

To install SingleFileZ in Chrome, open its Chrome Web Store listing, select Add to Chrome, then approve Add extension if Chrome asks. Once installed, open a webpage, wait for it to finish loading, and click the SingleFileZ toolbar button. It saves the page as a self-extracting HTML file for offline use. Chrome’s general extension installation steps are documented in Chrome Help.

1. Install SingleFileZ in Chrome

Open the SingleFileZ Chrome Web Store listing. The listing URL is based on the Chrome Web Store ID surfaced by search; its current availability and details should be checked on the store page.
Select Add to Chrome.
If a permission prompt appears, review it and select Add extension to finish installing.
Find the extension from the icon area to the right of Chrome’s address bar. If it is not immediately visible, open Chrome’s extensions menu and locate SingleFileZ there.

Chrome does not allow adding extensions in Incognito or Guest mode. On a work or school device, an administrator may also block extension installation. If the install option is missing or disabled, check with the device administrator or use a permitted Chrome profile.

2. Save your first webpage

Open the page you want to keep and let it finish loading. If the page fills in content as you scroll or after a delay, wait for that content to appear first.
Click the SingleFileZ button in the Chrome toolbar or extensions menu.
Wait for Chrome to finish saving. The result is a self-extracting HTML file; use Chrome’s normal download location and download controls to find it.
To check the result, open the downloaded file in a browser. Reopening a local file in Chromium may require the extension’s Allow access to file URLs setting and JavaScript enabled.

SingleFileZ is a fork of SingleFile that creates self-extracting HTML files. It is a distinct extension from SingleFile, so do not assume that instructions or current store details for SingleFile describe SingleFileZ.

3. Open the saved file offline

If the saved file does not display when opened from your filesystem in Chrome or another Chromium browser:

Open Chrome’s extensions management page and select SingleFileZ’s details.
Enable Allow access to file URLs if that option is available and you want the extension to handle local saved pages.
Make sure JavaScript is enabled in the browser. SingleFileZ’s saved-page viewing instructions indicate it is needed to display the self-extracting file.
Close and reopen the saved HTML file.

Local-file access is a browser permission. Enable it only if you want SingleFileZ to work with files opened from your device.

4. Troubleshooting

Problem	Likely cause	What to try
Chrome will not install the extension	You are in Incognito or Guest mode, or an organization policy blocks extensions.	Use a regular Chrome profile. On a managed device, ask the administrator whether extensions are allowed.
The SingleFileZ button is not visible	The toolbar does not show the extension button directly.	Open Chrome’s extensions menu and select SingleFileZ. Pinning controls, if available in your Chrome version, can keep it on the toolbar.
The saved page is missing content	The page had not finished loading, or some content appears only after scrolling or interaction.	Wait for the page and its important content to appear before saving. For interactive pages, open the relevant section or scroll it into view first, then save again.
The downloaded HTML file does not open correctly	Chromium may not have permission to use the extension on local files, or JavaScript may be disabled.	In SingleFileZ’s extension details, enable Allow access to file URLs, ensure JavaScript is enabled, and reopen the file.
The store listing is unavailable or its button differs	The listing’s availability or interface may have changed, or the device may use a restricted store.	Search the Chrome Web Store for the exact name SingleFileZ and confirm the publisher and listing before installing. Do not substitute SingleFile without checking that it is the extension you intend to use.

5. Practical limits and reliability

A saved page is a local snapshot, not a live copy of the website. Pages that rely on login sessions, remote services, interactive scripts, or content that loads only after an action may not behave exactly as they do online. For a more complete capture, wait for important content to appear and trigger it before saving.

The output is HTML, so file size and capture time depend on the page and its assets. Large, media-heavy pages can take longer to save and use more disk space. Keep the original URL with the file if you will need to revisit the live source. If a page is sensitive or account-specific, remember that the saved file is stored on your device and may contain information visible in that browser session.

6. Or skip the browser setup

If your goal is to capture a URL as an image or PDF for code, automation, or an AI workflow, ScreenshotNeo is a website screenshot API and MCP server. It does not save a self-extracting HTML archive; it returns a screenshot or PDF. Its capture flow can accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before the shot. Those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.

For example, this cURL request captures a page as WebP. See the ScreenshotNeo API documentation for the API options and response details.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

The same request in Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

And in Node.js:

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

ScreenshotNeo offers 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000 screenshots. Every feature is included on every plan. For image or PDF captures, it can avoid browser setup, clean common consent banners and popups, and let AI agents capture pages through MCP.

Frequently asked questions

Does SingleFileZ save a PDF?

The described SingleFileZ workflow produces a self-extracting HTML file. If you need a PDF, use a browser’s print-to-PDF feature or a PDF capture tool.

Is SingleFileZ the same extension as SingleFile?

No. SingleFileZ is a fork of SingleFile and has its own listing and output description. Check the extension name carefully before installation.

Can I use the saved page without an internet connection?

The file is intended for offline viewing, but content that depends on remote services or live page behavior may not be available offline.