Why Chrome Full-Size Screenshot Capture Is Not Found and How to Fix It

Chrome’s full-page command is named Capture a full size screenshot. It appears in Chrome DevTools only after you enable Device Mode, then open Device Mode’s More options menu. The separate Capture screenshot command captures only the visible viewport. Chrome’s documented workflow is described in the Device Mode documentation.

1. The correct way to capture the whole page

1. Open the page you want to capture in Chrome.
2. Open DevTools. You can right-click the page and choose Inspect, or use Ctrl+Shift+I on Windows/Linux or Cmd+Option+I on macOS.
3. Turn on Device Mode by selecting the phone and tablet icon in the DevTools toolbar. This is also called the Toggle device toolbar button.
4. In the Device Mode toolbar, open the More options menu. It is the three-dot menu in the device toolbar, not the main DevTools menu.
5. Choose Capture a full size screenshot.

Chrome captures the complete document, including content below the visible viewport. If you only need what is currently visible, choose Capture screenshot instead.

2. Why the command is not visible

The official instructions place the full-size command in Device Mode’s More options menu. If you are looking through the regular DevTools menus or the browser’s three-dot menu, you are looking in the wrong context. Enter Device Mode first, then inspect that toolbar menu.

The available Chrome documentation does not establish that a particular operating system, DevTools docking position, Chrome version, or setting causes the command to disappear. Treat those as troubleshooting checks rather than confirmed causes.

Check the capture context

Your goal	Documented route	What it captures
Visible viewport	Device Mode → More options → Capture screenshot	The current viewport only
Entire page	Device Mode → More options → Capture a full size screenshot	The whole page, including content outside the viewport
Selected rectangle	Command Menu → Capture area screenshot	An area you select manually

3. Device Mode details that affect the result

Device Mode emulates a mobile viewport. The screenshot therefore reflects the selected viewport width, height, device pixel ratio, and orientation. Before capturing, confirm:

• Device or Responsive mode: choose the layout you need to document.
• Width and height: set explicit dimensions when comparing screenshots.
• Device pixel ratio: a higher ratio produces a denser image and a larger file.
• Orientation: switch between portrait and landscape when the responsive layout changes.
• Zoom: keep page zoom consistent across captures.

Full-size capture includes the document’s content beyond the viewport. A page with lazy-loaded content may still need to load that content before capture; scroll through the page first if the site only loads sections after they enter view.

4. Command Menu shortcuts and area capture

Chrome’s Command Menu opens with Ctrl+Shift+P on Windows/Linux and Cmd+Shift+P on macOS. It documents commands such as Capture area screenshot. This is a separate workflow from Device Mode’s full-size screenshot command.

The Command Menu documentation states that area capture does not work when DevTools is undocked. That limitation is documented for area screenshots; it does not establish that undocking disables Device Mode’s full-size command. Use the Device Mode menu for a full-page capture.

5. A repeatable manual capture checklist

• Wait for the page’s primary content to finish loading.
• Dismiss any overlays that obscure the page.
• Set the intended viewport and device pixel ratio.
• Enable Device Mode.
• Open Device Mode’s More options menu.
• Select Capture a full size screenshot.
• Open the downloaded image and check the bottom of the page for missing sections.

6. Troubleshooting common problems

The menu shows “Capture screenshot” but not “Capture a full size screenshot”

Confirm that Device Mode is enabled and that you opened the More options menu inside the device toolbar. The two commands are adjacent but have different scopes. If you are in the main DevTools menu, switch to the device toolbar menu.

The screenshot is only the visible viewport

You selected Capture screenshot. Repeat the process and select Capture a full size screenshot. The latter is the documented whole-page action.

The bottom of the page is blank or missing images

The capture can only include content the page has rendered. Wait for network activity and client-side rendering to finish. For pages that lazy-load images on scroll, scroll through the document before capturing, then run the full-size command again.

A cookie banner, newsletter popup, or chat bubble covers the page

Close the overlay before capturing. If it reappears on every load, clear the site’s state or use a capture service that can handle consent and overlays before taking the screenshot.

The image is unexpectedly narrow or uses a mobile layout

Device Mode is active, so Chrome is using its emulated viewport. Change the width, device preset, or orientation to match the layout you need, then capture again.

Area capture does not work

Chrome’s Command Menu documentation says area capture does not work when DevTools is undocked. Dock DevTools again, or use the Device Mode full-size command when your goal is the entire page.

The command still cannot be found

Return to the documented sequence: open DevTools for the target page, enable Device Mode, open the device toolbar’s More options menu, and look for Capture a full size screenshot. The cited documentation does not identify a single version, operating-system, or docking-state explanation for every missing command.

7. Chrome version history

Chrome DevTools release notes say full-page screenshots were introduced in Chrome 59. That historical note explains why older Chrome installations may differ, but it is not evidence that a particular current configuration will hide the command. Use the current Device Mode instructions as the operational reference.

8. When a browser workflow is the wrong tool

Manual DevTools capture works well for a one-off image. It becomes difficult when you need the same viewport, cleanup rules, output format, and timing across many URLs or in CI. A browser automation script must also manage navigation, rendering waits, lazy content, cookies, overlays, failures, and file storage.

9. Or skip the browser setup

ScreenshotNeo provides a single GET request for a PNG, JPEG, WebP, or PDF screenshot. It accepts the cookie or consent banner like a visitor, then removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the result with X-Page-Verdict and X-Billed headers.

See the ScreenshotNeo API documentation for the complete option list, including full-page capture, CSS selectors, device presets, dark mode, retina scale, waits, custom CSS and JavaScript, cookies and headers, request blocking, caching, signed links, asynchronous jobs, bulk capture, PDFs, and usage reporting.

cURL

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

Python

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

An MCP server also lets Claude, Cursor, and other MCP clients call 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. Every feature is available on every plan.

Create a free ScreenshotNeo account and start with 1,000 screenshots a month at no charge and no card.

10. Performance, reliability, and cost considerations

Manual Chrome capture

• Performance: capture time depends on page rendering, image loading, and the amount of content.
• Reliability: results can vary when the page changes state, shows overlays, or loads content only after scrolling.
• Cost: there is no API charge, but repeated captures require manual browser work or automation maintenance.

Screenshot API capture

• Performance: use a fixed viewport, explicit waits, and caching when you need repeatable output.
• Reliability: inspect X-Page-Verdict and X-Billed to distinguish clean captures from bot checks, blank pages, failures, and cache hits.
• Cost: only clean shots are billed. Plans are Free (1,000/month), Starter ($5 for 3,000), Growth ($15 for 15,000), Pro ($39 for 60,000), Scale ($99 for 250,000), and Business ($249 for 1,000,000). Yearly billing gives two months free.

11. FAQ

Is “Capture a full size screenshot” the same as “Capture screenshot”?

No. The full-size command captures the entire page; Capture screenshot captures the visible viewport.

Can I use Ctrl+Shift+P to find the full-size command?

Ctrl+Shift+P (Cmd+Shift+P on Mac) opens the Command Menu, whose documented area-capture command is separate. Use Device Mode’s More options menu for full-size capture.

Does undocking DevTools disable full-page capture?

The cited documentation only says undocking prevents Command Menu area capture. It does not state that undocking disables Device Mode’s full-size command.

When was full-page capture added?

Chrome DevTools release notes identify Chrome 59 as the introduction point for full-page screenshots.

What should I use for automated batches?

Use an API such as ScreenshotNeo when you need repeatable options, cleanup of common overlays, status headers, and batch or asynchronous capture.