How to Screenshot a Full-Page Website in Chrome DevTools on Android
Capture the whole page open in Chrome on Android using remote DevTools, or use Android’s built-in scrolling screenshot when you only need a long image.
To capture a full-page screenshot of a website open in Chrome on an Android phone, connect the phone to a development computer, inspect its Chrome tab remotely, then choose Device Mode > More options > Capture a full size screenshot. DevTools runs on the computer while the page remains open on the Android phone. The nearby Capture screenshot command captures only the visible viewport.
If you only need a scrolling screenshot and do not need DevTools, Android has a built-in Capture more option on supported devices.
Capture the Android Chrome tab with DevTools
- Enable remote debugging on the phone. In Android settings, enable Developer options and USB debugging. The exact settings path varies by device. Open the page you want to capture in Chrome.
- Connect the phone to your computer. Use a USB cable that supports data, unlock the phone, and accept the debugging prompt if it appears. Chrome also documents connecting over Wi-Fi using ADB.
- Open the device inspector. On the computer, open
chrome://inspect/#devices. Find the phone and its open Chrome tab, then click Inspect beside the page. Chrome uses the version of Chrome installed on the phone to determine which DevTools version opens, so menus may differ on older versions. See Chrome’s remote debugging instructions. - Open Device Mode. In the remote DevTools window, turn on the Device Toolbar if it is not already active. Confirm the simulated viewport is phone-sized if that is the layout you want to capture. Device Mode simulates dimensions, but not every aspect of physical mobile hardware; check the real phone when device-specific behavior matters. See Chrome’s Device Mode guide.
- Capture the full page. Open Device Mode’s More options menu and choose Capture a full size screenshot. Save or inspect the resulting image.
The full-size command includes content outside the current viewport. For a screenshot of only what is currently visible, choose Capture screenshot instead. Chrome documents both options in its Device Mode guide.
Make sure the page is ready first
A screenshot captures the page’s current state. Some pages load images or other content only after you scroll, and dynamic pages may continue changing while you capture. If content is missing, scroll through the live page to trigger loading, wait for the content to appear, then capture again. Check the saved image for missing sections, overlays, or a page that changed during capture.
Use Android’s scrolling screenshot instead
For a quick long screenshot that does not require remote debugging, take a screenshot with the phone’s controls and tap Capture more, then adjust the crop guides. Google says this works on Android 12 and up on most screens that allow scrolling; support and labels can vary by device. This is a phone-native scrolling screenshot, separate from DevTools’ full-size capture. See Android Help’s screenshot instructions.
Which method should you choose?
| Need | Use | What to expect |
|---|---|---|
| Capture the actual page open in Android Chrome for development or QA | Remote DevTools | DevTools runs on a computer; connect the phone and select Capture a full size screenshot. |
| Save a long page image directly on a supported phone | Android Capture more | Available on Android 12+ on most screens that allow scrolling; device support varies. |
| Capture a website from a script, service, or repeatable workflow | A screenshot API such as ScreenshotNeo | Send a URL request instead of connecting a phone and operating DevTools. |
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. For a URL-based capture, make one GET request:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for authentication and request options. ScreenshotNeo accepts cookie and 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 and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
Create a free ScreenshotNeo account for 1,000 screenshots a month with no card.
Troubleshooting
| Problem | Likely cause | What to do |
|---|---|---|
The phone does not appear in chrome://inspect/#devices |
USB debugging is off, the phone is locked, the cable does not carry data, or the debugging prompt has not been accepted. | Unlock the phone, check Developer options and USB debugging, accept the prompt, and try a data-capable cable. Chrome advises confirming the cable by checking whether the computer can access files on the phone. You can also follow Chrome’s documented Wi-Fi ADB setup. |
| The page is not listed under the phone | The target page is not open in Chrome on the phone, or Chrome has not exposed the tab yet. | Open the page in the phone’s Chrome app and refresh chrome://inspect/#devices. |
| There is no full-size capture option | Device Mode is not active, or the DevTools interface differs by Chrome version. | Turn on the Device Toolbar and open its More options menu. Confirm you are in the remote DevTools window inspecting the phone tab. |
| The image contains only the visible screen | You chose Capture screenshot. | Repeat the capture using Capture a full size screenshot in Device Mode’s More options menu. |
| Images or sections are missing | The page may load content as it is scrolled or may still be updating. | Scroll the live page to trigger content loading, wait for it to settle, and capture again. Verify the result because dynamic-page behavior can vary. |
| Android does not show Capture more | The device or screen may not support scrolling screenshots. | Android Help limits the feature to Android 12 and up on most scrollable screens. Use remote DevTools if you need a full-page capture and have a computer available. |
Performance, reliability, and cost
Remote capture requires a working connection between the phone and computer and an open page. It is useful when the page’s actual Android Chrome state is what you need to inspect. Device Mode’s viewport is a simulation, so it does not guarantee reproduction of every hardware-specific behavior. For a complete-looking image, allow the page to load and check lazy content before capturing.
The documented DevTools workflow uses Chrome’s built-in capture command; the cited Chrome and Android guides do not specify a fee for it. The native scrolling screenshot also uses Android’s screenshot flow. ScreenshotNeo is an alternative for URL-based captures and automation: its plans are free for 1,000 screenshots per month, then $5 for 3,000 on Starter, $15 for 15,000 on Growth, $39 for 60,000 on Pro, $99 for 250,000 on Scale, and $249 for 1,000,000 on Business. Yearly billing gives two months free, and every feature is on every plan.
FAQ
Can I use this DevTools workflow entirely on my Android phone?
No. Chrome’s documented remote-debugging workflow opens DevTools on a development computer to inspect Chrome running on the phone.
Does full-size capture include content below the fold?
Yes. That is the purpose of Capture a full size screenshot; the separate Capture screenshot command captures the current viewport.
Do I need a USB cable?
No. USB is the wired route, and Chrome also documents a Wi-Fi ADB connection method.
Is Android’s Capture more the same as DevTools full-size capture?
No. Capture more is Android’s scrolling screenshot flow on supported phones and screens. DevTools captures the remotely inspected browser page from Device Mode.
