ShareX Transparent Window Capture Has a Black Background: How to Fix It

You capture a transparent, rounded, acrylic, or layered window with ShareX, but the saved image shows a black, solid, or otherwise incorrect background. This is different from an ordinary black-screen screenshot. The application itself may be visible while the pixels around it, behind it, or inside its translucent areas are wrong. The usual causes are Windows compositor behavior, the selected capture method, GPU-rendered surfaces, lost PNG transparency, or an image viewer that displays transparent pixels as black. Work through the tests below in order. Once a test produces the result you need, stop changing settings and save that working workflow.

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

Begin by identifying exactly where the black background appears. This prevents you from troubleshooting screen-capture failures when the real issue is alpha transparency or a destination application that cannot preserve it.

1.1 Inspect the saved file before copying or uploading it

Save the capture as a PNG and open the file directly in more than one transparency-aware editor or viewer. In an image editor, transparent pixels are commonly represented by a checkerboard. Some basic viewers instead draw those pixels over black, white, or a theme-dependent color.

If an editor shows a checkerboard but another program shows black, ShareX probably captured transparency correctly. The display or paste destination is adding the visible background. Stop changing ShareX capture settings and adjust the destination workflow instead.

If the PNG itself contains opaque black pixels, continue with the capture-method checks. You can confirm this by placing a bright colored layer beneath the captured image. True transparent areas reveal the color underneath. Opaque black pixels do not.

1.2 Separate transparency problems from black-screen problems

A transparency problem usually has one of these patterns:

• The main window content is visible, but rounded corners become black squares.
• Acrylic, glass, blur, shadows, or translucent areas turn black or solid.
• The captured window is correct, but the area outside its shape has the wrong color.
• The PNG looks correct in one editor and wrong after pasting into another application.

An ordinary black-screen problem is different. In that case, a video, game, browser surface, or entire application may be completely black because its rendered surface was unavailable to the capture path. Although hardware acceleration can affect both symptoms, this article focuses on transparency, layered-window, and compositor behavior.

1.3 Test a known transparent window

Use a simple window with obvious rounded corners or transparency rather than an application displaying protected video, a game, or rapidly changing GPU content. Keep the test window stationary and place it over a bright, contrasting desktop background. Capture it as a window, save it directly as PNG, and inspect it in an editor that exposes transparency.

Success means that the transparent area has an alpha channel or that the captured composited background matches what was visible on screen, depending on your goal. These are different outcomes. Decide whether you need a cutout with transparent pixels or a faithful screenshot of the translucent window blended with the desktop.

2. Check the ShareX Settings Directly Related to This Problem

ShareX provides several ways to capture content, but they do not all obtain pixels through the same route. A method that isolates a window may handle shadows, rounded corners, layered surfaces, and acrylic effects differently from a region capture of the already composed desktop.

2.1 Compare window capture with region capture

First, capture the affected application using the window-capture command. Then repeat the test using a rectangular region around the same visible window. Do not move or resize the application between tests.

A region capture generally records the final image displayed on the desktop. That makes it useful when you want acrylic, shadows, blur, and translucency to appear exactly as you see them. However, the desktop behind the window becomes part of the screenshot rather than remaining transparent.

A window capture attempts to target the selected window. Depending on how that application draws itself, pixels outside the conventional window rectangle may not contain usable alpha information. Shadows can become clipped, rounded corners can be filled, or layered portions can be returned differently from the final desktop composition.

If region capture looks correct while window capture produces black corners, use region capture for that application. Success is a screenshot that visually matches the screen, even if it includes the desktop behind translucent areas. Stop testing unrelated upload, OCR, or recording settings because they do not control these pixels.

2.2 Use PNG when transparency must survive

PNG can preserve an alpha channel. JPEG cannot. Confirm that the final output is actually saved as PNG and not converted later by an after-capture task, image host, clipboard destination, editor, or automation step.

File extensions alone are not enough if another tool re-encodes the image. Open the final file produced at the end of the workflow, not only an intermediate preview. If the local PNG is transparent but the uploaded or pasted version is solid, the capture succeeded and the later destination removed transparency.

