How to capture a whole scrolling page on Windows

No Windows tool captures beyond the visible screen. The fix depends on what you're capturing — and if it's a web page, your browser already has it.

Updated 15 September 2026

Web pages: your browser can already do this#

No installation, no extension, full page at full quality.

Chrome and Edge

1. Open the page and press F12 to open developer tools.
2. Press Ctrl+Shift+P to open the command menu.
3. Type screenshot and pick Capture full size screenshot.
4. A PNG of the entire page downloads.

It looks like a developer trick but it's the single best full-page capture on Windows — it renders the real page rather than stitching images together, so there are no seams, no repeated sticky headers, and text stays sharp at any length.

There's also Capture node screenshot, which grabs one element. Select a div in the Elements panel first and you get just that component, cropped exactly.

Firefox

Simpler. Right-click any empty part of the page, choose Take Screenshot, then Save full page. Or press Ctrl+Shift+S.

Everything else needs a third-party tool#

For a long Word document, a chat history, a spreadsheet or a code editor, Windows has nothing built in. The tools that do it work by capturing repeatedly while scrolling and stitching the results:

• ShareX — free and open source, has a dedicated scrolling capture mode. Fiddly to set up, reliable once configured.
• PicPick — free for personal use, the most forgiving scrolling capture of the free options.
• Snagit — paid, and the one that handles awkward cases like nested scroll panes and side-by-side scrolling best.

Comparison of what each actually does.

Or avoid stitching entirely#

Sometimes the better answer isn't a screenshot:

• Print to PDF. Ctrl+P, then choose Microsoft Print to PDF. You get the whole document with selectable text, smaller than any image would be. How to do this well.
• Zoom out first. Ctrl+minus shrinks a page until it fits one screen. Text gets small but stays legible on a high-resolution display, and one clean capture beats a stitched one.
• Capture in sections. Three overlapping screenshots with obvious overlap are often clearer to a reader than one enormous image they have to zoom around in.

Why stitching goes wrong#

Stitched captures fail in predictable ways, and knowing them saves debugging time:

• Sticky headers repeat every few hundred pixels, because the tool captures them on each pass.
• Animations and carousels change between passes, leaving visible mismatches.
• Custom scrollbars built in JavaScript don't respond to the tool's scroll commands at all.
• Dynamically loaded content arrives after the tool has passed that point.

All four are reasons to prefer the browser's developer tools method for anything on the web — it renders once at full height and never stitches.

For ordinary single-screen captures, the standard Windows shortcuts are faster than any of this.