ShareX Window Capture Includes Shadow or Border: How to Fix It

If a ShareX window capture includes a shadow, transparent border, rounded-corner padding, title bar, or a strip of the desktop, the capture is usually reflecting the window geometry reported by Windows rather than malfunctioning. Other common causes include selecting the whole window instead of its client area, applying an automatic image effect, or capturing a high-DPI window whose visible and calculated boundaries do not match exactly. The steps below isolate each possibility without disrupting unrelated ShareX features such as uploads, OCR, hotkeys, screen recording, or automation.

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

Before changing settings, determine whether the unwanted area is part of the Windows window itself, a ShareX post-capture effect, or a mismatch introduced by a particular application. This distinction prevents unnecessary changes to upload destinations, hotkeys, recording options, and other settings that cannot affect window boundaries.

1.1 Capture a basic application window

Open a simple Windows application, such as Notepad, and place it over a desktop background with a noticeably different color. Keep the window restored rather than maximized. Take one screenshot with ShareX window capture and another with region capture, drawing the region just inside the visible window boundary.

Compare the resulting files in an image viewer that can display transparency. Look for the following clues:

• A soft translucent area around every side is probably the Windows window shadow.
• Clear or semitransparent pixels outside rounded corners are transparent border padding.
• A solid strip showing wallpaper or another application indicates the capture rectangle extended onto the desktop.
• A decorative frame with a uniform color is more likely an image effect.
• A normal title bar is expected when the entire top-level window is captured.

If region capture produces the exact boundary you want while window capture includes extra pixels, ShareX is capturing a window boundary that differs from its visible content. That narrows the problem to window selection, Windows composition, or display scaling. Stop investigating upload and clipboard settings because they do not determine the original screenshot bounds.

1.2 Inspect the image before uploading it

Open the local file from ShareX task history or copy it into an editor before checking the uploaded version. If the local file already contains the border, the upload destination did not add it. If the local file is clean but a website displays a halo, that site may be placing the transparent image over a contrasting background.

Transparency is particularly easy to misinterpret. Pixels outside a rounded window can be transparent even though an image viewer displays them as white, black, or checkerboard padding. Testing the same PNG over light and dark backgrounds will reveal whether the apparent border is transparent.

1.3 Keep window capture separate from the wrong-window problem

This guide addresses extra material around the correct window. If ShareX captures a different active window, a menu, or a popup, that is a selection and timing problem. Likewise, if the desired content is cut off, the issue is cropping or an undersized capture area rather than an unwanted shadow or border.

2. Check the ShareX Settings Directly Related to This Problem

ShareX offers several capture paths, and they do not all define a window in the same way. Setting labels and locations can change over time, so inspect the capture-related options available in your installed build rather than relying on a version-specific menu path.

2.1 Compare window capture with region capture

A standard window capture asks Windows for information about the selected top-level window. That boundary can include non-client areas such as the title bar, resize frame, invisible padding, rounded corners, or shadow-related space. Region capture instead uses coordinates selected on the screen. It can therefore exclude pixels that belong technically to the window but are not wanted in the finished image.

Use window capture when you need speed and consistent selection of complete application windows. Use region capture when the visual edge matters more than the operating system's definition of the window. For repeat work, select the window through ShareX's region interface if that interface offers the boundary you want, or reuse a fixed region when the window remains in the same position.

Success means the captured PNG ends at the desired visible edge without including desktop pixels. Once one capture method consistently produces that result, stop changing capture settings and assign that method to the preferred hotkey.

2.2 Review window-related capture options

Open ShareX task settings or capture settings and review options specifically associated with window capture, transparency, cursor inclusion, or client-area capture. If your installation presents an option related to capturing a window shadow, disable it and repeat the Notepad test. If it offers a choice between the whole window and the client area, understand that client-area capture normally excludes the title bar and outer frame as well as the shadow.

Change one option at a time. A successful result is a screenshot whose dimensions shrink by the unwanted margin and whose corners no longer contain shadow or transparent padding. If disabling a shadow-related option solves the test, leave unrelated options unchanged.

2.3 Disable automatic image effects temporarily

ShareX can run after-capture actions and image effects automatically. A border, outline, background, canvas expansion, shadow, or watermark effect can make a clean capture look as though the capture operation included extra material.

