How to take a full page screenshot in Chrome

Which full-page capture method should you use?

Choose the method around the result you need:

A full-page screenshot covers one page, including content below the fold. It does not visit links or capture every page on a website. For a competitor review with a homepage, pricing page and checkout, capture each page separately.

How to take full page screenshot in Chrome without an extension

Prepare the page you want to capture

Open the correct page and put it into the state you want to show: select the relevant tab, expand the needed sections, and close menus or overlays that obscure the content.

Scroll down through the page and let images and sections load. Then return to the top. This can help with lazy-loaded content, which appears only when you approach it while scrolling. It does not guarantee that an endlessly updating feed or a large app table will become one complete image.

Decide on a useful endpoint before capturing an infinite-scroll page. If the task concerns one result, chart or error message, a focused capture may be more useful than the entire page.

Run Chrome’s screenshot command

1. Open Developer Tools. On Windows, press Ctrl + Shift + I. On Mac, press Command + Option + I. You can also open Chrome’s three-dot menu and choose More tools → Developer tools.
2. Open the Command Menu inside DevTools. On Windows, press Ctrl + Shift + P. On Mac, press Command + Shift + P. Make sure DevTools has focus first.
3. Type screenshot. The menu filters to the available screenshot commands.
4. Select Capture full size screenshot. Do not choose the shorter Capture screenshot command when you need content below the visible area.
5. Find the PNG. Check Chrome’s downloads list. The file usually goes to your configured download folder, often Downloads; Chrome may ask where to save it if you enabled that setting.
6. Open the saved image. Inspect the top, a section in the middle, and the bottom. Zoom in enough to read the text and check the detail that matters for your task.

Chrome distinguishes full-size, visible-area and other screenshot options; its screenshot overview illustrates the different capture types.

If the layout becomes narrower: docking Developer Tools beside the page reduces the space available to the website. Undock DevTools into a separate window, then check the page width before capturing. For a specific responsive layout, Chrome also provides viewport controls and full-size capture in Device Mode. You do not need to switch to a phone preset for a normal desktop screenshot.

How to capture and explain a page in Okea

In the current Okea build, the Full Page → Editor workflow lets you capture, annotate and export in one place. These steps apply if your popup shows Full Page, Selected Area and Visible Area; that interface may differ from your installed version.

1. Open the page you want to document and choose Full Page in Okea.
2. When the capture opens in Editor, inspect the result before adding notes.
3. Crop distracting content if needed. Add an arrow, a highlight or a short text note to identify the change you want.
4. Choose Download to save the result. Use the format control to select PNG, JPEG or PDF. If you want to paste the image into another app, choose Copy, then paste it into the destination.

Opening the Editor does not automatically download a file. Take the Download or Copy action when the result is ready.

If your popup instead shows “Capture as PNG” or “Capture as PDF”: that older workflow downloads directly rather than opening the Editor. Follow the controls you actually see.

Choose the smallest capture that explains the task

Use Full Page when the sequence or surrounding context matters, such as reviewing the order of sections on a landing page. Use Visible Area to show the current web-page viewport. Use Selected Area to draw a rectangle around a specific detail currently on screen.

For an existing PNG or JPEG, Add image brings it into the Editor. You can also use numbered steps for a short visual instruction and return to earlier results through History, when those controls are available in your version.

What if the screenshot misses part of the page?

A file can download successfully and still omit the thing you needed. Compare it with the page before treating it as a finished reference.

Images or the footer are missing

The page may load content as you scroll, or its height may change after the first view. Visit the missing section, wait until it appears, then capture again. Check the same section in the new file. If it is still absent, take a separate capture of that area rather than assuming another full-page attempt will include it.

Only one pane or part of a table appears

Some apps scroll inside a panel while the outer page stays still. A full-page capture does not necessarily expand that inner panel. Check which part of the app moves when you scroll. If the app offers an export or printable view, consider that; otherwise capture the needed panel in readable sections.

Long tables can also render only the rows near the current view. Scrolling through every row may not leave all of them available for a single screenshot.

A header repeats, or the page is extremely long

Sticky navigation and floating controls can obstruct content or appear unexpectedly in the output. Close optional floating panels through the site’s normal controls and inspect another capture. If the problem remains, use smaller sections that preserve the relevant context.

For feeds that keep loading, narrow the content with the site’s filters or choose a finite section. There may be no stable “bottom” to capture. A set of clearly labeled images is often easier to review than an enormous file with uncertain completeness.

Should you save a PNG, JPEG or PDF?

PNG is a useful starting point for interfaces, text and annotations because it avoids JPEG compression artifacts around letters and sharp edges. Chrome’s built-in full-size screenshot command produces a PNG.

JPEG may suit image-heavy pages when file size matters, but compression can soften text and introduce artifacts. Inspect the exported file at a readable size before choosing it for a detailed design review.

PDF is useful when the recipient wants a document attachment. Distinguish two routes: exporting a screenshot as PDF puts captured imagery into a document, while Print → Save as PDF asks Chrome to produce print output from the page. Neither route should be assumed to preserve interactive elements or provide searchable text in every case.

To try the print route, close or leave DevTools, focus the page, and press Ctrl + P on Windows or Command + P on Mac. Choose Save as PDF as the destination and inspect the preview. Check page breaks, clipped content and backgrounds before saving. If your goal is to show exactly where an interface element appeared, start with a screenshot and verify that visual detail in the result.

Make the screenshot useful in a ticket or review

Suppose a landing page puts an important offer below several unrelated sections. Keep the full-page image as context, then make a focused crop showing the offer and the section above it. Add an arrow and a specific note such as “Move this offer above customer stories.” The recipient can see both the problem and the requested change.

For a support instruction, mark the click target and number the steps in order. Avoid covering the button label with your annotation. Include the source URL in the ticket so a colleague can return to the live page.

Finally, check the image after attaching or pasting it. A chat or ticket preview may shrink a tall screenshot until its text is unreadable. Attach the original file for detail and use a crop in the message for the immediate action. Inspect visible account details and other information before sending.

Frequently asked questions