How to Save a Full Webpage as a Single HTML File with SingleFileZ

Short answer: SingleFileZ has been merged into SingleFile. To save a webpage in the self-extracting format associated with SingleFileZ, use SingleFile and select that format in the File format section of its options. The official repository directs users there; it does not provide a current click-by-click walkthrough, so the exact controls may depend on the installed version. SingleFileZ’s official repository.

What changed with SingleFileZ?

The project’s official repository says, “SingleFileZ has been completely merged into SingleFile.” SingleFile is where the self-extracting file option is now found. The repository also says existing SingleFileZ settings can be imported. If you are following older instructions that tell you to install SingleFileZ separately, use the current SingleFile project instead.

Save a webpage in the self-extracting format

Install or open the SingleFile browser extension for your browser.
Open the webpage you want to save and wait for the parts you need to appear. A page that has not loaded its deferred images or other content may not save with everything you expect.
Open SingleFile’s options and find the File format section.
Choose the self-extracting format there, then save the page using SingleFile.
Keep the resulting file and open it in a compatible browser with JavaScript enabled. Check the saved copy for important images, frames, and interactive content.

The official migration guidance identifies the File format section but does not document the current names of individual controls or a fixed sequence of menus. Follow the labels in your installed version rather than relying on old screenshots or version-specific directions.

What to expect from a self-extracting file

This format is not equivalent to a plain HTML file that contains every resource as ordinary embedded data. The SingleFileZ FAQ describes it as self-extracting and notes that it can retrieve additional resources present on the page, including resources that were not displayed or cached when the page was saved. That behavior can affect opening speed and what network requests occur when the saved file is opened.

JavaScript must be enabled to open pages saved in this format. Local-file restrictions also vary by browser. The FAQ says Chrome cannot open these files from the filesystem unless you use a command-line switch or install the extension. It also describes local-file conditions for Firefox and Safari. The documented Chrome limitation does not apply when the saved page is hosted on a server. See the SingleFileZ FAQ for the project’s browser-specific details.

Completeness, speed, and file size

Page state matters: Save after the content you need has loaded. The official material does not promise that every dynamic page, login-protected site, or embedded media item will be captured completely.
Smaller output can take longer: The FAQ says the default configuration favors smaller files. Removing hidden elements and unused styles can take more processing time and CPU; disabling those optimizations can make saving faster at the cost of a larger file.
Resource options have tradeoffs: Disabling frame removal or deferred-image saving can leave resources missing. If completeness matters, review those options before changing them.
Opening can take longer: The FAQ says the self-extracting format can take longer to save and open than a conventional single-file webpage format.
Browser security can block saving: Extensions cannot operate on some domains because of browser restrictions. A failure on a particular domain does not by itself mean the output format is broken.

Troubleshooting

Problem	Likely cause	What to do
SingleFile cannot save this page	The browser blocks extensions from accessing that domain.	Check whether the browser permits the extension on the page. The project FAQ describes this as a browser restriction on some domains.
The saved file takes a long time to create	Options that remove hidden elements or unused styles can require more CPU and processing time.	If a smaller file is not essential, disable those optimizations in the extension’s options and compare the result.
Images or embedded content are missing	The content may not have loaded before saving, or an option may prevent frames or deferred images from being saved.	Wait for the content you need to load, review the frame and deferred-image options, then save again.
Chrome will not open the file from disk	The format has a Chrome-specific local-file restriction.	According to the FAQ, Chrome requires a command-line switch or the extension to open these files from the filesystem. Hosting the saved page on a server avoids the described local-file condition.
The file does not behave like the original page	The self-extracting format requires JavaScript, and the original page may depend on dynamic behavior or resources not captured in the saved state.	Enable JavaScript and inspect the page after opening. The official material does not promise complete reproduction of every dynamic or protected page.

Privacy and reliability notes

The SingleFileZ FAQ says the extension does not upload saved data to third-party servers. It also says the self-extracting file may retrieve resources that were present on the page but were not displayed or cached. Treat that as a statement from the project FAQ, not as an independent security audit or a guarantee about requests made by the original webpage.

For an important archive, open the saved file in the browser and verify the specific content you need. Keep the original URL and save date with your archive if you need context later. The reviewed project materials do not make a guarantee that every page or embedded resource will remain available or reproducible.

Or skip the browser setup

If you need an image capture rather than an HTML archive, ScreenshotNeo can return a webpage screenshot with one API request. It is a screenshot API, so it does not produce the self-extracting HTML file described above. Its cookie and consent handling accepts the banner like a visitor 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 cost nothing, and the response identifies the page verdict and billing status in headers. ScreenshotNeo also has an MCP server for AI agents, with tools to take screenshots, get page information, and capture PDFs. The free plan includes 1,000 screenshots per month without a card; paid plans start at $5 for 3,000 screenshots.

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

Replace YOUR_API_KEY with your key. See the API docs for options. Sign up free for 1,000 screenshots a month, with no card required.

FAQ

Is SingleFileZ still a separate project?

The official repository says it has been completely merged into SingleFile. Use SingleFile’s options to choose the self-extracting format.

Does the self-extracting format need JavaScript?

Yes. The SingleFileZ FAQ says JavaScript must be enabled to open saved pages in this format.

Does SingleFile upload my saved page?

The SingleFileZ FAQ says the extension does not upload saved data to third-party servers. It also notes that the saved file may retrieve additional resources when opened.

Can I use ScreenshotNeo to make a single HTML archive?

No. ScreenshotNeo returns screenshots or PDFs. Use SingleFile’s self-extracting format when you need the HTML archive.