Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

If a Chrome screenshot ends at the bottom of the visible window, you likely captured the viewport instead of the full page. In DevTools Device Mode, open More options and choose Capture a full size screenshot. Chrome distinguishes this from Capture screenshot, which captures only the current viewport. Chrome DevTools’ Device Mode guide documents both commands.

Use Chrome’s full-size screenshot command

  1. Open the page in Chrome and open DevTools with Ctrl+Shift+I on Windows or Linux, or Command+Option+I on macOS.
  2. Turn on Device Mode by selecting the phone-and-tablet icon in the DevTools toolbar, or pressing Ctrl+Shift+M (Windows/Linux) or Command+Shift+M (macOS).
  3. Open the Device Mode More options menu.
  4. Select Capture a full size screenshot. Do not select Capture screenshot if you need content below the visible viewport; that command captures the current viewport.

Chrome’s documentation describes the full-size command as capturing the whole page, including content not currently visible in the viewport. The available documentation does not establish a single Chrome version or operating system for every interface detail, so labels or shortcuts may vary slightly.

If the screenshot is still incomplete

First confirm that you selected Capture a full size screenshot, not the viewport command. If the full-size image still has missing or awkward content, check the page itself and how it behaves as it loads. These are possible causes to investigate, not guaranteed explanations for every clipped capture.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Content loads as you scroll

Some pages load images or other content only as it approaches the viewport. Scroll through the page first, wait for content to appear, then try the full-size capture again. Whether this helps depends on the site’s implementation.

Fixed or sticky elements

A navigation bar or other element that stays attached to the viewport can appear unexpectedly in a long capture. A third-party commercial guide identifies fixed and sticky elements as possible sources of imperfect full-page captures; it does not confirm that they cause every clipping problem. If you need only a particular section, use a node or area capture instead of the whole page.

Dynamic pages and very long content

Pages that change while loading, or pages that are unusually long, may not produce the result you expect. The cited third-party guide also mentions these possibilities, but the available evidence does not establish a universal fix. Try waiting for the page to settle and capturing again; if only one component matters, capture that component rather than the entire document.

Choose a narrower DevTools capture when appropriate

A full-page screenshot is not always the right output. Chrome DevTools documents additional screenshot workflows, including capturing a node, an area, or a mobile view. Chrome for Developers’ screenshot techniques article, by Dale St. Marthe and last updated August 9, 2024, describes these options alongside full-page capture.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Node capture: use when you need a particular page element rather than the entire page.
  • Area capture: use when you need a selected region.
  • Mobile screenshot: use when the intended result is a mobile-sized view rather than a full desktop page.

Try an extension only if DevTools does not meet the need

GoFullPage is a Chrome Web Store extension for full-page screen capture. Its listing includes capture-related fixes in its change log, but that does not demonstrate that it will solve every page-specific problem. Consider it an alternative when the built-in workflow remains unsuitable, rather than a guaranteed repair. View GoFullPage in the Chrome Web Store.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Or skip the browser setup

For a screenshot generated from code, ScreenshotNeo takes a URL in one GET request and returns an image or PDF. Its clean-shot process accepts the cookie or consent banner like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. Developers can also use its MCP server with Claude, Cursor, or another MCP client.

Here is a cURL example; replace the URL with the page you want to capture. See the ScreenshotNeo API documentation for request options and response details.

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

ScreenshotNeo offers 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000. Learn about ScreenshotNeo, or sign up for the free plan.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

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.