How to Take a Scrolling Screenshot on Any Device

For a full webpage, use the browser’s own full-page command first: Edge Screenshot, Firefox Take Screenshot, or Chrome’s “Capture full size screenshot” command. Use Snagit or ShareX when you need to capture a desktop app, a horizontal region, or a scrollable panel inside a page. No method handles infinite feeds and virtualized lists perfectly.

Fact-checked August 4, 2026: current browser, desktop, iPhone, and Android workflows were reviewed against Microsoft, Mozilla, Chromium, TechSmith, Apple, and Google documentation. Menu labels can move, so the exact command names and linked vendor pages matter more than an old screenshot of a menu.

A scrolling screenshot can be created in two fundamentally different ways. A browser can render the full document beyond the visible viewport, or a tool can scroll and stitch successive frames. Browser rendering usually avoids repeated fixed headers; stitching is more flexible for desktop applications and nested panes but is more sensitive to animation, speed, and visual overlap.

Fastest method by target

If the target offers Export, Print, Download report, or Save as PDF, consider that first. A native export can preserve searchable text, rows, and page structure that a 20,000-pixel image discards. Use the screenshot when the rendered visual state itself is evidence.

Choose document rendering or scroll-and-stitch

A browser-native full-page command asks the rendering engine for the document beyond the visible viewport. It is fast, local to the browser, and usually the cleanest choice for a normal article or product page. It may still miss cross-origin frames, canvas content, elements that render only after visibility, and independently scrolling regions.

A scroll-and-stitch tool records overlapping frames while the content moves, then matches those overlaps. It can work outside the browser and can target a rectangle inside an app, but every moving or fixed element becomes a potential seam. Use it when the browser cannot see the target as one document.

Browser extensions add a third route. They can make Chrome capture easier and may add annotation or PDF output, but they also request access to page content. Review the publisher, update history, requested permissions, upload behavior, and organization policy before installing one. For a one-off public webpage, Chrome DevTools avoids that extra trust decision. For a recurring approved workflow, a vetted extension may save enough clicks to be worthwhile.

Decide what “complete” means before starting. For a legal page, it may mean the entire document. For a chat, it may mean one incident window. For an infinite feed, completeness is impossible; record the date, start point, end point, and why that slice was selected.

Microsoft Edge

1. Open the page and load the content you need.
2. Right-click and choose Screenshot, open it from the Edge menu, or press Ctrl+Shift+S.
3. Choose the full-page option.
4. Review the preview, then copy or save the image.

Microsoft’s current Edge page calls the feature Screenshot; older instructions may call it Web Capture. Microsoft says it can capture full pages and lets you mark up the result before copying or saving. Feature behavior can vary by browser version and device.

Edge is the simplest built-in Windows path for a normal webpage. A nested chat history, grid, or code panel may have its own scroll container, so the page command can capture the outer document while leaving the inner panel at its current position.

Firefox

1. Right-click an empty part of the page or press Ctrl+Shift+S on Windows/Linux and Command+Shift+S on Mac.
2. Choose Take Screenshot when using the context menu.
3. Select Save full page in the upper-right corner.
4. Download the PNG or copy it to the clipboard.

Mozilla’s Firefox instructions, updated June 15, 2026, also let you add a Screenshot button to the toolbar. The downloaded file uses the page title and timestamp. If the context-menu item is missing, the shortcut or toolbar control is the cleaner route.

Google Chrome without an extension

1. Open Developer Tools with Ctrl+Shift+I on Windows or Command+Option+I on Mac.
2. Open the command menu with Ctrl+Shift+P or Command+Shift+P.
3. Type screenshot.
4. Choose Capture full size screenshot.

Google’s current Chrome DevTools documentation confirms the full-size screenshot command and also exposes it in the device-toolbar options. The command works without an extension and downloads a PNG.

Pre-scroll the page once when it lazy-loads images, then return to the top and capture. The command renders the document page, not every independently scrolling chat pane, iframe, WebGL canvas, or virtualized data grid. If the result is blank or missing sections, try the browser’s print/export path or a controlled scrolling tool.

