How to take a full page screenshot in Chrome

Method 1 — Chrome's built-in command (no extension)

Chrome ships with a full page capture inside DevTools. It is free, it is already installed, and almost nobody knows it is there.

1. Open the page you want.
2. Press F12 — or Ctrl+Shift+I on Windows, Cmd+Option+I on a Mac — to open DevTools.
3. Press Ctrl+Shift+P (Cmd+Shift+P on a Mac). A command palette opens.
4. Type screenshot.
5. Choose Capture full size screenshot.

The PNG lands in your Downloads folder. There is no preview, no filename prompt and no editor.

The other entries in that list are worth knowing too: Capture screenshot takes just the viewport, Capture area screenshot lets you drag a box, and Capture node screenshot captures the single element selected in the Elements panel — which is the cleanest way to grab one card or one table out of a busy page.

Where it falls down

• Sticky headers repeat. A navbar with position: fixed is painted into every frame, so it appears as a stripe every screenful down the image.
• Lazy-loaded images come out blank. Anything that loads on scroll may never get the chance, leaving grey placeholder boxes.
• No annotation. You get a raw file and nothing else, so any arrow or highlight means a second app.
• It can cut very tall pages short without telling you the image was truncated.

Good for: a quick archival capture of a simple page. Bad for: anything you are about to send to another person.

Method 2 — Print to PDF

Press Ctrl+P and set the destination to Save as PDF. The result is a full page capture with selectable text, which is genuinely useful for receipts, invoices and anything you may need to search later.

The catch is that print stylesheets are not the page. Many sites strip backgrounds, hide navigation and reflow columns when printing, so the PDF can look nothing like what you were looking at. Tick Background graphics under More settings to get closer, and accept that it will still be an approximation.

Method 3 — One click from the toolbar

An extension exists to remove the three problems above at once: it hides sticky elements after the first frame, pauses at each scroll step so lazy images load, and hands you the result in an editor rather than a folder.

With CaptureFlow the whole thing is:

1. Click the CaptureFlow icon in the toolbar.
2. Choose Full Page.
3. The stitched image opens in the editor, ready to annotate.

From there you can draw arrows, blur the parts that should not be shared, add numbered steps, then download as PNG, JPG or PDF, copy straight to the clipboard, or generate a share link. The documentation covers every capture mode in detail, and the keyboard shortcuts skip the popup entirely.

The limits nobody mentions

Two ceilings apply no matter which method you choose, because they come from the browser rather than the tool.

• Roughly 32,000 pixels of height. That is the maximum size of a browser canvas. A very long article or a chat log will be truncated — a good tool warns you, but none can raise the limit.
• Infinite scroll never ends. A feed that loads more content as you scroll will capture whatever has already loaded and stop there. Scroll to the point you care about first.

Two more practical notes: pages inside an iframe (embedded checkout forms, some dashboards) may capture as blank boxes, and chrome:// pages and the Chrome Web Store cannot be captured by any extension at all — Chrome blocks extension scripts there deliberately. DevTools can still capture those.

Which one to use

If you take one screenshot a month, DevTools is genuinely fine and you should not install anything. If you explain things for a living — support, QA, design review, documentation — the annotation step is where the time actually goes, and that is the part DevTools does not have.

Next: how to blur sensitive information before you send a capture on, or how the Chrome screenshot extensions compare.