ShareX Screen Recording Is Black: How to Fix It

A ShareX screen recording black screen usually means the capture started successfully, but ShareX could not obtain the expected video frames. The finished file may be completely black, show only the pointer, capture the wrong monitor, or display only part of the selected area. The most likely causes are an incorrect region or display selection, protected video, hardware-accelerated content, an exclusive fullscreen application, mismatched administrator privileges, HDR or graphics driver behavior, or an unsuitable capture method for the target application.

Start with a short recording of the Windows desktop and Notepad. This simple test separates a general ShareX problem from an application-specific capture restriction. Once a test recording works, stop changing unrelated settings and test the original application again after applying only the relevant fix.

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

Before changing ShareX, confirm exactly what is black. This guide concerns black or blank video produced by screen recording. A black still screenshot can sometimes have the same cause, particularly protected or hardware-accelerated content, but screenshot problems can also involve different capture methods.

1.1 Record the desktop and Notepad first

Use a controlled test that does not involve streaming video, a game, a browser, or confidential software:

1. Open Notepad and enter a few lines of visible text.
2. Place the Notepad window on the monitor you intend to capture.
3. Start a ShareX screen recording and select a small region containing Notepad and part of the desktop.
4. Move the Notepad window slightly during the recording.
5. Stop after approximately five to ten seconds and open the saved video.

Success means the recording shows the desktop, the text, and the window movement. If this test works, ShareX can record normal desktop frames. The original problem is probably tied to the target application, its rendering mode, protected content, fullscreen behavior, HDR, or privilege level. Stop modifying ShareX globally and proceed to the section matching that application.

If the Notepad test is also black, focus on the selected region, monitor arrangement, recording configuration, graphics environment, permissions, and output file. Do not begin by changing browser or game settings because those cannot explain a black Notepad recording.

1.2 Identify the exact failure pattern

• Everything is black: Check the capture area, display configuration, recording setup, HDR, drivers, and permissions.
• The desktop appears but video is black: Suspect protected content or hardware acceleration.
• A window is visible until it becomes fullscreen: Suspect exclusive fullscreen rendering.
• Only part of the expected screen appears: Check the selected region, monitor coordinates, scaling, and display arrangement.
• The preview works but the saved file looks black: Test another media player and inspect the actual output file.
• The pointer appears over a black background: The pointer and desktop frames may be captured through different paths. Investigate accelerated or protected rendering.

2. Check the ShareX Settings Directly Related to This Problem

2.1 Select the intended monitor or region again

A stale or incorrect region can record empty coordinates, the wrong display, or only part of a window. This is especially likely after disconnecting a laptop from a dock, changing the primary monitor, rotating a display, rearranging monitors, or changing Windows display scaling.

Start a new recording and deliberately select a visible region rather than reusing a previous region. Keep the first test entirely inside one monitor. Avoid drawing a region across displays that use different scaling percentages or resolutions.

Success means the recorded boundaries match the rectangle you selected. If they do, stop adjusting the region. If the video captures a neighboring monitor or an offset area, open Windows Display settings, identify the monitors, and arrange them so their on-screen positions match their physical layout. Then restart ShareX and select the region again.

2.2 Verify that screen recording is actually starting

ShareX uses its configured screen-recording workflow to capture and encode video. Confirm that you selected screen recording rather than an unrelated capture action and that the recording visibly starts and stops. Check whether ShareX creates a new video file after the test.

If no file appears, the issue is not merely black video. The recording or encoding process may have failed before producing useful output. Review the task history and application log instead of repeatedly recording the same region.

2.3 Test a small region before a full display

A short, modestly sized recording is easier to diagnose than a long, multi-monitor capture. Select Notepad and a section of the desktop on one display. This reduces the influence of mixed scaling, unusual resolutions, high frame-processing demands, and cross-monitor coordinate problems.

Once the small test works, expand to a full monitor. If the full-monitor test fails while the small region works, investigate display layout, resolution, HDR, and graphics performance rather than changing every ShareX option.

2.4 Confirm the output file and playback application

Open the newest file from ShareX task history or its destination folder rather than an older file with a similar name. Then play the file in another reputable player or browser. A decoding or rendering problem in one media player can make a valid recording appear black.

Success means another player displays the recording correctly. In that case, ShareX captured the video and the original playback application is the problem. Stop changing ShareX and troubleshoot or replace that player.

3. Check Windows and Application Factors

3.1 Protected video and DRM limitations

Subscription streaming services, purchased films, protected browser players, and some corporate applications may deliberately prevent screen capture. The desktop, browser controls, captions, or pointer might be visible while the protected video area remains black. This is expected behavior when the content uses digital rights management or a protected video path.

