How to Take a Screenshot with Google Chrome

Quick answer: On Android, Chrome can capture a long page with More > Share > Long screenshot. For a normal device screenshot, press Power + Volume down; on Android 12 and later, tap Capture more to extend it on most scrollable screens. On desktop, open Chrome DevTools, run the command Capture full size screenshot, and save the result. The desktop command comes from a Chrome Community answer, so its wording and availability can vary by Chrome version.

Choose the capture you need

Goal	Best method	Result
What is visible now	Android system screenshot or desktop screen capture	Viewport-sized image
An entire web page on Android	Chrome Long screenshot	Scrollable image you crop before saving
An entire web page on desktop	Chrome DevTools command	Full-page image rendered by Chrome
Repeatable, automated captures	ScreenshotNeo API	PNG, JPEG, WebP, or PDF from one request

How do I take a screenshot of a web page on Android?

Use Chrome’s Long screenshot option

Open the page in Chrome.
Tap More (the three-dot menu).
Tap Share, then choose Long screenshot.
Drag the crop handles until the screenshot includes the length you need.
Tap Confirm, then save, copy, edit, or share the image.

These labels come from Google’s Chrome Android help. They can differ slightly by Chrome version or phone model. If Long screenshot is missing, use the device-level method below or update Chrome.

Use Android’s built-in screenshot controls

Open the page and position it at the content you want to capture.
Press Power + Volume down together. Some phones offer an alternative shortcut through the Power button menu.
For a scrolling capture, tap Capture more after the first screenshot.
Adjust the selected area and save or share it.

Google documents scrolling screenshots for Android 12 and later on most screens that allow scrolling. Support and button combinations vary by manufacturer, so a phone may show different controls.

How to take a full-page screenshot on desktop Chrome

The following workflow is described in a Chrome Community answer dated March 6, 2025. It is not a current official Chrome desktop help procedure, and command names can change.

Open the page in Chrome.
Open DevTools with Ctrl+Shift+I on Windows/Linux or Cmd+Option+I on macOS.
Open the DevTools command menu with Ctrl+Shift+P or Cmd+Shift+P.
Type capture full size screenshot.
Select the matching command and wait for Chrome to download the image.

If the command does not appear, check that DevTools has focus, try the alternate shortcut for your operating system, and search for screenshot rather than the complete phrase.

Capture only the visible viewport

For a quick image of what is currently visible, use your operating system’s normal screen-capture shortcut. This captures browser chrome and anything else in the selected region. Chrome’s full-page command is preferable when you need the document beyond the viewport.

Or skip the browser setup

ScreenshotNeo returns a clean screenshot from one GET request. Its capture options include full-page screenshots with lazy images loaded, CSS-selector element capture, dark mode, device presets or custom viewports, retina scale, custom CSS and JavaScript, click and wait actions, request blocking, headers, cookies, user agents, authorization, timezone, geolocation, transparent backgrounds, resizing, caching, signed links, asynchronous jobs, bulk capture, PDFs, and a usage API. See the ScreenshotNeo documentation for the complete parameter reference.

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,
)
r.raise_for_status()
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}`);
if (!res.ok) throw new Error(`Screenshot failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
require('node:fs').writeFileSync('shot.webp', image);

ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing; response headers identify the page verdict and whether the request was billed. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.

Options that affect screenshot output

Visible versus full page

A viewport capture is fast and matches what a person sees without scrolling. A full-page capture stitches or renders content below the fold and is better for documentation, audits, and visual regression. Long pages can produce very tall files; crop or resize them for downstream systems.

Lazy-loaded content

Scroll through the page before using a manual capture if images appear only after they enter the viewport. ScreenshotNeo’s full-page mode loads lazy images as part of capture.

Dynamic pages

Wait for a stable state before capturing dashboards, animations, or client-rendered content. In an automated service, wait for a selector, a delay, or network idle. For a manual Chrome capture, wait until the relevant data and fonts have rendered.

Device and scale

Mobile pages can change layout at different widths. Use the target device’s viewport when accuracy matters. Higher pixel density produces sharper images but larger files.

Troubleshooting

Problem	Likely cause	Fix
Long screenshot is not listed on Android	Chrome or the phone does not expose the feature	Update Chrome, try Android’s Capture more, or use a desktop/API capture.
Capture more is unavailable	Older Android version or a screen that is not recognized as scrollable	Check Android version, scroll manually and retry, or capture separate sections.
Desktop command cannot be found	DevTools lacks focus, wording changed, or the Chrome version differs	Click inside DevTools, open the command menu again, and search for `screenshot`. The documented community workflow may not work in every version.
Screenshot contains a cookie banner or chat bubble	The manual browser capture includes page overlays	Dismiss or hide the overlay before capture, or use ScreenshotNeo, which removes more than 60 known consent platforms plus newsletter popups and chat widgets.
Page is blank or incomplete	Network failure, bot check, JavaScript error, or content not yet loaded	Reload and wait for the page; check the console and network panel. For API jobs, use selector or network-idle waits and inspect the page verdict headers.
Images are missing	Lazy loading, blocked resources, or capture occurred too early	Scroll through the page, wait for images, and verify that requests are allowed.
Managed Chrome blocks screenshots	An administrator policy may prevent capture	Ask the administrator. Chrome’s documented screenshot-prevention policy applies to managed users and browsers with a Chrome Enterprise Premium license, not every personal Chrome installation.

Performance, reliability, and cost notes

Manual captures: They are convenient for one-off work but depend on the current device, viewport, login state, and page timing.
Repeatability: Record the URL, viewport, browser version, scroll state, and any waits or manual dismissals when screenshots will be compared later.
Large pages: Full-page images use more memory and disk space. Prefer element capture or a resized output when only one section is needed.
Automation cost: ScreenshotNeo bills only clean shots. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the X-Page-Verdict and X-Billed headers report the result.
Caching: Set a cache TTL when repeated captures can reuse an unchanged result. Cache hits are not billed.
Batch work: ScreenshotNeo bulk capture accepts up to 100 URLs per call; asynchronous jobs and signed webhooks help keep long runs out of request timeouts.

FAQ

Does Chrome take a screenshot of the whole page?

On Android, Chrome’s Long screenshot can include a selected length. On desktop, the DevTools full-size command is a community-described option whose availability varies by Chrome version.

What is the difference between Long screenshot and Capture more?

Long screenshot is a Chrome share action. Capture more is an Android system control that extends an initial screenshot and is documented for Android 12 and later on most scrollable screens.

A manual Chrome capture uses the session already open in the browser. An automated capture must provide the required cookies, headers, or authorization and comply with the site’s access rules.

Which format should I use?

PNG is useful for crisp text and transparency, JPEG for smaller photographic images, and WebP for a compact modern image. ScreenshotNeo can return PNG, JPEG, WebP, or PDF.

Why does my screenshot look different from the browser?

Viewport width, device scale, fonts, extensions, login state, animations, consent dialogs, and page timing can all change the result. Match those conditions before comparing images.