To capture complete bulk screenshots when images load only after scrolling, automate a browser to visit each URL, scroll through the page in viewport-sized steps, wait for newly requested content to render, and then save a full-page screenshot. Full-page capture and triggering lazy-loaded content are separate tasks: a tall screenshot does not guarantee that the browser has loaded everything the page reveals on scroll.
Why lazy-loaded images can be missing from a full-page screenshot
A full-page screenshot captures the scrollable document as one tall image, as though it fit on a very tall screen. But many pages request images or other content only when a section approaches the visible viewport. If the browser takes the screenshot without scrolling through those sections, some images may remain unloaded or appear as placeholders. A third-party guide describes this scroll-triggered omission, while Playwright documents full-page capture as a screenshot of the scrollable page: Playwright screenshots and Browserless guide to scraping images with Playwright.
As an Amazon Associate I earn from qualifying purchases.
The reliable workflow is therefore: navigate, trigger the relevant content by scrolling, wait for a meaningful ready condition, and only then capture. The exact wait condition depends on the site; a fixed pause can help, but it cannot guarantee that every image has loaded.
Prepare the batch
Use a plain-text file with one URL per line. Keep browser, viewport, output format, and file naming consistent so screenshots are comparable and failures easy to find. The example below uses Node.js and Playwright, saves PNGs in a shots directory, and records errors without abandoning the remaining URLs.
#1 Best Overall
- CRISP CLARITY: This 23.8″ Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
- WORK SEAMLESSLY: This sleek monitor is virtually bezel-free on three sides, so the screen looks even bigger for the viewer. This minimalistic design also allows for seamless multi-monitor setups that enhance your workflow and boost productivity
- A BETTER READING EXPERIENCE: For busy office workers, EasyRead mode provides a more paper-like experience for when viewing lengthy documents
Install Playwright and its Chromium browser in a Node.js project:
npm install playwright
npx playwright install chromiumCreate urls.txt with one address per line, then save the following as capture.js:
Rank #2
- CRISP CLARITY: This 22 inch class (21.5″ viewable) Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- 100HZ FAST REFRESH RATE: 100Hz brings your favorite movies and video games to life. Stream, binge, and play effortlessly
- SMOOTH ACTION WITH ADAPTIVE-SYNC: Adaptive-Sync technology ensures fluid action sequences and rapid response time. Every frame will be rendered smoothly with crystal clarity and without stutter
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
const fs = require('node:fs/promises');
const path = require('node:path');
const { chromium } = require('playwright');
const urls = (await fs.readFile('urls.txt', 'utf8'))
.split(/r?n/)
.map(line => line.trim())
.filter(line => line && !line.startsWith('#'));
const outputDir = 'shots';
await fs.mkdir(outputDir, { recursive: true });
const browser = await chromium.launch({ headless: true });
const failures = [];
try {
const page = await browser.newPage({
viewport: { width: 1365, height: 900 },
deviceScaleFactor: 1
});
for (let i = 0; i < urls.length; i++) {
const url = urls[i];
const filename = `${String(i + 1).padStart(4, '0')}.png`;
try {
const response = await page.goto(url, {
waitUntil: 'domcontentloaded',
timeout: 45000
});
if (response && !response.ok()) {
throw new Error(`Navigation returned HTTP ${response.status()}`);
}
// Trigger viewport-based lazy loading. Repeat if scrolling causes
// the document to grow, with a limit for infinite-scroll pages.
let previousHeight = 0;
let unchangedRounds = 0;
const maxRounds = 12;
for (let round = 0; round < maxRounds && unchangedRounds < 2; round++) {
const height = await page.evaluate(() => document.documentElement.scrollHeight);
for (let y = 0; y < height; y += Math.max(300, window.innerHeight - 100)) {
await page.evaluate(y => window.scrollTo(0, y), y);
await page.waitForTimeout(300);
}
await page.waitForTimeout(500);
const newHeight = await page.evaluate(() => document.documentElement.scrollHeight);
unchangedRounds = newHeight === previousHeight ? unchangedRounds + 1 : 0;
previousHeight = newHeight;
}
// Return to the top before capturing the whole document.
await page.evaluate(() => window.scrollTo(0, 0));
await page.waitForTimeout(200);
await page.screenshot({
path: path.join(outputDir, filename),
fullPage: true,
type: 'png'
});
console.log(`Saved ${filename}: ${url}`);
} catch (error) {
failures.push({ url, error: error.message });
console.error(`Failed: ${url}: ${error.message}`);
}
}
} finally {
await browser.close();
}
await fs.writeFile('failures.json', JSON.stringify(failures, null, 2));
console.log(`Finished ${urls.length} URL(s); ${failures.length} failure(s).`);Run the batch with node capture.js. The numbered filenames preserve input order; failures.json captures URLs that failed so they can be retried or reviewed separately. Playwright’s full-page option is fullPage: true in JavaScript and full_page=True in Python. See the Playwright Page API for navigation and screenshot options.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose a wait condition that matches the page
Use a known image or section when possible
If the page has a stable selector for the content that matters, wait for it to appear or for its image to finish loading. For example, after navigation you can wait for a known section with await page.locator('#main-content').waitFor({ state: 'visible' }). For a specific image, check its load state with a page-side condition appropriate to the site’s markup. A selector tied to the content you need is more meaningful than assuming that elapsed time alone proves readiness.
Rank #3
- Clear visuals. Fluid motion: A 144Hz refresh rate and 1ms MPRT deliver smooth, tear‑free motion across work, gaming, and streaming for clearer, more fluid viewing.
- Eye comfort: TÜV Rheinland 3‑star* certification reduces harmful blue light while preserving stunning color quality without compromise. *TÜV Rheinland 3-star eye comfort certification.
- Wide viewing angle: Get consistent views across a wide 178° /178° viewing angle.
- In-Plane Switching (IPS): See excellent color accuracy and consistency across wide viewing angles with In-plane Switching (IPS) technology.
- Ultra-thin bezels: Maximize your viewing experience with thin bezels.
Do not treat network idle as a universal readiness test
Playwright discourages relying on networkidle alone as a readiness criterion in tests; pages can maintain background requests or render content after network activity settles. The Page API documents navigation and related options at Playwright Page API. Use a page-specific condition, and inspect output when completeness matters.
Adjust the scrolling behavior for the site
- If images appear only after a longer delay, increase the short pause after each scroll or wait for a relevant image selector.
- If new sections extend the document, repeat the scroll pass until height stops changing for consecutive checks.
- For infinite scroll, set a deliberate stop rule such as a maximum number of passes, known item count, or maximum scroll depth. The example caps repeated passes instead of attempting to exhaust an endless feed.
- If the page uses a nested scrolling panel rather than the main document, scroll that container explicitly; moving the window may not trigger its content.
Check the output and recover from incomplete captures
Open a sample of the generated images, especially from pages known to use lazy loading. Look for empty image regions, placeholders, cut-off sections, or layout shifts. A page that keeps changing height or loading imagery may need a longer or more targeted wait rather than simply another full-page capture.
Rank #4
- CURVED FOR ENHANCED ENGAGEMENT: An immersive viewing experience with a curved monitor that wraps more closely around your field of vision; It creates a wider view, enhancing depth perception and minimizing peripheral distraction
- SMOOTH PERFORMANCE FOR SEAMLESS CONTENT: Stay in the action when playing games, watching videos, or working on creative projects; The 100Hz refresh rate reduces lag and motion blur so you don't miss a thing in fast-paced moments¹
- MORE GAMING POWER: Gain the edge with optimizable game settings; Color and image contrast can be adjusted to see scenes more vividly and spot enemies hiding in the dark; Game Mode adjusts any game to fill the screen so you can view every detail²
- KEEP IT EASY ON THE EYES: Care for your eyes and stay comfortable, even during long sessions; Advanced eye comfort technology certified by TÜV reduces eye strain by minimizing blue light and reducing irritating screen flicker²
- INCREASED VERSATILITY: Connect to more; Plug devices straight into your monitor for increased flexibility, making your computing environment even more convenient
- Blank or placeholder image areas: scroll farther or wait for the relevant image or section to load; confirm that the site did not defer the request behind a user interaction.
- Screenshot ends too early: check whether content was added after the initial height measurement; repeat passes or increase the maximum for finite pages.
- Navigation timeout or failed URL: record it and retry separately with a suitable timeout. Login walls, network problems, and bot checks can prevent the expected page from loading.
- Layout shifts during capture: wait for key images or fonts and disable or wait out animations where the site permits it. A fixed header, cookie notice, or overlay may also cover content.
- Only part of the page scrolls: inspect for nested scroll containers and change the script to scroll the container that actually reveals the content.
One generic script cannot guarantee identical results across sites. Authentication, anti-automation measures, animations, cookie notices, and page-specific loading logic may require targeted adjustments.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesManage time, output size, and batch reliability
Batch duration grows with the number of URLs and the time spent navigating, scrolling, and waiting. Keep the waits short but purposeful, and prefer content-specific conditions for pages where completeness is important. Very tall pages can produce large images; consider viewport-sized captures instead when the goal is visual review or documentation rather than a single continuous document image.
Best Value
- 【INTEGRATED SPEAKERS】Whether you're at work or in the midst of an intense gaming session, our built-in speakers provide rich and seamless audio, all while keeping your desk clutter-free.
- 【EASY ON THE EYES】 Protect your eyes and enhance your comfort with Blue-Light Shift technology. This feature reduces harmful blue light emissions from your screen, helping to alleviate eye strain during long hours of use and promoting healthier viewing habits.
- 【WIDEN YOUR PERSPECTIVE】Our sleek minimal bezel design ensures undivided attention. The nearly bezel-free display seamlessly connects in a dual monitor arrangement, delivering an unobstructed view that lets you focus on more at once, completely distraction-free.
For reliable operations, retain the input URL list, use deterministic filenames, save per-URL failures, and inspect outputs rather than assuming that a successful screenshot call means every image loaded. If a page is infinite-scroll, impose a stop rule to prevent an unbounded capture workflow.
Or skip the browser setup
ScreenshotNeo offers a one-request screenshot API and an MCP server for AI agents. Its full-page capture option supports lazy images, but pages that load content only on scroll may still need an appropriate readiness strategy. For a standard one-shot capture, use this cURL example; see the ScreenshotNeo documentation for parameters and response details.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts cookie or consent banners like a visitor and removes 60+ known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, or any MCP client. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
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.
