Does SingleFileZ Preserve Links and Page Formatting for Offline Viewing?

Short answer: SingleFileZ is designed to save a webpage and its captured resources as a self-extracting ZIP/HTML file, preserving much of its appearance for offline viewing. That does not guarantee pixel-perfect formatting on every site, make every linked destination available offline, or keep interactive features working. SingleFileZ has been merged into SingleFile; the current continuation is SingleFile’s self-extracting file format. The SingleFileZ repository points users to that option.

What “preserve links and formatting” means

Question	Practical answer
Will the saved page look like the original?	It is intended to retain the captured presentation and resources such as CSS, images, frames, and fonts. Results can vary by page and browser; fidelity is not guaranteed to be exact.
Does it preserve links?	A visible link may remain in the saved page, but that does not mean its destination was saved too. An external link usually still needs a network connection.
Can I click links without internet?	Only links whose destinations are available locally can work offline. SingleFileZ does not promise to save every linked page or create an offline copy of an entire site.
Will interactive elements still work?	Not necessarily. Scripts are blocked by default in SingleFile because they can alter rendering and are not guaranteed to work offline. Maps, carousels, expandable sections, and similar controls can behave differently.

Keep the distinction clear: formatting and resources belong to the captured page; a link points somewhere else. Saving one page is not the same as downloading the site it links to.

How to save and check a page with SingleFile

Install or open SingleFile in a supported browser and load the page you want to keep. Wait for the content you need to appear, including deferred images.
Open SingleFile’s options and choose File format. To continue the old SingleFileZ workflow, select a self-extracting ZIP format. The current format documentation distinguishes the universal and standard variants.
Save the page, then disconnect from the network or otherwise test it offline. Open the saved file in the browser you plan to use and check the sections, images, fonts, and links that matter.
Click representative links. If a destination is not itself stored locally, expect it to need a connection. Test interactive controls separately; their presence in the saved page does not ensure offline behavior.

SingleFile’s format options have tradeoffs. The regular HTML format does not depend on JavaScript to open. The self-extracting ZIP formats need JavaScript to open. The universal self-extracting ZIP format is intended to work from the filesystem across platforms; the other self-extracting ZIP format can encounter filesystem restrictions in Chromium- or WebKit-based browsers unless SingleFile is installed. The standard format is documented as producing files approximately 1% smaller than the universal format. A plain ZIP is not directly opened as a webpage in a browser.

For the exact browser and format behavior, see the SingleFile help for file formats and the SingleFileZ FAQ. Browser security and extension behavior can change, so test the resulting file in your target browser.

Links: what is saved and what is not

The official material describes capturing page resources; it does not make a blanket promise that all links are rewritten or that linked pages become available offline. A link can still be present and clickable while leading to a network-only address. If offline navigation across multiple pages matters, save and verify each required page independently, or use a web archiving workflow designed for collections.

External link: usually navigates to its original web address and therefore requires a connection.
Fragment link: a link to a section in the current page may work if that section and its anchor are present in the saved document.
Link to another saved file: it works only if its target exists at the expected local path and the browser permits that navigation.
Link to content behind a login or session: saving the current view does not guarantee that the linked destination or its protected content is captured.

Before relying on an offline copy, test the links that matter while disconnected. Do not infer that a link works offline just because its text and destination are visible in the saved HTML.

Formatting, resources, and interactive behavior

SingleFileZ’s stated purpose is a faithful copy of a page in a self-extracting ZIP file. Its FAQ describes capturing CSS, images, frame contents, and fonts, including resources present on the page even if they are not displayed or cached. This supports a qualified expectation of retained visual formatting, not a promise of identical rendering on every page or browser. See the SingleFileZ FAQ.

Scripts are a separate concern from appearance. SingleFile’s FAQ says scripts are blocked by default because they can change rendering and are not guaranteed to work offline. It documents options to save scripts and raw page content, but enabling them is an experiment, not a guarantee of functional offline behavior. Scripts may expect network services, session state, or browser capabilities that are unavailable in the saved copy. Review the SingleFile FAQ on interactive elements before changing those settings.

Settings that affect fidelity and speed

Setting or choice	Effect to consider
Remove hidden elements	Can reduce processing, but hidden content will not remain available in the saved page.
Remove unused styles	Can reduce processing and output size; styles needed only in a later state may be omitted.
Remove frames	Can make saving faster, but frame content may be missing.
Save deferred images	Disabling this can leave images that load lazily out of the saved file.
Allow scripts or save raw page	May help some dynamic content, but scripts may still require the original network, session, or runtime environment.

