Capture full-page screenshots that keep scrolling
Web pages don't end at the viewport. Your screenshots shouldn't either. Capture entire pages, long threads, and documents in one continuous image. Everything runs on your Mac.
Three ways to scroll-capture
Different pages need different approaches. Pick the mode that fits.
| Mode | Speed | Best for | Accuracy |
|---|---|---|---|
| Auto-scroll | Fastest | Standard web pages, documents, PDFs | High |
| Manual stitch | You control it | Complex layouts, parallax sites, iframes | Highest |
| Timed intervals | Adjustable (1-5s delay) | Lazy-loaded content, infinite feeds, heavy animations | High |
How to take a scrolling screenshot
Three steps. The app handles the hard part.
Choose your capture mode
Open ScreenshotEdits and pick scrolling capture. Auto-scroll works for most pages — it scrolls at a steady pace and grabs each frame. Switch to manual stitch if the page has parallax effects or nested scrollable containers. Timed intervals are your friend for anything with lazy-loaded images.
Pro tip: Not sure which mode to pick? Start with auto-scroll. If the result has gaps or duplicated sections, switch to manual stitch and scroll at your own pace.
Capture the full page
Select the region you want to capture. It can be the full browser window, a specific panel, or even a scrollable sidebar. ScreenshotEdits scrolls through the content, capturing overlapping frames and stitching them into one continuous image. You'll see a live preview as it works.
Pro tip: For pages with cookie banners or popup overlays, dismiss them before starting. They'll appear in every frame otherwise and mess up the stitching.
Review and export
The stitched image opens on your canvas. Zoom in to check the stitch points — especially around areas with animations or floating elements. Crop, annotate, or beautify if needed. Then export as PNG or JPEG, or copy straight to clipboard with ⌘C.
Pro tip: Long captures can produce massive files. If you're sharing via Slack or email, export as JPEG at 90% quality. You'll cut the file size dramatically with almost no visible difference.
What people actually capture
Regular screenshots stop at the bottom of your screen. That's fine for a button or a dialog box. But most of the things worth capturing — pages, threads, documents — don't fit in one viewport.
Full webpage archives
Redesigns happen. Pages get pulled down. Competitors change their pricing. A scrolling screenshot preserves the entire page exactly as it appeared — headers, footers, every section in between. Way more reliable than a bookmark.
Long chat threads
Slack conversations, iMessage threads, Discord channels. They scroll forever. Instead of taking 14 separate screenshots and hoping you got every message, one scrolling capture grabs the entire thread top to bottom.
Entire documents
Terms of service. Design specs. API documentation. Some documents run 20+ pages and you need the whole thing in one image. Timed intervals handle lazy-loaded sections so nothing gets cut off.
Social media feeds
Instagram profiles, Twitter threads, LinkedIn posts with all comments expanded. Feeds are designed to scroll infinitely. Timed capture keeps up with lazy loading so you don't end up with blank placeholder images.
Auto-scroll vs manual stitch
Both produce a single stitched image. The difference is control versus convenience.
Auto-scroll
Hit capture and walk away. ScreenshotEdits scrolls the page at a consistent speed, grabs overlapping frames, and stitches them together. Works great for static content like blog posts, documentation, and terms pages.
- Hands-off — no manual scrolling
- Fastest option for standard pages
- Best for: static content, articles, docs
Manual stitch
You scroll at your own pace. Capture each section when it looks right. This gives you full control over what gets included and when each frame is taken. Essential for pages where auto-scroll misses content or produces artifacts.
- Full control over timing
- Handles parallax and animations
- Best for: complex layouts, nested scrolls
When to use timed intervals: If auto-scroll captures blank placeholders where images should be, switch to timed intervals. A 2-second delay per scroll gives lazy-loaded content time to render before the next frame is captured.
Tips for cleaner scrolling captures
The difference between a messy stitch and a seamless one usually comes down to preparation.
Wait for lazy-loaded content
Most modern sites load images and content as you scroll. If you auto-scroll too fast, you'll get grey placeholders instead of actual content. Use timed intervals with a 2-second delay — it's slower, but you'll actually get everything.
Handle sticky headers
Navigation bars that follow you down the page will show up in every stitched frame. Either collapse the header before capturing, or let ScreenshotEdits auto-detect and remove the duplicates. Check the result for any leftover artifacts.
Choose the right format
A full-page screenshot of a content-heavy site can hit 15MB+ as PNG. Switch to JPEG at 90% quality for sharing — you'll barely see the difference and the file will be 3-4x smaller. Save PNG for when you need pixel-perfect accuracy.
Check stitching accuracy
Parallax effects, animations, and floating elements can trip up automatic stitching. After capture, zoom in on the stitch points and look for misaligned text or duplicated elements. Manual stitch mode gives you full control over tricky sections.
Everything you need for full-page captures
Scrolling screenshots used to mean taking a dozen captures and manually stitching them in Photoshop. Not anymore.
Frequently asked questions
How does auto-scroll capture work?
ScreenshotEdits scrolls through the page automatically, capturing each visible section and stitching them together into one seamless image. You just select the area and hit capture.
Can I capture pages with lazy-loaded content?
Yes. Use timed intervals to give each section time to load before the next scroll. Set the delay to 1-3 seconds for most pages with lazy-loaded images or infinite scroll feeds.
What about sticky headers and floating elements?
Sticky headers can appear duplicated in scrolling captures. ScreenshotEdits detects and removes repeated sticky elements during stitching. For stubborn cases, you can manually mark the header region to exclude.
What file format should I use for long screenshots?
PNG preserves every detail but creates large files for long captures. JPEG at 90% quality cuts file size by 60-80% with barely visible quality loss. For archival purposes, stick with PNG. For sharing, JPEG is usually the better call.
Is there a maximum page length?
There's no hard limit, but extremely long pages (50+ scrolls) may produce very large files. For practical purposes, most web pages and documents capture without issues.
Can I scroll-capture inside a specific element, not the whole page?
Yes. Select just the scrollable container — like a chat panel, code editor, or sidebar — and ScreenshotEdits will scroll within that element only. Useful for capturing Slack threads or embedded content.
Does everything stay on my Mac?
Yes. ScreenshotEdits runs in your browser or locally on your desktop. Nothing gets uploaded to any server. The capture, stitching, and export all happen locally.
Capture the whole page
Download free and stop piecing together screenshots by hand.