Success means the final PNG retains transparent pixels when placed over multiple background colors. At that point, do not keep modifying capture settings. Fix or replace the conversion, upload, paste, or export step that flattens the image.

2.3 Review after-capture and after-upload tasks

Temporarily disable tasks that modify the image, such as opening it in an editor, adding effects, resizing it, placing it on a canvas, applying a background, creating a thumbnail, or converting its format. Also test saving directly to a local folder before uploading.

Clipboard operations deserve special attention. A clipboard can expose an image through several formats, and the receiving application chooses which representation to paste. Some destinations preserve alpha correctly, while others flatten transparent pixels onto black or white. Compare the pasted result with the saved PNG.

If direct file insertion works but pasting does not, use the saved PNG as the transfer method. This is a destination compatibility issue, not evidence that ShareX is generally not working.

3. Check Windows, Display, and Application Rendering Factors

Modern Windows interfaces are often assembled by the Desktop Window Manager. An application may draw ordinary content, GPU surfaces, shadows, acrylic blur, and layered windows through different mechanisms before Windows composes the final desktop image. A targeted window capture does not always receive the same pixels that a person sees after composition.

3.1 Understand compositor and layered-window limitations

A layered window can use per-pixel transparency or a constant alpha value. Rounded windows, floating toolbars, overlays, menus, shadows, and frameless interfaces may use layered or separately owned windows. What looks like one object on screen can therefore be several surfaces assembled by Windows.

Acrylic and blur effects add another complication. The apparent color depends on content behind the window. There may be no independent transparent image that looks exactly like the screen because the compositor has already blended the foreground, tint, blur, and desktop background together.

This creates an important choice:

• Use region capture when you need a faithful record of the composed appearance.
• Use window capture when isolation matters and the application exposes suitable window pixels.
• Use manual masking when you need a clean transparent cutout that the application does not provide.

If a region capture matches the screen but an isolated capture does not, ShareX may be receiving incomplete or pre-composited window data. There may be no universal setting that reconstructs the missing alpha channel.

3.2 Test hardware acceleration in the affected application

If the wrong area is an internal panel, browser canvas, animated interface, or GPU-rendered surface, temporarily disable hardware acceleration in the affected application, restart that application completely, and capture it again. Do not change multiple applications or graphics settings at once.

If disabling acceleration fixes the pixels, you have identified a rendering-path compatibility issue. You can leave acceleration disabled if performance remains acceptable, use region capture while acceleration stays enabled, or re-enable it after taking the required images.

If nothing changes, restore hardware acceleration to its original setting. Avoid leaving unrelated performance options disabled without evidence that they help.

3.3 Check scaling, multiple displays, and graphics drivers

Display scaling does not usually create a black alpha background by itself, but mixed scaling or different GPU paths across monitors can complicate window coordinates and composition. Move the test window entirely onto one display and repeat both window and region captures. If possible, test on the primary monitor at its normal scaling.

A graphics-driver update or Windows update can change compositor behavior. If the problem began immediately after a change, restart Windows first, then test the same window on one display. Update the graphics driver through the device manufacturer or Windows Update when the installed driver is known to be unstable. Rolling back a driver should be reserved for a clearly correlated regression, not used as a first step.

Audio, microphone, network, and upload permissions do not determine whether a still PNG has transparent pixels. Network factors matter only if the local file is correct and an upload destination converts it. Keep troubleshooting focused on the stage where the background first becomes wrong.

4. Run a Clean Temporary Test With Minimal ShareX Settings

A minimal test separates the capture engine from custom hotkeys, image effects, uploaders, automation, and destination behavior. You do not need to erase your normal configuration.

4.1 Build a controlled comparison

1. Pause any workflow that automatically edits, converts, uploads, or deletes captures.
2. Choose a simple local folder as the destination.
3. Set the still-image output to PNG.
4. Capture the known test window using window capture.
5. Capture the same view using region capture.
6. Open both files directly in a transparency-aware editor.
7. Place each image over a colored layer to reveal its alpha behavior.

Record which method works. If the clean PNG is correct, restore your usual tasks one at a time until the background changes. The last restored task is the likely cause.

4.2 Define success before restoring the workflow

