Troubleshooting articles

An infinite scroll page has no total height, so there is no complete version to capture. Scroll to the point you want the capture to end, wait for loading to stop, then start. You will get everything currently in the document, which is the only well-defined answer available.

A full page screenshot cut off at the bottom is almost always the browser image size limit being hit without being handled: past roughly 16,384 pixels the draw fails and you are handed an image that looks complete but is not. The other four causes are lazy content, infinite scroll, a nested scrolling panel, and the tab losing focus mid-capture.

Any element visible on the screen becomes part of the image. To remove a cookie banner or popup, you must dismiss it manually before triggering the capture. If the banner reappears during a long scroll, disable automatic scrolling or delete the element directly in Chrome DevTools using the Elements panel before taking the shot.

Images that load only when scrolled into view have not finished downloading and decoding by the time a fast capture passes them, so they are photographed as empty placeholders. Scrolling the page to the bottom once before capturing forces every image to request, which fixes it in nearly every case.

A full page capture of a long site at 2x display density routinely produces a 40 to 80 MB PNG, which exceeds the upload limit of most issue trackers and chat tools. The four fixes, in order of how much they cost you: export JPG instead, export PDF, zoom out before capturing, or crop to the part that matters.

A sticky or fixed header sits in the viewport at every scroll position, so it appears in every individual capture and ends up stamped down the joined image. The fix is to neutralise fixed and sticky positioning for the duration of the capture, which puts the header back in the document flow where it appears exactly once.

If your website screenshot captures in dark mode when you expected light mode (or vice versa), it is because the site respects the operating system's `prefers-color-scheme` media query rather than its own default styling. The browser injects the current OS theme setting into the page context during rendering. To fix this, you must temporarily change your OS display settings or use a browser profile configured for the desired theme before triggering the capture.

If a capture returns exactly one screenful, the page body probably does not scroll at all. Application layouts commonly pin the body to the viewport height and put the scrollbar on an inner element, so scrolling the window does nothing. The capture has to detect that element and scroll it instead.