Temporarily disable image effects and take a new screenshot. Do not judge an old file because effects are baked into output when the task runs. If the new image is clean, inspect the active effects and remove only the border, shadow, canvas, or padding operation responsible. You can retain unrelated effects such as resizing or annotations if they do not alter the outer boundary.

Success means the unprocessed capture has the correct edge. At that point, re-enable effects one by one until the responsible operation is identified. There is no need to reset upload, OCR, or destination configuration.

2.4 Check after-capture actions

If ShareX automatically opens the image editor, applies effects, saves a modified copy, copies an image to the clipboard, and uploads another file, you may be comparing different outputs from the same task. Temporarily configure the test to save the image locally with no editing or effects. Then inspect that saved file.

If the saved original is correct but the clipboard or uploaded result is not, follow the workflow from capture through editing and upload. The unwanted border is being introduced after capture. If every output has the same edge, concentrate on capture geometry and Windows behavior.

3. Check Relevant Windows and Display Factors

3.1 Understand Windows shadows and rounded corners

Modern Windows interfaces draw visual effects around many application windows. A drop shadow extends beyond the solid frame, while rounded corners leave pixels near the corners outside the visible shape. Depending on how an application's window is created and how its bounds are reported, a screenshot tool may receive a rectangular area that contains those effects or transparent space.

This behavior can differ among traditional desktop applications, packaged Windows applications, browsers, and programs with custom title bars. One application's result does not prove that ShareX will calculate every other application's boundary identically.

If only one application produces the issue, region capture or post-capture cropping is usually safer than changing system-wide visual effects. Disabling Windows visual effects just to alter screenshots can affect the appearance of the entire desktop and still may not resolve custom application frames.

3.2 Test high-DPI scaling

High-DPI scaling can complicate the relationship between logical window coordinates and physical screen pixels. The symptom may appear only on a monitor using 125 percent, 150 percent, or another scaled setting, especially when monitors use different scale factors.

Move the same Notepad window to each monitor and repeat the window capture. Also compare a restored window with a maximized one. If the unwanted margin changes size, appears only on one display, or becomes uneven after moving the window, scaling is a likely contributor.

For a low-risk test, place the window completely on one monitor and restart the affected application after moving it. Avoid straddling the window across displays. Signing out or restarting applications may be necessary after changing Windows scaling, but changing global scaling should not be the first fix because it affects readability and layout throughout Windows.

Success means the window capture has consistent edges on the chosen monitor. If the problem persists only under a required scaling configuration, use region capture or a controlled crop instead of compromising the display setup.

3.3 Separate title bars from accidental borders

A title bar is not normally an accidental shadow. It is part of a full-window capture. If you need only the application content, choose a client-area option when available, select the content with region capture, or crop the top of the image afterward.

For documentation, retaining the title bar can be useful because it identifies the application and provides context. For presentations, tutorials, and web graphics, excluding it may create a cleaner result. Decide on the intended output before treating the title bar as an error.

3.4 Ignore unrelated systems unless evidence points to them

Audio settings cannot change the border of a still screenshot. Network and destination settings can affect uploads but not the pixels in the locally saved original. Permissions can prevent capture or saving, yet they are unlikely to create a precise shadow around an otherwise correct window. Investigate those systems only if ShareX reports a corresponding error or if the local and uploaded files differ.

4. Run a Clean Temporary Test With Minimal ShareX Settings

A clean test determines whether the issue comes from the capture itself or from a customized workflow. You do not need to uninstall ShareX or erase your configuration.

1. Open a restored Notepad window over a contrasting desktop background.
2. Temporarily disable automatic image effects and editing actions.
3. Configure the test to save the screenshot to a local file.
4. Take a normal window capture and inspect the local PNG.
5. Take a manually drawn region capture around the visible window edge.
6. Compare dimensions, corners, transparency, and desktop pixels.

If the clean window capture still has a shadow but the region capture does not, the result comes from window geometry rather than the upload workflow. Use region capture, a client-area mode, a shadow option if available, or cropping. If both images gain an identical decorative edge, an effect or later processing step may still be active.

