How to Screenshot a Website in Google Chrome Without an Extension

To screenshot a website in Chrome without an extension, use Chrome DevTools. Open the page, open DevTools, then open the Command Menu with Ctrl+Shift+P on Windows or Linux, or Cmd+Shift+P on macOS. Search for screenshot and choose Capture full size screenshot to save the whole page, including content below the visible viewport.

Chrome also has built-in commands for a viewport, a selected page element, or a rectangular area. This guide explains which one to use, how to prepare the page, and what to check if a capture command is missing or the image does not look right.

1. Capture a full webpage in Chrome

Open the webpage you want to capture and wait for the content you need to appear.
Open DevTools. On Windows or Linux, press Ctrl+Shift+I. On macOS, press Cmd+Option+I. Or use Chrome’s menu: More Tools → Developer Tools. You can also right-click a page element and select Inspect.
Open the Command Menu: Ctrl+Shift+P on Windows or Linux; Cmd+Shift+P on macOS.
Type screenshot in the menu’s search field.
Select Capture full size screenshot. Chrome generates and downloads an image of the full page.

This is the best built-in choice for a long article or landing page when you need the content below the fold in one capture. Chrome documents full-size capture in Device Mode’s More options menu as well. If you prefer that route, open Device Mode, select More options → Capture a full size screenshot.

A full-size capture includes content below the browser’s visible viewport.

Before capturing, put the page in the state you want to preserve. Scroll if you need to trigger content, close or open menus deliberately, and wait for visible content to settle. A screenshot records the page’s current rendered state; the DevTools documentation does not guarantee that every site’s lazy-loaded or changing content will render identically in a full-page capture.

2. Choose the right capture type

What you need	Chrome command	What it captures
The entire page	Capture full size screenshot	Content beyond the current viewport as one long image.
Only what is on screen	Capture screenshot	The current visible viewport.
One DOM element	Capture node screenshot	The selected element, such as a card, chart, or image.
A freeform rectangle	Capture area screenshot	The portion of the page inside the rectangle you drag.

For viewport and full-size captures, Chrome’s documented route is Device Mode → More options. For a node capture, select or inspect the element and use Capture node screenshot. For an area, search the Command Menu for Capture area screenshot, then drag over the desired region. Area capture requires DevTools to be docked; it does not work while DevTools is undocked.

3. Capture just the visible viewport

Open DevTools and enable Device Mode if it is not already active. The Device Mode toolbar is the phone-and-tablet icon.
Set the viewport to the size you want, or use the current visible dimensions.
Open More options in the Device Mode toolbar.
Choose Capture screenshot.

A viewport screenshot is useful for documenting exactly what a user sees at a particular scroll position. It does not include the rest of a long page. If the target is below the fold, scroll to it before capturing; if you need the whole document, use the full-size command instead.

4. Save one element as an image

Use a node screenshot when you need a specific component rather than the whole page. Chrome’s DOM guide describes using the Elements panel to inspect and select a node; its context menu includes Capture node screenshot. You can also search the Command Menu for that command.

Right-click the element in the page and choose Inspect, or open the Elements panel and select the node in the DOM tree.
Right-click the selected node in the Elements panel.
Choose Capture node screenshot.

This captures the selected node, not necessarily a visually related group of neighboring elements. If the result is incomplete, inspect whether the content you want belongs to a parent or child node and select the appropriate element. Chrome’s documentation says the image is saved to Downloads on Windows and macOS.

5. Capture a rectangular area

For a crop that does not match an element boundary, use Capture area screenshot from the Command Menu. Type screenshot, choose the area command, then drag across the page to select the rectangle. The Command Menu is Chrome’s built-in command finder; it also provides the other screenshot commands.

Keep DevTools docked while using area capture. If the command fails or is unavailable, check the docking state first. A viewport capture can be a practical fallback: resize or position the page content as needed, then capture the visible viewport.

6. Useful keyboard shortcuts

Action	Windows/Linux	macOS
Open DevTools	`Ctrl`+`Shift`+`I`	`Cmd`+`Option`+`I`
Open the Elements inspector	`Ctrl`+`Shift`+`C`	`Cmd`+`Option`+`C`
Open the Command Menu	`Ctrl`+`Shift`+`P`	`Cmd`+`Shift`+`P`