For an isolated asset, success means transparent pixels remain transparent in the final file and in the application where you will use it. For documentation, success may mean the screenshot reproduces the visible acrylic effect and surrounding desktop accurately. For automation, success means the file remains correct after every enabled task, including upload or clipboard delivery.

Once the required outcome works repeatedly, stop changing settings. A common troubleshooting mistake is to continue experimenting after finding a reliable capture path, which can obscure the actual fix.

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

Transparency failures do not always produce an error message. ShareX may complete the task successfully even when a later tool or destination flattens the image. Task history is still useful because it identifies the generated file, its format, the destination, and the sequence of actions that occurred.

5.1 Follow the image through each stage

Compare the image at four possible points:

1. The file saved immediately after capture.
2. The image after editing or effects.
3. The clipboard or exported version.
4. The uploaded or destination version.

The first stage where transparency disappears identifies the component to investigate. If stage one is wrong only for one application, focus on that application's rendering and the capture method. If stage one is correct but stage two is wrong, inspect editor effects or canvas settings. If only the upload is wrong, the host may be converting PNG to another representation or flattening alpha.

5.2 Use errors only when they match the symptom

Permission or destination errors can prevent a file from being saved, but they normally do not turn transparent pixels black. Likewise, hotkey conflicts can launch the wrong capture action, which matters if you intended region capture but triggered window capture. Verify the action recorded in task history before treating the problem as a compositor limitation.

When seeking support, provide the original local PNG, the application being captured, whether region capture works, whether hardware acceleration changes the result, and whether transparency disappears before or after pasting. This evidence is more useful than reporting only that ShareX is not working.

6. Quick Fix Checklist

• Open the original PNG in a transparency-aware editor and look for a checkerboard.
• Place the PNG over a colored layer to distinguish transparency from displayed black.
• Compare window capture with region capture of the same stationary window.
• Use PNG and disable temporary conversion, effects, canvas, and upload tasks.
• Insert the saved file directly instead of pasting through the clipboard.
• Use region capture when you need the final acrylic or blurred desktop appearance.
• Temporarily disable hardware acceleration in the affected app, then restart it.
• Move the window to one display and retest at normal scaling.
• Check task history to find where the background first changes.
• Use manual masking when no capture path provides a clean alpha boundary.

Stop as soon as the final image works in its intended destination. You do not need to make every capture mode produce identical results.

7. Frequently Asked Questions

7.1 Why does ShareX show black around rounded window corners?

The corners may be outside the application's actual painted content, while Windows supplies the visible rounded shape through composition, clipping, or layered-window behavior. A targeted window capture can receive opaque filler pixels instead of meaningful alpha. Test region capture. If it records the corners correctly, use it for a faithful screenshot or remove the corners manually when you need transparency.

7.2 Why is my PNG transparent in an editor but black after pasting?

The receiving application may choose a clipboard format that does not preserve alpha, or it may deliberately flatten transparent pixels over black. Insert or upload the saved PNG file directly. If that works, ShareX captured the image correctly and the paste destination caused the change.

7.3 Can ShareX capture acrylic blur as transparent pixels?

Not necessarily. Acrylic is a composed visual effect influenced by the desktop behind the window. The final appearance may already contain blurred and tinted background pixels rather than a reusable transparent layer. Region capture can preserve what was visible, but a clean isolated alpha image may require manual reconstruction.

7.4 Should I disable hardware acceleration permanently?

No. Disable it only as a controlled test in the affected application. If it fixes the capture, choose between keeping it disabled, enabling it only when needed, or using region capture. If it has no effect, restore the original setting.

7.5 When is manual background cleanup the realistic solution?

Manual cleanup is reasonable when the application provides no usable alpha channel, the window includes compositor-generated shadows or blur, or the desired cutout differs from what Windows actually displays. Capture against a contrasting solid background, then use selection, masking, or background-removal tools. For a small number of assets, this can be faster and more reliable than repeatedly changing capture settings.

7.6 What if every application has the same wrong background?

Check the image viewer, PNG output, image effects, clipboard destination, and upload conversion first. A problem affecting every transparent image is more likely to occur after capture than to be caused by one application's rendering. Run the minimal local PNG test to identify the first incorrect stage.