How to Save a Long, Lazy-Loaded Webpage with Save Page WE
Configure Save Page WE to reveal lazy-loaded content before saving, choose the right resource options, and troubleshoot missing content in your offline copy.
To save a long page with its later content and images, configure Save Page WE to load lazy content before saving. In its options, enable Load lazy content and choose Scroll Page or Shrink Page. If images already present in the page are missing, also enable Load lazy images in existing content. Then save the page and inspect the resulting HTML file. These settings try to trigger deferred content; they cannot guarantee that every page element or interaction will work offline.
Set up Save Page WE
- Install Save Page WE in Firefox or Chrome. Its listings describe the two browser versions as having the same functions and interface.
- Open the extension’s Options from the toolbar button’s context menu.
- In the saved-items options, enable Load lazy content and select one of its methods: Scroll Page or Shrink Page.
- If images within content that has already appeared are missing, enable the separate Load lazy images in existing content option.
- If the page adds results a short time after its load event, consider the option to delay starting the save after that event.
- Save with the toolbar button, its context menu, or the
Alt+Ashortcut. - Open the saved
.htmlfile locally and check the sections and images that matter to you.
The extension saves a single HTML file by default. Browser download settings still affect where the file goes. You can change the download behavior in the browser’s settings.
Choose what resources to save
Lazy-content loading and saved-item selection solve different problems. Loading lazy content attempts to make deferred page content appear before capture. The saved-item tier controls which resources are included in the file.
| Option | Documented coverage | When to choose it |
|---|---|---|
| Basic | Currently displayed HTML images, canvas graphics, stylesheets, and currently displayed CSS images | When the content already visible on the page is sufficient |
| Standard | Everything in Basic, plus all HTML images and HTML audio/video and object/embed files | When the page’s HTML images or media matter |
| Custom | Lets you select additional resource types | When you need control over which resource categories are saved |
The output contains the HTML elements as displayed when saved and referenced resources according to the selected options. Save Page WE converts external stylesheets to internal stylesheets and stores binary resources such as images and fonts as data URIs. A larger selection of resources can make the saved file larger.
Scroll Page or Shrink Page?
Save Page WE documents both Scroll Page and Shrink Page as methods for loading lazy content. Its listings do not publish a speed comparison, success rate, or a rule for which method works best on a particular site. If one method leaves content out, try the other and inspect the saved result.
Lazy loading is page behavior: a site may defer content or images until they approach the visible area. The extension’s options attempt to expose that content before the page is saved. This is not a promise that every deferred request will complete, or that content requiring a login, interaction, or another page state will be included.
What the saved file does and does not preserve
Treat the file as a saved representation of the page state available to the extension at capture time, not as a complete backup of the website. The documentation notes these limitations:
- Some cross-origin frames cannot be saved.
- Scripts in cross-origin frames are never saved.
- Saved scripts are disabled by default, though an option can allow them to execute.
- Some resources may fail to save; the extension can show a warning or list the failed resources.
Even if an element appears in the saved file, its original interactive behavior may depend on scripts or remote services that are unavailable offline. Review the file locally rather than assuming it is a fully functional offline version.
Save methods and browser differences
The extension listing describes an old and a new save method. The old method remembers the last save location in Firefox and Chrome, but can fail on some pages in Chrome 84 or later. The new method can save pages the old method may not, but does not remember the last location in Chrome. If a save fails, switching methods is a documented troubleshooting option. The browser’s own download handling also applies.
Firefox has built-in alternatives: Web page, complete saves a page with pictures in a directory, while HTML only saves the HTML without pictures. Firefox notes that the complete-page option may not preserve the original HTML link structure. Chrome’s pageCapture API can save MHTML, a single file containing a page and resources; Chrome documents that MHTML can only be loaded from the file system and only in the main frame. These are context, not substitutes for Save Page WE’s lazy-content controls.
Troubleshooting
| Symptom | Likely explanation | What to try |
|---|---|---|
| The saved page contains only the top portion | Deferred content may not have been exposed before saving. | Confirm Load lazy content is enabled. Try the other method, Scroll Page or Shrink Page, then save again. |
| Text appears but images are missing | The image may be lazy-loaded within existing content, or the selected tier may not include the needed images. | Enable Load lazy images in existing content. Check whether Basic is sufficient or use Standard or a Custom selection that includes the required resources. |
| New results are absent | The page may populate after its load event. | Use the option to delay starting the save after the page-load event, then inspect the saved file. |
| The save fails on a particular page | The selected save method may not handle that page in the current browser. | Try the other save method. In Chrome, the listing specifically says the new method may save pages the old method cannot. |
| A frame or interaction is missing offline | Cross-origin frame or script restrictions, or a remote dependency, may prevent it from being saved or working locally. | Check the extension’s warning or failed-resource list. Expect some frames and script-driven behavior not to be available offline. |
| The file is saved somewhere unexpected | Save location and handling follow browser download settings and the selected method. | Check the browser’s download settings. The new method does not remember the last location in Chrome. |
Performance, reliability, and file size
The available documentation does not specify a maximum page length, a capture-time estimate, or success rates for either lazy-content method. Very long pages and pages with many resources can take more work to capture and produce larger files; the exact result depends on the page and the resources selected. For a more complete saved copy, choose the resource categories you need, allow the page to expose deferred content, and verify the output. If a resource warning appears, use it to identify what did not make it into the file.
For reliable offline reference, keep the saved HTML file and check it on the same device or browser where you plan to use it. A single HTML file is convenient to move, but embedded resources increase its size, and missing scripts or cross-origin content can limit offline behavior.
Or skip the browser setup
If you need a screenshot rather than a local HTML archive, ScreenshotNeo captures a URL with one API request. It is a website screenshot API and MCP server from Yorker Media. Its clean-shot flow accepts cookie and consent banners like a visitor, then removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. AI agents can use its MCP server tools: take_screenshot, get_page_info, and capture_pdf.
For the API, use the ScreenshotNeo documentation. This 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.webpPython:
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)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 Bun.write('shot.webp', res);ScreenshotNeo includes full-page capture with lazy images loaded, selector capture, PDF output, custom CSS and JavaScript, wait conditions, viewport and device settings, resource blocking, caching, async jobs, bulk capture, and more. Free includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Every feature is on every plan. The free sign-up is 1,000 screenshots a month with no card.
FAQ
Does Save Page WE save the page as one file?
Yes. It saves a single HTML file by default, with resources embedded according to the selected saved-item options.
Can I guarantee that a saved page will work offline?
No. Some cross-origin frames and scripts are not saved, scripts are disabled by default, and some resources may fail. Inspect the local file for the content you need.
Is Scroll Page always better than Shrink Page?
The documentation does not establish that one is faster or more reliable. Try the other method if the first does not expose the content you need.
Does this create a full website backup?
No. It saves a representation of the page state and resources available during capture, with documented limits around frames, scripts, and failed resources.
