If Snagit scrolling capture is not working, check which part fails. Missing arrows call for a window-detection or permissions check. A capture that stops early needs a different test from an image with repeated headers or gaps. Start with a simple public page, then compare automatic and manual scrolling before changing your installation.
Save open work and record your Snagit version, operating system, browser and failing page. Use a test page without private data. If it works, you have narrowed the problem to a particular setup; you have not proved that every Snagit component or every other page is fault-free.
Documentation and release notes checked September 19, 2026. These are suggested diagnostic steps, not results of a hands-on test. The diagrams explain the sequence; menu labels and available settings can differ by version and platform.
Snagit scrolling capture not working: quick diagnosis
| Symptom | What to investigate | First check |
|---|---|---|
| No scrolling arrows | Window detection, nested panel or Mac permission | Try manual capture on a simple public page |
| Capture stops early | Page changes, focus or browser configuration | Preload a finite page and compare a smaller region |
| Gaps or missing content | Stitching or content loaded during capture | Wait for content and inspect overlapping sections |
| Repeated headers | Fixed page elements or capture boundary | Exclude the fixed area where practical |
| Mac automatic capture fails | Accessibility or a version-specific browser bug | Check permissions; see the Edge fix below |
| Excel repeats or skips rows | Worksheet panes, views or hidden scrollbars | Copy the required range into Editor |
| PDF has no arrows | All-in-One PDF-reader limitation | Use an allowed export, print or manual route |
| Snagit controls appear in the image | Capture preferences or selected boundary | Check the hide-controls option for your build |
Run one clean baseline test
- Save open work and record your app versions. Keep private windows and notifications out of the capture.
- Open a finite public page in a normal-sized browser window. Avoid a live feed for this first test.
- Set browser zoom to 100 percent so both tests use the same scale.
- Scroll through once, wait for images to load, and return to the top.
- Try automatic capture and note whether arrows appear and scrolling begins.
- Repeat with manual Scrolling Capture, formerly Panoramic Capture. Move steadily in one direction.
- Inspect the beginning, seams and end at 100 percent in Editor. Compare the result with the source page.
If manual capture succeeds but automatic capture fails on the same page, use the manual result after inspecting it and investigate automatic detection. If both fail, try another simple page before making system changes. Keep a note of each result; changing several settings at once makes the cause harder to identify.
No scrolling arrows appear
TechSmith's missing-arrows support page identifies window detection, security conflicts and unsupported scrolling surfaces. A page with an inner scrolling panel may need manual capture. Missing arrows alone do not establish that Snagit is broken.
Click the content and confirm which scrollbar actually moves it. Enlarge the window if you can, then select the useful inner area rather than the whole surrounding page. Keep the scrollbar and unrelated panels outside the region where practical. Test again before changing permissions.
For the manual capture route, select a region, choose scrolling capture on the All-in-One toolbar and scroll the target yourself. Automatic capture uses the detected direction arrows. Check the selected capture mode instead of assuming an ordinary region preset will scroll.
Capture starts but stops too early
First compare a shorter section of the same page. Wait for images, expand the content you need and dismiss permitted overlays before starting. A page that changes height during capture is a poor baseline. For an endless feed, choose a defined stopping point rather than waiting for a bottom that may never arrive.
During manual capture, keep a steady pace and one direction. If the result has gaps, retry a smaller section and inspect the overlap. Do not keep extending a failed capture in the hope that the missing rows will appear at the end.
A private-window test can help, but it does not prove an extension caused the failure: cookies, login state and page content may differ. Chrome lets individual extensions run in Incognito when allowed. Check that setting. On an unmanaged device, disable only nonessential extensions you are allowed to change, then retest one at a time in the normal window. Do not bypass company browser controls.
Gaps, repeated headers and uneven seams
A sticky header can remain visible while the page beneath it moves. Exclude it from the selection, use the site's own hide option if available, or take shorter sections with enough overlap to inspect. Do not hide content that the final image is supposed to document.
Keep vertical and horizontal movement separate. TechSmith's scrolling-control troubleshooting notes advise avoiding zigzag movement and unsuitable scroll speeds. A smaller region can also keep floating controls and unrelated page elements out of the capture.
Check whether apparent blur is just Editor zoom. A tall image may be reduced to fit the window. On Windows, use View Zoom Options and Always Shrink to Fit to inspect the original size. This changes the display scale, not missing pixels. If text is still unclear at 100 percent, inspect the captured image rather than treating fit-to-window as the cause.
The preview window or control bar is captured
Check Capture Preferences for the option to hide Snagit during capture and remove its controls from completed captures. TechSmith documents this option for version 2024.1.0 and later in its scrolling-control support note. Enable it where your build provides it, then make a harmless test capture.
The version number alone does not prove the setting is enabled or that every toolbar problem is fixed. Keep controls outside the selected area where possible. If they still appear, record the build, platform and capture mode and compare the relevant release notes below.
Mac: check the correct capture permissions
For automatic scrolling, follow TechSmith's Accessibility setup: Snagit > Settings > Capture > Fix Capture Permissions. Under Scrolling Capture, choose Enable, then Enable Scrolling Capture and Open Settings. Approve the Snagit and SnagitHelper entries in Accessibility. Restart Snagit if the status does not update.
Screen Recording approval is a separate requirement for capturing the screen. TechSmith's Mac permissions instructions say to choose Quit & Reopen when prompted. Use the current app's permission dialog; do not delete random application copies or reset every permission as a first step. Our Snagit Mac permissions guide separates these permissions in more detail.
For Chrome on Mac, TechSmith's Mac scrolling-failure article also lists View > Developer > Allow JavaScript from Apple Events. It is an older, browser-specific diagnostic, not a general macOS requirement. Check whether the option exists and whether your administrator permits it; use an approved manual route if changing browser automation permissions is not appropriate.
Mac App Store builds: check the exact edition
There is conflicting documentation here. TechSmith's 2021 App Store support note says automatic arrows are unavailable. The newer Snagit 2024 App Store version history includes automatic-scrolling fixes. The old blanket restriction is therefore not a reliable description of every later build; the newer notes do not guarantee support for your particular target either.
Record whether the app came from the App Store or TechSmith, plus its full version. Use the update channel approved for that installation. If automatic capture remains unavailable, try the manual mode offered by your build or an allowed document export. Do not replace a managed installation just to test this difference.
Chrome, Edge, Firefox and difficult web pages
Compare the same public page in another permitted browser. If it works there, keep the browser version and capture mode in your notes. A logged-out page in a private window may not be equivalent to the original page. For automatic Edge capture on Mac, check the specific September 2026 fix below before changing unrelated settings.
Virtualized tables may replace off-screen rows as you scroll. That does not make stitching categorically impossible, but a long image is not proof that every row was captured. Check row identifiers and totals against the source. If completeness matters, prefer the application's permitted table export and verify its filters and row count.
For a nested panel, put the pointer over the panel and check that it, not the outer page, scrolls. Select that region for a manual attempt. If the application keeps replacing content or the result omits rows, use smaller verified sections or its own export rather than trusting image length.
For the normal setup steps, use our Snagit scrolling capture guide. If you need a different capture method for this particular page, the scrolling screenshot hub separates browser and operating-system options.
PDF readers and Excel need different fallbacks
All-in-One capture does not detect PDF-reader scrollbars, according to TechSmith's missing-arrows note. Prefer an allowed export or print route when you need the document itself. For an image in Editor, Snagit Printer is an option on supported Windows installations where the component is installed; it is not supported on Windows on ARM. Some browser PDF views or manual capture may work, but check every required page. Do not bypass document restrictions.
TechSmith's Excel troubleshooting guide lists custom views, Print Preview, hidden scrollbars and worksheet panes as limitations; Page Layout can also fail. Finish any active cell edit. With panes, automatic capture can select the upper-left pane. For a defined range, copy it and use File > New from Clipboard in Editor. Check the first and last row, columns and values in the resulting image.
Security software and managed computers
Security software can block capture, but do not start by turning off protection. Review a relevant block notification or log with your administrator or security vendor. On a managed computer, use the approved diagnostic process; a screenshot problem is not permission to bypass capture restrictions.
If support asks for a controlled security test, agree on its scope and restoration steps first and use harmless content. A successful test identifies a possible conflict, not a safe permanent exception. Ask the vendor or administrator for the narrowest supported resolution; do not leave protection disabled.
Check version-specific Windows fixes
The Windows 2026 release history records three relevant fixes: 2026.1.0 addressed manual-scrolling freezes or crashes on some virtual-machine configurations; 2026.2.0 addressed a crash with a very small selection; 2026.3.0 addressed a crash when stopping manual scrolling. Match the symptom and installed version before choosing an update.
These fixes do not establish the cause of every failed capture. Avoid unrelated driver changes or permanent administrator mode as generic remedies. If a support engineer needs an elevated test, use only the trusted installed application, harmless content and the approved procedure. Record whether that specific test changes the result.
Check Mac fixes, then prepare a useful support report
The Mac 2026 release history says version 2026.3.2, released September 2, fixed automatic scrolling capture in Microsoft Edge. Version 2026.0.1, released February 4, improved accuracy for long automatic captures. Choose a build compatible with your Mac: the current requirements list macOS Golden Gate 27, Tahoe 26 or Sequoia 15. Do not blindly install a newer major version on an unsupported OS.
If the problem remains, send support the Snagit version and install source, OS, browser or target app, automatic/manual mode, selected region and the outcome on a simple page. Include a public reproduction URL or sanitized sample. Remove account names, tokens, customer data and private document content before sharing evidence.
A useful example report would be: automatic capture has no arrows on the public test page; manual capture works; the original application stops after the first panel. Add your actual versions and permission status. This is a sample report, not a test we performed. In an archived macOS 15 discussion, users reported different results and the original poster later said the issue had disappeared without knowing why. That is a reason to record reproducible steps, not evidence for a universal fix.
Snagit scrolling capture FAQ
Why are Snagit scrolling arrows not showing?
Missing arrows can involve window detection, a nested or unsupported surface, security restrictions or Mac Accessibility permissions. Try manual capture on a simple public page and record which mode fails; missing arrows alone do not prove a broken installation.
Why does Snagit scrolling capture stop early?
Changing page content, browser configuration or the capture method can contribute. Try a finite page at 100 percent browser zoom, wait for content and compare a smaller manual capture. A private-window success does not by itself prove an extension is responsible.
How do I enable Snagit scrolling capture on Mac?
Use Snagit > Settings > Capture > Fix Capture Permissions, then the Scrolling Capture setup. Approve Snagit and SnagitHelper in Accessibility and restart if needed. Screen Recording is a separate permission; use Quit & Reopen when prompted.
What is Panoramic Capture called now?
TechSmith calls the manual route Scrolling Capture, formerly Panoramic Capture. You select a region and scroll it yourself; automatic capture instead uses detected direction arrows.
Why are headers repeated in the final image?
A fixed header or floating element may remain visible while the page moves beneath it. Exclude it where practical or capture shorter sections, then inspect the seams. Do not omit information the final image needs to document.
Can Snagit automatically scroll a PDF?
TechSmith says All-in-One capture does not detect PDF-reader scrollbars. Use a permitted export, print, browser view or manual capture. Snagit Printer requires a supported Windows installation with that component installed and does not support Windows on ARM.
Why does Snagit repeat rows in Excel?
Worksheet panes, custom views, Print Preview and hidden scrollbars can interfere with automatic capture; Page Layout can also fail. Copy the required range and use File > New from Clipboard in Editor, then verify the rows and columns.
Should I reinstall Snagit?
Not as the first step. Compare automatic and manual capture on a simple page, check the relevant permissions and version-specific fixes, and use approved browser or security diagnostics. Preserve your work and involve support before resetting or reinstalling.