How to Capture a Scrolling Screenshot in Google Chrome
Capture an entire webpage in Chrome on desktop or Android, troubleshoot common problems, and automate full-page screenshots with an API.
To capture a scrolling screenshot in Chrome: on Android, open the page, choose More > Share > Long screenshot, adjust the crop handles, then confirm and save or share it. On desktop, open DevTools, open its Run/Command menu, search for screenshot, and choose Capture full size screenshot. The desktop workflow is reported in Chrome Community guidance and may vary by Chrome version.
1. Capture a full-page screenshot in Chrome on desktop
This method captures the page beyond the visible browser window and downloads a PNG.
- Open the webpage in Google Chrome.
- Open DevTools with F12, Ctrl+Shift+I on Windows/Linux, or Cmd+Option+I on macOS.
- Open the DevTools command menu. Depending on your version, use Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS, or open the DevTools menu and choose its command/run option.
- Type
screenshot. - Choose Capture full size screenshot.
- Wait for Chrome to download the PNG, then open it from your Downloads folder.
The exact menu labels and keyboard shortcuts can change. The desktop steps and PNG download behavior are documented here as a community-reported built-in workflow, rather than as a guarantee from the official desktop DevTools documentation. See the Chrome Community discussion.
Capture only part of a long page
The full-size command captures the document’s entire rendered height. If you need a smaller range, scroll to the required region and use a normal screenshot tool, or temporarily hide sections with DevTools before capturing. Chrome’s built-in desktop command does not provide the Android-style crop-handle workflow.
2. Capture a scrolling screenshot in Chrome on Android
Chrome’s Android help documents a Long screenshot option in the Share menu.
- Open the webpage in Chrome for Android.
- Tap More (the three-dot menu).
- Tap Share.
- Choose Long screenshot.
- Drag the crop handles to select how far down the page the image should extend.
- Tap Confirm.
- Share the image or save it to your device.
These steps come from Google Chrome Help. The option can depend on your Android and Chrome versions. If Long screenshot is missing, update Chrome, check that you are using Chrome rather than an embedded browser, and use your phone’s system screenshot tool as a fallback.
3. Desktop versus Android: which method should you use?
| Need | Best option | What it produces |
|---|---|---|
| Entire webpage on a computer | Desktop DevTools command | PNG download of the full rendered page |
| A selected length on a phone | Android Long screenshot | Image cropped with draggable handles |
| Repeatable captures for many URLs | Screenshot API | Automated image or PDF files |
| One element instead of the whole page | Automation or an API with CSS selector support | Screenshot of the selected element |
A scrolling screenshot is different from a viewport screenshot: it must render content below the initial window and stitch or capture the page at its full height. Long pages with lazy-loaded images, sticky headers, animations, consent dialogs, or infinite scrolling can therefore need extra handling.
4. Make the capture reliable
- Wait for content: allow client-side rendering and images to finish before invoking the command.
- Close overlays: cookie banners, newsletters, chat bubbles, and login prompts can cover the page.
- Check lazy loading: scroll through the page first if images appear only after entering the viewport.
- Disable animation: pause videos and animated sections so different captures do not vary.
- Use a stable viewport: browser width, zoom, device pixel ratio, and responsive breakpoints change the output.
- Check very tall pages: extremely long documents can create large PNG files or exceed browser memory.
5. Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| “Capture full size screenshot” is not listed | DevTools is not focused, or the command menu wording changed | Click inside DevTools, reopen the command menu, search for “screenshot,” and check your Chrome version. |
| The image stops at the viewport | You selected a normal viewport screenshot | Run the command again and choose “Capture full size screenshot.” |
| Images are blank or missing | Lazy loading has not triggered, or resources failed | Scroll through the page first, wait for images, reload, and check the Network panel for failed requests. |
| Sticky navigation appears repeatedly | The fixed element is rendered during each captured section | Temporarily hide the sticky selector in DevTools, then capture again. |
| A cookie banner covers the page | The consent dialog has not been dismissed | Accept or reject the banner before capture, or hide its element in DevTools. |
| The Android Long screenshot option is missing | Unsupported Chrome/Android version or an embedded browser | Update Chrome, open the URL in the standalone Chrome app, or use a system screenshot fallback. |
| The download is very large | PNG preserves full resolution and long page height | Crop the result, convert it to WebP or JPEG, or capture only the required element. |
6. Automate scrolling screenshots with ScreenshotNeo
For scheduled captures, many URLs, or server-side workflows, ScreenshotNeo provides a website screenshot API. Its full-page mode loads lazy images, and it can also capture one element by CSS selector, set a viewport or device preset, use retina scale, apply custom CSS or JavaScript, click an element, wait for a selector, delay, or network idle, and return PNG, JPEG, WebP, or PDF.
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)
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}`);See the ScreenshotNeo documentation for request parameters, response headers, and the OpenAPI specification. It supports custom headers, cookies, user agents, Authorization, timezone, geolocation, transparent backgrounds, resizing, caching with a chosen TTL, signed links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, and a usage API.
Or skip the browser setup
ScreenshotNeo accepts consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before the shot; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and every response identifies the result with X-Page-Verdict and X-Billed headers. Its MCP server lets Claude, Cursor, and other MCP clients call take_screenshot, get_page_info, and capture_pdf. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpCreate a free ScreenshotNeo account to get 1,000 screenshots per month without a card.
7. Performance, reliability, and cost notes
- Browser capture: free after Chrome is installed, but it uses your computer’s memory and CPU. Very tall pages, large images, and scripts increase capture time and file size.
- Repeatability: use the same viewport, zoom, device scale, login state, and page wait conditions for comparable results.
- API capture: caching with a selected TTL can reduce repeated work. Async jobs and signed webhooks help when a page takes longer to render.
- Billing: ScreenshotNeo bills only clean shots. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing; inspect
X-Page-VerdictandX-Billedin responses. - Output choice: PNG is lossless but larger. WebP or JPEG is usually smaller for previews, while PDF is suited to printable documents.
Frequently asked questions
Can Chrome copy a full-page screenshot directly to the clipboard?
The cited desktop community discussion describes a PNG download. It does not establish a built-in clipboard destination.
Does a scrolling screenshot include content loaded after scrolling?
Only if the page loads that content during capture. For lazy or infinite content, trigger loading first or use an automation/API wait and scrolling strategy.
Can I capture a single element instead of the whole page?
Chrome’s full-size command targets the document. ScreenshotNeo supports selecting one element by CSS selector.
What if the page requires authentication?
For a manual capture, sign in in Chrome first. For automated captures, use a tool that supports cookies or authorization headers and handle credentials securely.
For additional Chrome discussion and the original reader question, see the Google Search Community thread.
