How to take a full page screenshot in Chrome and edit it

Why a normal screenshot is not enough

Chrome's normal screenshot shortcuts only capture what is on screen. The moment a page is longer than the window, the part below the fold is gone, and stitching several screenshots together by hand never lines up cleanly.

A full page screenshot solves that by capturing the whole document in one pass. It keeps the full context of an article, a settings screen, a long form, or a dashboard, which is exactly what you need for bug reports, documentation, and design review.

Method 1: Take a full page screenshot in Chrome without an extension (DevTools)

Chrome's DevTools can capture the full scrolling page with no install. It is the right choice for a one-off capture when you do not need to edit the result.

1. Open the page and let it finish loading.
2. Open DevTools. Press F12, or Ctrl+Shift+I on Windows and Cmd+Option+I on Mac.
3. Open the Command Menu. Press Ctrl+Shift+P on Windows or Cmd+Shift+P on Mac.
4. Run the command. Type screenshot, choose Capture full size screenshot, and press Enter.
5. Find the file. Chrome saves a PNG of the entire page to your downloads folder.

This works well on straightforward articles and documents, and it costs nothing. It also has real limits. Sticky or fixed headers can repeat or cover content. Pages that load sections only as you scroll may capture blank areas, because the DevTools screenshot tools do not always trigger that lazy content first. Extremely long pages can get cut off at the browser's image size limit. And there is no editing: you get a raw PNG with no way to frame it, point at anything, or hide sensitive data.

Method 2: One-click full page capture with the FramedShot extension

If you take full page screenshots regularly, or you need to edit the result, a Chrome screenshot extension removes the DevTools steps and hands the image straight to an editor.

1. Open the page you want to capture.
2. Open the FramedShot popup. Click the FramedShot icon in the Chrome toolbar.
3. Click Full Page. FramedShot scrolls the page automatically and stitches each screenful into one tall image. A small on-page notice shows the progress so you know what is happening while the page scrolls.
4. Edit the result. The stitched capture opens in the FramedShot editor, ready to frame, annotate, redact, or export.

Because capture and editing live in the same place, you skip the round trip of saving a PNG, opening a separate design tool, and re-exporting. You can also trigger full page capture with a keyboard shortcut by assigning the capture-fullpage command on Chrome's extension shortcuts page.

DevTools vs the extension: which to use

Use DevTools when you just need the pixels once. Use the extension when the screenshot is going to a customer, a changelog, documentation, or a social post and needs to look intentional.

What to do after you capture a full page

A full-page image is rarely the finished asset. The page is long, so the important part needs to stand out, and the edges often need cleanup. This is where capturing inside an editor pays off.

• Frame it. A clean background and a browser frame make a long capture read as a deliberate visual instead of a raw scroll. See how to add a browser frame to a screenshot.
• Annotate it. Add arrows, highlights, or text to point at the section that matters, so the viewer does not have to scan the whole page.
• Redact it. Long pages frequently include account names, emails, or dashboard data. Hide them before sharing. See how to redact sensitive info in screenshots.
• Export it. Save as PNG, JPG, or WebP at 1x, 2x, or 3x depending on where it is going.

If the motion matters more than a single tall image, for example a scroll-through or a hover state, a clip can be clearer than a screenshot. In that case, see how to record a browser tab in Chrome.

Common uses for full page screenshots

• Bug reports. Capturing the whole page keeps the context a developer needs instead of a cropped fragment. See bug report screenshots.
• Documentation. A full page reference shows an entire settings screen or form in one image.
• Design and UX review. Reviewers can see spacing, hierarchy, and flow across the whole page.
• Archiving. A dated full-page capture records what a page looked like before a change.
• Marketing and launch visuals. A framed full-page capture of a landing page works as a clean showcase image.

Review long captures before sharing

A full page screenshot captures more than a normal one, so it is easier to include something you did not mean to share. A long dashboard, an email thread, an account menu, or a billing section can all end up in the image.

FramedShot processes the capture locally in your browser and does not upload the screenshot content. Local processing avoids an unnecessary upload step, but it does not replace a review. Look over the full image before sending it, and redact anything sensitive. For credentials specifically, blur is not enough; use a solid fill.

Current limitations to know

Full page capture in FramedShot is built for vertical scrolling pages. A few limits are worth knowing before you rely on it.

• It captures vertically and clamps to the viewport width. It does not stitch horizontally.
• Fixed and sticky elements are handled on a best-effort basis. On some layouts a sticky header may still appear more than once.
• Extremely long pages are scaled down to stay within the browser's image size limit, so a very tall page may not be at full native resolution.

If a page breaks one of these, the DevTools method is a useful fallback for that specific capture.

Troubleshooting full page capture in Chrome

The capture is missing content or shows blank sections

The page likely loads content as you scroll. Scroll to the bottom once so everything loads, then capture again.

A sticky header repeats down the image

Some layouts pin elements during scrolling. Try the DevTools method for that page, or capture only the section you need.

The image looks lower resolution than expected

Very long pages are scaled to fit the browser's maximum image size. Capture a shorter section at full resolution if you need maximum detail.

FAQ

How do I take a full page screenshot in Chrome without an extension?

Open DevTools with F12, open the Command Menu with Ctrl+Shift+P or Cmd+Shift+P, type screenshot, and choose Capture full size screenshot. Chrome saves a PNG of the entire page.

What is the difference between a full page screenshot and a normal screenshot?

A normal screenshot captures only what is visible in the window. A full page screenshot captures the entire scrolling document, including everything below the fold, as one tall image.

Can I edit a full page screenshot after capturing it?

Yes. With FramedShot the capture opens directly in an editor where you can frame, annotate, redact, and export it. The DevTools method gives you a raw PNG that you would edit in a separate tool.

Are full page screenshots uploaded anywhere?

In FramedShot the capture is processed locally in your browser and the screenshot content is not uploaded. Always review a long capture and redact sensitive data before sharing it.

What format can I export a full page screenshot in?

FramedShot exports PNG, JPG, or WebP at 1x, 2x, or 3x. Chrome's DevTools method exports PNG only.