The first four tradeoffs are described in the SingleFileZ FAQ; the script behavior is described in the SingleFile FAQ.

Browser compatibility and opening saved files

The SingleFileZ FAQ documents browser-specific restrictions for self-extracting files opened directly from the filesystem. It says Firefox and Safari can view them under stated conditions, while Chrome requires the extension; it also says hosting the saved page on a server avoids those filesystem restrictions. Because browser security rules and extension behavior can change, treat this as a compatibility note to verify, not a permanent guarantee.

If you are choosing a format for local offline reading, the current SingleFile help describes self-extracting ZIP (universal) as the portable choice, with JavaScript required to open it. The non-universal self-extracting ZIP can be smaller, but can face local-file restrictions in browsers based on Chromium or WebKit unless SingleFile is installed. Regular HTML avoids the self-extracting JavaScript requirement. Test your actual saved file and browser combination before sharing it.

Troubleshooting incomplete or unexpected saves

Symptom	Likely cause	What to try
Images are missing	Images may be deferred, unloaded, or dependent on a cross-origin request or referrer.	Wait for images to load before saving; check the deferred-image setting. For sites that require a referrer, consult SingleFile’s FAQ and its documented cross-origin referrer option.
Frames or embedded content are absent	The page may use frames, or a speed setting may omit them.	Check that frame removal is disabled and save again. Some embedded content can still depend on live services.
Styles or fonts differ	A resource may not have been captured, or browser rendering may differ.	Try saving after the page is fully loaded. Review options that remove unused styles, then reopen the result in the intended browser.
A map, carousel, or folding section does not respond	Its scripts may have been blocked, or its behavior may require network services.	Read the SingleFile FAQ’s script guidance. You can try adjusting script and raw-page options, then test offline; the result is not guaranteed.
A self-extracting file will not open locally	The selected ZIP format may rely on a browser extension or a filesystem capability the browser restricts.	Try the universal self-extracting ZIP format or regular HTML, or open it in a browser with SingleFile installed. Check the current format documentation.
Saving is slow	Removing hidden elements and unused styles can take extra processing.	The SingleFileZ FAQ suggests disabling those optimizations to speed saving. Recheck the output because changing options can affect what is retained.
The extension cannot save a particular page	Browsers block extensions on some protected domains for security reasons.	Check the extension’s FAQ for restricted-domain behavior; this may not be a setting you can override.

Performance, reliability, and archival limits

Saving a page involves processing its content and resources, so complex pages can take longer and produce larger files. The SingleFileZ FAQ specifically notes that removing hidden elements and unused styles can improve speed, while removing frames or skipping deferred images can result in missing resources. Choose settings based on whether you prioritize a quick compact copy or retaining the content you need.

For reliability, verify important pages after saving: reopen them offline, inspect key visual sections, and test required links. Keep the original URL and capture date alongside the file when context matters. The saved copy represents a captured state; it is not a guarantee of the site’s future state or complete reproduction of server behavior.

SingleFile’s FAQ says the extension is not intended as a professional web archiving tool and points to tools based on the WARC specification for that use. Use SingleFile for convenient self-contained reading or sharing, and choose a WARC-based workflow when archival completeness and replay are requirements.

Or skip the browser setup

If you need a visual record of a page rather than a self-contained HTML file with links, ScreenshotNeo can return a screenshot or PDF through one API request. It does not create an offline navigable copy: use SingleFile for that. ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed; and its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots per month with no card, and paid plans start at $5 for 3,000. See the ScreenshotNeo API documentation.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python

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()
with open("shot.webp", "wb") as image:
    image.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(({ writeFile }) => writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));

FAQ

Is SingleFileZ still maintained as a separate project?

The SingleFileZ repository says it has been completely merged into SingleFile. Use SingleFile’s self-extracting file format option as the current continuation.

Can a saved page link to another saved file offline?

Potentially, if the target file is present at the path the link expects and the browser allows the local navigation. Verify the exact files and links offline.

Is a saved SingleFile page a complete web archive?

No. The SingleFile FAQ explicitly distinguishes it from professional web archiving and points to WARC-based tools for that purpose.

Does ScreenshotNeo make an offline copy?

No. ScreenshotNeo returns a screenshot or PDF. For an offline webpage with page markup and links, save it with SingleFile and check the result offline.