Full page screenshot: capture an entire webpage in one image

Press Print Screen and you get the window. Not the article, not the dashboard, not the checkout flow — the window. Everything below the fold is simply absent, and on a modern page that is usually most of it.

A full page screenshot solves that by treating the page as a document rather than a view. The page is scrolled from top to bottom, each screenful is captured, and the captures are joined back into one image at the page's real height. What you get is the whole thing: header, body, footer, in a single file you can send, archive or print.

What a full page capture produces

Concrete numbers, so you know what to expect before you install anything.

Typical output width

Page width × display density

Typical output height

3,000–30,000 px

Typical file size (PNG)

4–80 MB

Maximum single-image edge

16,384 px (browser limit)

Time for a 12,000 px page

About 4–8 seconds

Formats

PNG, JPG, PDF

How to take one

Three actions. Everything else happens on its own.

1. 1

   Open the page you want

   Any normal http or https page works. Chrome blocks every extension from running on chrome:// pages, the Web Store and other extensions' pages, so those cannot be captured by any tool.

2. 2

   Click the toolbar icon

   Or press the keyboard shortcut. The page begins scrolling itself, and a badge on the icon counts the progress.

3. 3

   Save the result

   The finished screenshot opens in a new tab where you can crop it, annotate it, blur anything private, and save as PNG, JPG or PDF. See the step by step guide for the detailed walkthrough.

What actually makes this hard

Scrolling and pasting screenshots together sounds trivial. These are the five things that break a naive implementation, and what a capture has to do about each.

Sticky headers repeat

A navigation bar pinned to the top of the viewport appears in every single capture, so the joined image ends up with a nav bar every 800 pixels. The fix is to neutralise fixed and sticky positioning during the capture and restore it afterwards, so the header appears once, where it belongs. See automatic scrolling.

Lazy images are still blank

Images that load only when scrolled into view have not finished arriving by the time a fast scroll passes them, leaving grey rectangles. The capture has to pause long enough for them to decode.

Animations get caught mid-frame

Fade-in-on-scroll effects are half-transparent at the moment of capture. Fast-forwarding transitions to their end state before photographing avoids ghosted sections.

Scroll positions do not land where you asked

Browsers clamp and round scroll offsets. Assuming each step moved exactly one viewport produces seams and duplicated strips. Measuring where the page actually landed, and trimming the overlap from that measurement, is what makes joins invisible.

Very tall pages exceed what a canvas can hold

Browsers cap a single image at 16,384 pixels on a side. Past that the capture has to be split into parts that tile the page exactly. See long webpage screenshots.

Where the file goes

Full Page Screenshot does the whole capture inside your browser. There is no server, no upload, and no account. The extension requests no host permissions at all: Chrome grants access to one tab at the moment you press the button and takes it back when the capture finishes.

Its own pages ship a Content Security Policy containing connect-src 'none', which means the browser itself blocks outbound requests rather than us promising not to make them. More detail on how the privacy model works.