How to Save Online Study Notes as Offline Webpages with SingleFileZ

To save online study notes as an offline webpage, use the current SingleFile browser extension and choose its self-extracting file format. SingleFileZ is no longer a separate project: its repository says it was completely merged into SingleFile. You can also import former SingleFileZ settings into SingleFile.

The self-extracting format packages a page and its resources into one HTML/ZIP hybrid file. Save the page while it is fully loaded, open the saved file locally to check it, and remember that browser rules—especially Chrome’s handling of local files—can affect whether it opens as expected.

1. What happened to SingleFileZ?

SingleFileZ’s project page announces that it has been completely merged into SingleFile. For a new setup, install or open SingleFile and configure its File format option. If you used SingleFileZ before, import your old settings where available. Do not assume an old SingleFileZ installation is the current extension or that its old workflow is the only way to create self-extracting files.

SingleFile is a browser extension, not a command-line program. There is no SingleFileZ command or code snippet required for the basic save workflow: use the browser interface described below.

2. Save a study page as one offline file

Install or open SingleFile. Use the extension store for your browser and review the extension’s permissions and settings.
Set the output format. Open SingleFile’s settings and choose the self-extracting file format. If you want a conventional HTML file instead, choose the ordinary HTML format.
Open the study notes page and wait. Let the page finish loading before saving. If notes, images, or other content appear only after scrolling or waiting, allow that content to load first.
Save the current page. Click the SingleFile toolbar button. The extension listing also documents context-menu actions for saving selected content, frames, links, or multiple tabs. The “Annotate and save the page…” command can highlight text, add notes, or remove content before saving.
Find the file. SingleFile saves to the browser’s configured downloads folder unless you choose another destination through the browser’s download flow. Move it into a clearly named study folder if that helps you organize notes by class or topic.
Verify it before going offline. Open the saved file from the filesystem while you still have internet access. Check the important text, diagrams, images, and page sections. This catches missing resources or browser-specific opening problems before you need the notes offline.

The self-extracting result is a single file that contains the page and its resources. It is also a valid ZIP archive and can be extracted if you need to inspect or recover its contents. It requires JavaScript to open in its intended self-extracting form.

3. Can I open a SingleFileZ page offline in Chrome?

Sometimes, but local-file behavior depends on the browser and the file format. The SingleFileZ FAQ says Chrome requires the SingleFileZ extension or a command-line switch to open local SingleFileZ pages. Since SingleFileZ has merged into SingleFile, use the current extension and consult its current documentation for the supported local-file workflow. Do not assume double-clicking a self-extracting file will work in every Chrome configuration.

The FAQ describes different conditions for Firefox and Safari. A page hosted on a web server is not subject to the same local-file restrictions, but hosting a copy changes where it is stored and potentially who can access it. For offline study, test the local file in the browser and setup you plan to use.

4. Choose the right saved-page format

SingleFile documents several formats. The best choice depends on whether you need one file, compression, broad browser compatibility, or later access to the embedded resources.

Format	One file?	Compressed?	JavaScript needed to open?	Portability and extraction
Ordinary HTML	Yes, but external resources may depend on how the page is saved and configured	No	No	Can be viewed without running JavaScript; check whether all resources are embedded for your chosen settings.
Self-extracting ZIP / HTML	Yes	Yes	Yes	Page and resources are packaged together; the file can also be extracted as a ZIP. Local opening has browser-specific conditions.
MHTML	Yes	Format-specific	No self-extraction step	Browser support differs, so test the target browser before relying on it.
Safari Webarchive	Yes	Format-specific	No self-extraction step	Intended for Safari workflows; do not assume other browsers will handle it identically.
HTML plus folder	No	No	No	The HTML and resources are separate, which can be useful when inspecting files but makes moving the page easier to disrupt.

For the specific goal of one portable file with extractable resources, use the self-extracting format. If avoiding JavaScript when opening the saved page matters more, ordinary HTML may be a better fit. Browser support for MHTML and Webarchive varies; verify the format in the browser you will actually use.

5. Settings and content that can affect the result

Saving a web page is more than copying the text currently visible. SingleFile can collect resources such as images, CSS, frames, and fonts, including resources that may not already be displayed or cached. That can improve completeness and increase processing time or file size.

