Save Page WE Settings to Reduce Saved HTML File Size

To reduce a saved page’s file size in Save Page WE, enable Merge duplicate CSS images. For a smaller file, choose Basic Items if its included resources are enough, or use Custom Items and deselect resource types you do not need offline. Save a sample and open it to confirm the content you care about is still available.

These settings do not promise a particular reduction. Save Page WE’s documentation identifies merging duplicate CSS images as a way to reduce file size, but does not publish a percentage or benchmark. The result depends on the page and the resources it uses.

1. Enable duplicate CSS image merging

Open Save Page WE’s options.
Find and enable Merge duplicate CSS images.
Save a page that uses repeated CSS images and compare its size with a prior save if you want to assess the effect on your own page.

This option targets duplicate images referenced by CSS. It is not a general image compressor: it does not promise to reduce the dimensions or quality of every image. The documentation says CSS images referenced repeatedly within a frame are stored once in that frame.

2. Choose which page resources to save

Save Page WE stores the current HTML and referenced resources together in one HTML file. External stylesheets become internal stylesheets, and binary resources such as images, fonts, audio, and video can be embedded as Base64 data URIs. Selecting fewer resource classes can therefore produce a smaller file, at the cost of offline completeness.

Setting	What it includes	When to choose it
Basic Items	HTML elements; currently displayed HTML images; canvas graphics; CSS stylesheets; currently displayed CSS images; and CSS fonts used by the browser.	Choose this lean preset when the displayed page and its basic styling are enough. It still includes currently displayed images and other basic resources.
Standard Items	Basic Items plus all HTML images, HTML audio and video, HTML object and embed files, and WOFF CSS fonts for any browser.	Choose this when you want broader media and object coverage offline. It may create a larger file than Basic Items because it can include more resource classes; this is an inference from the documented inclusions, not a measured comparison.
Custom Items	Basic Items plus resource classes you select, such as all HTML images, audio/video, embedded objects, all CSS images or fonts, or scripts in same-origin frames.	Choose this when you need a middle ground. Include only the extras required for your intended offline use.

Scripts in cross-origin frames are never saved. Cross-origin frames may also have limits on what can be saved. A page that depends on a third-party frame may not work exactly as it does online, even if you include many other resources.

3. Configure Custom Items for your offline needs

Start with the Basic Items preset.
In Custom Items, add only the resource classes your offline copy needs. For example, add all HTML images if images below the current display matter, or audio/video if you need those media files.
Leave unneeded media, embedded objects, CSS images, fonts, or same-origin frame scripts out.
Save the page, then open the resulting HTML file and inspect the sections and resources you need.

Basic Items is the smallest documented preset, not a guarantee that every page saved with it will be small. A page with large displayed images, complex styling, or canvas content can still produce a large file. Custom Items lets you selectively include additional resource classes, but the exact available checkboxes and labels can depend on the extension version.

4. Consider hidden and lazy-loaded content

Save Page WE has options for removing or re-hiding page elements, including elements hidden by the page or other extensions. Removing content you do not need may help avoid retaining it, although the documentation does not quantify the effect.

Lazy loading is a separate tradeoff. Options to scroll or shrink a page to load content, or to load lazy images in existing content, may cause more content to be captured. That can make the saved copy more complete and may also increase its size. Decide whether you need below-the-fold content before enabling these options.

5. Check the saved file

Open the saved HTML file locally.
Check the text, images, styling, and any media or embedded content needed for your use.
If something important is missing, add the relevant resource class in Custom Items and save again.
If the file is still large, review whether you need all images, media, fonts, embedded files, or lazy-loaded content.

This check matters because saving fewer resource types can reduce what is available offline. The best setting is the smallest one that preserves the parts of the page you actually need.

6. What affects the final file size

Included resource types: Standard Items and expanded Custom Items can retain additional images, media, objects, and fonts.
Repeated CSS images: The merge option addresses duplicate CSS images. It is not documented as applying general image compression.
Per-reference resources: The documentation says CSS fonts and HTML images, audio, and video are stored once for each reference. Repeated references can therefore matter.
Lazy content: Loading more lazy images or scrolling to reveal content can add resources to the saved page.
Page structure: Frames and external scripts can be represented using data URIs or srcdoc; cross-origin restrictions can affect what is retained.

There is no documented general savings percentage, expected file size, or benchmark. Compare saves of the same page under the settings you intend to use if you need to know the result for your particular content.

7. Troubleshooting

Symptom	Likely cause	What to do
The saved file is still large.	Displayed images, canvas graphics, stylesheets, or other Basic Items can themselves be substantial; extra resource classes or lazy-loaded content may also be included.	Review Custom Items and lazy-loading options. Disable resource classes you do not need, then save and inspect another copy.
Images or media are missing offline.	The selected preset may not include all HTML images, audio/video, embedded objects, or other optional resources.	Add the missing resource class through Custom Items or use Standard Items, then save again.
The page looks different when opened locally.	A stylesheet, font, image, frame, or other dependency may not have been retained; cross-origin frames have limitations.	Identify the missing resource type and include it where possible. Scripts in cross-origin frames are never saved, so a page that depends on them may not behave as it does online.
Enabling merge barely changes the file.	The page may not use repeated CSS images, or most of its size may come from other resources.	Keep the option enabled if useful, but review resource inclusion. The merge setting is not general image compression.
The save workflow behaves differently across Chrome versions or methods.	The extension listing describes an old and a new save method with different compatibility and save-location behavior.	Check the extension’s current options and listing. The listing says the old method remembers the last save location but can fail on some pages in Chrome 84 or later; the new method can save all pages but does not remember the last save location in Chrome.

8. Performance, reliability, and cost

These settings are a size-versus-completeness choice, not a documented compression benchmark. Including fewer resources may reduce the amount of data placed in the single HTML file, while enabling lazy-content loading or saving additional media may add data. The documentation provides no expected percentage reduction, timing figures, or size guarantees.

For reliability, preserve a copy of the original page or save again with additional resource classes if the offline file is missing something important. Save Page WE’s Chrome listing identifies version 33.9, updated September 5, 2023, and describes automatic selection of the original or new save method; check the current listing for up-to-date compatibility details. These settings concern a browser extension and do not require purchasing physical products.

9. Or skip the browser setup

If your goal is a screenshot or PDF rather than a self-contained offline HTML file, ScreenshotNeo is a website screenshot API and MCP server. It does not replace Save Page WE’s offline HTML use case, but it can capture a page without setting up your own browser automation.

One GET request returns an image or PDF. This runnable cURL example saves a WebP screenshot:

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()
open("shot.webp", "wb").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(`ScreenshotNeo returned ${res.status}`);
const fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));

See the ScreenshotNeo API documentation for request options and setup. Cookie banners are accepted like a visitor and more than 60 known consent platforms, newsletter popups, and chat widgets are removed before the shot; each 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. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.

The free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 screenshots; every feature is on every plan. Sign up free and get 1,000 screenshots a month with no card.

10. FAQ

Does merging duplicate CSS images compress every image?

No. The documented option merges duplicate CSS images; it is not described as general image compression.

Which preset should I try first?

Try Basic Items when a lean copy is the priority. Use Custom Items to add only the extras you need, or Standard Items when its broader resource coverage is more useful.

Can I know the exact size reduction in advance?

No published percentage or benchmark supports an estimate. It depends on the page’s content and selected resources.

Will a saved page work fully offline?

It may not. The result depends on which resources were saved, and cross-origin frame restrictions can leave some content or behavior unavailable.