TL;DR

  • Neither macOS nor Windows can screenshot a full scrolling page natively — their tools stop at the visible screen.
  • Chrome can do it hidden inside DevTools ("Capture full size screenshot"), Firefox has it built into right-click; both give you a raw file and no way to annotate or share it.
  • The Clipy Chrome extension does it in one click: Full page auto-scrolls, hides sticky headers so they don't repeat, handles apps that scroll inside an inner panel, and stitches everything into one PNG.
  • The result can go straight to an annotation editor and an unlisted share link — no file juggling.
  • Free, no watermark, and the capture is a lossless PNG.

The problem: your screenshot tool stops at the fold

You need the whole page — a full article for reference, a complete order confirmation, an entire settings screen for a support ticket, a competitor's pricing page for the team, a long design for review. You press ⇧⌘4 or open the Snipping Tool, and you get… the part that happened to be on screen. The rest of the page might as well not exist.

So people improvise: five overlapping screenshots pasted into a doc, a phone photo of the monitor (it happens), or printing the page to PDF and mailing a 14-page file where every page break lands mid-sentence. All of it is workaround energy for something a browser can genuinely do — because a browser knows exactly how tall the page really is.

Let's go through every real way to capture a full scrolling page, including the free built-in ones, and then the honest reasons a dedicated tool is still worth it.

The built-in options (and their catches)

Chrome DevTools: hidden, but free

Chrome has shipped full-page capture for years — buried where no normal person will find it:

  1. Press ⌥⌘I (Mac) or F12 (Windows) to open DevTools.
  2. Press ⇧⌘P (Mac) or Ctrl+Shift+P to open the command menu.
  3. Type "screenshot" and pick Capture full size screenshot.

Chrome renders the entire page height and drops a PNG in your Downloads folder. The catches: it's a three-step incantation you'll forget, it captures the page as the renderer sees it — which on some sites means lazy-loaded images that haven't loaded yet appear as gray boxes — and what you get is a file, full stop. No markup, no link, no redaction before it goes somewhere it shouldn't.

Firefox: genuinely good at this

Right-click any page → Take Screenshot → Save full page. Firefox deserves credit here — full-page capture right in the visible UI. Microsoft Edge has a visible version too (menu → Screenshot → Capture full page). Same limitation on the other end though: you get a PNG file and you're on your own for everything after.

macOS and Windows: not really

macOS's screenshot tools (⇧⌘3/4/5) capture screens and windows — never scrollback. Windows 11's Snipping Tool has been rumored to gain scrolling capture for years; as of today, mainstream builds don't have it. Safari technically can via File → Export as PDF, but it mangles real-world layouts often enough that we can't recommend it for anything you'll share.

Bottom line: on the OS level, scrolling capture doesn't exist. It has to come from something that lives inside the browser.

The one-click version: Clipy's Full page button

Install the Clipy extension, open the page you want, click the Clipy icon, and under "Screenshot this tab" press Full page. The extension scrolls the page for you, captures each viewport as a lossless PNG, and stitches them into one tall image. Then — this is the part the built-ins can't do — it drops you into a markup panel, and one more click gives you either a downloaded PNG, a clipboard copy, or an unlisted share link your teammate can open without an account (creating the link takes a free sign-in; viewing never does).

(One honest limitation: capture lives in the popup — there's no keyboard shortcut for it yet, and it works on normal http/https pages, not on Chrome's internal pages or the Web Store.)

Why full-page capture is harder than it looks

"Scroll and stitch" sounds trivial. It isn't, and the difference between tools that handle these cases and tools that don't is the difference between a clean capture and a mess you have to redo by hand. Here's what Clipy's implementation actually deals with:

Sticky headers would repeat forty times

Nearly every site has a navbar with position: fixed or sticky. Scroll-and-stitch naively and that navbar appears again at the top of every stitched frame — the classic broken full-page screenshot. Clipy captures the first frame with the header in place, then hides fixed and sticky elements for every subsequent frame, so the header appears exactly once, where it belongs.

