SingleFile Chrome Extension Review: What It Saves and What It Misses
SingleFile saves a webpage and its resources as one HTML file. See what it preserves, where gaps can appear, and how to troubleshoot offline copies.
SingleFile is a Chrome extension that saves a webpage as one HTML file, with associated resources such as CSS, images, fonts, and frames. Wait for the page to finish loading, then click the SingleFile toolbar button. The result is useful for keeping many pages for offline reading, but it is not a guarantee that every interactive or dynamic detail will survive.
What SingleFile saves
The Chrome Web Store listing describes a saved page as a single HTML file that can include its CSS, images, fonts, and frames. SingleFile’s FAQ says it can fetch resources present in the page even when they are not displayed or already cached. That can make the resulting file substantially larger than the visible text alone suggests. “Complete” describes the product’s goal; fidelity can vary with the page and browser restrictions.
Depending on the workflow and settings, SingleFile also offers annotation tools to highlight text, add notes, or remove content, as well as options for saving selected content or frames. You can use context-menu actions for the current tab, selected links, or groups of tabs. The extension listing also describes autosaving after pages load and a configurable keyboard shortcut.
What it can miss
The project’s documented known issues include cases where browser security prevents saving the image representation of a canvas or a snapshot of a video element. Certain protected pages, including pages hosted on chrome.google.com, addons.mozilla.org, and some other Mozilla domains, cannot be saved for security reasons.
These limitations do not mean ordinary images always fail or that all video-related content is lost. They mean that special page elements and restricted origins need to be checked in the saved result. Dynamic content also deserves care: the store instructs users to wait until a page is fully loaded, but behavior for lazy-loaded, authenticated, scripted, or highly interactive pages depends on the page itself. Save a representative sample and inspect it before relying on an archive workflow.
Save a page in Chrome
- Open the page you want to keep and allow it to finish loading. If important content appears after a delay or an interaction, wait for that content first.
- Click the SingleFile toolbar button to start saving.
- Wait for processing to finish, then open the resulting HTML file and check the sections and media you care about.
- If processing is underway and you want to stop it, click the toolbar button again to cancel, as described in the extension listing.
For batch work, use the extension’s context-menu actions for selected links or selected, unpinned, or all tabs. For a focused archive, consider saving selected content or a selected frame where that is the material you need. Review the output after changing annotation or content-removal options, since those tools intentionally alter the saved page.
Options and practical choices
| Need | Relevant SingleFile capability | What to check |
|---|---|---|
| Keep a whole page | Save the current tab as one HTML file | Confirm the page finished loading and inspect the saved copy. |
| Keep only a portion | Save selected content | Check whether the selection includes the context or resources you need. |
| Save a frame | Save a selected frame | Verify the frame’s content independently in the result. |
| Archive several pages | Save selected links or batches of tabs | Keep batches manageable and check that each page completed. |
| Annotate or simplify | Highlight text, add notes, or remove content | Make sure edits do not remove material needed for later reference. |
| Automate saving after load | Autosave option and keyboard shortcut configuration | Validate timing on pages whose content arrives dynamically. |
Chrome may require the “Allow access to file URLs” permission on the extension page to show SingleFile’s infobar when viewing a saved page or to save a page already on the filesystem. This is a browser permission for local files; it is not a requirement for saving ordinary web pages.
How to check an offline copy
- Open the saved HTML file locally in Chrome.
- Compare the parts that matter: text, images, styles, embedded frames, and any relevant interactive content.
- Check pages with canvas or video elements separately because their image or snapshot representations may be unavailable.
- For pages behind authentication or pages that populate content through scripts, verify the saved copy with the same kind of page you intend to archive. The available documentation does not establish a universal result for those cases.
- Keep the original URL with your archive if you may need to revisit the live source or check for later changes.
ScreenshotNeo alternative for image captures
SingleFile is for a portable HTML copy. If your goal is a rendered screenshot or PDF rather than an offline webpage archive, ScreenshotNeo is the alternative to try first. It is a website screenshot API and MCP server: one GET request returns a PNG, JPEG, WebP, or PDF. It is not a replacement for an HTML archive.
ScreenshotNeo accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and responses identify page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. Plans include 1,000 shots per month free with no card; paid plans start at $5 for 3,000 shots. Every feature is available on every plan.
For setup, parameters, and the other capture options, see the ScreenshotNeo documentation.
Or skip the browser setup
Use a single GET request to capture a rendered page. This runnable cURL example saves a WebP image:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpCookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. You get 1,000 screenshots a month free with no card; paid plans start at $5 for 3,000. Sign up for free.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Part of the page is absent | The content may not have loaded before saving, or it may depend on scripts or interaction. | Wait for the page to finish loading, trigger the needed content, save again, and inspect the local file. |
| A canvas or video looks blank or missing | Browser security can prevent saving a canvas image representation or video snapshot. | Check whether the information is available in another form on the page; do not assume the media can be reconstructed from the saved file. |
| A protected site cannot be saved | Chrome security restrictions block some browser and add-on store pages. | This is an origin restriction documented by the project. Save a permitted page instead. |
| The SingleFile infobar does not appear on a local file | Chrome may not have granted access to file URLs. | Open the extension’s Chrome settings and enable “Allow access to file URLs” if you need the infobar or need to save a filesystem page. |
| The file is much larger than expected | The archive can include resources present in the page even if they are not visible or already cached. | Allow for resource-heavy pages to produce larger files, and check that the saved artifact fits your storage and sharing needs. |
| A batch is incomplete | Some tabs may still be loading or may encounter a page-specific restriction. | Review each result and retry individual pages after they finish loading. |
Performance, reliability, and cost
SingleFile runs in the browser and produces a local HTML artifact. Capture time and output size depend on the page and the resources it includes; the documentation cited here gives no universal time or size benchmark. Resource-heavy pages can take longer to process and produce larger files. Wait for completion, use cancellation if needed, and validate representative pages before making an archive process routine.
The result is useful for offline reading, but it should not be treated as a guaranteed interactive replica. Protected origins, canvas and video representations, and pages that change dynamically are relevant reliability limits. The cited materials do not establish a controlled comparison with Chrome’s built-in save formats or competing archivers, so choose based on whether you need one HTML file, annotations or batch saving, and whether your pages rely on elements that may not serialize.
The cited SingleFile materials do not state a purchase price. ScreenshotNeo’s listed pricing is free for 1,000 shots per month without a card, then Starter at $5 for 3,000, Growth at $15 for 15,000, Pro at $39 for 60,000, Scale at $99 for 250,000, and Business at $249 for 1,000,000; yearly billing gives two months free. Compare those costs only for screenshot or PDF capture needs, since that output differs from SingleFile’s HTML archives.
FAQ
Can I open a SingleFile page offline?
The purpose of saving the page and associated resources into one HTML file is to keep it available as a local copy. Open the saved file offline and verify that the parts you need are present.
Does SingleFile preserve the exact live page?
Not necessarily. The product aims to save the page and its resources, but browser security and dynamic page behavior can affect what survives.
Does a missing video mean SingleFile cannot save videos?
No universal conclusion follows. The documented limitation concerns cases where browser security prevents saving a snapshot of a video element.
Is it the right tool for a screenshot?
Use SingleFile when you need a local HTML archive. For a rendered image or PDF, a screenshot service such as ScreenshotNeo serves a different purpose.
Sources
- SingleFile official project repository — workflow, supported browsers, and known issues.
- SingleFile on the Chrome Web Store — stated output, features, and setup guidance.
- SingleFile official FAQ — resource handling and Chrome file URL context.
