How to Save Webpages with SingleFile Without Embedded Fonts

To reduce font data in a SingleFile save, open the extension’s options and enable both Remove unused fonts and Remove alternative fonts under Fonts. These options target unused font CSS rules and alternative fonts; SingleFile’s documentation does not promise that they remove every embedded font from every saved page.

1. Open SingleFile’s options

1. Wait for the webpage to finish loading.
2. Right-click the SingleFile toolbar button.
3. Choose Options or Manage extension, then open its options page if needed.
4. In the Fonts section, enable both Remove unused fonts and Remove alternative fonts.
5. Save the settings if the options page asks you to, then save the webpage with SingleFile.

SingleFile recommends checking both options. They are cleanup controls intended to reduce the saved file’s size, rather than a setting documented to strip all font data.

2. Understand what the font options remove

Option	Documented behavior	When it helps
Remove unused fonts	Removes font CSS rules that do not match any content.	When the page includes font rules that its content does not use.
Remove alternative fonts	Removes fonts that are alternatives to the ones used.	When the page defines alternative fonts beyond the ones in use.

The help says each option should not alter the document and recommends enabling it. Treat that as intended behavior, not a guarantee for every site or every saved-file viewer. If you require a file with no embedded font resources whatsoever, these documented controls alone do not establish that guarantee.

3. Check the saved result

Save a fresh copy after changing the options. If you are inspecting the HTML source, look for embedded font data or font-related CSS, but remember that resource presence does not necessarily mean a font is displayed. SingleFile’s FAQ notes that resources present on a page may be saved even when they are not displayed or are already cached.

Compare the saved page with the original in the browser where you intend to view it. Removing font data can affect how text renders if a needed font is removed or unavailable; the documentation’s “should not alter” wording is not a universal rendering guarantee. Keep the original page or an unmodified save if exact appearance matters.

4. Troubleshoot when fonts remain

Symptom	Likely cause	What to do
Font data still appears in the saved HTML.	The options are selective; a font used by page content is not necessarily unused or alternative.	Confirm both font options are enabled. Do not interpret them as a remove-all-fonts switch.
The options appear enabled, but a new save behaves differently.	The save may use a different profile or page-specific automatic settings.	Check the effective profile for that save and confirm the options are enabled in it. Verify any page-specific auto-settings rule.
The saved page looks different.	A font needed for the page’s appearance may have been removed, or the viewing browser may render fonts differently.	Compare with the original, try a save with the cleanup options disabled, and retain the version that meets your fidelity needs.
Some resources seem unnecessary but are present.	SingleFile can save resources found on the page even if they are not displayed or are already cached.	Check whether the resource is actually referenced or rendered before treating its presence as a failure.
The result does not reflect the latest page state.	The page may still have been loading when saved.	Wait until the page is fully loaded, then save it again.

5. Performance, reliability, and file size

Removing unused and alternative font rules can considerably reduce file size, according to SingleFile’s help, but the amount depends on the page. There is no documented percentage or processing-time figure to rely on. Waiting for the page to finish loading helps ensure SingleFile captures the intended page state, though pages that continue changing after load can still vary between saves.

For repeatable results, use the same browser, profile, page state, and font settings for each save. If keeping typography exactly as displayed is more important than minimizing file size, compare a save with both options enabled against one with them disabled.

6. Save a rendered screenshot instead of a self-contained HTML file

If your goal is to keep a visual record rather than an editable, self-contained webpage, ScreenshotNeo captures a page as PNG, JPEG, WebP, or PDF. A screenshot records the rendered appearance; it does not create a saved HTML page that you can browse or edit offline.

Or skip the browser setup:

Make one GET request to capture a page. See the ScreenshotNeo API documentation for configuration details.

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 and consent banners, newsletter popups, and chat widgets before the shot; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server lets AI agents use screenshot and PDF capture tools. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.

Sign up for 1,000 free screenshots a month, with no card required.

FAQ

Does SingleFile have a setting that guarantees no embedded fonts?

The documented font options remove unused font CSS rules and alternative fonts. The documentation does not guarantee that all embedded font data will be absent.

Should I enable both font options?

Yes. SingleFile recommends checking both. Their scopes differ, so enabling one does not replace the other.

Will removing fonts always preserve the page’s exact appearance?

The help says the options should not alter the document, but it does not promise identical rendering on every site and browser. Compare the saved page with the original when fidelity matters.

Why does the saved file include a font resource that is not visible?

SingleFile’s FAQ says resources present on the page may be saved even when they are not displayed or are already cached.