ShareX settings cannot reliably or appropriately override content protection. Confirm the diagnosis by recording a normal webpage or a local, unprotected test video. If ordinary content records but one protected title remains black, stop troubleshooting ShareX. Use the service's supported offline, sharing, or accessibility features where available, and respect copyright and usage terms.

3.2 Hardware acceleration in browsers and media players

Browsers, conferencing tools, and media players can render video through the GPU in a way that ordinary desktop capture does not receive correctly. The application frame and controls may appear while the video surface is black.

Temporarily disable hardware acceleration in the affected application, fully close it, reopen it, and record a short, non-protected test. The setting is commonly found under system, performance, advanced, display, or graphics preferences. Exact wording varies by application.

Success means the video surface appears in the new recording. You can leave hardware acceleration disabled while recording if application performance remains acceptable, or re-enable it afterward. If disabling acceleration makes no difference, turn it back on and continue. Avoid leaving unrelated performance settings changed without evidence.

Hardware acceleration does not defeat DRM. If only protected streaming content remains black, the protection is the likely cause even when acceleration is disabled.

3.3 Exclusive fullscreen games

Some games use exclusive fullscreen rendering or graphics APIs that are not dependable through a general desktop-region recorder. ShareX may capture a black frame, a frozen image, the desktop behind the game, or nothing after the game switches display modes.

Change the game to windowed or borderless windowed mode and record a short segment. If borderless mode works, keep that mode for ShareX recordings. Also try matching the game and ShareX privilege levels.

If the game must run in exclusive fullscreen, or if you need dependable high-frame-rate gameplay recording, use software designed for game capture. OBS Studio provides dedicated game and window capture sources, while GPU vendors offer recorders integrated with their graphics software. ShareX is excellent for screenshots, quick region recordings, uploads, OCR, hotkeys, and automation, but it is not always the best tool for demanding game capture.

3.4 Match administrator privilege levels

Windows separates applications running at different integrity levels. If the target program runs as administrator but ShareX does not, ShareX may be unable to interact with or capture the target as expected.

First, close the target and reopen it normally if administrator access is unnecessary. If it genuinely requires elevation, close ShareX and run ShareX as administrator for a temporary test. Do not permanently elevate either program unless its function requires it.

Success means the elevated target becomes visible in the recording when both applications run at matching privilege levels. Stop there. If the Notepad test was already successful and matching privileges changes nothing, return both programs to their normal launch mode and examine rendering or fullscreen behavior instead.

3.5 HDR and mixed-display configurations

HDR can complicate desktop capture, color conversion, and playback. A recording may appear black, extremely dark, washed out, or limited to one display, particularly in systems that mix HDR and standard dynamic range monitors.

Temporarily turn off HDR for the monitor being recorded in Windows Display settings, close and reopen the target application, and make a new test. Keep the capture region on that monitor. If the recording becomes visible, HDR or its interaction with the graphics stack is involved.

You can record with HDR disabled, move the target to a non-HDR display, or use a recorder with explicit support for your HDR workflow. If disabling HDR does not change the result, restore your preferred setting rather than treating HDR as the cause.

3.6 Graphics drivers and GPU selection

Graphics driver defects or unusual hybrid-GPU arrangements can affect screen capture. This is more plausible when the issue began after a driver or Windows update, affects multiple recording tools, or changes depending on which monitor or application is captured.

Install a stable graphics driver from Windows Update or the official support channel for your GPU or computer manufacturer. Restart Windows after installation. If the problem began immediately after a driver update, consult the manufacturer's supported rollback or clean-install guidance.

On laptops with integrated and discrete graphics, the target application and recorder may run on different GPUs. Windows graphics preferences can assign an application to a power-saving or high-performance GPU. Test consistent GPU assignments only after simpler checks succeed or fail. Record Notepad after each change so you can identify whether the graphics adjustment actually helped.

3.7 Audio, network, and destination factors

Audio and network settings rarely cause video frames themselves to become black. However, a failed recording, interrupted upload, cloud preview, or incomplete output can be mistaken for a capture problem.

• Test without depending on an automatic upload. Open the local file first.
• Confirm that the destination drive has free space and is writable.
• Use a short recording so the file closes and saves quickly.
• If audio configuration causes the recording process to fail, temporarily test video without optional audio sources.
• Do not judge the recording solely from a website thumbnail or cloud preview.

If the local file plays correctly, the capture is successful. Troubleshoot the upload destination, network, or web preview separately.

4. Run a Clean Temporary Test With Minimal ShareX Settings

A minimal test helps determine whether a custom workflow, automation action, upload step, destination rule, or hotkey sequence is interfering with the result. The objective is not to erase your setup. It is to create the simplest possible path from capture to local playback.

