Ideas, case studies, and tips for improving the quality of customer service.

How to Take a Full-Page Screenshot in Chrome (4 Ways)

Chrome has no full-page screenshot button. The keyboard shortcuts in Windows and macOS only capture what fits on your screen, so a long page, a checkout flow or a support article gets cut off at the fold. You have four reliable ways around that: a hidden DevTools command, DevTools device mode, a dedicated full-page extension, or a bug-reporting extension that captures the page and lets you mark it up before you share it.

Steps and feature lists were checked against the Chrome for Developers documentation, Firefox’s help center and each extension’s own site on 13 October 2026. Menus move between Chrome versions, so labels on your screen may differ slightly.

Which method should you use?

Method Install needed Full page Annotate or blur Best for
DevTools Command Menu No Yes No A quick one-off capture
DevTools device mode No Yes No Capturing the mobile layout of a page
GoFullPage Extension Yes Premium only Frequent full-page captures, PDF export
Screendesk Extension Yes Yes, free Bug reports and support tickets

Method 1: the DevTools Command Menu (no extension)

Every copy of Chrome includes a full-page capture command. It’s tucked inside the developer tools, but you don’t need to know anything about code to use it.

  1. Open the page you want to capture and scroll back to the top.
  2. Open DevTools: press F12, or Ctrl+Shift+I on Windows and Cmd+Option+I on Mac.
  3. Open the Command Menu: Ctrl+Shift+P on Windows, Cmd+Shift+P on Mac.
  4. Type screenshot.
  5. Choose Capture full size screenshot. Chrome saves a PNG to your Downloads folder.

The same menu offers Capture area screenshot (drag to select a region), Capture screenshot (the visible viewport) and Capture node screenshot (the element selected in the Elements panel). Node screenshots are handy for grabbing one card, table or form without cropping.

Limits: there’s no editor. If you need to point at something or hide an email address, you’ll need a separate image editor. Pages that load content as you scroll (infinite feeds, lazy-loaded images) can come out with blank sections, so scroll to the bottom once before capturing.

Pick a capture method: DevTools command — full page yes, mark up no; Device mode — full page yes, mark up no; GoFullPage — full page yes, mark up partial; Screendesk — full page yes, mark up yes
Full-page capture options in Chrome and whether each lets you mark up the image. Premium-only annotation in GoFullPage is shown as partial.

Method 2: DevTools device mode (capture the mobile layout)

When a customer reports that something looks wrong on their phone, capture the page at a phone’s width instead of your desktop’s.

  1. Open DevTools, then select the Toggle device toolbar icon (a phone and tablet), or press Ctrl+Shift+M (Cmd+Shift+M on Mac).
  2. Pick a device from the dimensions list at the top of the viewport.
  3. Open the device toolbar’s More options menu (three dots) and choose Capture full size screenshot, or Capture screenshot for just the visible part.
  4. To include a device frame, choose Show device frame first, then capture.

Device mode simulates the viewport size and touch input. It doesn’t reproduce a real phone’s browser, so a bug that only happens in Safari on iOS still needs a capture from the device itself.

Method 3: a dedicated full-page extension (GoFullPage)

If you capture long pages every day, an extension saves the DevTools detour. GoFullPage is the best-known option: click its icon and it scrolls the page, stitches the captures together and opens the result in a new tab.

  • Free version: unlimited screenshots, scroll capture, and downloads as PNG, JPG or PDF. GoFullPage says no extra permissions are required to install it.
  • Premium (US$1 a month, with a one-week trial): cropping, URL and timestamp stamps, smart PDF page splitting, and annotations such as blur, text and highlight.
  • Browsers: Chrome, Edge and Firefox.

GoFullPage is a capture tool. The output is an image or PDF you then attach somewhere yourself, without the browser or page details a developer would need to debug a problem.

Method 4: capture, mark up and share with Screendesk

Most screenshots in a support team end up in a ticket or a bug report. The Screendesk Chrome extension is built for that job:

  1. Install the extension and select its icon in the Chrome toolbar.
  2. Choose Capture Screenshot, then pick an area, the visible part of the page, or the full page.
  3. Mark up the capture: draw with the pen, add rectangles, arrows and text, and blur anything private, like a card number or a customer’s email.
  4. Share the link or attach it to the open Zendesk or Intercom ticket. Engineers see the browser, operating system, screen size and page URL alongside the image.

The free plan includes 10 recordings and bug reports a month. When a screenshot isn’t enough to show what happened, the same extension records the tab or saves an instant replay of the last two minutes, with console logs and network requests attached. You can try the drawing and blur tools on a sample page on the Chrome extension page.

What about Firefox and Edge?

Firefox has full-page capture built in. Right-click an empty part of the page, choose Take Screenshot (or press Ctrl+Shift+S, Cmd+Shift+S on Mac), then select Save full page. You can also drag to select a region, or click a highlighted section of the page to capture just that part.

Microsoft Edge is built on Chromium, and its DevTools include the same Command Menu, so the screenshot commands above work there too. Edge can also install many extensions from the Chrome Web Store, so check each extension’s listing for Edge support.

Fixes for common full-page screenshot problems

  • Sections are blank or images are missing. The page loads content as you scroll. Scroll to the bottom and back to the top, wait for images to load, then capture again.
  • The header or chat widget repeats down the page. Sticky elements are pinned to the viewport, so stitching extensions can capture them more than once. The DevTools command renders the page in one pass and usually avoids this.
  • The image is huge or blurry when zoomed out. Very long pages produce very tall images. Capture the section that matters with an area or node screenshot instead, or export a PDF that splits into pages.
  • You captured personal data. Blur names, emails, card numbers and tokens before the image leaves your machine. Cropping isn’t enough if the data also appears elsewhere on the page.

Frequently asked questions

Can Chrome take a full-page screenshot without an extension?

Yes. Open DevTools, open the Command Menu with Ctrl+Shift+P (Cmd+Shift+P on Mac), type “screenshot” and choose Capture full size screenshot.

What’s the keyboard shortcut for a full-page screenshot in Chrome?

There isn’t a single one. The fastest keyboard route is F12, then Ctrl+Shift+P, then typing “full size”. Extensions can add their own shortcut.

How do I take a scrolling screenshot in Chrome?

A “scrolling screenshot” is the same thing as a full-page screenshot: either DevTools’ Capture full size screenshot or an extension that scrolls and stitches the page for you.

How do I send a screenshot to a support team?

Capture the relevant part of the page, blur personal details, add an arrow or note on the problem, and include the page URL and what you expected to happen. If the problem involves several steps, a short recording is clearer than a series of screenshots. See our guide to writing a support ticket.

Share this article
Shareable URL
Leave a Reply

Your email address will not be published. Required fields are marked *