ShareX Captures a Black Screen in Games: How to Fix It

A ShareX game capture black screen usually means the game is being rendered in a graphics context that ShareX cannot capture through the selected method. The saved image or recording may be completely black, show only the desktop, omit the game while preserving other windows, or stop updating after you switch into fullscreen mode. The most likely causes are exclusive fullscreen rendering, mismatched permission levels, conflicts with GPU overlays, protected or anti-cheat-controlled content, and limitations involving DirectX, Vulkan, or hardware-accelerated surfaces. Work through the tests below in order. Once a test capture shows the game correctly, stop changing settings so you do not introduce a second problem.

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

Before changing ShareX or Windows settings, identify exactly when the failure occurs. This separates a game-rendering problem from an ordinary ShareX screenshot or recording problem.

1.1 Compare a desktop capture with a game capture

Start by opening an ordinary desktop application, such as File Explorer or Notepad. Use the same ShareX hotkey or capture command that fails in the game. Confirm that the resulting image or recording contains the expected content.

• If desktop content is captured correctly but the game is black, focus on fullscreen mode, graphics APIs, overlays, permissions, and game protections.
• If desktop content is also black, the problem is broader than game capture. Review the selected capture action, monitor selection, recording source, graphics driver, and ShareX configuration.
• If the game is missing but the desktop behind it appears, ShareX is capturing the display or window without receiving the game's rendered surface.
• If screenshots work but recordings fail, troubleshoot the screen-recording workflow rather than changing every screenshot setting.

Success at this stage means you can describe one repeatable failure, such as “desktop screenshots work, but the game becomes black only in exclusive fullscreen.” That detail determines which fix to try next.

1.2 Test the game in windowed or borderless windowed mode

Open the game's video or display settings and switch from exclusive fullscreen to borderless windowed mode. If borderless is unavailable, use ordinary windowed mode temporarily. Return to gameplay and take another ShareX capture.

Exclusive fullscreen can give a game more direct control over display output. A general desktop capture tool may then receive a black frame, the desktop beneath the game, or a stale image. Borderless windowed mode presents the game more like a desktop window, which is often easier for ShareX to capture.

The test succeeds when the game appears normally in the saved screenshot or recording while borderless mode is active. If that happens, you have found a practical solution. Keep using borderless mode for ShareX captures, or use a game-focused recorder if exclusive fullscreen is essential. Do not continue changing GPU and permission settings unless borderless mode creates another specific problem.

1.3 Test a still screenshot before testing video

A video recording adds more variables, including the recording source, FFmpeg configuration, frame rate, codec, audio devices, and hardware encoding. First test a single fullscreen or region screenshot. If still images work, proceed to a short recording of five to ten seconds.

If the screenshot is correct but the recording is black, the game's basic display is capturable and the remaining issue is likely in the recording method or hardware-accelerated video path. If both are black, continue with the display-mode and conflict checks below.

2. Check the ShareX Settings Directly Related to This Problem

ShareX includes several capture actions, and they do not all interact with games in the same way. Verify the active action instead of assuming that a familiar hotkey still runs the expected workflow.

2.1 Verify what the hotkey actually does

Open ShareX and review the hotkey settings. Find the shortcut you press while playing and confirm whether it starts fullscreen capture, active-window capture, region capture, screen recording, or a custom workflow. A changed or duplicated hotkey can make ShareX capture the desktop, the wrong monitor, or the foreground window after focus has shifted.

For a first test, use ShareX directly from its main window instead of relying on an in-game hotkey. Choose a simple fullscreen or region screenshot action, enter the game, and complete the capture. If this works, repair or recreate the problematic hotkey rather than changing graphics settings.

Success means both the manually started capture and the assigned hotkey produce the same correct result. Stop adjusting ShareX when the action and output are consistent.

2.2 Confirm the intended monitor and region

Multi-monitor systems can make a failed capture look like a graphics problem. A game may launch on a different monitor, switch displays after changing fullscreen mode, or alter which screen Windows considers primary. Check that the capture region or fullscreen selection covers the monitor where the game is currently displayed.

During diagnosis, avoid a tightly cropped custom region. Capture the entire game monitor once. If that image works, create a smaller region afterward. A successful full-monitor capture with a failed region capture points to selection coordinates or display scaling, not an inability to capture the game.

2.3 Separate screenshot settings from recording settings

If ShareX not working refers specifically to recording, open the screen-recording options and confirm that the intended video source is selected. Run a brief desktop recording, then repeat it with the game in borderless mode. Keep the initial test simple and disable unnecessary workflow steps such as automatic uploads or external actions.

Do not spend time changing audio devices to fix a black video frame. Audio configuration can cause silent recordings or device errors, but it does not normally determine whether a game image is visible. Address audio only after video capture works.

