How to Screenshot a Long Webpage in Chrome When the Page Uses Lazy Loading

To screenshot a long webpage in Chrome when it uses lazy loading, scroll down through the page first and pause as new sections appear. This gives images and other deferred content a chance to load. Then use Chrome DevTools’ Capture a full size screenshot command and inspect the downloaded image from top to bottom. Scrolling first is a practical workaround, not a guarantee: some pages load content differently, so verify the result.

Why lazy-loaded content can be missing

Lazy loading defers some images or other content until it approaches the visible part of the page. A full-height capture started from the top may not trigger the same scroll-driven loading behavior as visiting each section. The result can be a screenshot with blank spaces or missing images, even if the page looked complete while you browsed it.

There is no universal scroll distance or wait time that works for every site. Loading can depend on image size, network speed, scripts, and the page’s implementation. The reliable approach is to scroll through the actual content, wait for new material to appear, and check the capture.

Recommended workflow in Chrome

1. Open the page and let it settle. Wait for the initial visible content to finish loading before you start.
2. Scroll down in manageable increments. When a new section or image appears, pause long enough to see whether it loads. Continue until you reach the bottom.
3. Check the end of the page. Wait briefly, then look again for late-loading sections or images. If new content appears, scroll through it too.
4. Open DevTools. Use Ctrl+Shift+P on Windows or Linux, or Cmd+Shift+P on Mac, to open the Command Menu.
5. Find the full-size capture command. Search for Capture full size screenshot and select the matching command. Chrome also offers this option in Device Mode under More options.
6. Inspect the downloaded screenshot. Check the full image from top to bottom for blank gaps, missing images, cut-off sections, or repeated sticky elements. If something is missing, do another scroll-and-wait pass and capture again.

Chrome documents the full-size screenshot option in its Device Mode guide and the Command Menu shortcut in its Command Menu documentation.

Pages that need extra care

• Infinite scrolling: The page may keep adding items as you scroll. Decide how much content you need and load through that point. A finite screenshot cannot contain every item in an unbounded feed.
• Virtualized lists: Some apps remove off-screen items from the document and render only the visible rows. Scrolling may load more entries without leaving all earlier entries available for one full-page capture. Check the output; capture sections separately if necessary.
• Nested scroll panels: A feed, table, or chat area may scroll inside the page instead of scrolling the document. Identify the area that actually moves. DevTools’ full-size page capture covers the document, so an inner panel may need its own capture approach.
• Carousels and embedded content: Content that appears only after interaction may not load just because you scroll past it. Open or advance the relevant component before capturing if those states belong in the screenshot.
• Sticky headers and repeated elements: A sticky element may appear in an unexpected position or seem repeated in a long capture. Inspect the result and consider capturing sections separately when the layout makes one continuous image unsuitable.

Alternatives and load diagnostics

Scroll-aware capture extensions

Some Chrome extensions advertise full-page capture that handles lazy-loaded images. For example, the FullPageShot Chrome Web Store listing makes that claim. It is the extension publisher’s feature claim, so check the resulting image on your page before relying on it. Review the extension’s permissions and privacy information in its listing before installing.

Use Network screenshots to investigate timing

If you need to understand when content appears, Chrome DevTools’ Network panel can capture screenshots during page loading. Enable Capture screenshots in Network settings, focus the panel, and reload. The thumbnails help relate visible changes to the loading timeline and requests. This is a diagnostic aid; it does not replace the full-page capture workflow.

Troubleshooting

Symptom	Likely cause	What to try
Images are blank or missing	The page did not load them until they approached the viewport.	Scroll through the page again, pause when each new section appears, wait at the bottom, and recapture.
The Command Menu finds no matching command	The search wording may not match the command label, or DevTools may not be open.	Open DevTools, press the platform shortcut, and search for full size screenshot. You can also find the option in Device Mode’s More options menu.
Only part of a feed appears	The page uses infinite scrolling or a virtualized list.	Scroll until the specific items you need have loaded. Check whether earlier items remain in the page; capture sections separately if they do not.
The inner list is missing or shows only its initial items	The list scrolls inside a panel, while the screenshot command captures the document.	Scroll the panel itself and determine whether its content can be captured separately. Verify the output rather than assuming the page capture includes every panel item.
The capture has awkward sticky elements or layout seams	The page uses fixed or sticky positioning, or the long layout is difficult to represent as one image.	Inspect the full result. If the artifact makes the page hard to read, capture smaller sections and keep their order clear.
Content still appears late after scrolling	Scripts, embeds, or network requests may complete after a section first enters view.	Pause longer at affected sections, check the page again at the bottom, and use Network-panel screenshots to investigate loading timing.

Performance, reliability, and cost

For a manual capture, the main cost is time: you need to visit the page’s sections, wait for deferred content, and inspect the output. Longer pages and slower-loading media usually require more waiting. Capturing an extremely tall page can also produce a large image that is cumbersome to open or share, so separate captures may be more practical when the whole page is not needed at once.

Reliability depends on the page. Scrolling can trigger viewport-based loading, but it cannot guarantee that every script-driven, interactive, virtualized, or failed resource will appear. Treat the screenshot as complete only after inspecting it. For work that needs a repeatable capture, record the page state and the scroll-and-wait process so you can compare results.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. Its full-page capture loads lazy images. A single GET request returns an image or PDF; the example below saves a WebP screenshot of Stripe. See the ScreenshotNeo API documentation for request options.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python

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}`);

ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot. Bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.

Sign up for 1,000 free screenshots a month, with no card required.

FAQ

Can Chrome capture the whole page without an extension?

Yes. DevTools includes a full-size screenshot command in Device Mode and in the Command Menu.

Does scrolling guarantee every lazy image will appear?

No. Scrolling often triggers viewport-based loading, but each page behaves differently. Inspect the downloaded image and retry or capture sections separately if content is missing.

Where does Chrome save the screenshot?

The browser downloads the image. Check Chrome’s download shelf or the downloads location configured in your browser.