Chrome does not provide a documented switch that disables every kind of website lazy loading. To include deferred images or content, trigger the page’s own loading behavior—usually by scrolling through the areas you need—then capture the page. For repeatable captures, Headless Chrome can take a screenshot after a specified delay, but a delay alone cannot make a site load content it has not been prompted to show.
Why content is missing from a Chrome screenshot
Lazy loading defers non-critical or off-screen content until it is needed. Sites may rely on the browser’s built-in lazy loading, JavaScript such as IntersectionObserver, or another library, so the trigger varies by site. Google recommends loading relevant content when it becomes visible in the viewport; applying that behavior to a screenshot is a practical workflow, not a guarantee for every page. Google Search Central’s lazy-loading guidance describes these approaches.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
The 138 Best Chrome Extensions | $2.99 | Buy on Amazon |
For an infinite-scroll page, decide how far you want the capture to go. The page may keep adding items instead of reaching one naturally finite end. Google’s guidance for infinite scroll recommends paginated chunks with persistent, unique URLs and stable content, but that is implementation guidance rather than a Chrome screenshot setting.
Load deferred content before capturing
- Open the target page in Chrome. Wait for its initial content to appear.
- Scroll through the sections you want in the screenshot. If content loads as it enters the viewport, move downward in increments and pause for the page to respond. Repeat until the desired images or sections have appeared.
- For infinite scroll, keep triggering the page until your chosen endpoint is present. There is no universal wait time or scroll sequence; it depends on the site’s behavior and network response.
- Capture the page. Use the screenshot capture command available in your installed Chrome DevTools, or use Headless Chrome for a repeatable command-line capture as described below.
- Inspect the result. If content is absent, return to the page, trigger the relevant area again, allow it to load, and recapture.
Diagnose loading with the Network panel
DevTools can help you see when the page changed during a reload, but its Network screenshots are a diagnostic aid—not a lazy-loading off switch.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →#1 Best Overall
- Open Chrome DevTools and select the Network panel.
- Open Network panel settings and enable Capture screenshots.
- With the Network panel focused, reload the page.
- Review the screenshot frames in the load timeline. Select a frame to inspect the page’s visual state and the network activity up to that point.
See Chrome DevTools’ Network reference for the panel controls. The same reference describes Disable cache as a way to disable browser caching and emulate a first-time visit; it does not disable the site’s lazy-loading logic.
Capture from the command line with Headless Chrome
For a repeatable screenshot, Chrome Headless documents --screenshot and --window-size. For example:
chrome --headless=new --screenshot --window-size=412,892 https://example.com/This captures a screenshot using the specified viewport. The example dimensions are illustrative, not a universal recommendation. To wait a fixed interval before capture, add --timeout with a delay in milliseconds:
chrome --headless=new --screenshot --window-size=412,892 --timeout=5000 https://example.com/Chrome documents --timeout as the delay before --screenshot, --dump-dom, or --print-to-pdf captures page content. Without a timeout or virtual-time budget, capture occurs as soon as the page is loaded. A fixed delay can help with asynchronous rendering, but it does not guarantee that deferred content has been triggered or finished loading. See Chrome Headless documentation for the available capture options.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchControls that do not disable lazy loading
- Disable cache: changes browser caching behavior; it is not documented as a lazy-loading control.
- Disable JavaScript: turns off JavaScript so you can observe the page without it, but may break or alter content. Because some sites use JavaScript libraries or IntersectionObserver for deferred loading, this is not a reliable general fix. Chrome’s DevTools Preferences reference describes the setting and advises reloading to see how the page behaves with JavaScript off.
- A longer timeout: gives already-triggered work more time, but does not necessarily trigger content farther down the page.
Common problems and fixes
| What you see | Likely reason | What to try |
|---|---|---|
| Images lower on the page are blank or missing. | The page has not loaded them until they enter the viewport. | Scroll through the affected areas, pause for loading, and capture again. |
| The screenshot ends before the content you need. | The capture viewport or capture method did not include the desired page area, or more content must be triggered. | Trigger the missing content first. In Headless Chrome, adjust the viewport or use the full-page capture option available in your installed DevTools workflow. |
| Headless capture still misses deferred items. | A fixed timeout does not trigger every site-specific loading behavior. | Use the page’s normal scroll or interaction triggers before capture; increase the delay only if triggered content needs more time. |
| Content disappears or changes after disabling JavaScript. | The page depends on JavaScript for rendering or lazy loading. | Turn JavaScript back on and load content through the page’s normal behavior. |
| The page keeps growing and never appears complete. | It uses infinite scroll and continues loading additional items. | Choose a specific endpoint, such as a target section or number of loaded items, then capture that state. |
Or skip the browser setup
ScreenshotNeo can capture a page with one API request. Its clean-shot steps accept the cookie or consent banner like a visitor and remove more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Only clean shots are billed: bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and responses identify the page verdict and billing status in headers. It also offers an MCP server for AI agents, with the tools take_screenshot, get_page_info, and capture_pdf.
For lazy-loaded content, remember that a screenshot request does not guarantee every site-specific deferred item will be triggered. The API supports full-page capture with lazy images loaded, along with waits such as a selector, delay, or network idle; choose the behavior appropriate to the page. The ScreenshotNeo API documentation lists the request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpReplace YOUR_API_KEY with your key and change the target URL as needed. ScreenshotNeo returns a screenshot in PNG, JPEG, or WebP, or a PDF, depending on the request. It includes 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000. Learn about ScreenshotNeo or sign up for 1,000 free screenshots a month with no card.
Frequently Asked Questions
Does Chrome have a universal lazy-loading disable setting?
No universal switch is documented in the cited Chrome guidance. The practical approach is to trigger the page’s own loading behavior, typically by scrolling content into view.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesWill Headless Chrome’s timeout load every lazy image?
No. The timeout waits before capture; it does not guarantee that the page has triggered or completed every deferred load.
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.