Safari on Mac

Safari on macOS does not provide the same one-click full-page PNG command that Edge and Firefox expose. Choose the output by purpose:

1. For a searchable document, choose File → Print.
2. Open the PDF menu and choose Save as PDF.
3. For the exact rendered visual as one image, use Snagit Scrolling Capture or open the page in Firefox and use Save full page.
4. For a temporary offline copy that keeps page assets and links, Safari also offers File → Save As → Web Archive.

Apple’s current PDF instructions for macOS confirm the Print → PDF → Save as PDF path, while the Safari guide documents Web Archive and Page Source. A PDF may use print CSS, paginate content, or omit interactive states, so compare it with the live page when visual fidelity is the point.

For Linux, use Firefox Save full page or Chrome/Chromium DevTools. Those browser-native commands do not depend on a Windows or Mac desktop capture utility.

Snagit for apps and nested scroll regions

Snagit offers two related routes. Automatic Scrolling Capture detects a compatible window and shows scrolling arrows. Scrolling Capture, formerly called Panoramic Capture, lets you select a region and scroll it manually, including horizontally. The manual route is better when the target is a desktop application, spreadsheet, PDF viewer, or inner panel rather than an ordinary webpage.

TechSmith’s February 2026 troubleshooting guide recommends a larger window, excluding the scrollbar, disabling floating toolbars, scrolling smoothly, and moving in one direction rather than zigzagging. It also warns that parallax pages can be difficult and that security software, drivers, other utilities, or unsupported apps can interfere.

For ShareX on Windows, use Capture → Scrolling capture, select the region, and read the completion indicator. Green means the stitch succeeded, yellow means one or more matches were imperfect, and red means the first pair could not be combined. A finished file with a yellow result still needs seam-by-seam inspection.

For a wide spreadsheet or timeline, capture one direction at a time. Finish the vertical pass before attempting horizontal movement, or make separate labeled sections. Two-dimensional panning multiplies the possible overlaps and makes a missing column much harder to notice in the final image.

Our focused Snagit scrolling capture guide covers Chrome, Excel, PDF, Mac permissions, missing arrows, and security-software conflicts. Use that page for Snagit-specific failures rather than repeating fixes here.

If the same target is captured every week, a named capture preset can preserve the input type, destination, and other repeatable settings. The Snagit presets guide explains the setup. A preset does not guarantee a clean stitch; the content and window state can still change between runs.

iPhone, iPad, and Android

On iPhone, take a normal screenshot, open its editor, and choose Full Page when the content supports it. Apple’s current iPhone guide says a full-page capture can be saved as an image to Photos or as a PDF to Files. Use the preview strip to inspect and crop the page. The option is not available for every app or arbitrary inner panel.

Google’s Android instructions specify Android 12 or newer for scrolling screenshots on most screens that allow scrolling: press Power + Volume Down, tap Capture more, then use the crop guides. Manufacturers may expose a different label, but a missing control often means the current screen does not support system-level scrolling capture.

When Capture more is missing on Android

Use the physical Power + Volume Down shortcut before deciding the feature is unavailable. On Pixel phones, a screenshot taken from the Recent Apps overview can omit Capture more even when the button shortcut exposes it. App support also matters: a June 2026 Pixel 10 community report found Capture more available in Chrome but not Firefox, and a July 2026 thread reported similar app-specific behavior. These reports are device evidence, not a guarantee for every Android build.

If Firefox for Android does not expose Capture more, use Mozilla’s documented Share → Save as PDF route for an ordinary webpage. For a chat, inner panel, or interface state that PDF cannot represent, capture overlapping screens and stitch only a finite, reviewed section.

Why scrolling screenshots fail