If neither clean output has the unwanted edge, restore your regular actions one at a time. Test after enabling image effects, editing, clipboard copying, and uploading. Stop as soon as the symptom returns. The last restored step is the strongest lead.

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

Task history is useful for comparing the original local path, thumbnail, upload result, and timing of recent captures. Open several affected entries and determine whether the symptom began after a hotkey, workflow, image-effect, or destination change.

Logs are more useful when ShareX is not working at all, a task fails, or an external action modifies the file. A normal successful window capture with an unwanted shadow may not generate an error because ShareX considers the requested rectangular capture successful.

When troubleshooting automated workflows, verify which file is passed to later actions. An editor or script may expand the canvas, add a frame, convert transparency to a background color, or upload a processed file instead of the original. Compare file dimensions at each stage. An increase in width or height after capture identifies where padding was added.

If task history shows the correct local image and only the destination preview looks bordered, download the uploaded file and inspect its actual pixels. Web pages often place transparent images on backgrounds or add CSS frames to previews. That display treatment does not mean the source screenshot contains a border.

6. Use Cropping When It Is the Reliable Fix

Manual cropping is not merely a workaround. It is often the most dependable solution when an application uses custom window chrome, Windows reports a rectangular frame around rounded corners, or high-DPI behavior varies across monitors.

Use ShareX's image editor after capture, choose region capture from the start, or apply a carefully configured crop effect when the unwanted margin is always the same size. Automatic cropping is appropriate only when the excess pixels are predictable. If the shadow width changes with scaling, window state, or application type, a fixed crop can remove legitimate content.

A reliable crop should meet three conditions:

• No application content is removed at any edge.
• No desktop pixels or shadow remain in the final image.
• The process remains consistent across repeated captures in the same workflow.

For occasional screenshots, manual region selection is usually faster than diagnosing every difference in window composition. For large documentation projects, create a repeatable workflow and validate it on every display scale and application type you intend to capture.

7. Quick Fix Checklist

• Test a restored Notepad window over a contrasting desktop background.
• Compare window capture with a tightly drawn region capture.
• Inspect the locally saved PNG before checking an upload or preview.
• Check whether the apparent border is actually transparent corner padding.
• Disable any available window-shadow capture option and retest.
• Use client-area capture if you want content without the title bar.
• Temporarily disable border, shadow, canvas, and padding image effects.
• Test the window entirely on one monitor at a time.
• Compare results across monitors with different DPI scaling.
• Restore workflow actions one at a time after a clean test.
• Use region capture or manual crop when window geometry remains inconsistent.

Stop changing settings as soon as a fresh local screenshot has the required edges. Upload, clipboard, OCR, recording, and automation settings should remain untouched unless testing shows that a later workflow stage changes the image.

8. Frequently Asked Questions

8.1 Why does ShareX include a shadow around a window?

Windows may report or render a rectangular area that includes the window's drop shadow, resize frame, or invisible border. ShareX can capture that area when performing a full-window capture. A shadow-related capture option, region capture, client-area capture, or cropping can produce a tighter result.

8.2 Why are there transparent pixels around rounded corners?

A digital image is rectangular, but many Windows windows have rounded visible corners. Pixels outside the rounded shape may remain transparent within the rectangular screenshot. They can appear white, black, or checkerboard-patterned depending on the viewer or destination background.

8.3 How can I remove the title bar without cutting off content?

Use a client-area capture option if one is available and works with the application. Otherwise, draw a region around the content area or crop the title bar in the image editor. Test carefully with applications that place controls or tabs inside a custom title bar.

8.4 Can high-DPI scaling cause an extra border?

It can contribute to boundary mismatches, particularly with mixed-scale monitors or applications moved between displays. Test the same basic window on each monitor, keeping it fully contained on one display. If the border changes with display scale, region capture is often the least disruptive fix.

8.5 Why does the uploaded image look bordered when the local file does not?

The destination may display transparent pixels against a colored background or add a visual frame around its preview. Download the uploaded file and compare its dimensions and pixels with the original. If they match, the border belongs to the website's presentation rather than the screenshot.

8.6 What should I do if ShareX is not working after changing settings?

Undo only the last capture or workflow change, then repeat the minimal local-save test. Check task history and logs if capture, saving, or uploading fails. Avoid resetting the entire application when the issue began after one identifiable option was changed.