ShareX Fullscreen Screenshot Is Black: How to Fix It

A ShareX fullscreen screenshot may come out completely black, blank, or partly black even though the desktop looked normal when you pressed the capture hotkey. The cause usually falls into one of several categories: protected video that blocks capture, hardware-accelerated content displayed on a separate graphics layer, an exclusive fullscreen game, a permission mismatch, an HDR or graphics driver issue, or a ShareX workflow that processes the image after capture. The fastest way to fix the problem is to identify exactly which content turns black before changing multiple settings.

1. Confirm the Symptom and Reproduce It With a Simple Test

Begin by determining whether ShareX fails on the ordinary Windows desktop or only inside a particular application. This distinction prevents you from treating a protected video or game limitation as a general ShareX problem.

1.1 Test a normal desktop capture

Minimize games, browsers, media players, remote desktop tools, and streaming applications. Display the Windows desktop with a simple application such as Notepad open, then use ShareX to take a fullscreen screenshot.

Open the resulting image directly from ShareX task history or its destination folder. Do not rely only on a thumbnail, upload preview, or clipboard preview.

• If the desktop and Notepad appear normally, ShareX can capture the desktop. Stop changing global capture settings and investigate the specific application that becomes black.
• If the entire image is black, focus on permissions, display configuration, HDR, graphics drivers, and ShareX capture settings.
• If only one rectangle is black, that application probably uses protected content, hardware acceleration, an overlay, or a separate graphics surface.
• If the saved file is correct but an uploaded or edited copy is black, the capture succeeded and the later workflow is responsible.

1.2 Compare fullscreen, region, and window capture

Capture the same visible content three ways: fullscreen capture, region capture around the application, and window capture. This comparison reveals whether the failure is tied to the entire display, ShareX's method of selecting a window, or the application's rendered content.

If region capture works while window capture does not, use region capture as a practical workaround and investigate the application's rendering mode. If every method shows the same black area, ShareX may not have access to the pixels being displayed. If only fullscreen capture fails, check monitor selection, HDR, multiple-display behavior, and the fullscreen capture configuration.

Success means that a newly saved image contains the expected desktop and application pixels. Once one capture method works reliably, stop changing unrelated settings. You already have a usable workaround and can isolate the remaining issue without destabilizing the rest of your ShareX setup.

2. Check the ShareX Settings Directly Related to This Problem

ShareX supports hotkeys, automated after-capture tasks, image effects, uploads, OCR, and multiple destinations. That flexibility can make a successful capture appear broken if a later action modifies the image or if the hotkey runs a different task than expected.

2.1 Verify what the hotkey actually does

Open ShareX hotkey settings and inspect the shortcut used when the black image appears. Confirm that it starts a fullscreen capture rather than screen recording, active-window capture, a custom workflow, or a task with unexpected overrides.

For testing, start a fullscreen capture directly from the main ShareX window. This bypasses confusion caused by duplicate shortcuts, another screenshot utility intercepting the key, or a custom hotkey profile.

Success means that the direct capture and hotkey capture produce the same correct result. If direct capture works but the hotkey does not, repair or recreate that hotkey rather than changing display or graphics settings.

2.2 Temporarily disable after-capture processing

Review the enabled after-capture tasks. Image effects, annotation steps, clipboard operations, file conversions, custom commands, and external applications can alter or replace a valid screenshot. Temporarily reduce the workflow to saving the image to a file and showing it in task history.

Also check whether an image effect preset contains a background, transparency, crop, resize, or other operation that could make the output look empty. The objective is not to permanently remove your automation. It is to determine whether the original captured bitmap is correct.

If the minimally processed file looks normal, re-enable tasks one at a time. Stop as soon as the black output returns. The last enabled action is the likely cause.

2.3 Confirm the correct monitor and image file

On a multi-monitor system, a fullscreen action may capture a different display from the one you expected, especially after monitors have been disconnected, rearranged, or switched between duplicate and extended modes. Move the pointer to the target monitor before triggering the capture when the configured behavior depends on the active screen.

Open the saved file from its actual folder and confirm its dimensions. A tiny image, an old file, or a capture matching another monitor's resolution indicates a selection or workflow problem rather than black rendering.

3. Check Windows, Applications, and Display Factors

If ShareX captures the ordinary desktop correctly but a specific application is black, the next steps depend on what that application is displaying. Games, protected video, browsers, media players, and HDR displays have different failure modes.

3.1 Protected video and DRM limitations

