Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsTo capture a full-page screenshot in Chrome DevTools without missing lazy-loaded images, scroll through the page first, pause for offscreen images to load, and then use Device Mode → More options → Capture a full size screenshot. The full-size command captures content beyond the visible viewport, but it does not guarantee that every site’s lazy-loading code has fetched all images.
Why lazy-loaded images may be missing
Many pages defer loading images and other resources that are outside the viewport until they approach the visible area. That can make a page’s initial load appear complete even while images farther down the page have not been requested. MDN explains this behavior in its lazy-loading guide.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
The 138 Best Chrome Extensions | $2.99 | Buy on Amazon |
The page’s load event is not proof that all lazy-loaded images are ready. You can check an individual image’s Boolean complete property, documented by MDN for the <img> element, but visual inspection is still useful: a completed image can be broken or not display the content you expect.
Capture the full page after triggering lazy loading
- Open the page in Chrome and open DevTools. Use the browser’s DevTools command or shortcut for your operating system.
- Turn on Device Mode. Select a viewport or device configuration if the screenshot should represent a particular screen size. Chrome documents Device Mode and its screenshot commands in Simulate mobile devices with device mode.
- Let the initial content render. Do not treat the initial page load as evidence that images lower on the page are ready.
- Scroll down through the page in increments. Pause at sections with images so they have an opportunity to be requested and rendered. If the page loads more content as you scroll, continue until you reach the end.
- Check areas where images appeared late. If an expected image is still absent, inspect it in the page or Elements panel. For an image element, examine its
completeproperty; use the page’s visual result as the final check. - Capture the page. In Device Mode, open More options and choose Capture a full size screenshot. Chrome saves a screenshot that includes content outside the current viewport.
- Review the saved image. Look for blank image regions, layout shifts, sticky elements, overlays, and content that only appeared after interaction. If the page changed while scrolling, repeat the relevant scroll-and-check steps before capturing again.
Chrome documents the full-size capture command, not a guarantee that it forces every site’s custom lazy-loading implementation to fetch all images. Scrolling and reviewing are practical ways to trigger ordinary offscreen loading and catch pages that need more interaction.
Recommended Free Tools
#1 Best Overall
Choose the DevTools capture that matches your goal
| Goal | DevTools option | What it is for |
|---|---|---|
| Save the entire page as one screenshot | Device Mode → More options → Capture a full size screenshot | Captures page content beyond the visible viewport. |
| Save only what is currently visible | Device Mode → More options → Capture screenshot | Captures the current viewport, not the full page. |
| Inspect appearance during loading | Network panel → enable Capture screenshots, then reload with Network focused | Shows screenshot thumbnails associated with stages of page loading and helps correlate appearance with network activity. See Chrome’s Network features reference and Inspect network activity. |
| Inspect visual changes frame by frame | Performance panel → enable Screenshots before recording | Captures screenshots for frames in a Performance recording; it is for diagnosing rendering changes, not the final full-page image. See Chrome’s Performance features reference. |
For a cold-load investigation, Chrome’s Network documentation describes disabling cache and using Empty Cache And Hard Reload while DevTools is open. This can help reproduce first-visit behavior, but clearing cache is not required for an ordinary full-page screenshot.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup:
ScreenshotNeo can return a website screenshot in one GET request. Its capture options include full-page screenshots with lazy images loaded. Put your API key and target URL into this cURL command; see the ScreenshotNeo documentation for API details.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before the shot. Bot checks, blank pages, timeouts, and failed loads are not billed; cache hits are not billed either, and response headers report the page verdict and billing status. Its MCP server gives AI agents screenshot tools. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.
Learn about ScreenshotNeo, or sign up free for 1,000 screenshots a month with no card.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Troubleshooting missing or incomplete images
- Images lower on the page are blank: Scroll farther down in increments and pause near those images, then capture again. Offscreen resources may not be requested until they approach the viewport.
- The page looks loaded but the screenshot is incomplete: The load event does not establish that lazy images finished loading. Check the relevant image’s
completeproperty and inspect the rendered page before capture. - Images still do not appear after scrolling: The site may use custom JavaScript or require an interaction. Continue through the page, perform the relevant interaction if appropriate, and verify the final area visually. A generic scroll sequence cannot guarantee activation of every custom implementation.
- The output contains only what was on screen: Use Capture a full size screenshot, not Capture screenshot.
- You need to understand when an image appeared, not just save the final page: Use Network-panel screenshots during reload for loading context, or Performance screenshots during a recording for frame-level rendering changes. Neither replaces Device Mode’s full-size capture for the finished page.
- You need to reproduce a first-visit state: With DevTools open, use the Network panel’s cache controls and Empty Cache And Hard Reload. This is a diagnostic step, not a prerequisite for screenshot capture.
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.
