How to Capture an Entire Webpage in Chrome (Desktop and Android)

The quickest desktop method is built into Chrome: open DevTools, press Ctrl+Shift+P on Windows/Linux (or Cmd+Shift+P on macOS), type screenshot, then choose Capture full size screenshot. Chrome saves one tall image containing content below the visible viewport. If you need a paginated document instead, use Chrome’s print dialog and choose Save as PDF.

Capture the whole page on desktop Chrome

1. Open the page. Load the exact URL you want to preserve and wait for its visible content to finish rendering.
2. Open DevTools. Press Ctrl+Shift+I on Windows/Linux, or Cmd+Option+I on macOS. You can also open Chrome’s menu and choose the developer-tools entry.
3. Open the Command Menu. Click inside DevTools, then press Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (macOS).
4. Run the full-page command. Type screenshot and select Capture full size screenshot.
5. Retrieve the image. Chrome downloads the result to its configured download folder. If Chrome is set to ask where to save files, choose a destination when prompted.

The result is a single continuous image, not a stack of Letter- or A4-sized pages. Extremely long pages can therefore produce very tall files that need cropping or layout work before magazine or print use.

#	Preview	Product	Price
1		The 138 Best Chrome Extensions	$2.99	Buy on Amazon

What the command captures

DevTools captures the page’s full rendered length, including content outside the current viewport. It is different from taking repeated viewport screenshots and stitching them manually. The page must still be able to render its content; a blocked request, sign-in wall or script-dependent section can leave gaps in the final image.

When to wait before capturing

• Scroll through the page once if images or other sections load only after entering the viewport.
• Wait for animation, cookie dialogs or chat panels to settle, or dismiss them before opening the Command Menu.
• For authenticated pages, confirm that the correct account and permissions are active in the same tab.

Choose the right Chrome output

Capture only a selected region

1. Open DevTools and press Ctrl+Shift+P (or Cmd+Shift+P).
2. Search for screenshot.
3. Choose Capture area screenshot.
4. Drag over the region and release to save it.

Keep DevTools docked to the browser window. The documented area-capture command does not work when DevTools is undocked.

#1 Best Overall

The 138 Best Chrome Extensions

$2.99

Buy on Amazon

Save the page as a PDF instead

Use PDF when your recipient needs pages that can be printed, cited or attached to a document rather than one continuous bitmap.

1. Press Ctrl+P on Windows/Linux or Cmd+P on macOS.
2. In the print dialog, set the destination to Save as PDF.
3. Choose the page range and other available print settings, then save.
4. Open the resulting PDF and check page breaks, missing backgrounds, clipped columns and links before sharing it.

A PDF is a separate output from a full-size screenshot. Chrome’s print engine may apply print CSS, reflow columns or omit screen-only controls, so visual output can differ from the browser tab.

Save the webpage file (not an image)

For an editable or locally inspectable copy, use Chrome’s desktop menu: More > More tools > Save page as, choose a location if prompted, and save. This creates a webpage file and associated resources according to Chrome’s save behavior. It should not be treated as a guaranteed, self-contained archive of dynamic data, video, scripts or authenticated application state.

Take a long screenshot on Android Chrome

1. Open the page in Chrome for Android.
2. Tap More (the three-dot menu), then Share.
3. Choose Long screenshot.
4. Drag the crop handles to include the desired length.
5. Confirm, then save or share the image.

This produces an adjustable extended image from the Android share flow; it is not the same interface as desktop DevTools.

Troubleshooting full-page captures

The screenshot command is missing

Make sure DevTools has focus before pressing the Command Menu shortcut. Search for screenshot rather than scrolling through commands. If the label differs after a Chrome update, look for the command containing “full size” or “full page.”

The result stops before the bottom

• Reload the page and wait for network activity and lazy-loaded images to finish.
• Scroll through the page once to trigger viewport-based loading, then run the command again.
• Close overlays that intercept the page or obscure content.

Images are blank or sections are missing

Lazy loading, blocked third-party resources, consent gates and scripts that require interaction can prevent content from rendering. Capture after completing the required interaction, or use the page’s print view if a document is the real goal.

The file is too tall or too large to use

Open the image in an editor and crop it into logical sections, or switch to Save as PDF for page-shaped output. Reducing browser zoom changes the rendered layout and may make text harder to read, so use it only when you control the final dimensions.

Area capture does nothing

Dock DevTools again, then rerun Capture area screenshot. Undocked DevTools is the documented limitation for this command.

The PDF looks different from the screen

Inspect print preview before saving. Print styles can hide navigation, alter colors or move elements across page breaks. If exact screen appearance matters, use the full-size image instead.

Automating captures without operating Chrome

For one-off work, DevTools is sufficient. For scheduled pages, batches, API-driven workflows or AI agents, ScreenshotNeo provides a website screenshot API and MCP server. It is the first service to try when you need clean captures: it accepts cookie/consent banners before capture, removes more than 60 known consent platforms plus newsletter popups and chat widgets, and bills only clean shots. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed; each response reports the result in X-Page-Verdict and X-Billed headers.

Or skip the browser setup

Make one GET request to the API. The endpoint can return PNG, JPEG, WebP or PDF; the example below saves a WebP file.

ScreenshotNeo API documentation

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)
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}`);

ScreenshotNeo also supports full-page captures with lazy images loaded, CSS-selector element captures, dark mode, 12 device presets plus custom viewports, retina scale, PDF paper sizes/margins/landscape/page ranges, custom CSS and JavaScript, click-before-capture actions, selector hiding, waits for selectors/delays/network idle, ad/tracker/request/resource blocking, custom headers/cookies/user agents and Authorization, timezone and geolocation, transparent backgrounds, image resizing, configurable-TTL caching, signed public-image links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API and an OpenAPI specification. Parameter names used by other screenshot APIs also work, which can simplify migration.

An MCP server exposes take_screenshot, get_page_info and capture_pdf to Claude, Cursor and other MCP clients, so an AI agent can perform captures without a custom browser harness. Every feature is included on every plan: 1,000 shots per month free with no card, 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; yearly billing gives two months free.

Create a free ScreenshotNeo account to use the 1,000 monthly shots without a card.

Practical quality checklist

• Confirm the URL, account and page state before capture.
• Dismiss consent, newsletter and chat overlays when using Chrome manually.
• Trigger lazy-loaded sections and wait for images to render.
• Choose a full-size image for visual fidelity, PDF for paginated sharing, or Save page as for a webpage file.
• Open the saved output and inspect the bottom, interactive sections, fonts and images.
• For repeatable jobs, record the viewport, zoom, timing and authentication conditions so later captures are comparable.

Frequently Asked Questions

Can Chrome capture a full page without opening DevTools?

The documented desktop full-page command is in DevTools’ Command Menu. Without DevTools, use Chrome’s print dialog for a PDF or an Android Long screenshot on supported Android Chrome.

Does a full-page screenshot include content below the fold?

Yes. Capture full size screenshot is designed to include content outside the visible viewport, provided that content successfully renders.

Should I use PNG, JPEG or PDF?

Use an image when preserving the rendered appearance matters; use PDF when readers need paginated pages. ScreenshotNeo can return PNG, JPEG, WebP or PDF for automated jobs.

Why is my saved webpage different when opened offline?

Save page as creates a webpage file, but dynamic scripts, remote resources and authenticated state may not be self-contained.

Quick Recap

Bestseller No. 1

The 138 Best Chrome Extensions

$2.99

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.