How to Capture a Website Screenshot on an Android Phone Using Chrome DevTools

To inspect a website that is actually open in Chrome on an Android phone, enable USB debugging, connect the phone to desktop Chrome, and open its tab from chrome://inspect/#devices. That gives you remote DevTools for the live phone page. Screenshot controls documented for desktop DevTools Device Mode capture an emulated mobile viewport; the documentation does not establish that those commands capture the remotely connected phone. For a picture of the physical screen, use the phone’s own screenshot control.

Choose what you need to capture

Goal	Method	What the result represents
See and debug the page running on your Android phone	Remote debugging through `chrome://inspect/#devices`	The live tab on the connected phone; capture availability depends on the current DevTools interface.
Save the phone’s actual screen	Use Android’s built-in screenshot control	The physical screen. Depending on how it is taken, the image may include browser and device interface elements.
Make a mobile-sized screenshot from desktop Chrome	Device Mode screenshot commands	A simulated mobile viewport rendered by desktop Chrome, not proof of how that exact phone rendered the page.
Capture just a region in desktop DevTools	Command Menu → Capture area screenshot	A selected area of the desktop DevTools page; DevTools must be docked.

Use a real device when the exact phone/browser combination matters. Device Mode is useful for repeatable viewport captures, but simulation does not reproduce every part of a mobile device.

Connect Android Chrome to desktop DevTools

On the phone, open Developer Options and enable USB debugging. If Developer Options are not visible, follow the instructions for your Android version and device from its manufacturer; the steps vary.
On a Windows, Mac, or Linux computer, open Chrome and go to chrome://inspect/#devices.
Enable Discover USB devices.
Connect the phone directly to the computer with a USB data cable. Check that the connector fits both devices and that the cable supports data, not only charging.
If prompted on the phone, authorize USB debugging for that computer.
Open Chrome on the phone and navigate to the page you want to inspect.
Find that tab in the device list on the computer and click Inspect. A DevTools window for the live page opens.

This is remote inspection of the phone’s actual Chrome tab. It is distinct from enabling Device Mode in a normal desktop tab. For device discovery problems, see Chrome’s remote debugging guide.

Capture the page

Capture the actual phone screen

If you need a screenshot of what is physically displayed on the Android device, use Android’s built-in screenshot control. The exact gesture or button combination can vary by device and Android version, so use the instructions for your phone. This can include browser controls, status indicators, or other device interface depending on the capture method. Remote inspection lets you debug the page, but the reviewed Chrome documentation describes its remote-debugging and Device Mode screenshot workflows separately; it does not promise that the Device Mode capture commands act on a remote Android target.

Capture an emulated mobile viewport in desktop Chrome

Open the page in desktop Chrome and open DevTools.
Turn on Device Mode using the device toolbar control.
Choose a device preset or set the viewport dimensions and device scale settings you need.
Open Device Mode’s More options menu and choose Capture screenshot for the visible viewport, or Capture full size screenshot for the whole page, including content outside the viewport.

These commands capture the emulated desktop viewport. For responsive checks, keep the viewport, page state, and zoom consistent between captures. Lazy-loaded content may require scrolling or waiting before it appears, depending on the page.

Capture a selected area with DevTools

Open the Command Menu: Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on Mac.
Type screenshot.
Choose Capture area screenshot, then drag across the region to capture.

Google documents that area capture will not work when DevTools is undocked from its window. This is a desktop DevTools command, not a documented capture command for the remote Android screen. See the DevTools Command Menu documentation.

Or skip the browser setup

If you need a webpage image without connecting a phone, ScreenshotNeo is a website screenshot API and MCP server. It captures a URL from one GET request; the output can be PNG, JPEG, WebP, or PDF. This is a server-side page capture, not a screenshot of your particular Android device.

See the ScreenshotNeo API documentation. Replace the example URL and use your API key:

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,
)
r.raise_for_status()
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 like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers say the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Sign up for 1,000 free screenshots a month, no card required.

Troubleshooting

Problem	Likely cause	What to try
Phone does not appear on `chrome://inspect/#devices`	USB debugging or device discovery is off, the connection is charge-only, or the computer has not been authorized.	Enable USB debugging and Discover USB devices, accept the prompt on the phone, check the cable supports data, and try a direct computer connection instead of a USB hub.
Phone is connected but no tab appears	Chrome is not open on the phone, or there is no page tab to inspect.	Open Chrome and the target page on the phone, then refresh the devices page.
Authorization prompt does not reappear	An earlier USB debugging authorization may be stale or incorrect.	Revoke USB debugging authorizations in Android Developer Options, reconnect, and accept the prompt again.
Device still is not detected	USB mode or the connection path may be interfering.	Try a direct connection rather than a hub. Chrome’s guide also lists changing Android USB mode to PTP as a troubleshooting option.
DevTools looks different from instructions	The Chrome version on the phone affects the remote DevTools instance and available interface.	Check the current menus and update Chrome on the phone if appropriate; do not assume a Device Mode command captures the remote target.
Capture area option fails	DevTools is undocked.	Dock DevTools to the browser window and try the Command Menu action again.
Full-page image omits content	The page may load content lazily or only after interaction or scrolling.	Wait for the page to settle and scroll through the content before capturing; verify the result at the required viewport size.

Performance, reliability, and cost

Remote debugging requires a compatible USB connection and authorization, but it inspects the page on the actual phone. This makes it the appropriate choice when device-specific browser behavior is the subject of the check. Device Mode is quicker for repeatable viewport work because it does not require connecting a phone, but it remains an emulation. A screenshot itself is a static image: it does not preserve page behavior, and dynamic content may differ between captures as the page changes.

The Chrome workflow described here has no per-screenshot service charge; it uses the phone, computer, cable, and Chrome. For automated URL-to-image capture, ScreenshotNeo provides a hosted API with configurable waits, caching, bulk capture, and asynchronous jobs. Cost depends on plan and usage: Free offers 1,000 shots/month, then Starter is $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. All features are on every plan. These service captures do not substitute for validating the actual Android device.

FAQ

Does Chrome DevTools take a screenshot of my connected Android phone?

Remote debugging opens DevTools for the live phone tab. The reviewed documentation treats that workflow separately from Device Mode’s screenshot commands and does not establish that those commands capture the connected phone. Use the phone’s screenshot control for an image of its actual screen, or check the current remote DevTools interface for available capture actions.

Will the screenshot include Chrome’s address bar?

A screenshot from the phone can include browser or device interface depending on how it is taken. Device Mode page captures target the emulated webpage viewport, not the phone’s full physical display.

Can I capture a full page?

Desktop DevTools Device Mode documents a full-size screenshot command. For the remote Android target, the cited guide does not document that command as a real-device full-page capture.

Does a Device Mode screenshot prove the site works on Android?

No. It shows a simulated mobile viewport. Use a real Android device when the result depends on actual device or browser behavior.