How to save a webpage as one HTML file in Chrome using SingleFileZ
SingleFileZ has merged into SingleFile. Here’s how to save a page in Chrome as one HTML file or a compressed self-extracting archive.
Direct answer: SingleFileZ has been merged into SingleFile. In Chrome, install the current SingleFile extension, open and load the page, then click the extension button to save it as one HTML file. If you specifically want the compressed, self-extracting format associated with SingleFileZ, open the extension’s Options → File format and choose self-extracting ZIP (universal) before saving. That archive requires JavaScript to open; ordinary HTML does not. The project repository confirms the merger.
1. Install the current extension
Use the SingleFile Chrome Web Store listing. You do not need a separate SingleFileZ extension for the workflow described here. Once installed, you can pin the extension button to Chrome’s toolbar for easier access.
2. Save a page as one HTML file
- Open the page you want to preserve in Chrome.
- Wait for the page to finish loading. If it loads content as you scroll, visit the relevant parts first and allow images or other content to appear.
- Click the SingleFile button in Chrome’s extension toolbar.
- Wait for the save to finish. The file is normally placed in Chrome’s configured download folder; check Chrome’s downloads list if you are unsure where it went.
The extension’s toolbar action saves the current tab. The Chrome Web Store listing also describes context-menu actions for selected content, frames, links, and multiple tabs. Those options can help when you need to save something other than the whole current page.
3. Choose between HTML and the SingleFileZ-style archive
To produce the compressed, self-extracting file associated with SingleFileZ, change SingleFile’s file format:
- Right-click the SingleFile toolbar button and open Options.
- Open File format.
- Select self-extracting ZIP (universal).
- Return to the page and click the toolbar button to save it.
SingleFile’s help describes the universal variant as working across platforms. It opens as a self-extracting page, and JavaScript must be enabled for it to work. The regular HTML format is also one file, but it does not need JavaScript just to open. These are distinct output formats: choose based on whether you value direct HTML access or the self-extracting archive behavior.
| Format | What you get | Opening and extraction |
|---|---|---|
| HTML | One HTML file containing the saved page and its embedded resources | Opens as HTML without requiring JavaScript for the file format |
| Self-extracting ZIP (universal) | One compressed, self-extracting file | Requires JavaScript to open; can be unzipped to extract saved resources |
| MHTML | A single-file web archive format | Compatibility and rendering depend on the software used to open it |
| HTML plus a resource folder | An HTML document accompanied by its resource files | Keep the HTML file and folder together when moving or sharing the saved page |
SingleFile lists these other formats in its options. If the requirement is specifically one self-contained file, use HTML or the self-extracting ZIP format rather than HTML plus a resource folder.
4. Improve the saved result
- Wait for page content: save only after the page has rendered the material you need. For lazy-loaded images, scrolling through the page first may give the browser a chance to load them.
- Save a specific frame or selection: use the extension’s context-menu options when available instead of saving the whole tab.
- Keep the output type in mind: if someone else needs to open the result without enabling JavaScript, use ordinary HTML.
- Check the saved copy: open it locally and inspect key images, embedded frames, and sections before relying on it as an archive.
- Preserve the file intact: for the folder-based output, keep the HTML and resource folder together. For a self-extracting archive, retain the single file and allow JavaScript when opening it.
A saved page is a snapshot, not a guaranteed offline replica of every live feature. Interactive forms, authenticated content, scripts that depend on the original site, and dynamically loaded resources may not behave the same way after saving.
5. Limits, privacy, and reliability
Some pages cannot be saved completely. The project’s FAQ says browser security restrictions block extensions on some domains. Page behavior and resource loading also matter: disabling certain resource-related options can result in missing frames or images. Options that remove hidden elements or unused styles can affect save time. If a particular page is incomplete, try saving after it has fully loaded and review the extension’s settings before repeating the capture.
The SingleFileZ FAQ states that processing happens in the browser and that the extension does not upload page data to third-party servers. The current Chrome Web Store listing also reports the developer’s disclosure that it will not collect or use user data. These are project and developer disclosures, not an independent security audit. The project also notes that the extension may download page resources that were not displayed or cached.
6. Troubleshooting
| Problem | Likely cause | What to try |
|---|---|---|
| The extension button cannot save this page | Chrome security restrictions prevent extensions from accessing some domains or pages. | Try another page to determine whether the restriction is page-specific. The extension cannot override browser security restrictions. |
| Images or frames are missing | Resources may not have loaded, or a resource-related setting may prevent them from being saved. | Wait for the content to load, scroll to lazy-loaded material, then review resource-related options and save again. |
| The self-extracting file does not open | The self-extracting format needs JavaScript enabled. | Open it in a JavaScript-enabled browser. If you need a file that opens without this requirement, save as ordinary HTML instead. |
| The page looks different offline | Some live features rely on scripts, network requests, authentication, or resources that are not preserved. | Treat the file as a page snapshot. Check the important content in the saved copy and retain access to the original page when interactive behavior matters. |
| The save takes a long time | Large pages or options that remove hidden elements or unused styles can increase processing time. | Allow the save to finish. Review those options if save time is a concern, bearing in mind that changing options can affect the output. |
| You cannot find the saved file | The extension uses the browser’s configured download folder by default. | Check Chrome’s downloads list and configured download location. |
| The result is a folder plus HTML instead of one file | The selected output format is HTML plus a resource folder. | In Options → File format, choose HTML or self-extracting ZIP (universal), then save again. |
7. When a file is not the right deliverable
SingleFile is suited to keeping a local copy of a page. If your actual goal is a rendered image or PDF for documentation, review, or an automated workflow, a screenshot capture is a different output: it records appearance rather than packaging the page as HTML.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. It returns a PNG, JPEG, WebP, or PDF from one GET request. It does not save a webpage as HTML; use it when a rendered screenshot or PDF is the deliverable.
Here is a runnable cURL example that saves a WebP screenshot:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpEquivalent 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)Equivalent Node.js (Node 18 or later, which includes fetch):
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 res.text()}`);
const fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));See the ScreenshotNeo API documentation for request parameters and response details. Cookie banners, newsletter popups, and chat widgets are removed before the shot; each cleanup 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. Its MCP server includes take_screenshot, get_page_info, and capture_pdf for AI agents. The free plan includes 1,000 screenshots a month without a card; paid plans start at $5 for 3,000 screenshots.
Sign up for 1,000 free screenshots a month, with no card required.
FAQ
Is SingleFileZ still a separate Chrome extension?
No. The project says SingleFileZ has been completely merged into SingleFile. Use SingleFile’s options for the self-extracting format.
Does the self-extracting ZIP need an extension to open?
The universal format is described as opening across platforms, but it requires JavaScript. It can also be unzipped to extract its saved resources.
Can I save a webpage as one file without JavaScript?
Yes. Choose the ordinary HTML output. The JavaScript requirement applies to the self-extracting format.
Will the saved page work exactly like the original?
Not necessarily. Saving preserves a page snapshot, and browser restrictions, dynamic loading, or site behavior can leave content or live features unavailable offline.