3. Check Windows, Graphics, Permission, and Workflow Factors

If the basic ShareX settings are correct, inspect the boundaries between the game, Windows, and the graphics driver. These checks are especially relevant when only one game fails or when the problem began after enabling an overlay.

3.1 Match the permission level of ShareX and the game

Windows separates normal and elevated applications. If a game or its launcher runs as administrator while ShareX runs normally, ShareX may be unable to interact with the game as expected. The reverse mismatch can also complicate hotkeys and automation.

Close both programs. Check the game executable and launcher properties to see whether either is configured to run as administrator. For a controlled test, start ShareX at the same permission level as the game. If the game must run elevated, launch ShareX as administrator only for the test.

Success means the capture and hotkey work when both processes use the same permission level. Use the lowest permission level that supports your workflow. Running ShareX as administrator increases what its capture, upload, and automation features can access, so do not make elevation permanent without a reason.

3.2 Disable competing GPU and game overlays temporarily

Multiple applications may try to hook into or draw over the same game. Examples include GPU recording overlays, Windows gaming overlays, chat overlays, performance monitoring displays, frame-rate tools, streaming software, and launcher overlays. These tools can conflict even if their visible overlay is hidden.

Exit competing capture and overlay applications completely, then restart the game and test ShareX again. Disable one category at a time if you need to identify the specific conflict. Common categories include:

• GPU instant-replay and recording features
• Game launcher overlays
• Chat and voice overlays
• Frame-rate counters and performance monitoring tools
• Other screenshot, streaming, or recording applications
• Color filters, post-processing injectors, and visual enhancement tools

The fix is confirmed when the game appears after one conflicting tool is closed or its overlay is disabled. At that point, stop changing ShareX. Re-enable other tools individually and leave only the confirmed conflict disabled during capture.

3.3 Understand DirectX, Vulkan, and hardware acceleration limits

Modern games commonly render through DirectX or Vulkan and may use fullscreen presentation methods that do not behave like normal desktop windows. ShareX is highly capable for screenshots, desktop recording, OCR, uploads, editing, hotkeys, and automation, but it is not a universal game-hooking recorder. A capture method that reads the desktop can miss frames presented through a protected, exclusive, or otherwise inaccessible graphics surface.

This is not necessarily a broken ShareX installation. If borderless mode works but exclusive fullscreen remains black, the capture-method limitation has been demonstrated. Driver updates may change behavior, but repeatedly reinstalling ShareX is unlikely to make a general desktop capture method behave like a dedicated game capture hook.

Hardware acceleration can also explain why menus, launchers, or overlays appear while the main game scene remains black. The visible components may be rendered through different paths. Use borderless mode first. If that is not acceptable, move to a recorder designed to capture games through a game-specific source.

3.4 Respect anti-cheat and protected-content restrictions

Some multiplayer games use anti-cheat systems that restrict injection, hooks, overlays, automation, or access to rendered frames. Protected video and some secure graphics surfaces can produce similar black results. Do not disable anti-cheat, modify protected files, inject unapproved software, or attempt to bypass capture restrictions just to make ShareX work.

Check the game's official support information and rules before using overlays, automation, or capture utilities. Even harmless tools can be treated differently across games and competitive platforms. If the game intentionally blocks the capture path, use an officially supported recording feature, a permitted platform capture tool, or external capture hardware.

Success here may mean determining that ShareX should not be used with that title. Knowing when to stop is part of safe troubleshooting.

3.5 Check graphics assignment on multi-GPU systems

Laptops and some desktops can run the game on a high-performance GPU while ShareX or the desktop compositor uses another graphics adapter. This does not always cause failure, but it can contribute to black or inconsistent capture behavior.

In Windows graphics settings, inspect the GPU preference assigned to the game and ShareX. For a temporary test, place them on the same GPU preference, restart both applications, and capture the game in borderless mode. Change only one assignment at a time so the result remains meaningful.

If matching the GPU resolves the black frame, retain that assignment only after checking power use and overall performance. If it makes no difference, restore the previous preference rather than accumulating unnecessary system changes.

3.6 Keep uploads and destinations out of the first test

A successful local capture can appear to fail if a later workflow step uploads the wrong file, opens an old destination, or triggers an external action. During diagnosis, save the result locally and inspect the exact file immediately.

Network availability affects uploads, not whether the original game frame was captured. Likewise, a destination-folder permission problem may prevent saving, but it does not usually turn a valid frame black. Confirm the local image or video first, then restore upload and automation tasks.

4. Run a Clean Temporary Test With Minimal ShareX Settings

A clean test helps distinguish a graphics limitation from a complicated workflow. The goal is not to erase your configuration. Instead, temporarily remove optional steps from one capture task.