• Lazy loading: content was never rendered; scroll through once before capture.
• Sticky headers: the same element appears in every stitched segment; hide it or use browser full-page capture.
• Infinite feeds: there is no natural endpoint; define a finite section.
• Virtualized lists: off-screen rows are removed from the page; capture sections or export data instead.
• Nested panes: the page body is not the element that scrolls; select the inner region with a capable tool.
• Animations/video: different frames appear in stitched strips; pause motion.
• Fixed chat composer: repeated overlays cover content; use export/print when available.

A seamless-looking image can still be wrong. Check row numbers, repeated timestamps, missing cards, truncated paragraphs, duplicated avatars, and sudden changes in scrollbar position. For evidence, compliance, or bug reproduction, preserve the source URL, capture time, application version, and a focused screenshot of the critical state alongside the long image.

Once the capture is structurally correct, use the Snagit Editor workflow to crop, label, and preserve an editable master. Do not annotate before seam review: a callout can distract you from a duplicated line directly beneath it.

Prepare the page before capture

1. Close cookie banners, chat widgets, and notifications.
2. Set a stable browser zoom and window width.
3. Load images by scrolling once.
4. Expand only the sections the reader needs.
5. Replace private data with a safe account or redact after capture.
6. Capture, then inspect the entire seam from top to bottom.

Pause auto-refresh and animations where possible. Do not resize the window or change zoom during a stitched capture. If the page has a sticky sidebar, collapse it before capture so it cannot cover repeated content. For a long table, prefer a native CSV/PDF export when values must remain exact.

PNG or PDF?

Use PNG when the output is one long visual that will be cropped or annotated. Use PDF when the page is a document people will print or search. For an article, several focused screenshots are usually more readable than a 20,000-pixel image. The Snagit export guide explains format tradeoffs.

Review, redact, and split the result

View the image at 100%, not only fit-to-screen. Scan top to bottom once for seams and again for private data. Long captures can hide email addresses, account names, tokens, ticket IDs, chat text, and browser tabs far below the fold. Apply an opaque redaction where secrecy matters, flatten a delivery copy, and reopen that export.

The Snagit redaction guide covers opaque masks, metadata, and export verification. Add arrows or numbered steps only after that privacy pass; the annotation guide helps keep each focused crop readable.

For a help article, split the long image at meaningful task boundaries and place each crop next to its instruction. Keep the original full-page capture only as a source or downloadable reference. Add alt text to each focused image; do not expect one enormous alt attribute to replace the whole page.

FAQ

How do I take a scrolling screenshot in Chrome?

Open DevTools, open the command menu, type “screenshot,” and choose Capture full size screenshot.

Can Windows Snipping Tool capture a full webpage?

For a webpage, Edge Screenshot is the more direct built-in Windows method. Use Capture full page.

Why is my sticky header repeated?

A scroll-and-stitch tool captured the fixed element in multiple frames. Hide it or use a browser-native full-page command.

Can I capture an infinitely scrolling page?

Only a finite loaded section. Decide the endpoint; an infinite feed has no complete final image.

What should I use for a scrolling desktop app?

Use Snagit Scrolling Capture or another tool that can target a region and follow controlled manual scrolling.

How do I capture a full page in Safari on Mac?

Use File → Print → PDF → Save as PDF for a searchable document. For one long PNG of the rendered page, use Snagit Scrolling Capture or Firefox Save full page.

Why is Capture more missing in Firefox on Android?

Android scrolling capture depends on the app and how the screenshot was triggered. Try Power + Volume Down. If Firefox still does not expose Capture more, use its Share → Save as PDF option for a webpage.

What is the difference between a full-page screenshot and a scrolling screenshot?

A browser full-page screenshot renders the whole document beyond the viewport. A scrolling screenshot records overlapping frames while content moves and stitches them together, so it also works in apps and inner panels but is more vulnerable to repeated headers and broken seams.

Related Snagit guides

• Snagit Scrolling Capture: How to Capture Full Pages
• Snagit vs Snipping Tool
• Snagit Black Screen Capture: Causes and Safe Fixes
• Snagit Beginner Tutorial: Capture, Edit, and Share