Lots of modern apps never scroll the window

Dashboards, documentation sites, chat tools, admin panels — a huge share of modern web apps put their content in an internal scrollable panel while the window itself never moves. Naive tools capture one viewport and declare victory. Clipy checks whether the window actually scrolls, and if it doesn't, finds the dominant scrollable container on screen and captures that — so a long dashboard or docs page comes out complete, not cropped to the first screen.

Infinite scroll would never end

Point a full-page tool at a social feed and "the whole page" is a trap — the page grows as fast as you scroll it. Clipy caps capture at 40 viewport-heights and clamps the final image to 32,000 pixels tall, so you get a long, complete-enough capture instead of a hung tab. Each scroll step also waits a beat for the page to settle, which helps keep lazy-loaded images from showing up half-rendered.

And your page is put back the way it was

Scroll position restored, hidden elements re-shown — capturing shouldn't rearrange the thing you were reading.

This is where the built-in options quietly cost you the most time. A full-page capture is usually for someone — a teammate, a support agent, a client — and long screenshots are exactly the ones that need a "look here, not at the other 12,000 pixels" arrow.

A Clipy capture can go straight into your screenshot library, where the web annotation editor gives you arrows, boxes, text labels, auto-numbered step badges, pixelated redaction for anything sensitive, and crop — all non-destructive, so you can fix an annotation after you've already shared the link. The link itself (clipy.online/s/…) is unlisted, opens for anyone without an account, and always shows your latest saved version.

Compare the endgame of each approach:

  • DevTools/Firefox: a PNG in Downloads → open some editor → mark it up (destructively) → attach the file somewhere → it gets compressed → repeat entirely if you made a mistake.
  • Clipy: Full page → arrow + redact → share link. Mistake? Edit and save; the same link updates.

What to use when: a fair decision table

  • You capture a long page once a year: Firefox's built-in, or the Chrome DevTools trick. Free, already installed, fine.
  • You're a developer who needs pixel-exact renders at custom viewport sizes: DevTools — it's the only option with device emulation attached.
  • You capture pages regularly and they go to other people: a one-click tool with annotation and links. That's the Clipy case — especially if you already use it for screen recording, since it's the same extension, account, and library.
  • The page's behavior — not its appearance — is the thing to show: stop screenshotting and record the scroll as a video instead; a 30-second recording beats any still for "it breaks when I scroll fast".

FAQ

How do I screenshot a whole webpage that requires scrolling?

Use a browser-level tool: the Clipy extension's Full page button (one click, then annotate/share), Firefox's built-in Take Screenshot → Save full page, or Chrome DevTools' "Capture full size screenshot" command. OS screenshot tools can't scroll.

Can I take a scrolling screenshot on a Mac without installing anything?

Only through a browser: Firefox has it built in, and Chrome hides it in DevTools. macOS itself has no scrolling capture — ⇧⌘3/4/5 stop at the visible screen.

Why does my full-page screenshot show the header repeated?

The tool stitched scrolled frames without hiding sticky elements, so the fixed navbar was re-captured in every frame. Use a tool that hides fixed/sticky elements after the first frame — Clipy does this automatically.

Why is my full-page capture only one screen tall?

The app you captured scrolls inside an internal panel, not the window, and your tool only watched the window. Clipy detects the dominant scrollable container and captures it instead.

How long a page can Clipy capture?

Up to 40 viewport-heights, clamped to a 32,000-pixel-tall image — several complete magazine articles' worth. Longer pages get a truncated (but valid) capture rather than a failure.

What format is the output?

Lossless PNG, both for the capture and for anything you export after annotating.

Try it on the page you're reading

This article is a long scrolling page. Install the extension, click the Clipy icon, hit Full page, and watch it come out as one clean image — header once, footer once, everything in between. Then drop an arrow on your favorite paragraph and send someone the link.