Wait for deferred content: let lazy images and page sections load before capturing. The FAQ notes that speed-related settings can omit deferred images.
Frames: content inside frames may need to be included. The FAQ notes that disabling frame removal can affect the result; check the relevant setting if an embedded section is absent.
Cleanup and speed: disabling hidden-element cleanup or unused-style removal may improve speed, but the output can include more page data.
Annotations and selection: use the annotate-and-save command for highlights, notes, or removing content; use context-menu actions when saving a passage, frame, link, or group of tabs.
Protected pages: browsers block extensions on certain protected domains for security reasons. The extension may not be able to save those pages.
Access and terms: inspect the result rather than assuming logged-in, interactive, streaming, or access-controlled study content will be preserved perfectly. Follow the source site’s terms and copyright rules.

6. Privacy and where the saved page goes

The SingleFileZ FAQ says processing takes place in the browser and that it does not upload data to third-party servers. That describes the local capture workflow. The extension can upload to destinations such as Google Drive or GitHub if you explicitly enable those options, so check your settings if you want the saved copy to remain on your device.

A USB flash drive is optional. It can carry or back up saved pages for use on another computer, but it is not required by SingleFile. Keep a second copy only if it fits your backup needs, and verify the copy opens before relying on it.

7. Troubleshooting

Symptom	Likely cause	What to do
The extension cannot save the page	The browser blocks extensions on a protected domain.	Try saving from a normal webpage where extensions are allowed. Browser security restrictions cannot be bypassed by a page-capture setting.
Chrome will not open the local self-extracting file	Chrome applies special restrictions to local files in this format.	Use the supported SingleFile extension workflow or the command-line approach documented by the SingleFileZ FAQ. Confirm the current SingleFile instructions after the project merger.
Images or embedded sections are missing	Content may not have loaded yet, may be deferred, or may be in a frame affected by settings.	Reconnect, reload the source page, wait for content to appear, review frame and deferred-image options, save again, and inspect the copy.
The save is slow or the file is large	The page has many resources, or settings are collecting hidden content and styles.	Review hidden-element cleanup and unused-style removal settings. Disabling those cleanups may improve speed, though it can leave more data in the saved page.
The page works online but not offline	The local browser may handle the format differently, or the page may rely on interactive or access-controlled behavior.	Test the saved file in the target browser before disconnecting. Treat the saved copy as a snapshot, not a guarantee that live features or protected content will continue to work.
The file is not where expected	The browser uses its own download location or prompts for a save destination.	Check the browser’s downloads list and configured download folder, then move the file into your study folder if needed.
You are unsure whether the file is complete	Not all content may have loaded or been captured.	Open it while online and check the specific notes and resources you need, including images and frames.

8. Performance, reliability, and file size

Capture time and output size depend on the page and the resources SingleFile collects. A page with many images, stylesheets, fonts, or frames can take longer and produce a larger file than a mostly textual page. Waiting for the page to finish loading improves the chance that deferred material is present, while the extension’s speed options can trade completeness for a faster save.

For reliable study access, verify the file in the browser where you plan to read it, keep the original page URL with your course notes, and retain a second copy if the notes matter. A saved webpage is a snapshot: it does not guarantee that interactive services, streaming media, sign-in flows, or access-controlled material will work offline.

Or skip the browser setup

If you need a screenshot of a study page instead of a self-contained webpage, ScreenshotNeo provides a website screenshot API and MCP server. It returns PNG, JPEG, WebP, or PDF from one GET request; screenshots are images or documents, so use SingleFile when you specifically need an offline webpage you can reopen and browse.

For API parameters and the complete option list, see the ScreenshotNeo documentation. Example using the supplied endpoint and a public URL:

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)
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 Bun.write('shot.webp', new Uint8Array(await res.arrayBuffer()));

In a Node.js project that does not use Bun, replace the final line with a file-writing method such as await import('node:fs/promises').then(({writeFile}) => writeFile('shot.webp', Buffer.from(await res.arrayBuffer()))) inside an async function.

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. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for free ScreenshotNeo screenshots.

FAQ

How do I save study notes to read offline?

Choose SingleFile’s self-extracting format, save the fully loaded page, and verify the local file while you are still online.

How do I save a webpage as one file?

In SingleFile settings, select the self-extracting file format, then use the toolbar button on the page. The resulting HTML/ZIP hybrid contains the page and its resources.

Can I open a SingleFileZ page offline in Chrome?

The SingleFileZ FAQ says Chrome needs the extension or a command-line switch for local saved files in this format. Since SingleFileZ merged into SingleFile, check the current SingleFile workflow and test your file before going offline.

Can the self-extracting file be unpacked?

Yes. The listing and README describe the self-extracting file as a valid ZIP archive that can be extracted.