For a reliable full-page screenshot, first scroll through the page to trigger viewport-based lazy loading, then wait for the images needed in the capture to finish loading. A browser’s load event alone is not enough: lazy images may still be pending. The precise scroll increments and waits depend on the page, so treat this as a preparation strategy—not a guarantee that every site will load every image.
Why screenshots miss lazy-loaded images
With native loading="lazy", the browser may defer fetching an image until it is within a browser-calculated distance of the viewport. That distance is not necessarily the point where the image becomes visibly onscreen. A page’s initial navigation can therefore finish while images farther down the document have not yet been requested.
As an Amazon Associate I earn from qualifying purchases.
MDN explains that the load event fires when eagerly loaded content has loaded; lazily loaded content may still be pending. A full-page screenshot includes the page’s scrollable content, but asking a browser to capture the full page does not itself establish that each site’s lazy-loading logic has run or that all image requests have finished. The latter follows from how viewport-triggered loading and full-page capture work; it is not a guarantee made by the browser APIs.
Recommended Free Tools
Sources: MDN: Lazy loading, MDN: Intersection Observer API, and Playwright: Screenshots.
#1 Best Overall
- 🌟 All-in-One Screen Solution: Essential for seamless window screen replacement & repairs. This versatile screen repair kit Perfect for DIY screen spline insertion, frame rolling, and mesh tightening – your go-to tool for screen for windows projects.
- 🔷 Dual Roller Innovation: Features convex (round) & concave (grooved) steel rollers. The concave roller prevents delicate screen tearing during spline rolling, while the convex wheel ensures tight sealing. Ultimate precision for window screen tool tasks.
- ❖ Ergonomic Wooden Handle: Solid hardwood handle delivers superior comfort during prolonged screen roll installation. Non-slip grip reduces hand fatigue when replacing window screens. Durable steel bearings ensure smooth roller rotation – ideal for screen door repair marathons.
- 🔧Spline Tool + Screen Roller Tool: Offers three roller diameter options for selection. When replacing window screens, choose the corresponding roller based on the Spline specifications to completely eliminate tool size mismatch issues.
- 💎 Pro-Grade Durability: Carbon-steel rollers withstand aggressive spline rolling without deformation. your lifetime screen repair tool investment.
Choose the preparation method for the capture
Viewport-only screenshot
If the image covers only the initial viewport, wait for the page’s required state and then check the images relevant to that viewport. There is no need to scroll the entire document unless the page’s own behavior requires it.
Full-page screenshot
For a full-page capture, move through the document in increments so images approach the viewport and viewport observers can trigger their loading behavior. After scrolling, wait for the relevant images before capturing. The appropriate increment and pause vary with page layout, scripts, nested scroll containers, and network conditions; browser documentation does not establish a universal setting.
Rank #2
- ⭐【QUALITY MATERIALS】- Solid wood handle + double carbon steel bearing metal wheels, heavy beech wood handles are hard and crack-free, thickened and enlarged metal convex and concave double wheels, each of them is finely crafted and durable, suitable for the replacement of aluminum alloy plastic steel doors and windows of any specification.
- ⭐【SCREEN TOOLS SET】- The screen rolling tool has two different wheels, cams and recessed rollers, which can help you get the job done better and faster. Screen roller is compact and easy to carry,which is can solve your problem well. Every one is meticulously crafted and durable, A good helper for replacing screens at home.
- ⭐【EASY TO USE】- Installing a screen with a screen rolling tool makes the job much easier. This essential tool is comfortable in the hand and the wheels turn smoothly to roll the screen and spline into the frame. It’s extremely economical and adds great value to big and small screen repair jobs.
- ⭐【ERGONOMIC HANDLE】- The wood handle has ergonomic design, it is easy to hold. wooden handle and steel convex and concave roller wheels,the steel wheels of our screen rolling tool is smooth The hooks are sharp and the aged battens can be hooked out.
- ⭐【CONVEX & CONCAVE 】– The combination screen rolling tool has a 1-5/16" x 3/32" convex (round edge) steel roller at one end and a 1-5/16" x 3/32" concave (grooved edge) steel roller at the opposite end.
Implement a scroll-and-wait flow with Playwright
The following Node.js example navigates to a URL, scrolls down in viewport-sized steps, waits for image elements to complete, and takes a full-page screenshot. It uses a bounded loop and timeout so a page that grows continuously or contains a stalled image does not wait forever. Set TARGET_URL to the page you control or are authorized to capture.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsimport { chromium } from 'playwright';
const url = process.env.TARGET_URL;
if (!url) throw new Error('Set TARGET_URL to the page to capture');
const browser = await chromium.launch();
const page = await browser.newPage({ viewport: { width: 1440, height: 900 } });
try {
await page.goto(url, { waitUntil: 'domcontentloaded', timeout: 30_000 });
// Scroll through the current document to trigger viewport-based loading.
let previousHeight = 0;
for (let pass = 0; pass < 20; pass++) {
const height = await page.evaluate(() => document.documentElement.scrollHeight);
for (let y = 0; y < height; y += Math.max(400, window.innerHeight * 0.8)) {
await page.evaluate((scrollY) => window.scrollTo(0, scrollY), y);
await page.waitForTimeout(150);
}
await page.waitForTimeout(300);
const newHeight = await page.evaluate(() => document.documentElement.scrollHeight);
if (newHeight === previousHeight || newHeight === height) break;
previousHeight = newHeight;
}
// Wait for image requests to settle, while allowing broken images to be reported
// rather than hanging the capture indefinitely.
await page.waitForFunction(() =>
[...document.images].every((img) => img.complete),
{ timeout: 15_000 }
).catch(() => {});
const imageStatus = await page.evaluate(() =>
[...document.images].map((img) => ({
src: img.currentSrc || img.src,
complete: img.complete,
loaded: img.complete && img.naturalWidth > 0
}))
);
const failed = imageStatus.filter((img) => !img.loaded);
if (failed.length) console.warn('Images incomplete or broken:', failed);
await page.screenshot({ path: 'page.png', fullPage: true });
} finally {
await browser.close();
}Run it with TARGET_URL=https://example.com node capture.mjs after installing Playwright and its browser. The short pauses and the maximum number of passes are example safeguards, not generally correct values. Tune them for your target pages. The completion check uses HTMLImageElement.complete; because a broken image can also be complete, the example additionally checks naturalWidth to distinguish successful image loads from failures.
Rank #3
- --- 𝐏𝐀𝐓𝐄𝐍𝐓 𝐀𝐏𝐏𝐋𝐈𝐄𝐃 𝐅𝐎𝐑---
- 🏡【𝐊𝐢𝐧𝐠&𝐂𝐡𝐚𝐫𝐥𝐞𝐬 𝐑&𝐃 𝐈𝐧𝐭𝐞𝐧𝐭𝐢𝐨𝐧】Versatile Screen Tool - combines the core functions of multi-size roller, hidden hooks, and replaceable blades, and designed this multifunctional screen tool. It solves the problems of traditional screen installation tools with single functions, lack of safety and adaptability. It truly realizes multiple uses of one tool, making screen replacement time-saving, labor-saving, and worry-free. One-time purchase can meet your installation or replacement needs.
- 🏡【𝟑 𝐒𝐢𝐳𝐞𝐬 𝐈𝐧𝐭𝐞𝐫𝐜𝐡𝐚𝐧𝐠𝐞𝐚𝐛𝐥𝐞 𝐑𝐨𝐥𝐥𝐞𝐫𝐬】Flexible Adaptation - In view of the differences in thickness of different window splines, we gift the roller into three specifications: Convex 0.13", Concave 0.13", and Concave 0.18", ensuring perfect matching with the mainstream rubber strip sizes on the market. Feature①: The roller is made of high-hardness plastic, which is strong and durable while avoiding the risk of traditional metal rollers scratching the screen mesh. Feature②: Metal bearing design - smoother rotation, even pressure without deviation. TIPS: you can use the provided Allen wrench to quickly disassemble and replace them.
- 🏡【𝐁𝐥𝐚𝐝𝐞 𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧-𝐑𝐞𝐭𝐫𝐚𝐜𝐭𝐚𝐛𝐥𝐞&𝐒𝐭𝐨𝐫𝐚𝐠𝐞&𝐑𝐞𝐩𝐥𝐚𝐜𝐞𝐚𝐛𝐥𝐞】①Retractable-When in use, just hold button, blade will slow rollout, convenient trimming and cutting. Blade can be retracted to prevent Accident scratches. ②Blade has double locking device: it automatically locks to prevent retraction during work and is completely closed to prevent accidental touch when retracted. Ansure your safety. ③Replaceable - A separate button is provided for changing the blades. ④Blade is made of steel-sharp, durable and won't rust. ⑤Storage-Handle has built-in blade storage design to place complimentary blade.Extra equipped 2xreplacement blades- increase service life of tool.
- 🏡【𝐇𝐢𝐝𝐞𝐚𝐛𝐥𝐞 𝐑𝐞𝐦𝐨𝐯𝐚𝐥 𝐇𝐨𝐨𝐤】The hooks are sharp and can hook out the aged spline. The removal hook can be stored and hidden in the handle slot box. OPEN the box cover, take out the hook and insert it into the groove for use. can RETRACT after use to prevent the hook tip from scratching clothes or tool boxes. Hook made of Stainless steel material won't rust.
Playwright’s waitForLoadState can wait for a navigation load state, but it does not substitute for a capture-specific check of lazy images. Playwright often auto-waits for ordinary actions; explicit image readiness is a separate concern when the screenshot depends on those images. Sources: Playwright: Page API and MDN: Lazy loading.
Native lazy loading, Intersection Observer, or capture-time scrolling?
| Approach | Trigger and useful fit | Trade-off |
|---|---|---|
Native loading="lazy" |
Browser-managed deferral based on calculated distance from the viewport; simple for ordinary image markup. | The browser controls the trigger distance, and the page’s load event does not certify lazy-image completion. |
| Custom Intersection Observer | Script runs when targets intersect a viewport or configured root. A positive rootMargin can begin work before an image is visible. |
Requires callback and fallback behavior. It remains viewport-triggered; targets far from the root do not load until they approach it. |
| Screenshot preparation scroll | A capture worker scrolls through the document to activate viewport-triggered content, then waits for images. Useful for full-page capture. | Nested scrollers, dynamic content, page-specific scripts, and network delays can require tailored readiness logic. It cannot guarantee success on every site. |
For your own site, give images explicit width and height. MDN notes that an unloaded lazy image without dimensions may have zero dimensions, which can cause disruptive layout shifts when it loads. Stable dimensions also make it easier for a capture workflow to reason about page layout.
Sources: MDN: Intersection Observer API and MDN: The Image Embed element.
Common problems and fixes
- Images are absent even though navigation completed: The
loadevent covers eagerly loaded content, not necessarily lazy images. Scroll through the relevant regions and check image completion separately. - The page height changes while scrolling: Lazy content may add images or other elements after the first measurement. Recheck document height and make another bounded pass rather than assuming the original height is final.
- An image reports complete but looks broken: Completion does not mean success. Check
naturalWidthor inspect the request and image URL; the example logs images with zero natural width. - Some images remain missing after scrolling: The page may use a nested scrolling container, custom scripts, delayed requests, or a trigger other than the main viewport. Adapt the scroll target and readiness check to that page; there is no universal increment or wait time.
- The wait never finishes: A failed or stalled request may remain incomplete. Bound the wait, report incomplete images, and decide whether to retry, omit the page, or capture with an explicit warning.
- Layout shifts move content during capture: Set image dimensions where possible and wait for layout-changing content to settle before taking the screenshot.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. Its full-page capture loads lazy images. Before capture, it accepts cookie and consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status in headers.
One GET request returns an image or PDF. This cURL example saves a WebP screenshot:
Best Value
- WINDOW SCREEN REMOVAL TOOL: Designed to easily engage, lift, and remove window screens without damaging frames or mesh.
- Durable Nylon Construction – Made from high-strength, impact-resistant nylon that's tough enough to handle repeated use yet gentle on delicate surfaces, won't rust or corrode like metal tools.
- DUAL-END DESIGN: Features a forked end to engage and lift screen edges and a flat pry tip on the opposite end for versatile use.
- HIGH-VISIBILITY COLOR: Bright orange construction makes this tool easy to spot and prevents it from being misplaced on the job site.
- DIY-FRIENDLY: The ideal tool for homeowners and professionals tackling window screen repair, replacement, or seasonal removal tasks.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. Its 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.
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
Frequently Asked Questions
Does a full-page screenshot automatically load every lazy image?
No. Full-page capture covers the scrollable page, but it does not by itself prove that viewport-triggered loading ran or that every image request finished.
Should I wait for the browser’s load event before checking images?
You can wait for the required navigation state, but treat image readiness as a separate condition: lazy-loaded images may still be pending after the load event.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
