How to Take a Scrolling Screenshot on Mac
A screen is only as tall as it is. Capturing a long conversation, a settings pane or an entire web page means scrolling, capturing repeatedly, and joining the results — which is exactly the kind of tedious, error-prone job worth automating.
Press ⌃+⌥+S over the window you want. Snip Studio finds the scrolling region, scrolls it, captures frames, and stitches them into one continuous image.
Capture a scrolling page
-
Press the scroll capture hotkey
Press ⌃+⌥+S with the window you want in front. Snip Studio offers three ways to decide what gets captured:
One keystroke starts it; the stitching is automatic either way. - Auto-Main — finds the main scrolling region for you. Right most of the time.
- Multi-Select — pick from the scrollable regions it detected, for a page with more than one.
- Manual — draw the exact region yourself.
Auto-Main is the default; Manual is there for when it guesses wrong. -
Let it scroll
Snip Studio scrolls the region itself and captures frames as it goes, up to 240 of them. Fixed navigation bars and footers that would otherwise appear in every frame are detected and cropped out.
Without Accessibility permission, Snip Studio cannot drive the scroll for you — so it guides yours instead, prompting you down the page and capturing each frame automatically as you reach it. The stitching, the header cropping and the result are the same; only who does the scrolling changes.
When it finishes, your scroll position is put back where you left it.
The result is a single image, not a PDF and not a folder of frames. -
Use the Safari extension for web pages
For pages specifically, Snip Studio's Safari extension clips the visible viewport, the full page, or a single element you pick. It hides sticky headers and cookie banners, waits for web fonts to finish loading so the type is not swapped mid-capture, and stitches tall pages — clamped to WebKit's 14,000-pixel ceiling.
Element capture is the underused one: rather than the whole page, grab just the pricing table or the comment thread.
Viewport, full page, or one element. -
Redact before it goes anywhere
Long captures collect things you did not mean to include — an email address halfway down a thread, an account number in a settings pane, a name in a table. Snip Studio reads the stitched image on your Mac and lists what it found, so you can blur, pixelate or black it out and export a flattened copy.
On a 6,000-pixel-tall capture this is the difference between a quick check and scrolling through the image at full zoom looking for problems.
Everything detected, listed once, however long the capture.
Area, window, full screen, circle and lasso captures are free, along with the library and its search. Scrolling capture, the Safari extension, the editor, recording and automations are part of the paid ULTRA upgrades.
Why stitching is harder than it looks
Worth knowing, because it explains why results vary between pages and what to do about it.
Sticky elements. A navigation bar fixed to the top of the viewport appears in every captured frame. Naive stitching gives you an image with the same header repeated fifteen times. Detecting which pixels are fixed and cropping them is the hard part, and it is what Auto-Main is doing.
Lazy loading. Most modern pages load images only as they approach the viewport. A capture that scrolls faster than the page loads leaves gaps. Scrolling the page through once by hand first genuinely helps.
Virtualised lists. Long lists in some apps keep only the visible rows in memory, destroying and rebuilding them as you scroll. There is no complete version of the list to capture — it does not exist all at once.
Scroll anchoring. Some pages adjust their scroll position when content above finishes loading, which shifts everything mid-capture and misaligns the seams.
None of these are solvable in general, which is why any scrolling-capture tool works beautifully on some pages and imperfectly on others. The practical advice is the same everywhere: scroll the content through once first, then capture.
What you can capture this way
- A long Slack, Messages or Mail thread
- A settings pane that scrolls past the window
- An entire web page, including everything below the fold
- A code file in an editor
- A table or spreadsheet longer than the window
- A terminal scrollback
Element capture, when the whole page is too much
A full-page capture of a long article is often less useful than a capture of the one part that mattered. The Safari extension can pick a specific element rather than the page — a pricing table, a comment thread, an error banner, a single card — cropped exactly to its bounds with none of the surrounding layout.
This sidesteps most of the stitching problems above at a stroke. An element that fits on screen needs no scrolling, no seam detection and no sticky-header cropping, and the result is tight to the thing you were documenting.
Long captures and what is in them
A 6,000-pixel-tall capture of a conversation or a settings pane usually contains more than you noticed while scrolling past it. Checking that by eye means panning the image at full zoom.
Snip Studio recognises the text across the whole stitched image on your Mac and lists what it found once — emails, URLs, file paths, faces, codes — with masked previews. Bulk-redact every email or every URL in one action, then export a flattened copy. On a long capture that is the difference between a genuine check and a hopeful glance.
Capturing and the searchable library are free. Automations, the editor, recording, scroll capture and the Safari extension are part of the paid ULTRA upgrades, bought in-app through Apple.
Common problems
The stitched image has a repeated header
A sticky element was not detected as fixed. Use Manual mode and draw the region below the header.
The capture stops partway down
Infinite-scroll pages have no bottom. Scroll to the point you want to end at first, or use element capture in the Safari extension to grab a defined section.
Images are missing from the middle
Lazy-loaded images that were never on screen were never downloaded. Scroll the page through once by hand before capturing.
Scroll capture asks for a permission
Scrolling a window on your behalf is the one place Snip Studio needs more than Screen Recording — that is Accessibility, and it is optional. Decline it and scroll capture still works: Snip Studio guides your scroll instead, prompting you down the page and capturing each frame automatically as you reach it. Same stitching, same header cropping, same result. The full permission list is in the Privacy Policy.
The page is far too tall to be useful
A 20,000-pixel image is technically correct and practically unreadable. Capture the section that matters instead — Manual mode or element capture both do this.
The seams do not line up
Usually scroll anchoring: content above the viewport finished loading and shifted the page mid-capture. Let the page settle fully, then capture again.
Frequently asked questions
How do you take a scrolling screenshot on a Mac?
Press ⌃+⌥+S in Snip Studio over the window you want. It detects the scrolling region, scrolls it, and stitches the frames into one image.
How do you screenshot an entire web page?
Use Snip Studio's Safari extension, which captures the full page as an image — hiding sticky headers and cookie banners, and waiting for web fonts to load first. You can also capture a single element rather than the whole page.
Can you capture a long Slack or Messages conversation?
Yes, with scroll capture. Bear in mind that some apps recycle off-screen rows, so scrolling the thread through once first gives a better result.
How long a page can it capture?
Up to 240 stitched frames. In the Safari extension, tall pages are clamped to WebKit's 14,000-pixel limit.
Is scrolling capture free?
No — scroll capture and the Safari extension are part of the paid ULTRA upgrades. Area, window, full screen, circle and lasso captures and the library are free.
Scroll capture behaviour, frame limits and the Safari extension's WebKit clamp described from Snip Studio's own documentation. Permissions match the published Privacy Policy. Last checked 1 September 2026.