How to Use SingleFileZ to Save a Webpage on a Slow Connection

Short answer: Open the page while you have a connection, wait for its main content and images to load, then click the SingleFileZ toolbar button and let it process. If saving is taking too long, turn off the options that spend time analyzing hidden content and unused styles. Disabling frame or deferred-image capture can also reduce work, but may leave parts of the page out.

There is no documented minimum connection speed or reliable time estimate. SingleFileZ still needs the page to load, and saving can involve fetching resources the browser has not displayed or cached. A slow save may therefore reflect the page’s resources and the extension’s processing as well as your connection. The SingleFileZ project FAQ and Mozilla add-on listing describe the workflow and its limits.

1. Load and save the page

Open the page in Firefox while you still have internet access. Wait until the page’s main content and important images finish loading. A page that loads content as you scroll may need more time or interaction before capture.
Click the SingleFileZ toolbar button. Leave the tab open while the extension processes and saves the page.
If you need to stop processing, click the toolbar button again to cancel.
Open the saved file while you are still connected, if possible. Check that the text, images, and other content you need are present.

SingleFileZ’s context menu also offers actions for saving the current tab, selected content, a selected frame or link, and groups of tabs. Its Mozilla listing documents Firefox Desktop and Firefox Mobile, including Firefox for Android, and a configurable Ctrl+Shift+Y keyboard shortcut. Browser permissions and interface details can differ by version.

2. Adjust options when processing is slow

Open the extension’s options and consider these changes if saving takes too long. The exact option labels are useful when locating them:

Option	What changing it may do	Tradeoff
HTML content > remove hidden elements	Turning it off can reduce processing time and CPU use.	Hidden page content may remain in the saved file.
Stylesheets > remove unused styles	Turning it off can reduce stylesheet analysis work.	The resulting file may retain styles the page does not need.
HTML content > remove frames	Turning frame removal off can avoid frame-related processing.	Frames may be missing from the saved page.
Images > save deferred images	Turning it off can avoid fetching images that were deferred.	Deferred or lazy-loaded images may be absent.

Start with hidden-element removal and unused-style removal: the project FAQ specifically identifies these as options that can save time and CPU. Change frame or deferred-image handling only if the missing content is an acceptable tradeoff. The FAQ says the default configuration is optimized to produce small pages; that does not mean every page will save quickly or that the extension can bypass a slow network.

3. What “entire webpage” includes

SingleFileZ aims to package a webpage and resources such as CSS, images, fonts, and frames into a single HTML/ZIP hybrid file. But a saved file is not guaranteed to be a perfect offline replica:

Not-yet-loaded content: Sites may load content only after scrolling, clicking, or waiting. Check important sections before saving.
Resources the page does not display: The FAQ says saving may fetch resources that are present but not displayed or already cached. This can add work even when the visible page looks ready.
Frames and deferred images: Disabling their capture can leave those resources out.
Browser restrictions: Browser security restrictions can prevent an extension from operating on some domains.
External or dynamic content: A page that relies on external resources or runtime interactions may not behave offline exactly as it did online.

4. Troubleshooting

Symptom	Likely cause	What to try
The page is incomplete in the saved file.	Some content had not loaded, was deferred, or was inside a frame.	Reconnect, wait for the page and images, scroll or interact to load important sections, then save again. Keep deferred-image and frame capture enabled if you need those resources.
Saving appears stuck or takes a long time.	The connection is slow, the page has many resources, or the extension is doing additional processing.	Allow the page to finish loading first. Turn off hidden-element removal and unused-style removal. If acceptable, turn off frame or deferred-image capture too.
The toolbar action does not work on a site.	Browser security restrictions may block extension access on that domain.	Try a page where the browser permits extension access. The FAQ does not provide a setting that overrides these restrictions.
The saved page opens but looks different.	Some resources may depend on the network, dynamic site behavior, or browser support.	Open the file in the browser you plan to use, while online if possible, and check whether the missing resource can be captured. Treat the archive as a saved copy, not a guarantee of identical offline behavior.
The extension or its instructions do not match current project guidance.	SingleFileZ has been merged into SingleFile.	See the project’s merge notice. It directs users to SingleFile’s options page and its File format section for self-extracting files; existing settings can be imported.

5. Privacy and optional cloud destinations

The project FAQ says the work is done in the browser and SingleFileZ does not upload data to third-party servers. It also explains that saving can download resources from the source page. Downloading those source-page resources is distinct from uploading the finished archive. The Mozilla listing describes optional Google Drive and GitHub destinations; neither is required for the local-save workflow.

6. A practical checklist before going offline

Open the page and wait for the main text and images to load.
Scroll through content that appears only as you move down the page.
Keep frame and deferred-image capture enabled if those parts matter.
If processing is slow, first disable hidden-element removal and unused-style removal.
Save the file locally, then open it and inspect the content you need.
Keep a second copy if the page is important; one saved archive cannot guarantee every external or dynamic feature will work offline.

7. Or skip the browser setup

If you need an image or PDF of a page rather than a self-contained offline webpage, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. It is not a replacement for SingleFileZ when you need a bundled HTML archive.

For a PNG screenshot, replace the example URL with the page you want to capture. See the ScreenshotNeo API documentation for available formats and options.

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

Cookie banners are accepted and removed before capture; known consent platforms, newsletter popups, and chat widgets can also be removed.
Bot checks, blank pages, and failed loads are never billed; response headers identify the page verdict and billing status.
An MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents and MCP clients.
The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.

FAQ

Can SingleFileZ save a page after the internet disconnects?

The page must load before you save it. Afterward, the saved file is intended to be opened locally, but externally hosted or dynamic content may still be missing or behave differently offline.

Will turning off processing options make a slow connection faster?

It can reduce some extension processing time and CPU use. It does not make the network faster or guarantee a shorter total save time.

Is SingleFileZ still a separate project?

The GitHub repository says it has been completely merged into SingleFile and points users to SingleFile’s File format option for self-extracting files. Mozilla’s listing still shows the SingleFileZ add-on, with a listed version and update date; that listing alone does not establish whether the extension is broken.

Does ScreenshotNeo save the webpage as one offline HTML file?

No. It returns a screenshot image or PDF. Use SingleFile or SingleFileZ when your goal is a bundled webpage archive.