How to save a webpage with SingleFileZ on a low-data connection
SingleFileZ is now part of SingleFile. Learn which save options can reduce downloads, what they leave out, and how to save pages with less data.
Short answer: SingleFileZ has been merged into SingleFile. To save a page using less data, open SingleFile’s options and consider removing frames and disabling the saving of deferred images. These settings can omit page resources, so the saved copy may be less complete. The official documentation does not quantify the data savings or guarantee a particular reduction.
1. What happened to SingleFileZ?
The official SingleFileZ repository says the project has been completely merged into SingleFile. It directs users to SingleFile’s File format options for saving self-extracting files. If you searched for SingleFileZ, use the current SingleFile extension and its options.
SingleFile saves a page in the browser. The extension’s help says to wait for the page to load, then click the extension button to save it. To change settings, right-click the extension button and choose Options. The current options may vary by browser and extension version.
2. Choose settings that use fewer resources
- Open SingleFile’s options. Right-click the extension button and select Options.
- Review page-content settings. Find the settings for frames and deferred images. The precise labels and grouping can change between versions.
- Consider removing frames. Frames can contain separate page content and resources. SingleFile’s help says removing frames can considerably reduce the saved file size and may decrease save time.
- Consider disabling the saving of deferred images. Deferred images may not be loaded until they are needed or brought into view. If you disable saving them, some images may not be present in your saved copy.
- For a self-extracting save, review File format. This is where the SingleFileZ project points users for the self-extracting file option. File format is about the output format; it does not by itself establish a specific data saving.
- Save a page and check the result. Open the saved file and inspect the parts you need, especially embedded content and images further down the page.
Change one setting at a time if you need to identify which omission is acceptable. Keep frames or deferred images enabled when they contain information you need offline.
3. Why a save can use data even when it runs locally
SingleFile’s FAQ explains that saving can download resources present in a page, including images, CSS, frame contents, and fonts that are not displayed or cached. As a result, the visible text alone does not tell you how much resource data a save may fetch.
The FAQ also says SingleFileZ works in the browser and does not upload user data to third-party servers. That is a privacy statement, not a promise of zero network use: the browser may still fetch resources from the page while creating the saved copy. You can read the details in the official FAQ.
4. Decide how much completeness you need
| Choice | Likely tradeoff | Good fit when |
|---|---|---|
| Keep frames and deferred images | More page content may be retained, and more resources may need to be fetched. | You need a closer offline copy, including embedded content or images not immediately visible. |
| Remove frames | Frame content may be absent. The help says the output can be considerably smaller and saving may be faster. | The framed content is unnecessary for your offline reading. |
| Do not save deferred images | Some images may be missing from the saved page. | Images that load later are not important to the purpose of the copy. |
These are ways to omit resources, not a data-budget control. Actual network use depends on the page and its resources. The documentation reviewed here provides no measured reduction, so treat the settings as tradeoffs to inspect rather than a promised amount of savings.
5. Troubleshooting
The saved page is still large
Cause: The page may include many images, stylesheets, fonts, or other resources, including ones not currently visible. Fix: Review whether removing frames or excluding deferred images is acceptable. These settings cannot guarantee a target file size or data use.
Images or embedded content are missing
Cause: The page may rely on deferred images or frames that were excluded. Fix: Re-enable the relevant setting and save again when completeness matters, ideally on a connection where fetching the page’s resources is acceptable.
I cannot find the SingleFileZ settings
Cause: SingleFileZ was merged into SingleFile, so the current options are in SingleFile. Fix: Open the SingleFile extension’s options by right-clicking its button and choosing Options. For a self-extracting file, consult the File format options.
Does local saving mean no data is used?
No. The extension’s browser-based processing and the browser’s fetching of page resources are separate things. A save may download resources even though the FAQ says user data is not uploaded to third-party servers.
6. Performance, reliability, and data limits
Removing frames may reduce file size considerably and may shorten save time, according to SingleFile’s help. Disabling deferred-image saving can also omit resources, but the reviewed documentation does not provide a measured time or data comparison. Results depend on what the page contains and what has already loaded or been cached.
For a more complete copy, retain the content you need and verify the saved file. For a leaner copy on a limited connection, omit only resources you can live without. The official sources do not promise an exact data ceiling, savings percentage, or save time.
7. Or skip the browser setup
If you need a screenshot rather than a self-contained offline webpage, ScreenshotNeo provides a website screenshot API and MCP server. Its API returns a PNG, JPEG, WebP, or PDF from one GET request. See the ScreenshotNeo API documentation for the available options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport 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}`);ScreenshotNeo accepts cookie or consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server offers screenshot, page-info, and PDF-capture tools for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. A screenshot is an image or PDF output, not a substitute for a self-contained webpage you can browse offline.
Sign up for 1,000 free screenshots a month with no card.
8. FAQ
Can I still install or use SingleFileZ as a separate project?
The official repository says it has been completely merged into SingleFile and points users to SingleFile’s options.
Where is the self-extracting file option?
In SingleFile’s File format options, as directed by the SingleFileZ repository.
Does the documentation say how many megabytes these settings save?
No measured data-savings figure is provided in the reviewed official documentation.
Sources
- SingleFileZ official repository: merge status and self-extracting format guidance.
- SingleFileZ official FAQ: resource downloads, privacy, and options that may omit resources.
- SingleFile official help: opening options, saving a page, and removing frames.
