SingleFileZ vs SingleFile: Which Browser Extension Should You Use?
SingleFileZ has merged into SingleFile. Here’s how to choose between ordinary HTML and the self-extracting ZIP format, and what each can preserve offline.
For most people, use SingleFile. SingleFileZ has been merged into SingleFile, so you generally do not need to install a separate SingleFileZ extension. Choose ordinary HTML for simpler offline viewing; choose SingleFile’s self-extracting ZIP format when compression and the ability to extract saved resources matter. The best choice is a file-format setting, not a contest between two equally current extensions.
What changed: SingleFileZ is part of SingleFile
The SingleFileZ project repository says the project has been completely merged into SingleFile. Its self-extracting ZIP-style output is available as a format option in SingleFile. That makes SingleFile the practical starting point for new users; SingleFileZ remains useful context for older guides and files, but is no longer the necessary separate install for this format. SingleFileZ project repository
Choose a format based on how you will use the saved page
| Need | Choose | Why |
|---|---|---|
| Open a saved page as simply as possible | Ordinary HTML | The documented format comparison says it can be viewed without JavaScript. |
| A compressed single-file bundle and extractable page resources | Self-extracting ZIP format | The output is an HTML/ZIP hybrid; resources can be extracted by unzipping it. |
| Install a browser extension for the current workflow | SingleFile | SingleFileZ’s project says it merged into SingleFile; set the output format there. |
| Academic or professional preservation | A WARC-oriented archival workflow | SingleFile describes itself as a convenient page saver, not a professional web-archiving tool. |
Both formats can be one file, and the project comparison lists minification of HTML and styles and removal of unused HTML and styles for both. The trade-off is how the output opens and how its resources are packaged. No format guarantees a perfect copy of every interactive page.
How to save with SingleFile
- Install or open the current SingleFile extension for your browser, and open the page you want to save.
- Use the extension’s save command for the current tab. The Chrome Web Store listing also documents saving selected content, a selected frame or selected links, processing selected/unpinned/all tabs, autosaving after load, annotations, and a configurable shortcut.
- Open SingleFile’s options and select the desired file format. Keep ordinary HTML for the simplest file-opening behavior; select the self-extracting ZIP format if compression and extracting resources are important.
- Save a representative page and test it in the browser and location where you expect to read it. In particular, test local-file opening before adopting the self-extracting format for a team workflow.
- If using an optional upload destination, configure it explicitly and confirm where the output will be stored. The Chrome listing documents Google Drive, Dropbox, GitHub and WebDAV destinations.
SingleFile’s available capture and upload controls can vary by browser and version. Treat store-listing features as documented capabilities and consult the current extension options for exact names and behavior.
What the two outputs contain
Ordinary HTML
SingleFile packages the page as a self-contained HTML file, embedding binary resources in the HTML. The documented comparison says ordinary HTML can be viewed without JavaScript. This is the straightforward choice when you want a file that behaves like a page and do not need the archive’s extraction workflow.
Self-extracting ZIP format
The self-extracting output is an HTML/ZIP hybrid, is compressed, and lets you extract page resources by unzipping it. Opening the saved page requires JavaScript. The format is useful when the packaged resources matter as files, but browser handling of local files affects whether it opens conveniently.
Neither output necessarily preserves the original page’s live behavior. SingleFile’s FAQ says scripts are removed by default because they can change rendering and may not work offline. Maps, carousels, folding sections and other interactive elements may consequently behave differently or stop working.
Browser compatibility and opening saved files
Ordinary HTML is generally the easier output to open locally. The SingleFileZ FAQ documents that its self-extracting files can be opened from the filesystem in Firefox and Safari under specified conditions. Chrome may require the extension or a command-line switch to open local self-extracting files. Browser security behavior can change, so check current browser behavior and the extension’s documentation before distributing this format.
The self-extracting format also takes longer to save and open, according to the SingleFileZ FAQ. The sources provide no comparative benchmark or file-size measurements, so the practical difference depends on the page and should be checked with representative files.
Privacy and what is actually saved
The SingleFile and SingleFileZ project FAQs say processing happens locally and page data is not uploaded to third-party servers by default. Optional upload destinations are a separate, user-configured action: if you enable one, the resulting file is sent to the service you selected. SingleFile may retrieve page resources as part of saving, which is distinct from uploading the saved result.
Saving can still be incomplete. Browser restrictions may block access to protected domains; some sites require a Referer header to retrieve images; and content that depends on live network requests may not be available offline. Inspect important files after saving instead of assuming that a successful download means every asset and interaction is preserved.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| The self-extracting file does not open in Chrome from disk | Chrome’s local-file restrictions affect this format. | Open it with the extension as documented, or use ordinary HTML for simpler local viewing. Check current browser instructions before relying on a command-line switch. |
| The saved page looks different or an interaction no longer works | Scripts may be removed by default, or the feature depends on network resources. | Use the saved file as a static copy; verify whether the needed content can be captured and whether the relevant extension options suit the page. |
| Images are missing | The site may require a Referer header, or the browser may block extension access to a protected domain. | Check the project FAQ and browser permissions; confirm whether the source images are accessible from the page’s origin. |
| The save takes longer than expected | The page has many or large resources, or the selected archive format takes longer to process. | Try ordinary HTML if extraction is unnecessary, and save after the page has finished loading. No fixed speed difference is documented. |
| The file is present in a cloud service unexpectedly | An optional upload destination may be configured. | Review SingleFile’s destination settings and disable or change the selected destination if you want local-only output. |
| A bulk save misses some tabs | The selected-tab processing mode or tab state may not match the intended set. | Check whether the command targets selected, unpinned or all tabs, and retry with the intended selection. |
Limits: when a page saver is not an archive
Use SingleFile for convenient reading and sharing of saved pages, not as a preservation guarantee. The SingleFile FAQ explicitly says it is not a professional web-archiving tool, especially for academic archiving. If you need a formal preservation or citation workflow, choose a WARC-based tool and validate that workflow’s capture requirements.
Or skip the browser setup
If your goal is to capture a clean screenshot of a page rather than save an offline HTML copy, ScreenshotNeo is the website screenshot API and MCP server from Yorker Media. It is a different output workflow: one GET request returns a PNG, JPEG, WebP or PDF. Cookie banners are accepted and removed before capture, along with 60+ known consent platforms, newsletter popups and chat widgets; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads and cache hits cost nothing, and response headers report 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.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo API documentation. 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000. Sign up for free and capture your first 1,000 screenshots.
FAQ
Is SingleFileZ still a separate extension I should install?
For the self-extracting format, the project says to use SingleFile’s format option because SingleFileZ has merged into SingleFile.
Can I extract resources from an ordinary SingleFile HTML file?
The documented extraction workflow applies to the self-extracting ZIP-style output. Choose that format if separately accessible resources are part of your use case.
Will a saved file work forever if the original site disappears?
It can preserve captured content for offline viewing, but it does not promise complete reproduction or archival preservation. For formal preservation, use a WARC-based workflow.
Does SingleFile upload my page by default?
The project says processing is local by default. Upload occurs when you configure an optional destination.
Is a screenshot API a replacement for SingleFile?
No. A screenshot is a visual image or PDF; SingleFile saves a webpage file for offline reading. Choose based on the artifact you need.
