ShareX Scrolling Capture Not Working: How to Fix It

ShareX offers a powerful scrolling capture feature to capture entire web pages or long documents that extend beyond the visible screen. However, sometimes this feature might not work as expected, resulting in incomplete captures, distorted images, or the capture process failing altogether. This guide provides troubleshooting steps and explanations for common issues encountered when using ShareX's scrolling capture. Before diving into specific problems, ensure you are using the latest version of ShareX, as updates often include bug fixes and improvements to the scrolling capture mechanism. If you are experiencing general issues with any type of capture, you might find solutions in our guide on

.

Why Scrolling Capture Fails

ShareX's scrolling capture works by taking multiple screenshots of a window as it scrolls down, then stitching them together. This process can be disrupted by various factors, primarily related to how the target application or web page renders its content. The most common reasons for failure include:

• Incompatible Applications: Some applications or complex web frameworks do not use standard Windows scrolling mechanisms. ShareX relies on these standard mechanisms to detect scrollable areas and simulate scrolling. Applications that render content dynamically or use custom scrollbars might not be compatible.
• Dynamic Content Loading: Web pages that load content only when it becomes visible (lazy loading) can confuse the scrolling capture process. ShareX might try to capture an area that hasn't fully loaded yet.
• Fixed Elements: Sticky headers, footers, or sidebars that remain in place while the rest of the content scrolls can interfere with the stitching process, leading to overlaps or missing sections.
• Scrolling Speed and Delays: If the scrolling is too fast or the system is under heavy load, ShareX might not capture each segment completely, resulting in partial or blank sections.
• Browser Zoom Levels: Non-standard browser zoom levels can sometimes cause misalignments during the stitching process.
• Insufficient Permissions: While less common for scrolling capture specifically, ensuring ShareX has necessary permissions to interact with other windows can prevent issues.
• Intermittent Network Issues: For web pages, slow or unstable internet connections can delay content loading, affecting the capture.

Understanding these underlying causes can help you identify the specific problem you are facing and apply the most appropriate solution. For a general overview of the feature, refer to the main scrolling screenshot guide.

Duplicated or Overlapping Rows

Duplicated or overlapping rows in your scrolling capture often indicate an issue with how ShareX detects the scrollable area or the timing of its captures. This typically happens when ShareX miscalculates the amount to scroll or when fixed elements interfere.

Adjusting Scrolling Region and Delay

1. Initiate a scrolling capture by selecting Capture > Scrolling capture from the main ShareX window, or by using your assigned hotkey.
2. When the capture area selection tool appears, carefully select the scrollable region. Ensure you are selecting only the content that actually scrolls, avoiding any fixed headers, footers, or sidebars.
3. Before starting the capture, a small window titled "Scrolling capture options" will appear.
4. Look for the "Delay between scrolls (ms)" option. If you are experiencing overlaps, try increasing this value. Start with an increase of 50-100ms (e.g., from 100ms to 150ms or 200ms). This gives the application more time to render content between scrolls.
5. Also, check the "Scroll amount (pixels)" setting. If the scroll amount is too small, it might lead to excessive overlaps. If it's too large, it might miss content. For most standard applications, the default value works well, but experimentation might be needed for unusual cases.
6. Click "Start scrolling capture" and observe the result.

Handling Fixed Elements

If the overlaps are consistently caused by a sticky header or footer, you might need to try a different approach:

• Crop After Capture: If the fixed elements are small and consistently appear, capture the entire page including the overlaps, then use the built-in ShareX Image Editor to crop out the duplicated sections manually.
• Browser Developer Tools: For web pages, temporarily hide fixed elements using your browser's developer tools (often accessible by pressing F12). Find the HTML element for the sticky header/footer and set its `display` property to `none` or `position` to `static` before initiating the scrolling capture. Remember to revert these changes afterward.

Sticky Headers and Floating Bars

Sticky headers, footers, or floating navigation bars are a common cause of issues in scrolling captures because they remain visible and in the same position even when the content behind them scrolls. ShareX attempts to stitch images based on content movement, and these static elements disrupt that process.

Workarounds for Fixed Elements

