How to Take a Full-Page Screenshot in Chrome on Android
Capture an entire webpage in Chrome on Android with Capture more, Long Screenshot, or a reliable API fallback.
On Android 12 or newer, open the page in Chrome, press Power + Volume Down, tap Capture more, adjust the crop handles, then save or share the image. Google says this works on most screens that allow scrolling. The labels full-page screenshot, long screenshot, and scrolling screenshot describe the same general result.
1. Use Android’s built-in Capture more tool
- Open the webpage in Chrome.
- Wait for the content, images, and menus you need to finish loading.
- Press Power and Volume Down at the same time.
- When the screenshot preview appears, tap Capture more.
- Drag the top and bottom handles until the selection includes the required part of the page.
- Tap Save, or use Share to send the image to another app.
The capture editor normally lets you choose a longer region than the initially visible screen. Review the bottom edge before saving so the final section is not cut off.
What Capture more can and cannot capture
- It is designed for scrollable content and works on most supported screens.
- It captures the rendered page as one tall image rather than producing separate screenshots.
- It may not appear for a non-scrollable screen, an app surface that blocks scrolling screenshots, or an unsupported device or Android version.
- Very long pages can create large image files. If sharing fails, crop to the needed section or use a lower-resolution workflow.
2. Try Chrome’s Long Screenshot command
Some Chrome-on-Android builds expose a separate command:
- Open the page in Chrome.
- Tap the three-dot menu.
- Choose Share.
- Select Long Screenshot, if it is available.
- Set the top and bottom of the page in the editor, then save or share.
This menu is dependent on the Chrome version, device, rollout, and any required experimental setting. A guide published on March 13, 2025 describes enabling a Chrome flag before using Share → Long Screenshot; the flag and menu may not exist in your build. Do not rely on this route when documenting a process for a mixed fleet of devices.
3. Troubleshooting missing or incomplete screenshots
| Problem | Likely cause | Fix |
|---|---|---|
| Capture more is missing | Android version, device support, or the current screen is unsupported. | Check that the device runs Android 12 or later, confirm the page can scroll, and try the Chrome Share menu. |
| Long Screenshot is missing | The Chrome build or rollout does not expose the command, or an experimental flag is unavailable. | Use the system screenshot shortcut and look for Capture more. Update Chrome only through your normal device store and avoid depending on an unavailable flag. |
| The image stops before the bottom | The crop handle was not extended far enough, or the page stopped scrolling. | Open the editor again, drag the bottom handle farther, and wait for lazy-loaded content before taking the screenshot. |
| Images or text are blank | Content was still loading, requires interaction, or is rendered after a delay. | Reload, wait for the page to settle, dismiss overlays, and capture again. For a page that needs clicks or authentication, use an automated browser or screenshot API. |
| The screenshot is too large to share | A full-page image has high pixel dimensions or compression is insufficient. | Crop the selection, export as JPEG when acceptable, or resize the image before sharing. |
| A cookie dialog, chat bubble, or newsletter popup covers the page | The overlay is part of the rendered page. | Dismiss it before capture. If you need repeatable cleanup across many URLs, use the API workflow below. |
When a third-party Android app is the fallback
If both built-in controls are absent or fail on a particular page, a dedicated app such as Web2Pics advertises full-page and scrolling website screenshots. Check its current Google Play availability, permissions, and privacy terms before installing. A desktop extension such as GoFullPage is a Chrome Web Store tool for desktop browsers; it is not the Android Chrome method.
4. Choosing the right method
| Method | Availability | Scope | Editing control | Privacy and permissions |
|---|---|---|---|---|
| Android Capture more | Android 12+ on supported, scrollable screens | System-level screen content | Crop handles before saving | Built into the device |
| Chrome Share → Long Screenshot | Chrome-build and rollout dependent | Webpage-oriented | Top and bottom controls | Built into Chrome when present |
| Third-party app | Depends on the app and device | Usually webpages and scrolling views | Varies by app | Review permissions and privacy terms |
| ScreenshotNeo API | Any environment that can make HTTPS requests | Automated webpage capture | CSS selectors, waits, devices, output formats, and more | Configure headers, cookies, user agent, timezone, and geolocation |
Use the built-in tool for an occasional screenshot on your own phone. Use an automated workflow when you need repeatable captures, a consistent viewport, scheduled jobs, many URLs, or a clean result without manual overlay dismissal.
5. Or skip the browser setup
ScreenshotNeo returns a PNG, JPEG, WebP, or PDF from one GET request. It supports full-page capture with lazy images loaded, device presets or custom viewports, retina scale, dark mode, custom CSS and JavaScript, selector-based element capture, clicks, waits, request blocking, cookies, headers, authorization, timezone, geolocation, caching, signed links, asynchronous jobs, webhooks, bulk capture, and a usage API. See the ScreenshotNeo API documentation for the complete option list.
The service accepts and removes cookie or consent banners, newsletter popups, and chat widgets from more than 60 known platforms before capture; each cleanup step can be disabled. Bot checks and CAPTCHAs, 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.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" \
-d access_key=YOUR_API_KEY \
--data-urlencode url=https://stripe.com \
-o shot.webpPython
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());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));ScreenshotNeo also provides an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 shots each month with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.
6. Reliability, performance, and cost considerations
- Wait for content: Android captures what is currently rendered. Let fonts, images, and lazy sections load before taking the screenshot.
- Keep pages manageable: A very tall image consumes more storage and memory. Capture only the required range when possible.
- Repeatability: Manual screenshots depend on device size, browser build, page state, and timing. An API can fix the viewport, device scale, waits, headers, and cookies.
- Privacy: Built-in tools avoid adding another app. For third-party apps or APIs, review the permissions and decide whether private URLs, cookies, or authorization headers may be used.
- API cost: ScreenshotNeo bills only clean shots. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and every response reports billing and page verdict headers.
7. FAQ
Does full-page screenshot work on every Android phone?
No. Google documents Capture more for Android 12 and later on most scrollable screens. Device makers and individual apps can still omit or restrict it.
Is a long screenshot the same as a full-page screenshot?
Usually. “Long,” “scrolling,” and “full-page” are overlapping terms for one image that extends beyond the visible viewport.
Why can I scroll a page but not capture it?
Scrolling and screenshot support are separate capabilities. The screen or app may block the system capture tool, or the device may not implement the required feature.
Can I capture a page that requires login?
The phone method captures your current session. For repeatable authenticated captures, an automated browser or ScreenshotNeo can send configured cookies, headers, user agents, or authorization values.
What should I do if the page changes while I capture it?
Wait for dynamic content to settle, close overlays, and retry. For consistent archives, use fixed waits or selector conditions in an automated capture workflow.