1. Close other recorders, overlays, monitoring tools, and unnecessary game launchers.
2. Set the game to borderless windowed mode.
3. Run ShareX and the game at the same permission level.
4. Use a basic fullscreen or region screenshot action.
5. Save the image locally without uploading it or launching external tools.
6. Inspect the newly created local file.
7. If the screenshot works, record a five-to-ten-second local video.
8. Add overlays, uploads, and custom workflow steps back one at a time.

The clean test succeeds when a newly saved local file clearly shows live game content. Once it succeeds, preserve that working baseline. Reintroduce only the features you need, testing after each change. The first reintroduced feature that restores the black screen is the likely conflict.

If the minimal screenshot remains black in borderless mode, test another game or a hardware-accelerated application. One failing title suggests a game-specific protection or renderer issue. Several failing games suggest a broader driver, GPU-assignment, permission, or capture-method problem.

5. Check Task History, Errors, and Recent Workflow Output

ShareX task history is useful when the capture seems to disappear, the wrong file opens, or a post-capture action fails. Locate the most recent task and verify its timestamp, file path, dimensions, and thumbnail. Open the local file directly rather than relying on an uploaded copy or an image cached in another application.

A full-size black image means a capture was completed but the game pixels were unavailable. A desktop image means the capture source saw the surface behind the exclusive game. A missing or zero-length output suggests a save, encoding, or workflow failure instead of the classic fullscreen black-frame problem.

For recording failures, note any displayed FFmpeg or device error exactly as written. An encoder initialization error, unavailable device, or invalid output path requires a different fix from a completed video containing black frames. Preserve the error text before restarting because it is more useful than a general statement that ShareX is not working.

Also check whether recent files are being saved somewhere unexpected. Custom workflows can change destinations, naming patterns, or post-capture actions. Once you find a correctly timestamped local file, evaluate its visual content before troubleshooting uploads, clipboard actions, or external editors.

6. Quick Fix Checklist

• Confirm that ordinary desktop screenshots work.
• Switch the game from exclusive fullscreen to borderless windowed mode.
• Test one still screenshot before troubleshooting video recording.
• Verify the ShareX hotkey runs the intended capture action.
• Capture the entire game monitor to rule out region-selection errors.
• Run ShareX and the game at the same permission level.
• Close GPU, chat, launcher, monitoring, and recording overlays.
• Save locally before enabling uploads or external workflow actions.
• Test matching GPU preferences on systems with multiple graphics adapters.
• Do not bypass anti-cheat or protected-content controls.
• Use a game-focused recorder if exclusive fullscreen capture is required.

Stop troubleshooting when a repeatable configuration captures the correct game image. For many users, borderless windowed mode plus disabled competing overlays is the stable endpoint. More changes are not better once the symptom is resolved.

7. Frequently Asked Questions

7.1 Why does ShareX capture my desktop instead of the fullscreen game?

The game is likely using an exclusive or otherwise separate graphics presentation path. ShareX captures the desktop surface behind it, so the resulting image shows the desktop instead of the visible game. Switch the game to borderless windowed mode and test again. If that works, use borderless mode or a game-focused capture tool.

7.2 Why is the ShareX screenshot completely black?

A full black image often means the capture completed but could not access the game's rendered frames. Common reasons include exclusive fullscreen, a DirectX or Vulkan presentation limitation, protected content, anti-cheat restrictions, GPU mismatch, or another overlay holding a conflicting capture hook.

7.3 Can running ShareX as administrator fix game capture?

It can help when the game runs as administrator and ShareX does not. Match their permission levels for a controlled test. Do not automatically run ShareX elevated all the time, especially if you use automatic uploads, custom commands, or other automation. Use only the permissions required for the task.

7.4 Should I disable anti-cheat to make ShareX work?

No. Do not disable, bypass, or interfere with anti-cheat protections. Doing so can violate game rules, create security risks, or lead to account penalties. Use an officially supported capture method, borderless mode if permitted, or a game-focused recorder accepted by the game's publisher.

7.5 Why do screenshots work while ShareX recordings are black?

Still capture and video recording can use different paths. The recording workflow also depends on its selected source, FFmpeg, codecs, frame timing, and hardware acceleration. First confirm a borderless screenshot, then make a short local recording with minimal settings. If only recording fails, focus on the recording source and any displayed encoder errors.

7.6 When should I use another recorder instead of ShareX?

Use a game-focused recorder when you need reliable exclusive-fullscreen capture, high-frame-rate gameplay recording, game-specific hooking, or advanced audio-track management. ShareX remains an excellent choice for screenshots, desktop clips, OCR, quick editing, uploads, hotkeys, and automated workflows. Choosing a specialized recorder for gameplay is not an admission that ShareX is broken. It is the appropriate response when the game's rendering method falls outside a desktop capture workflow.