Why your full page screenshot is cut off at the bottom

Short answer

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.

Updated 25 July 2026Written by the Full Page Screenshot team

The frustrating part of this failure is that nothing warns you. There is no error, no partial-result notice, no truncation marker. You get a large image, it opens fine, and the missing half only becomes obvious when you scroll to the end looking for something that should be there.

Five things cause it. They are distinguishable in about ten seconds each.

Cause 1: the browser image size limit

The most common by a wide margin, and the only one that is not the page's fault.

What is happening: Browsers cap a single image at 16,384 pixels on a side. A capture tool that draws past that gets a silent failure from the graphics layer rather than an exception, so it finishes and hands you what it has.
How to confirm it: Check the image height. If it is exactly 16,384 pixels, or suspiciously close, this is it. On a 2x display the page only needs to be about 8,192 CSS pixels tall to reach the limit.
The fix: Use a tool that splits at the limit into parts that tile the page, or export to PDF, which paginates instead. Zooming the browser out to 67% before capturing also works, at the cost of rendered detail.

Causes 2 to 5

Lazy content never loaded: If sections below the fold load on scroll, a capture that moves faster than the network reaches the end of a shorter document than the one you would have seen. Scroll to the bottom manually first, wait, then scroll back up and capture. Covered in blank images in screenshots.
The page has infinite scroll: There is no bottom to reach. The capture stops where the document currently ends. See capturing an infinite scroll page.
The real scroller is a panel: If the page body does not scroll and an inner element does, the capture may measure the document height as one viewport and finish immediately. See pages with their own scrollbar.
The tab lost focus: Chrome only permits photographing the visible tab. Switching tabs, minimising the window or letting the screen lock stops the capture where it stood.

Diagnosing by image height

Open the file and read its pixel dimensions. The number tells you which cause you have.

Exactly 16,384 px tall: Canvas limit
A clean multiple of your viewport: Tab lost focus or capture stopped
Exactly one viewport tall: Nested scroll container
Shorter than the page, no pattern: Lazy content or infinite scroll

Frequently asked questions

Why does my screenshot stop halfway down the page?

Most often the 16,384 pixel image size limit. Check the height of the file you got: if it is at or near that number, the tool truncated rather than split.

Can any tool capture a page taller than 16,384 pixels in one image?

No. It is a browser graphics limit that applies to every extension equally. The options are splitting into parts or exporting to PDF.

Does zooming out help?

Yes. At 67% zoom the page renders about a third shorter in pixels, which often brings it under the limit. You lose rendered detail in exchange.

Why did the capture stop when I switched tabs?

Chrome only allows an extension to photograph the tab currently in view. There is no way around it, so the tab has to stay in the foreground.

Capture your first full page screenshot

Free, no account, and nothing leaves your computer.

Add to Chrome — Free Read the guide

Keep reading