A screenshot that stops at the bottom of the visible window usually means the capture used viewport or clipped-region mode—not full-page mode. If the tool did request the whole page, an unusually tall document may instead be hitting a limit in that capture path. The right fix depends on what produced the image, so start by checking the capture method.
First, identify how the screenshot was made
Chrome’s built-in developer tools, a browser extension, a screenshot API, an automation script, and an operating-system capture can use different capture paths. A capture of the visible viewport or a defined region is expected to stop there. A desktop screenshot shortcut captures the display rather than the entire scrollable document.
As an Amazon Associate I earn from qualifying purchases.
If you are not sure which mode was used, check the tool’s screenshot settings or documentation for “full page,” “full-page,” or “capture beyond viewport.” Do not assume that a button labeled “screenshot” includes content below the fold.
Check that the capture explicitly includes the whole page
Browser automation tools distinguish a viewport screenshot from a full-page screenshot. In the Chrome DevTools Protocol, screenshot capture has a clipping option for a specific region and a captureBeyondViewport option; its documented default is false. A caller that leaves that setting at its default may capture only the viewport. See the Chrome DevTools Protocol Page reference.
Puppeteer
In Puppeteer, set fullPage: true. Its ScreenshotOptions documentation describes this as taking a screenshot of the full page when the option is true. A minimal example:
import puppeteer from 'puppeteer';
const browser = await puppeteer.launch();
const page = await browser.newPage();
await page.goto('https://example.com', { waitUntil: 'networkidle2' });
await page.screenshot({ path: 'page.png', fullPage: true });
await browser.close();Replace the example URL with the page you need. If your existing code specifies a clip rectangle, remove it when you want the whole page: a clip intentionally limits the captured area. See the Puppeteer ScreenshotOptions reference.
Playwright
Playwright also has a full-scrollable-page screenshot mode. Use fullPage: true for a page capture, or use its element screenshot method when only one element is wanted. Its documentation does not allow combining full-page mode with a target element.
import { chromium } from 'playwright';
const browser = await chromium.launch();
const page = await browser.newPage();
await page.goto('https://example.com', { waitUntil: 'networkidle' });
await page.screenshot({ path: 'page.png', fullPage: true });
await browser.close();For an element-only capture, locate the element and call its screenshot method instead, without fullPage. See Playwright’s screenshot documentation. Puppeteer is a Chrome automation library; Chrome for Developers outlines its role in automating Chrome with Puppeteer.
Consider page-size limits on exceptionally long pages
If you have confirmed that the tool requested full-page capture but the result still stops at a consistent point on a very tall page, the capture implementation may be unable to produce an image of that size. Chromium source code reviewed for this article checks full-page dimensions and can reject very large captures with “Page is too large.” The same implementation comment mentions a 16K limit in headless mode. These are details of a particular implementation revision, not a universal pixel cutoff for every Chrome build, operating system, or screenshot tool. The Chromium page handler source shows the implementation path.
For a page that exceeds the tool’s limits, capture smaller sections or use a workflow that can split the page into multiple outputs. Do not treat one threshold as a guarantee: limits can vary by browser version and capture method.
Rank #3
Troubleshoot the cutoff by symptom
| What you see | Likely branch to check | What to do |
|---|---|---|
| The image ends at the browser’s visible window height. | The capture likely used viewport mode, a region clip, or a desktop display capture. | Switch to the tool’s explicit full-page option; if using the DevTools Protocol, check whether beyond-viewport capture is enabled. |
| The image always ends at about the same point on a very long page. | The full-page request may be exceeding an implementation or output-size limit. | Try section captures or a workflow that splits the output. The exact limit is tool- and build-dependent. |
| The screenshot contains only one component, even though the page is longer. | The tool may be targeting an element rather than the document. | Capture the page rather than the element. In Playwright, full-page capture and a target-element capture are separate modes. |
| You cannot tell whether the tool requested the full page. | The interface or wrapper may hide the underlying capture setting. | Inspect its screenshot options or API request; look for a full-page setting, clipping coordinates, or a beyond-viewport parameter. |
The available browser documentation establishes the viewport, clipping, element, and full-page distinctions. It does not identify a universal cause for every cutoff, or establish that CSS, lazy-loaded content, or a particular extension caused yours. Investigate those only if you can reproduce the issue with the page and tool in question.
Free tools Windows power users keep installed
One-click scans. No signup required.
Or skip the browser setup
For a repeatable capture without configuring browser automation, ScreenshotNeo provides a website screenshot API and MCP server. A single GET request returns an image or PDF; this cURL example saves a WebP screenshot:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo API documentation for the key setup and available parameters. Cookie banners are accepted before capture and 60+ known consent platforms, newsletter popups, and chat widgets are removed; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and whether it was billed. Its MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Frequently Asked Questions
Does Chrome’s screenshot feature always capture the entire webpage?
No. A viewport or clipped-region capture covers only its selected area; the capture tool must provide and use a full-page mode.
Is there one maximum page height for full-page screenshots in Chrome?
No universal cutoff is established. Limits depend on the Chrome build and capture method.
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.