1. Exit unnecessary overlays, remote-desktop tools, game overlays, and other recorders.
2. Open ShareX and initiate a basic screen recording manually.
3. Select a small region containing the Windows desktop and Notepad.
4. Record for five to ten seconds.
5. Stop the recording and open the exact local output from task history.
6. Repeat with the target application in windowed mode.
7. Enable only one relevant feature or workflow step at a time.

If the minimal Notepad recording works, ShareX itself is functioning. Reintroduce your normal region, audio source, target application, upload action, and automation steps individually. The first change that brings back the black output identifies the area requiring attention.

If the minimal test remains black, restart ShareX and Windows before retesting. Then verify display selection, HDR, drivers, and privilege levels. Reinstalling software should be a later step because it does not resolve DRM restrictions or an application's exclusive fullscreen rendering.

5. Check Task History, Logs, and Recent Output

ShareX task history helps confirm whether a recording was created, where it was saved, and which output belongs to the latest attempt. Open the most recent local file directly. Check its creation time and file size. A tiny or zero-byte file suggests that recording or encoding did not complete, which is different from a normally sized file containing black frames.

When the process fails, review ShareX's application log for messages generated at the time of the test. Look for references to recording startup, encoding, missing components, invalid paths, permissions, or write failures. Copy the exact message before changing settings. Exact error text is more useful than reporting only that ShareX is not working.

If a valid local video exists but an uploaded copy is unavailable or black only in an online preview, the recording stage succeeded. Investigate the upload service's processing, supported formats, or preview behavior. If both local and uploaded files contain the same black frames, return to capture-related causes.

6. Quick Fix Checklist

• Record the desktop and Notepad to separate general capture problems from application-specific ones.
• Select a fresh region entirely inside the intended monitor.
• Open the newest local file from task history and test another player.
• Do not expect ShareX to capture DRM-protected video.
• Temporarily disable hardware acceleration in the affected browser or media player.
• Run games in borderless windowed mode instead of exclusive fullscreen.
• Run ShareX and the target application at matching privilege levels.
• Temporarily disable HDR on the captured monitor.
• Update or, when appropriate, roll back the graphics driver using official guidance.
• Test locally without uploads, overlays, or complex automation.
• Use OBS Studio or a dedicated game recorder when the workload requires specialized capture.

Stop changing settings as soon as a repeatable test succeeds. Confirm the fix with two short recordings, then restore unrelated settings. This preserves a clear explanation of what solved the problem and prevents new issues.

7. Frequently Asked Questions

7.1 Why does ShareX record the browser but not the video?

The browser interface and video surface may use different rendering paths. Hardware acceleration can place video on a GPU-rendered surface that desktop capture does not receive correctly. Protected streaming video can also intentionally appear black. Test an ordinary webpage and an unprotected local video. If disabling browser hardware acceleration fixes the unprotected video, acceleration was involved. If only protected content remains black, ShareX cannot provide an appropriate workaround.

7.2 Why does ShareX record only part of my screen?

The selected region may belong to the wrong monitor coordinates, especially after changing display arrangement, scaling, docking, rotation, or resolution. Select a new region inside one monitor and verify the Windows display layout. Mixed scaling across monitors can also contribute to offsets. Once a single-monitor test works, expand the region carefully.

7.3 Why is my game black in ShareX?

The game may use exclusive fullscreen rendering or a graphics path unsuitable for general desktop recording. Switch to borderless windowed mode and match the privilege levels of ShareX and the game. For reliable fullscreen gameplay, high frame rates, or scene-based production, OBS Studio or a GPU vendor's game recorder is generally more appropriate.

7.4 Can audio settings cause a black recording?

Audio settings usually do not turn valid video frames black. They can, however, prevent a recording process from starting or completing if an audio device or recording configuration fails. Test a short local recording without optional audio. If video then works, add audio sources back one at a time.

7.5 Should I reinstall ShareX immediately?

No. Reinstallation will not fix DRM protection, exclusive fullscreen games, an incorrect region, mismatched privileges, or hardware-accelerated video. Run the Notepad test and check the relevant factors first. Consider reinstalling only when basic recording fails, logs indicate damaged or missing components, and simpler configuration and Windows checks have not helped.

7.6 When should I stop troubleshooting ShareX and use another recorder?

Use another recorder when the desktop and Notepad record correctly but the target workload consistently requires specialized capture. Examples include exclusive fullscreen games, complex scenes, multiple audio tracks, high-frame-rate gameplay, or an HDR production workflow. OBS Studio and dedicated GPU game recorders are built for those scenarios. Changing tools will not bypass protected-content restrictions.