How to Take a Full-Page Screenshot of a Website in Chrome for Documentation

To capture a full-page screenshot in desktop Chrome, open the page, open DevTools, press Ctrl+Shift+P on Windows or Linux (or Cmd+Shift+P on Mac), type screenshot, and select Capture full size screenshot. Chrome captures page content beyond the visible viewport. Chrome DevTools documents the Command Menu, and its Device Mode documentation describes the full-size capture option.

This built-in method is usually enough for a one-off documentation image. Choose a different capture command if you need only the visible screen or a selected region; use print-to-PDF when you need a paginated document.

Capture the full page in Chrome

Open the website in desktop Chrome and navigate to the page you want to document. Put it in the state you want to record, such as the correct tab, expanded content, or selected options.
Open DevTools. For example, right-click the page and choose Inspect.
Open the Command Menu with Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on Mac.
Type screenshot to filter the available commands.
Choose Capture full size screenshot.

Chrome’s documentation establishes that the full-size command captures the page, including content beyond the viewport. It does not promise how every site’s dynamic content will appear. Check the resulting image before adding it to documentation, especially on pages with lazy-loaded images, animations, sticky navigation, or content that changes while loading.

Choose the right capture type

Need	Chrome option	Result
Record the entire page as one image	Capture full size screenshot in the Command Menu	Captures content beyond the visible viewport.
Record only what is currently visible	Capture screenshot in Device Mode’s More options menu	Captures the viewport.
Record a particular section	Capture area screenshot in the Command Menu	Drag to select the region to capture.
Save a document for printing or filing	Chrome’s print dialog, then Save as PDF	A paginated PDF document rather than a screenshot image.

The Command Menu shortcut and area capture are described in the Command Menu documentation. The distinction between viewport and full-size capture is covered in Device Mode. For PDF, follow Chrome Help’s print instructions.

Make the screenshot useful as documentation

Set the page state first. Dismiss dialogs you do not want documented, open the relevant menus, and enter representative values in forms if the documentation requires them.
Wait for important content. If images or sections load as you scroll, check that they are present in the captured result. Chrome’s documented command does not settle the behavior of every lazy-loading implementation.
Consider sticky elements. A fixed header or floating widget may affect the captured appearance. Review the image for repeated, overlapping, or obstructive elements.
Choose scope deliberately. A full-page image can become tall and difficult to read. A viewport capture or area capture may be clearer for a specific instruction.
Use PDF for a document workflow. Print-to-PDF is intended for a paginated record. It is a different output from capturing the page as an image.
Review sensitive content. Check for account details, personal information, or other material that should not appear in shared documentation.

Or skip the browser setup

If you need repeatable screenshots from code, ScreenshotNeo is a website screenshot API and MCP server. One GET request can return an image or PDF, and the API accepts parameters used by other screenshot APIs to make switching straightforward. See the ScreenshotNeo API documentation for request options.

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 import('node:fs/promises').then(({ writeFile }) => writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));

Replace YOUR_API_KEY with your key and change the target URL. ScreenshotNeo can accept cookie banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, with response headers identifying the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots a month without a card; paid plans start at $5 for 3,000 screenshots.

Troubleshooting

Problem	Likely cause	What to do
You cannot find the screenshot command.	The Command Menu is not open, or the search text does not match.	Open DevTools, press the platform shortcut, then type `screenshot`. Select the full-size command from the results.
The image shows only the visible screen.	You selected the standard screenshot command rather than the full-size command.	Repeat the process and choose Capture full size screenshot. The standard Device Mode capture is for the viewport.
Part of the page appears blank or incomplete.	The site may load content dynamically or only when it becomes visible.	Wait for the page to settle, scroll through important sections if needed to trigger content, and capture again. Inspect the result; the documented Chrome command does not guarantee behavior for every site.
A menu, dialog, or consent banner is in the image.	The page was captured in that state.	Set the page to the state needed for the documentation before capture, then take a new screenshot.
The full-page image is awkward to use in a guide.	One tall image may be hard to read at the size used in the documentation.	Use an area or viewport capture for the relevant step, or use print-to-PDF if the deliverable should be paginated.

Performance, reliability, and output notes

A one-off capture uses Chrome’s built-in DevTools workflow and does not require an extension for the basic task. For reliability, make sure the page has reached the state you intend to document and inspect the output for dynamic or lazy-loaded content. Chrome’s official guidance describes the capture choices but does not specify a universal rendering result for every site, saved image format, or save location, so check the browser’s actual result rather than relying on those details in a procedure.

For recurring captures across many URLs, browser setup and manual review can take time. ScreenshotNeo offers bulk capture for up to 100 URLs per call, caching with a chosen TTL, asynchronous jobs with signed webhooks, and a usage API. Its pricing is Free: 1,000 shots/month; Starter: $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, and every feature is on every plan. Use the API’s billing headers to distinguish billable captures from failed loads and cache hits.

Frequently asked questions

Do I need a Chrome extension for a full-page screenshot?

No. Chrome DevTools includes a full-size screenshot command for this basic workflow.

Can I capture just part of a page?

Yes. Use Capture area screenshot from the Command Menu and drag to select the region.

Should I use a screenshot or a PDF for documentation?

Use a screenshot when the visual appearance of the page is the record you need. Use Chrome’s print-to-PDF workflow when you need a paginated document.

Can I save a full-page screenshot directly to the clipboard?

The official documentation cited here does not establish a clipboard workflow for the full-size command. Check the current Chrome interface for available actions rather than assuming the downloaded capture can be copied directly.