Chrome DevTools can capture a page beyond the visible viewport, but a full-size screenshot does not guarantee that lazy-loaded or scroll-triggered content has loaded first. If images or sections are missing, identify how the page loads them, give the page a chance to trigger and finish loading, then inspect the result.
What a Chrome full-page screenshot does—and does not do
In DevTools Device Mode, choose More options > Capture a full size screenshot to capture the page beyond the currently visible viewport. Choose Capture screenshot instead when you want only the current viewport. Chrome’s documentation describes the full-size option as capturing the whole page, including content not currently visible (Chrome for Developers: Simulate mobile devices with device mode).
As an Amazon Associate I earn from qualifying purchases.
That setting controls the screenshot’s extent. It is not documented as a command to scroll through the page, simulate a visitor, or fire every custom scroll handler. A screenshot records the rendered state at capture time; offscreen content that has not been requested or rendered can therefore appear as placeholders, blank areas, or missing sections.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsWhy is my Chrome full-page screenshot missing images?
The remedy depends on what is delaying the content. Determine whether the page uses native image lazy loading, custom visibility or scroll logic, or an infinite-scroll request.
Native loading="lazy"
With browser-level lazy loading, an offscreen image is deferred until it approaches a browser-calculated distance from the viewport. That distance is heuristic and can vary with browser implementation and resource or connection conditions; it is not a fixed screenshot threshold you can rely on. Google’s web.dev documentation records historical threshold changes in July 2020, but those values should not be treated as current, universal Chrome settings (Browser-level image lazy loading).
For images likely to be visible as soon as the page opens, avoid lazy loading them. Setting loading="eager" removes lazy deferral for that image, but does not by itself give it higher priority than other resources; Chrome guidance treats fetch priority as a separate consideration. For images that should be lazy-loaded, provide width and height so the browser can reserve layout space. Without dimensions, a gallery can initially have zero-size images, affecting how the browser judges what is near the viewport.
Custom JavaScript and scroll handlers
A site may load content through an IntersectionObserver, a scroll listener, or other JavaScript that waits for an element to approach or enter the viewport. Expanding the screenshot area is not the same as scrolling through the page, so those callbacks may not run. For a one-off capture, scroll through the page in increments, pause for requests and rendering, and then capture. This is an operational workaround, not a Chrome guarantee: inspect the final image to confirm that each expected section appeared.
Infinite scroll
An infinite-scroll page may fetch new items only as the reader reaches the end of the currently loaded content. One full-page screenshot may show only the chunks loaded so far; it is not proof that every item or asynchronous element was reached. Scroll to load successive chunks and capture the resulting states separately when completeness matters. For sites you operate, stable URLs for chunks, sequential links, and updating the displayed URL as the user moves between chunks make content easier to reach and reproduce. Google’s guidance also advises loading relevant lazy content when it becomes visible, without requiring a user interaction (Google Search Central: Fix lazy-loaded content).
How to capture a lazy-loaded page reliably
- Open Device Mode. In Chrome DevTools, switch to Device Mode and set the viewport you need. The screenshot will reflect the page state and dimensions at capture time.
- Identify what loads the missing content. Check whether images use native lazy loading, whether JavaScript observes visibility or scroll position, or whether the page fetches more items as you reach the bottom.
- Trigger the relevant loading behavior. For custom scroll-driven pages, scroll down in manageable increments. On infinite-scroll pages, continue until the chunks you need have appeared.
- Wait for loading and rendering to settle. Allow network requests and visual updates to finish after each scroll. Do not assume that a fixed delay works for every site.
- Capture the page. Select More options > Capture a full size screenshot for the expanded page, or Capture screenshot for the current viewport.
- Verify the output. Check the image for missing sections, placeholders, or cut-off content. Repeat the triggering and waiting steps if the content has not rendered.
How to make lazy-loaded content appear on a page you control
- Load relevant content when it becomes visible; do not make visibility-triggered content depend on an explicit click or other user gesture. Google notes that its crawler does not interact with a page and advises ensuring relevant lazy content loads whenever it is visible.
- Avoid lazy-loading images likely to be immediately visible. For an important image, eager loading removes lazy deferral; use fetch priority separately if higher priority is needed.
- Set image width and height to reserve layout space and reduce layout shifts. This also avoids zero-size gallery edge cases that can affect loading behavior.
- For infinite-scroll content, provide stable chunk URLs and sequential links, and update the displayed URL as a reader moves into a new chunk when appropriate. This improves reproducibility and helps ensure content is reachable beyond one loaded state.
Protocol automation: screenshot extent is separate from page loading
If you automate Chrome through the DevTools Protocol, Page.captureScreenshot includes a captureBeyondViewport parameter for capturing beyond the viewport. It controls screenshot geometry; it does not replace a separate plan for causing lazy or dynamically loaded content to load. Trigger the page’s required loading behavior, wait for it to finish, and then request the capture (Chrome DevTools Protocol: Page domain).
Common problems and fixes
| Symptom | Likely cause | What to do |
|---|---|---|
| Images below the fold are blank or show placeholders | They have not reached the browser’s lazy-load distance, or custom visibility logic has not run. | Scroll through the page in increments, wait for images to render, then capture and inspect. On a page you control, load relevant content when visible. |
| Only the currently loaded portion of an infinite list appears | The page fetches more content only after scrolling to a trigger point. | Scroll until the required chunks load and capture each state if needed. Use stable chunk URLs and sequential links on sites you maintain. |
| Content shifts or sections overlap in the final image | Images may lack reserved dimensions, or content may still be rendering when captured. | Set image width and height on pages you control; wait for visual updates before capturing. |
| A full-size capture still misses content that appears after scrolling | Screenshot extent was expanded, but the page’s scroll-triggered loading was not activated. | Trigger the required scroll or visibility behavior first. The full-size option does not promise to simulate scrolling. |
Or skip the browser setup
ScreenshotNeo can return a page capture from one request. For the full set of parameters, see the ScreenshotNeo documentation.
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 and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server provides screenshot and PDF tools for AI agents. The free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots. Learn more at ScreenshotNeo, or sign up free.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Frequently Asked Questions
Does Chrome’s full-size screenshot option guarantee every lazy-loaded image will appear?
No. It captures beyond the visible viewport, but does not guarantee that native lazy loading or custom scroll-triggered code has run.
Does loading="eager" make an image load at higher priority?
It removes lazy-loading deferral, but does not on its own raise the image’s fetch priority.
Can one screenshot prove an infinite-scroll page is complete?
No. It shows a rendered state; content in later chunks may not have loaded.
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.
