Can SingleFile Preserve Links and Page Layout in an Offline Archive?

Generally, yes. SingleFile saves the current web page and resources such as stylesheets, images, fonts, and frames into one HTML file. That file can usually be opened offline in a browser, with the page’s recognizable layout and links still present. But saving a link is not the same as saving the page it points to: linked destinations may still require internet access, and dynamic features may not work offline. SingleFile’s project site describes the saved page as viewable offline in a browser without the extension.

What SingleFile preserves

SingleFile captures the page you are viewing and packages many of its resources into a standalone HTML file. Its official materials identify images, stylesheets, fonts, and frames as resources that can be included. This can retain the page’s visual structure and make the saved document useful when the original site is unavailable.

Links within the saved page may remain as references. If a link points to another page on the web, clicking it generally still needs a connection unless you separately saved that destination. SingleFile does not promise to recursively archive every page reachable from the captured page.

Page component	What to expect offline
Layout and styles	Often retained when the needed stylesheets and resources were available during capture.
Images and fonts	Can be embedded or otherwise included, but protected or unavailable resources may be missing.
Frames	Can be included as resources; inspect the saved result for the frames you rely on.
Links to other pages	May remain clickable references, but their destinations are not automatically captured as a site archive.
Interactive features	May not work. Scripts are removed by default, and saved scripts are not guaranteed to function offline.

Save and verify an offline copy

Open the page and wait until it has finished loading. The Chrome listing recommends waiting for the page to load before saving.
Use SingleFile’s browser extension to save the current page. If the page relies on deferred images or iframes, review the available options to load them before capture.
Save the resulting HTML file somewhere accessible, then open it in a browser.
For a meaningful offline check, disconnect from the network and inspect the parts that matter: layout, images, fonts, frames, links, and interactions.
If you need a linked page offline too, visit and save that page separately. Repeat for each destination you need; do not assume the first capture includes them.

The offline check is a practical verification step, not a guarantee that every resource or behavior will be preserved.

Links, layout, and interaction: the important distinctions

Link references versus archived destinations

A saved page may retain anchors and their target URLs. That preserves the reference, not necessarily the content at the target. A link to an external page ordinarily needs the network, and a relative link may not resolve as expected when the standalone file is opened from local storage. If offline navigation matters, capture the linked pages too and verify how their links behave in the local copies.

Visual layout versus complete resource availability

Layout fidelity depends on whether the browser could obtain the resources used to render the page. A page can look close to the original while still missing an image, font, or embedded frame. The SingleFile FAQ notes that some sites protect images against hotlinking. It says passing a Referer header after a cross-origin request error may help; this option is not enabled by default for privacy reasons.

Rendered appearance versus working JavaScript

SingleFile removes scripts by default because they can change rendering and are not guaranteed to work offline. This can preserve a useful visual snapshot while disabling behavior that depends on code. Folding sections, dynamic maps, carousels, menus, and other interactive elements may need JavaScript or live services.

The FAQ describes settings to allow scripts and, optionally, adjust treatment of hidden elements, unused styles, and raw page content. These settings can change the saved output; they do not ensure that a site’s interactive features will work without its server or network dependencies.

Options and scope to consider

Current page: the usual capture is a single page.
Selected content, frames, and links: the Chrome listing describes options for capturing selected content, selected frames and links, and multiple tabs. These are capture choices, not a promise to crawl and archive a whole website.
Deferred resources: the project lists options to load deferred images and iframes before capture.
Referer for protected resources: consider enabling the Referer option if protected images fail with a cross-origin request error.
Scripts and page content: scripts can be allowed through settings when you need to preserve more behavior or raw content, with the offline limitations above.
Local files in Chrome: Chrome blocks extension access to local files by default. To show SingleFile’s infobar on saved pages or save a page stored on the filesystem, enable “Allow access to file URLs” for the extension.

SingleFile is available as a browser extension and as a command-line version according to its project site. Check the official site for current browser install options and platform details.

When a standalone HTML file is not enough

SingleFile is suited to portable captures of individual pages. Its FAQ explicitly distinguishes it from tools used by professional web archivists, who often prefer WARC-based workflows. If your need is collection management, broader preservation, or repeatable archival records across many pages, evaluate an archival workflow designed for that scope.

The project says the work is performed in the browser and that it does not upload data to third-party servers. It also notes that it may download page resources that are present but not displayed or already cached. Treat this as the project’s description of its workflow, not as a broader privacy guarantee.

Troubleshooting

Problem	Likely cause	What to try
Images are missing	The resource was unavailable during capture or the site uses hotlink protection.	Wait for the page to finish loading, check deferred-image options, and consider the Referer setting if the FAQ’s cross-origin request condition applies.
The layout differs from the live page	A stylesheet, font, frame, or other resource was unavailable or loaded late.	Capture after loading completes, use options for deferred images and iframes where relevant, and inspect the saved file offline.
A link opens a blank page or fails offline	The linked destination was not saved, or the link requires the original site.	Save the destination separately and verify its local link behavior.
A menu, map, carousel, or folding section does not work	It depends on JavaScript, a remote service, or live data. Scripts are removed by default.	Try the script-related settings if appropriate, then verify offline. Some features cannot work without their original server or network.
SingleFile does not show its infobar for a local HTML file in Chrome	Chrome restricts extension access to local file URLs by default.	Enable “Allow access to file URLs” in the extension settings.

Performance, reliability, and cost

SingleFile’s capture work happens in the browser, and the project notes that it may fetch resources beyond those currently displayed. Pages with many or large resources may therefore take longer to capture or produce larger HTML files. Wait for loading to finish, then check that the result opens and contains the resources you need.

Reliability depends on the page’s state and resource access at capture time. A successful save is not proof that linked pages, scripts, or remote services are available offline. Keep the original URL with your saved file if you may need to revisit the source. The project describes SingleFile as free and open source; consult its official site for current details.

Or skip the browser setup

If your goal is a clean screenshot rather than a portable HTML archive, ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. One GET request returns a PNG, JPEG, WebP, or PDF, and its API documentation covers the request 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)
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 removes cookie banners, popups, and chat widgets before the shot. 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 a month with no card; paid plans start at $5 for 3,000 screenshots.

FAQ

Does SingleFile save a whole website?

No. It captures a page and offers options for selected content, frames, links, and multiple tabs, but it does not promise to recursively save every linked destination.

Can I open the saved HTML without installing SingleFile?

Yes. The project says saved pages can be displayed offline in a browser without the extension.

Will interactive features work if I allow scripts?

Not necessarily. A feature may need remote data, services, or other site behavior that the HTML file does not contain.

Is SingleFile intended for professional web archiving?

Its FAQ says it is not a tool used by professional web archivists and points to WARC-based approaches as the preferred direction for that work.