Streaming services and other rights-managed applications can mark video as protected. Windows, the graphics stack, or the application may deliberately prevent those frames from appearing in screenshots and screen recordings. The result can be a black video rectangle while browser controls, subtitles, menus, or the surrounding desktop remain visible.

This is not necessarily a ShareX defect. A screenshot program cannot reliably or appropriately bypass protection enforced by the operating system, graphics driver, browser, player, or content provider. ShareX may be technically unable to access those pixels, and capturing or redistributing protected material may also violate applicable terms or laws.

Test the same browser or player with an ordinary unprotected webpage, local image, or permitted test video. If normal content captures correctly but protected playback remains black, stop troubleshooting ShareX. Use an authorized download, a publisher-provided still, a permitted sharing feature, or another lawful source instead.

3.2 Hardware acceleration in browsers and media players

Browsers and media players often use GPU acceleration to render video and animation efficiently. In some configurations, the visible content is placed on an overlay or graphics surface that a screenshot method does not receive correctly. This can produce a black or transparent rectangle even when the rest of the screen is captured.

As a diagnostic test, disable hardware acceleration in the affected browser or player, fully close the application, reopen it, and capture ordinary non-protected content again. The exact setting name varies, but it is commonly found under system, performance, graphics, or advanced settings.

If the new screenshot contains the previously black content, acceleration or an overlay was involved. You can leave acceleration disabled if performance remains acceptable, use region capture, update the application and graphics driver, or re-enable acceleration and use another permitted capture workflow. Disabling acceleration will not defeat DRM, so protected video may remain black by design.

3.3 Exclusive fullscreen games

A game running in exclusive fullscreen mode can take direct control of a display and use a presentation path that ordinary desktop screenshot tools cannot capture reliably. The screenshot may be black, show the desktop behind the game, or contain an outdated frame.

Change the game's display mode to borderless windowed or windowed, then test ShareX again. Also try the game's built-in screenshot command or an authorized platform capture feature. Built-in tools are often better integrated with the game's rendering pipeline.

Success means that a borderless or windowed capture shows the current game frame. If it does, keep that mode for ShareX captures or use the game's own screenshot function. Do not continue changing ShareX settings when only exclusive fullscreen mode fails.

3.4 Administrator permission mismatch

Windows can restrict interaction between processes running at different integrity levels. If the target application is running as administrator but ShareX is not, ShareX hotkeys, window detection, or capture behavior may be inconsistent.

Check whether the affected application displays an elevation prompt when launched or has the Run as administrator option enabled. For a controlled test, close both programs. Start both normally without elevation and try again. If the target must run elevated, test ShareX at the same permission level.

Running ShareX as administrator all the time increases its privileges and is usually unnecessary. Use matching elevation only when the mismatch is confirmed. Success means the same capture works when both applications run at the same integrity level.

3.5 HDR, multiple GPUs, and graphics drivers

HDR changes how Windows and the display pipeline represent brightness and color. Driver defects, mixed HDR and SDR monitors, multiple GPUs, docking stations, and display overlays can contribute to black, washed-out, or partially missing captures.

First, capture a normal desktop with HDR enabled. Then temporarily turn HDR off in Windows display settings and repeat the same capture. If disabling HDR fixes it, update the graphics driver from the GPU or computer manufacturer and install applicable Windows updates before testing HDR again.

Laptops may route applications through an integrated GPU while an external monitor is connected through a discrete GPU or dock. Close graphics overlay tools, performance overlays, color utilities, and remote-display software for a temporary test. Avoid changing several GPU options simultaneously because that makes the result difficult to interpret.

Success means the same desktop test produces a correctly rendered image after one specific change. Once identified, retain that change or update the relevant driver. If HDR makes no difference, turn it back on if you normally use it and move to the next cause.

3.6 Destination and workflow factors

Network access and audio settings generally do not determine whether still-image pixels are black. They matter only when the screenshot is correct locally but fails during upload, opens incorrectly from a remote destination, or appears black after an external tool processes it. Audio devices are relevant to screen recordings, not ordinary screenshots.

Always compare the local file created immediately after capture with the uploaded or edited result. If the local file is correct, do not troubleshoot HDR, games, or desktop capture. Check the uploader, destination response, custom command, file conversion, or application used to view the image.

4. Run a Clean Temporary Test With Minimal ShareX Settings

A clean test helps separate ShareX configuration from Windows or application rendering. You do not need to delete your normal configuration to perform it.

