Is SingleFileZ Free, and Does It Have Any Paid Features?
SingleFileZ’s self-extracting format is now part of SingleFile, which is free and open source. Here’s what that means for cost, cloud storage, and opening saved pages.
Yes. SingleFileZ’s self-extracting page format is now part of SingleFile, which its official website describes as free and open source. The official sources reviewed disclose no SingleFileZ subscription or paid upgrade for that feature. SingleFileZ has been merged into SingleFile; to save a self-extracting file, use SingleFile’s file-format option. SingleFileZ repository · SingleFile website
What happened to SingleFileZ?
SingleFileZ was a browser extension for saving a page as a self-extracting ZIP-style HTML file. Its repository says the project has been completely merged into SingleFile and points users to the File format setting in SingleFile’s options. Existing SingleFileZ settings can be imported.
The resulting self-extracting file is HTML that is also a valid ZIP archive containing page resources, such as images, fonts, stylesheets, and frames. You can view it as a page or extract its resources with an archive utility. SingleFile repository and format details
Does SingleFileZ have paid features?
The official SingleFile website says the project is free and open source and lists self-extracting ZIP files among its features. The official material reviewed does not identify a paid tier for the self-extracting format. You do not need a SingleFileZ subscription to use that capability in SingleFile.
SingleFile supports optional destinations such as Google Drive, Amazon S3, GitHub, and WebDAV. Those are integrations, not evidence of a paid SingleFileZ upgrade. A destination provider may have its own pricing, account requirements, or storage limits; check its terms separately. The SingleFile documentation establishes that destinations are supported, not that third-party storage is free.
What you get in SingleFile
SingleFile saves a page and its associated resources as one HTML file. Its listed capabilities include saving the current, selected, or all tabs; selecting page content; adding annotations; autosaving; batch-saving URLs; saving bookmarked pages; and choosing a destination. The self-extracting format is one option within that broader tool.
Self-extracting files versus regular SingleFile HTML
| Question | Self-extracting format | Regular SingleFile HTML |
|---|---|---|
| Is it compressed? | Yes; it is also a ZIP archive. | The format comparison distinguishes it from the compressed self-extracting format. |
| Can you extract page resources? | Yes, with an archive utility. | It is a saved HTML page with associated resources. |
| Does viewing require JavaScript? | Yes. | The repository says regular SingleFile HTML can be viewed without running JavaScript. |
| Are there local browser caveats? | Yes. Chromium browsers have extra viewing restrictions; Chrome may require a command-line switch or the extension for local files. | Fewer viewing caveats according to the project’s format comparison. |
Choose the self-extracting format if compression and the ability to recover embedded resources matter. Choose regular HTML when straightforward viewing without JavaScript is more important. Browser behavior can vary, so keep the original page or another copy if the file must be opened in a restricted environment.
How to move from SingleFileZ to SingleFile
- Install or open the SingleFile extension from its official project listing.
- Open the extension’s options and locate File format.
- Select the self-extracting format to save pages in the format previously provided by SingleFileZ.
- If you have an existing SingleFileZ configuration, follow the repository’s settings-import guidance.
- Save a page and confirm it opens in your target browser. For local-file restrictions, see the compatibility notes below.
For exact current option labels and supported browsers, use the project’s own migration notes and SingleFile documentation.
Privacy and page completeness
The SingleFileZ FAQ says processing happens in the browser and that SingleFileZ itself does not upload saved data to third-party servers. It also notes that saving may download page resources that are not currently displayed or cached. If you choose a cloud or WebDAV destination, that destination necessarily has its own handling and privacy terms; review them before saving sensitive pages there.
A saved page may not behave exactly like the live site. Dynamic content, scripts that depend on a server, resources blocked by the browser, and content that was not loaded during saving can affect the result. A self-contained copy is useful for reference and archiving, but it is not a guarantee that every interactive feature will continue to work offline.
Compatibility and common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The self-extracting file does not open or render correctly. | JavaScript is disabled, or the browser restricts scripts in local files. | Enable JavaScript for the file and consult the project’s browser-specific guidance. Chrome may need a command-line switch or the extension to open local files this way. |
| The saved page is missing images or other resources. | A resource was not loaded, was blocked, or was not available for saving. | Let the page finish loading before saving, check that the resource is available in the live page, and review settings for frames and deferred images. |
| Saving is slow. | Default settings prioritize a smaller output, and processing extra page resources can take time. | Review cleanup options; the FAQ says turning off some cleanup can improve speed. Avoid disabling frame or deferred-image handling if those resources need to be included. |
| A cloud save fails or asks for an account. | The selected destination has its own authentication, configuration, or service limits. | Check the destination’s credentials and terms. This is separate from whether SingleFile itself is free. |
| An old SingleFileZ setting is missing. | The standalone project was merged and settings may need to be imported into SingleFile. | Follow the import instructions in the SingleFileZ repository and configure the format in SingleFile’s options. |
Cost, speed, and reliability considerations
- Cost: SingleFile is described by its official site as free and open source. The reviewed sources disclose no charge for the self-extracting format. Third-party storage can have separate costs.
- Speed: Saving can take longer when the extension processes and fetches many page resources. The FAQ says some cleanup settings can be disabled to improve speed, with possible tradeoffs in output.
- Completeness: Frames and deferred images may need special handling. Disabling their handling can make saves faster but may omit those resources.
- Reliability: The archive is a local file, but opening it depends on browser support and JavaScript behavior. Verify important archives in the browser where they will be used.
- Privacy: The FAQ says the extension does its work in the browser. Sending a saved file to an optional cloud destination changes where that file is stored.
Or skip the browser setup
If your goal is to capture a rendered page as an image or PDF instead of keeping a self-extracting archive, ScreenshotNeo offers a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. Its capture flow accepts cookie banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before the shot; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and billing status. An MCP server provides screenshot tools for Claude, Cursor, and other MCP clients.
Here is a cURL request, using the documented API. The ScreenshotNeo API documentation describes the available parameters and response behavior.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
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)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(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));ScreenshotNeo includes full-page capture, element capture, device and viewport settings, PDF options, custom CSS and JavaScript, waits, request blocking, caching, signed links, async jobs, bulk capture, and a usage API. It has 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month with no card.
FAQ
Is SingleFileZ still a separate extension?
The repository says it has been completely merged into SingleFile and directs users to SingleFile’s file-format option.
Can I open a self-extracting page without JavaScript?
No. The SingleFileZ FAQ says JavaScript must be enabled to open these saved pages.
Does saving to Google Drive or S3 mean SingleFile has a paid plan?
No. These are optional destinations. Their availability does not establish a SingleFileZ subscription, and each provider sets its own terms.
Does the extension upload my saved pages?
The SingleFileZ FAQ says processing is done in the browser and SingleFileZ does not upload saved data to third-party servers itself. A separately selected cloud destination has its own data handling.
