SingleFileZ vs WebScrapBook for Archiving Webpages
Compare SingleFileZ and WebScrapBook by archive format, collection features, browser support, setup, and portability—and choose the right fit.
Choose the SingleFile lineage when you mainly want one webpage saved as a portable, self-contained file. Choose WebScrapBook when you want to build and search an organized collection, annotate pages, and choose among several archive formats. One important status detail: the SingleFileZ repository says SingleFileZ has been completely merged into SingleFile; its self-extracting format is available as a format option there. Check the SingleFileZ project status and guidance before installing or relying on older SingleFileZ instructions.
This is a comparison of documented workflows and features, not a controlled capture-quality or performance test. Neither tool guarantees that every interactive webpage can be reproduced perfectly. Try the current browser version on representative pages before adopting either workflow for important archives.
At a glance
| Need | SingleFileZ / SingleFile | WebScrapBook |
|---|---|---|
| Save one page into a portable file | Its distinctive self-extracting HTML file is also a ZIP archive containing page resources. The project says this feature has moved into SingleFile. | Can save a single HTML file, as well as folders and archive formats such as HTZ and MAFF. |
| Manage a collection | SingleFile supports page capture and annotation; its documented workflow is not primarily a hierarchical scrapbook tree. | Supports one or more hierarchical scrapbooks, notes, editing, annotation, and indexed full-text search. Some collection features depend on its backend. |
| Choose among archive formats | SingleFile documents its own HTML and SingleFileZ formats and compares them with formats such as MAFF, MHTML, Safari Webarchive, and HTML-plus-folder. These are not all SingleFileZ output formats. | Documents folder, HTZ, MAFF, and single HTML options. |
| Use on mobile | SingleFile documents Firefox mobile support; check the current extension support for your exact browser. | Documents Firefox for Android and Kiwi, and says iOS is unsupported. |
| Set up remote or searchable collection features | Browser-extension workflow for saving pages. | Some collection, search, and remote capabilities require the PyWebScrapBook backend. |
What happened to SingleFileZ?
SingleFileZ is no longer a separate actively maintained project according to its repository: it says the project has been completely merged into SingleFile and directs users to SingleFile’s “File format” option to save self-extracting pages. If you are following an old tutorial, check whether it refers to the former extension or the current SingleFile option before installing or troubleshooting.
The format is intended to put a webpage and its resources into one self-extracting HTML file that is also a ZIP archive. Its portability has a caveat: the saved page requires JavaScript to open, and browser handling of local files differs. The SingleFileZ FAQ notes Chrome restrictions when opening these files from the filesystem and says saving and opening can take longer than with SingleFile. Treat that as a browser- and settings-dependent limitation, and verify it in your target environment.
How the archive formats differ
SingleFileZ / SingleFile: a page you can carry as one file
The main appeal of the SingleFileZ format is the one-file archive: page content and resources are packaged together rather than delivered as a separate HTML file plus an assets folder. This can make it convenient to move or share an individual saved page. SingleFile’s documentation also describes other format choices and related formats; check the current format setting and documentation so you know exactly what the extension will produce.
Because the self-extracting file uses JavaScript and is opened from the local filesystem, it may not behave like an ordinary static HTML file in every browser. If a recipient’s browser restricts local-file behavior, use a format and opening workflow they support, or choose another documented archive format.
WebScrapBook: choose a format for the collection
WebScrapBook documents several ways to store a capture: a folder, a ZIP-based HTZ or MAFF archive, or a single HTML file. The right choice depends on how you expect to open, move, inspect, or manage the archive. A single HTML file is convenient to carry; folders expose their contents as separate files; archive formats package content; a scrapbook adds organization around the saved pages.
WebScrapBook’s collection workflow includes hierarchical scrapbooks, notes, annotation and editing, and indexed full-text search. Some of these capabilities, as well as remote access, are documented as depending on PyWebScrapBook. Account for that backend in your setup decision rather than assuming every feature is provided by a standalone browser extension.
Organization, editing, and search
If you save pages as evidence, reading material, or project references, collection management may matter more than whether each capture is a single file. WebScrapBook is the stronger fit in the reviewed documentation for users who want pages organized into a hierarchy and want notes, annotations, editing, and indexed full-text search. Confirm which features require the backend for your intended deployment.
SingleFile also documents annotation features, including highlighting, notes, and removing content through “Annotate and save the page.” That can help curate an individual capture. The cited documentation does not describe its main workflow as a scrapbook tree with the same collection-management emphasis.
Browser and device support
WebScrapBook documents desktop Chromium-based and Firefox-based browsers, plus Firefox for Android and Kiwi. Its documentation reports no iOS browser support. SingleFile documents Firefox mobile among compatible environments. Browser extension availability and local-file behavior can change, so check the current project documentation and extension store for your exact browser and version.
For a team, check more than whether the extension installs. Confirm that every user can save in the required format, open the resulting archive, and use any backend-dependent feature from their device. If archives will be shared, test the recipient’s browser too.
Privacy and preservation limits
The SingleFileZ FAQ says processing happens in the browser and that it does not upload data to third-party servers. This is a statement about SingleFileZ as described in that FAQ; it does not establish an equivalent privacy comparison for every WebScrapBook configuration. For WebScrapBook, consider whether you use local capture only or configure a backend and remote access, and review the current project documentation for the setup you choose.
Neither archive should be treated as a perfect copy of every live application. The SingleFile documentation lists caveats involving browser-internal and add-on pages, some canvas or video snapshots, and some sandboxed frames. Dynamic content, authentication, scripts, and external resources can also affect what a capture contains. The practical safeguard is to open and inspect representative archives, especially before depending on them for long-term preservation.
Which one should you choose?
- Choose the SingleFile lineage if you usually save one page at a time and want a self-contained file. Use SingleFile’s current format option for the self-extracting behavior that was associated with SingleFileZ.
- Choose WebScrapBook if you want multiple documented archive formats and a managed, searchable collection with annotations, and a PyWebScrapBook backend fits your needs where required.
- Test both on the pages that matter. Include pages with images, long or lazy-loaded content, interactive elements, and any browser-specific behavior your workflow depends on.
Or skip the browser setup
If your goal is to get a screenshot of a page for documentation, review, or an AI workflow—not to maintain a local archive collection—ScreenshotNeo is the alternative to try first: it returns a screenshot or PDF through one API request. It is a capture service, not a replacement for a scrapbook archive.
For example, this cURL request saves a WebP screenshot of a page. See the ScreenshotNeo API documentation for the available parameters.
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 Bun.write('shot.webp', new Uint8Array(await res.arrayBuffer()));ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots, and the free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month, with no card.
Troubleshooting
| Problem | Likely cause | What to do |
|---|---|---|
| A SingleFileZ tutorial does not match the extension or settings you see | The project says its feature was merged into SingleFile, so older instructions may refer to the former project. | Use the current SingleFile documentation and look for its “File format” option for self-extracting pages. |
| A self-extracting archive will not open from disk | JavaScript is required, and browser local-file restrictions differ. The SingleFileZ FAQ specifically notes restrictions in Chrome. | Try a supported browser and opening workflow, check the current format documentation, or save in a different format suited to your recipient. |
| Opening or saving a self-extracting page is slow | The SingleFileZ FAQ says this format can take longer than SingleFile; page size and resources may also affect your experience. | Test on representative pages. If one-file self-extraction is not required, use a different format offered by the current tool. |
| WebScrapBook search or remote collection features are unavailable | Some documented capabilities depend on the PyWebScrapBook backend. | Check the feature’s backend requirement and configure the backend if it is needed for your workflow. |
| A capture is missing content or behaves differently from the live page | Some browser pages, frames, canvas/video content, or dynamic resources have capture limitations. | Review the tool’s known caveats, capture from a supported page and browser, and inspect the saved result before relying on it. |
| The extension is unavailable on a phone or tablet | Support varies by browser and operating system; WebScrapBook reports no iOS support. | Check current browser extension support. WebScrapBook documents Firefox for Android and Kiwi; SingleFile documents Firefox mobile. |
Performance, reliability, and cost
The reviewed project documentation does not provide a controlled head-to-head speed or fidelity benchmark, and no relevant named performance statistics were found. Do not choose on an assumed speed ranking. Page size, resource loading, browser restrictions, and format affect the experience; test your own pages and opening devices.
Both workflows involve browser capture, so results can depend on the browser and page state at save time. For WebScrapBook, include backend setup and maintenance in the operational cost if you need backend-dependent collection or remote features. For either tool, preserve the original URL and capture date in your own recordkeeping if provenance matters, and keep additional copies of archives you cannot afford to lose. The research sources provide no prices for either project; check current project listings for any costs or hosting requirements relevant to your setup.
FAQ
Is SingleFileZ still a separate project?
The repository says it has been completely merged into SingleFile and directs users to SingleFile’s format option for self-extracting pages.
Can WebScrapBook save one page as a single file?
Yes. Its documentation lists single HTML as one option, alongside folders, HTZ, and MAFF.
Does WebScrapBook require a server?
Some collection, search, and remote capabilities require the PyWebScrapBook backend. Check the requirements for the particular feature you want.
Which is better for long-term preservation?
There is no universal winner in the reviewed evidence. Choose based on the archive format and collection workflow you can open and maintain, then test important pages and target browsers before relying on the result.