1. Close the application that produces the black area.
2. Pause custom uploaders, external commands, image effects, and unnecessary after-capture actions.
3. Set the test workflow to capture the fullscreen image and save it locally.
4. Open Notepad on the normal Windows desktop.
5. Start fullscreen capture from the ShareX main window rather than a hotkey.
6. Open the newly created file from task history.
7. Repeat with region capture and window capture.
8. Open the problematic application and repeat the comparison.

If the clean desktop captures are black, investigate permissions, HDR, displays, drivers, and competing overlay software. If the desktop works but the application fails, focus on protected content, acceleration, exclusive fullscreen, or application-specific rendering. If the clean workflow works but your normal workflow fails, restore automation one task at a time.

Keep a short record of each test and change only one factor between attempts. Stop when the expected content appears consistently in two consecutive captures. Further random changes can hide the real fix or create new ShareX troubleshooting problems.

5. Check Task History, Logs, and Recent Output

Task history can show whether ShareX created a local file, copied an image, ran an action, or attempted an upload. Open the most recent task that corresponds to your test and verify its timestamp, filename, dimensions, and destination.

A black image with the correct dimensions suggests that the capture operation completed but did not receive the expected pixels. A missing file or task points toward a hotkey, permission, destination, or workflow failure. A correct local image followed by a bad uploaded image points toward post-processing or upload behavior.

Review relevant error messages when ShareX reports a failed task. Upload authentication errors, inaccessible folders, blocked custom commands, and network failures can explain missing output, but they do not normally explain a correctly saved image whose pixels are black. Keep the diagnosis tied to the observed symptom.

If the issue began after changing a hotkey, image effect, application display mode, monitor arrangement, graphics driver, HDR setting, or overlay utility, reverse that single change and repeat the desktop test. Recent changes are more useful than broadly resetting unrelated preferences.

6. Quick Fix Checklist

• Capture Notepad on the desktop to determine whether ShareX works outside the affected application.
• Compare fullscreen, region, and window capture using the same visible content.
• Open the original local file rather than relying on an upload or clipboard preview.
• Confirm that the hotkey runs fullscreen capture and not a custom task.
• Temporarily save locally without image effects, commands, uploads, or other processing.
• Expect DRM-protected video to remain black when capture is intentionally blocked.
• Test hardware acceleration off for ordinary, non-protected browser or player content.
• Switch games from exclusive fullscreen to borderless windowed or windowed mode.
• Run ShareX and the target application at matching permission levels.
• Temporarily disable HDR and retest the same normal desktop scene.
• Update graphics drivers if HDR, overlays, multiple GPUs, or external displays are involved.
• Stop changing settings as soon as the same capture succeeds consistently.

7. Frequently Asked Questions

7.1 Why is only the video black in my ShareX screenshot?

The video may be DRM-protected or rendered through a hardware overlay that is not available to the screenshot operation. If browser controls and the surrounding desktop appear but the video rectangle is black, test ordinary non-protected content. Protected playback may intentionally block capture, in which case there is no appropriate ShareX setting that guarantees access.

7.2 Why does region capture work when fullscreen capture is black?

The two operations may interact differently with monitor selection, window detection, display scaling, or the application's rendering path. Region capture is a valid workaround when it consistently produces the expected image. You should then focus on fullscreen display configuration rather than resetting all ShareX settings.

7.3 Can disabling hardware acceleration fix the problem?

It can fix black captures caused by GPU overlays or accelerated rendering in a browser or media player. It will not necessarily capture protected video because DRM restrictions are separate. Restart the application after changing acceleration, test non-protected content, and re-enable the setting if it makes no difference.

7.4 Why is a fullscreen game black but the desktop works?

The game may use exclusive fullscreen rendering that bypasses ordinary desktop composition. Switch it to borderless windowed mode and test again. If that works, use borderless mode, the game's screenshot feature, or an authorized platform capture tool.

7.5 Should I always run ShareX as administrator?

No. Elevation is useful only when the target application must run as administrator and a permission mismatch is causing the failure. Running both programs normally is preferable when possible. Do not grant permanent elevated access merely as a general screenshot fix.

7.6 What should I do if ShareX still captures the entire desktop as black?

Repeat the minimal local-save test, verify the selected monitor, match application permissions, disable HDR temporarily, close overlays, and update the graphics driver. If multiple ShareX capture methods fail on a plain desktop while Windows' own screenshot tools also fail, the evidence points toward the Windows display or graphics stack rather than a ShareX workflow.