How to Fix Chrome Full-Page Screenshots that Are Cropped on Mac

If a Chrome screenshot on your Mac stops at the visible part of the page, use Capture a full size screenshot in DevTools. The similarly named Capture screenshot command captures only the current viewport. In Chrome, open DevTools, turn on the device toolbar, open More options, and choose Capture a full size screenshot. Chrome documents this command for capturing the page content outside the viewport. Chrome DevTools: Device Mode.

1. Capture the whole page in Chrome on Mac

1. Open the page you want to capture in Chrome.
2. Open DevTools with Command+Option+I, or right-click the page and choose Inspect.
3. Turn on the device toolbar using the phone-and-tablet button in DevTools. You can also use Command+Shift+M.
4. In the device toolbar, open More options and choose Capture a full size screenshot.
5. Wait for the capture to finish. Chrome saves the screenshot as a downloaded image; check your Downloads folder.

The key distinction is the menu item: Capture screenshot means the visible viewport; Capture a full size screenshot means the full page. If the result is still incomplete, use the diagnostics below rather than assuming every crop has the same cause.

2. Pick the capture command that matches what you need

What to capture	Chrome method	Scope and limitation
Visible viewport	Device toolbar → More options → Capture screenshot	Only what is currently visible.
Whole document	Device toolbar → More options → Capture a full size screenshot	Includes page content outside the viewport.
One DOM element	Elements panel → right-click the node → Capture node screenshot	Captures the selected node, including below-the-fold content supported by the node capture feature.
A rectangular viewport region	Open the Command Menu and choose Capture area screenshot	Captures a selected region; DevTools must be docked to the browser window.

3. Capture one element or a selected area

Capture a DOM node

Use node capture when the thing you need is one card, table, chart, or other element rather than the entire document:

1. Open DevTools and select the Elements panel.
2. Use the element picker or inspect the DOM tree to locate the target.
3. Right-click the node and select Capture node screenshot.
4. Find the downloaded image in Downloads on macOS.

Chrome 89 introduced capture of a full node, including content below the fold. See Chrome for Developers: What’s New in DevTools (Chrome 89) and the DOM guide.

Capture a rectangular region

Focus DevTools, press Command+Shift+P to open the Command Menu, type Capture area screenshot, select the command, then drag over the region. If the command is unavailable or does not behave as expected, dock DevTools to the browser window; area capture does not work when DevTools is undocked. Chrome’s DevTools 74 release notes describe the Mac shortcut and selection workflow.

4. Diagnose a screenshot that is still cropped

1. Confirm the command. If you chose Capture screenshot, repeat with Capture a full size screenshot. The first command is viewport-only.
2. Check the capture scope. If only one region or component matters, try node capture. If you need a rectangle within the visible page, use area capture.
3. Inspect where the missing content lives. Some pages scroll within a nested panel rather than the main document. Scroll that panel and capture its node if that is the intended target. Full-page capture is documented for the whole page, but the docs do not promise identical behavior for every site-specific layout.
4. Check whether content has appeared yet. If the missing section loads only after scrolling, clicking, expanding a disclosure, or waiting, perform that action first and capture again. This is a diagnostic step: the correct command alone cannot make content that has not rendered appear.
5. Record the reproduction details. Note your Chrome version, the exact menu command, whether DevTools was docked, and whether the missing content belongs to the main document or a nested scroller. These details help distinguish a command mismatch from page-specific behavior.

A crop on one site does not establish a universal Mac or Chrome defect. Chrome’s documentation describes the command’s intended scope; individual page structure and state still matter.

5. Troubleshooting common problems

Symptom	Likely cause	What to do
Image ends at the bottom of the visible window	Viewport-only Capture screenshot was selected.	Use Capture a full size screenshot from the device toolbar’s More options menu.
One component is cut off even in a full-page image	The content may be inside a separate scrolling element, or it may not have rendered yet.	Inspect the DOM, scroll or expand the component, then try Capture node screenshot.
Area capture is missing or cannot be selected	DevTools is undocked, or the wrong Command Menu entry was chosen.	Dock DevTools, press Command+Shift+P, and select Capture area screenshot.
Screenshot captures the wrong thing	The command’s scope does not match the intended result.	Use full-size for the document, node capture for an element, or area capture for a rectangle.
Downloaded node image is hard to find	The file was saved to the browser’s download location.	Check Downloads on macOS, as described in Chrome’s DOM guide.
Steps do not match the visible Chrome UI	The DevTools interface or page state may differ from the documented flow.	Reopen DevTools, verify the device toolbar is enabled, and record the Chrome version and exact available menu labels for a reproducible report.

6. Or skip the browser setup

For repeatable captures from scripts or services, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns an image or PDF. The example below requests a WebP screenshot of the page; see the ScreenshotNeo API documentation.

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

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)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

ScreenshotNeo accepts cookie or consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots.

Create a free ScreenshotNeo account for 1,000 screenshots a month with no card.

7. Performance, reliability, and cost

Chrome DevTools is built into Chrome, so its capture workflow does not require an API key or per-shot service plan. A very long page can produce a large image and take longer to capture or save. If content is lazy-loaded or interaction-dependent, make it appear before capturing. Chrome’s cited documentation does not specify a universal image-size limit, completion time, or Mac-specific success rate.

For automated workflows, account for page readiness and failures in the calling application. ScreenshotNeo’s documented billing behavior means blank pages, bot checks, timeouts, failed loads, and cache hits are not billed; inspect X-Page-Verdict and X-Billed on responses. 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); annual billing gives two months free. Every feature is on every plan.

FAQ

What is the Mac shortcut for Chrome’s Command Menu?

Press Command+Shift+P while DevTools is focused. Use it to find commands such as Capture area screenshot.

Can Chrome capture just one element below the fold?

Yes. Select the node in Elements, right-click, and choose Capture node screenshot. Chrome documents full-node capture including below-the-fold content.

Why is there no single fix for every cropped page?

The command may be correct while a page’s content is in a nested scroller or has not appeared yet. The site, capture scope, and page state are needed to diagnose a specific reproduction.

Does area capture work with DevTools detached?

No. Dock DevTools to the browser window before using Capture area screenshot.