1. Adjust Capture Region: When selecting the capture area, try to exclude the sticky header or footer. Select only the main scrollable content area. This might mean you capture only the body of a web page and miss the header, but it can produce a clean scroll.
2. Increase "Fixed header height" or "Fixed footer height": In the "Scrolling capture options" window that appears after selecting your region, you can manually specify the height of a fixed header or footer in pixels. ShareX will attempt to account for these elements during stitching. You may need to experiment with the exact pixel values to match the height of the fixed element.
3. Use Browser Developer Tools (Web Pages): For web pages, this is often the most effective solution.
   • Open the web page in your browser.
   • Press F12 to open developer tools.
   • Use the element inspector (usually an arrow icon) to select the sticky header or footer.
   • In the "Styles" tab of the developer tools, find the CSS property that makes it sticky (e.g., `position: fixed;` or `position: sticky;`).
   • Temporarily uncheck or modify this property, or add `display: none;` to hide the element.
   • Once the fixed element is no longer visible, perform the ShareX scrolling capture.
   • After the capture, you can close developer tools or refresh the page to restore the original layout.
4. Scroll Manually and Stitch: As a last resort, if the automated scrolling capture consistently fails, you can manually take multiple regular screenshots, scrolling down slightly for each, and then use an image editing tool to stitch them together. This is time-consuming but guarantees full control.

Sections Missing from the Middle

When parts of your content are skipped, resulting in gaps or incomplete sections, it often points to issues with dynamic content loading, insufficient scrolling, or an aggressive scrolling speed.

Addressing Dynamic Content and Loading Delays

• Increase Delay Between Scrolls: In the "Scrolling capture options" window, significantly increase the "Delay between scrolls (ms)". If the page loads content dynamically, a longer delay gives the content more time to render before ShareX takes the next screenshot. Try values like 500ms, 1000ms (1 second), or even higher for very complex or slow-loading pages.
• Reduce Scroll Amount: Decreasing the "Scroll amount (pixels)" can sometimes help, especially if the page is loading content in smaller chunks. This ensures ShareX captures more frequent segments.
• Wait for Page Load: Before initiating the scrolling capture, ensure the entire visible portion of the page has fully loaded, including any images or embedded elements.
• Pre-scroll Manually: For some web pages with lazy loading, manually scrolling down the page once or twice before starting the ShareX capture can force the browser to load most of the content.

Checking for Hidden Scrollbars or Elements

Sometimes, the application might have internal scrollable areas that ShareX doesn't immediately detect, or content might be hidden behind an overlay.

• Identify the Correct Scrollbar: Ensure you are capturing the outer scrollbar of the main window or the primary scrollable element, not an internal scrollbar of a sub-frame or specific div.
• Close Pop-ups/Overlays: Any pop-up windows, consent banners, or overlay elements that appear during the scrolling process can obstruct content and lead to missing sections. Close them before initiating the capture.

Blank, Black, or Partial Output

A blank, black, or only partially captured image from a scrolling screenshot indicates a more fundamental problem with ShareX's ability to interact with the target window or render the content.

Common Causes and Solutions

• Hardware Acceleration Conflicts: Some applications (especially web browsers) use hardware acceleration, which can sometimes conflict with how ShareX captures their content.
  • For Web Browsers: Try disabling hardware acceleration in your browser's settings. For example, in Chrome, go to Settings > System and toggle off "Use hardware acceleration when available." Restart the browser and try the capture again.
  • For Other Applications: Check if the application has a similar setting.
• Application Rendering Issues: If the application itself is struggling to render content quickly, ShareX might capture a blank section.
  • Close other demanding applications.
  • Ensure your system resources (CPU, RAM) are not maxed out.
• Incorrect Capture Region: Double-check that you are selecting the correct scrollable region. If you select an area that doesn't actually scroll or is outside the active window, you might get a blank output.
• Administrator Privileges: While not always necessary, running ShareX as an administrator can sometimes resolve issues where it struggles to interact with other applications, particularly those running with elevated privileges. Right-click the ShareX shortcut and choose "Run as administrator."
• "Capture transparent windows" Setting: In ShareX's Task settings > Capture > Screen recorder > Screen recording options, there's a setting for "Capture transparent windows". While primarily for video, sometimes related rendering issues can affect scrolling capture. Experiment with this setting if other solutions fail. You can find more details about these kinds of options in capture settings that affect scrolling.
• Alternative Scrolling Method: In the "Scrolling capture options" window, there's a "Scrolling method" dropdown. The default is usually "Auto." Experiment with "Method 1" or "Method 2" if available, as these use different underlying techniques for scrolling.

Windows That Will Not Scroll at All

If ShareX initiates the scrolling capture but the target window simply doesn't scroll, or the capture fails immediately without producing any output, it usually means ShareX cannot detect a scrollable area or interact with the application's scrolling mechanism.

Troubleshooting Scroll Detection