Shortcuts can vary with keyboard layout, browser configuration, or system-level shortcuts. If one does not open the expected panel, use Chrome’s More Tools → Developer Tools menu and then open the Command Menu from DevTools.

7. Make the capture more reliable

Wait for the page to settle. Let images, fonts, and visible page sections finish loading before capture.
Check lazy content. Some pages load images or sections as you scroll. Scroll through the page to bring those sections into view before taking a full-page image.
Set the state first. Expand accordions, dismiss dialogs, or open menus according to what the image should show.
Choose the capture scope deliberately. Full page, viewport, node, and area commands produce different results; a viewport capture will not include below-the-fold content.
Review the downloaded image. Confirm that the bottom of a long page is present and that overlays or sticky elements did not obscure important content.

These steps reduce surprises, but websites can update while a capture is being made. Pages with animations, personalized content, delayed requests, or infinite scrolling may not have one stable final state. For a repeatable record, capture at a consistent point in the page’s loading and interaction sequence.

8. Troubleshooting Chrome screenshots

Problem	Likely cause	What to try
“Capture area screenshot” is missing or does not work	DevTools is undocked.	Dock DevTools to the browser window and run the area command again.
The image only shows the visible part of the page	You used Capture screenshot, which is for the viewport.	Use Capture full size screenshot in Device Mode or from the Command Menu.
The full-page image is missing images or sections	Content may load lazily or after a delay.	Scroll through the page, wait for content to appear, then capture again.
The wrong element was captured	A different DOM node was selected than the visible component you intended.	Inspect the page and select the correct node or a containing element before using Capture node screenshot.
A shortcut does nothing	The platform shortcut differs, another app intercepted it, or focus is outside the browser.	Click the page, use the platform-specific shortcut, or open DevTools through Chrome’s menu.
The menu command is hard to find	The command list is long or the search term is too specific.	Open the Command Menu and search for `screenshot`.

Chrome’s menus can move between releases, and the documentation does not provide a compatibility matrix for every browser version, operating system, or managed-browser policy. If a command is unavailable, check that DevTools is open, search the Command Menu for screenshot, and use Device Mode for viewport or full-size capture.

9. Browser capture, automation, and cost

DevTools is convenient for an occasional manual screenshot and needs no extension. It also depends on a person opening the page and selecting the capture command. If you need captures from scripts, a browser-based workflow or an API can fit better. For automated use, decide how to handle page state, retries, output storage, and sites that show consent or bot-check screens.

Automated capture can clear common overlays before saving the page image.

Local browser capture has no per-image API charge, but it takes setup and time when repeated across many URLs. A screenshot service adds a request and service cost, so check the provider’s plan, output needs, and failure behavior before building a recurring job. For long captures, account for image dimensions and downstream storage or transfer needs. The Chrome documentation cited here establishes the capture workflows, not performance guarantees or image-size limits.

Or skip the browser setup

If you need screenshots from code or across many URLs, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. The API accepts common screenshot parameter names, which can make switching easier. 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,
)
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 accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each of these steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing. The response identifies the page verdict and billing status in X-Page-Verdict and X-Billed headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.

The free plan includes 1,000 shots per month with no card. Paid plans start at $5 for 3,000 shots; yearly billing gives two months free. Every feature is available on every plan. Sign up for 1,000 free screenshots a month, with no card.

Frequently asked questions

Can I take a full-page screenshot in Chrome without installing anything?

Yes. Chrome DevTools includes a full-size screenshot command. Open the Command Menu, search for screenshot, and select Capture full size screenshot.

Does “Capture screenshot” include the whole page?

No. It captures the visible viewport. Use Capture full size screenshot for content beyond the viewport.

Can I save a single image or chart from a webpage?

Yes. Inspect the relevant DOM element and use Capture node screenshot.

Where does Chrome save the screenshot?

Chrome downloads the capture. For node screenshots, its documentation specifically notes the Downloads location on Windows and macOS.

Can I capture a page without opening DevTools?

The workflows described here use DevTools. For an API-driven screenshot, use a screenshot service such as ScreenshotNeo, or automate a browser separately.