1. Verify Scrollability: First, manually verify that the window or application can actually be scrolled. Use your mouse wheel, keyboard arrow keys, or the application's scrollbars to confirm. If it doesn't scroll manually, ShareX cannot scroll it either.
2. Select the Correct Scrollbar: When the capture region selection tool appears, ensure you are precisely clicking on the main vertical scrollbar of the target window. ShareX uses this to identify the scrollable element.
3. Try Different Scrolling Methods: In the "Scrolling capture options" window, change the "Scrolling method."
   • Auto (Default): ShareX attempts to automatically detect the best method.
   • Method 1: A more direct approach to simulate scroll wheel events.
   • Method 2: Might use a different API to interact with the window.
   Experiment with each method. Some applications respond better to one over another.
4. "Detect window scrollbar automatically" Option: In the "Scrolling capture options" window, ensure "Detect window scrollbar automatically" is checked unless you specifically need to manually define a region. If it's unchecked, ShareX might not correctly identify the scrollable area.
5. Compatibility with Specific Applications: Some applications (e.g., certain older Windows forms applications, specialized software, or applications with custom UI frameworks) may not expose their scrolling mechanisms in a way ShareX can interpret. In such cases, a manual multi-screenshot approach might be the only viable option.
6. Browser Specific Issues: For web browsers, ensure the page is fully loaded and that no JavaScript errors are preventing the page from scrolling normally.
7. Focus the Window: Ensure the target window is the active, focused window before you initiate the scrolling capture. ShareX needs to interact with the foreground window.

A Test Sequence to Isolate the Problem

When troubleshooting, a systematic approach can help pinpoint the exact cause of the scrolling capture failure. Follow these steps to isolate the problem:

1. Test with a Simple Web Page: Open a very simple, long web page in a common browser (e.g., a Wikipedia article with lots of text, or a news article). This reduces variables like complex JavaScript, lazy loading, or custom UI elements.
   • Perform a scrolling capture. Does it work correctly?
   • If yes, the issue is likely specific to the more complex application or web page you were originally trying to capture.
   • If no, the issue might be with your ShareX configuration or system-wide settings.
2. Experiment with "Scrolling method" and "Delay between scrolls (ms)":
   • For the simple test page (or your original target if the simple page failed), initiate a scrolling capture.
   • In the "Scrolling capture options" window, try each "Scrolling method" (Auto, Method 1, Method 2) one by one, keeping the "Delay between scrolls" at its default.
   • If none work, revert to "Auto" and increase "Delay between scrolls (ms)" incrementally (e.g., 100ms, 200ms, 500ms, 1000ms).
3. Check Browser Hardware Acceleration (if applicable): If the issue is with a web browser, disable hardware acceleration in the browser settings and restart the browser before trying the capture again.
4. Run ShareX as Administrator: Close ShareX, then right-click its shortcut and select "Run as administrator." Attempt the scrolling capture again.
5. Review ShareX Logs: In the main ShareX window, go to Application settings > Advanced > Log. This log might contain error messages or warnings related to the capture process that could provide clues. You might also find useful information by looking at the general scrolling capture documentation.
6. Test with a Different Application: Try capturing a long document in a different application, like Notepad++, a long file in File Explorer, or a long chat window. This helps determine if the problem is application-specific or a broader ShareX issue.

Frequently Asked Questions

Why does scrolling capture sometimes produce an incomplete image?

Incomplete images often result from insufficient "Delay between scrolls (ms)" in the scrolling capture options, causing ShareX to capture before content fully loads or renders. Dynamic content loading (lazy loading) on web pages is a common culprit. Ensure the target window is fully loaded and try increasing the delay.

Can ShareX capture scrolling content in any application?

No, ShareX's scrolling capture relies on standard Windows scrolling mechanisms. Applications with custom UI frameworks, older software, or certain modern web applications that use non-standard rendering techniques might not be compatible. If an application doesn't scroll normally with your mouse wheel, it's unlikely ShareX can scroll it.

How do I deal with sticky headers or footers in my scrolling captures?

The best way to handle sticky headers or footers is to either precisely select only the scrollable content area, use the "Fixed header height" or "Fixed footer height" options in the scrolling capture settings, or temporarily hide these elements using browser developer tools for web pages.

My scrolling capture results in a black or blank image. What can I do?

Black or blank images often indicate a conflict with hardware acceleration in the target application (especially web browsers). Try disabling hardware acceleration in the application's settings. Also, ensure ShareX is running with sufficient permissions (e.g., "Run as administrator") and that the capture region is correctly selected.