ShareX Region Capture Offset on High DPI Displays: How to Fix It

You select one area of the screen in ShareX, but the resulting screenshot comes from somewhere else. It may be shifted sideways, cropped incorrectly, enlarged, reduced, or captured from an adjacent monitor. This symptom usually points to a coordinate and scaling mismatch rather than a broken capture workflow. It is especially common to investigate when Windows uses 125 percent or 150 percent scaling, connected monitors use different scale values, ShareX was open during a display change, or a Remote Desktop session altered the desktop layout.

The most effective approach is to isolate the display condition that causes the offset. Start with a repeatable region test, compare it with an active-window capture, and then simplify the monitor layout. Avoid reinstalling ShareX or changing unrelated upload, audio, network, and destination settings until you have tested scaling. Those settings can affect later workflow stages, but they do not normally explain why the selected rectangle and captured pixels use different coordinates.

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

Before changing anything, verify that the problem is specifically a region-coordinate error. A consistent test makes it easier to tell whether a change fixed the issue or merely changed the size of the offset.

1.1 Create a Clear Capture Target

Open a simple window with obvious boundaries, such as Notepad, File Explorer, or a browser window displaying a page with large text. Position the window away from the edges of the screen. Run ShareX region capture and select a small, recognizable area inside that window.

Examine the saved image or the preview in ShareX. A scaling-related region problem commonly produces one or more of these results:

• The image starts above, below, left, or right of the selected rectangle.
• The output contains more or less content than the selection indicated.
• The error becomes larger as the selected area moves farther from the screen origin.
• The capture works on one monitor but fails on another.
• The problem appears only after moving between monitors with different scaling values.
• The cursor overlay, magnifier, or selection border does not line up with the underlying pixels.

Repeat the test near the upper-left and lower-right portions of the same monitor. If the displacement grows with distance, that is strong practical evidence of a coordinate conversion or scaling mismatch.

1.2 Compare Region Capture With Active Window Capture

Capture the same application using ShareX active-window capture. If active-window capture is correct while region capture is shifted, focus on region selection, DPI awareness, monitor layout, and scaling. Active-window capture obtains a window boundary through a different path and can succeed even when manually selected coordinates are being translated incorrectly.

If both capture types are wrong, the problem may involve a wider graphics, session, or desktop-composition issue. If the image is captured correctly but uploaded to the wrong place, renamed unexpectedly, or processed incorrectly, the display offset is not the primary problem.

1.3 Record the Current Display Conditions

Write down the scale and resolution shown in Windows Display settings for every connected monitor. Also note which display is marked as the main display and where each monitor appears in the arrangement diagram. Common test cases include:

• A laptop display at 150 percent and an external monitor at 100 percent.
• One monitor at 125 percent and another at 150 percent.
• Two monitors using the same scale but different resolutions.
• A remote session whose resolution changed after connection.

This record prevents guesswork. It also gives you a known configuration to restore after testing.

2. Check the ShareX Settings Directly Related to This Problem

ShareX contains many settings for destinations, hotkeys, uploads, recording, OCR, image effects, and automation. Most of them have no bearing on region geometry. Concentrate on the capture path and any setting that changes how the region tool behaves.

2.1 Restart ShareX After Display Changes

Exit ShareX completely, rather than only closing its main window. Use the notification-area icon to exit if ShareX is still running in the background. Start it again after Windows has settled on the intended monitor arrangement and scale values.

This matters after connecting or disconnecting a monitor, changing the main display, changing scaling, waking a docked laptop, rotating a display, or entering or leaving Remote Desktop. A running application can retain display information from the earlier desktop state.

Run the same small-region test again. Success means the selected rectangle and output now match on the affected monitor. If they do, stop changing settings. There is no benefit in modifying hotkeys, upload destinations, or image effects after the coordinate problem has disappeared.

2.2 Test the Standard Region Capture Path

Trigger region capture directly from ShareX instead of through a complex after-capture workflow. Temporarily avoid scrolling capture, screen recording regions, OCR, custom commands, image effects, and automated actions. These features can introduce additional steps that make the result harder to diagnose.

If direct region capture works, restore your normal workflow one stage at a time. The first restored stage that brings back the problem identifies where further investigation should focus. If direct region capture remains offset, continue testing display scaling.

2.3 Review Windows Compatibility Overrides

Find the ShareX executable or its shortcut, open Properties, and inspect the Compatibility tab. If someone previously enabled a high-DPI scaling override, record its current value before changing it. Compatibility modes and forced scaling behavior can affect how Windows presents coordinates to an application.

For a clean test, remove manually applied compatibility settings that were added during earlier troubleshooting, restart ShareX, and repeat the capture. Do not randomly cycle through every override. The goal is to return to normal Windows behavior first. If your organization deliberately requires a compatibility setting, consult its administrator before making a permanent change.

Success means region and active-window captures both align without requiring a forced compatibility mode. Once alignment is restored, leave the working configuration unchanged.

3. Check Windows and Display Factors That Affect Coordinates

Windows can use logical coordinates for interface layout while the display contains a larger number of physical pixels. Per-monitor DPI support allows applications to adapt as a window moves between displays, but mixed scale factors create more opportunities for stale or incorrectly translated coordinates.

3.1 Test Common Scale Values

Open Windows Settings, select System, and then Display. Select each monitor in the diagram and check its Scale value. Values such as 125 percent and 150 percent are normal and supported, but they are important clues when a region capture is offset.

If the issue occurs at 125 percent or 150 percent, temporarily test the affected monitor at 100 percent. Sign out if Windows requests it, or at minimum exit and restart ShareX after the change. Then repeat the exact capture target.

If 100 percent scaling fixes the offset, you have confirmed a DPI-related condition. That does not mean 100 percent must be the permanent solution. Restore the preferred scale, restart ShareX, and test again. If the problem returns only at the higher value, keep that evidence for further ShareX or driver troubleshooting instead of reinstalling unrelated components.

3.2 Simplify a Mixed-Monitor Setup

Mixed DPI is a particularly useful test case. A desktop might use 100 percent on a large external screen and 150 percent on a laptop panel. Moving ShareX, its region overlay, or the target application between those displays can expose a per-monitor DPI transition problem.

Try these tests in order:

1. Move the ShareX main window to the monitor where you intend to capture.
2. Move the target application to that same monitor.
3. Exit and restart ShareX while both are on that monitor.
4. Test region capture without crossing the boundary between displays.
5. Set both monitors temporarily to the same scaling value and test again.
6. Disconnect the secondary display and test one monitor at 100 percent.

After each step, stop if the capture rectangle and saved image match. A successful one-monitor test establishes that ShareX can capture correctly and that the multi-monitor coordinate space is the differentiating factor.

3.3 Check Monitor Arrangement and Negative Coordinates

In Windows Display settings, make sure the monitor rectangles reflect their physical positions. A second display placed to the left of the main monitor can use coordinates extending left of the primary desktop origin. A monitor above the main display can similarly extend the desktop upward.

Temporarily arrange the affected display to the right of the main monitor, apply the change, restart ShareX, and retest. This is a diagnostic step, not necessarily a permanent layout. If captures work only in a simpler arrangement, the offset is connected to the virtual desktop coordinate layout.

3.4 Consider Graphics Drivers and Docking Changes

A graphics driver translates between Windows, the desktop compositor, and connected displays. Driver problems are less common than scale mismatches, but they become more plausible when multiple applications show incorrect screen geometry, displays are detected at the wrong size, or the problem began after a driver, dock, or monitor change.

Use Windows Update or the computer or graphics hardware manufacturer's official tools to check for an appropriate driver. Restart Windows after an installation. Do not use unknown driver-download websites. If the problem began immediately after a driver update, consult the manufacturer's documented rollback or support options.

Success means the Windows display arrangement remains stable and ShareX produces the same correctly aligned region after a reboot.

3.5 Test Remote Desktop Separately

Remote Desktop can resize or rescale a session when the client window changes, when a session reconnects, or when it moves between local monitors. First determine where ShareX is running. A copy running inside the remote session captures the remote desktop. A copy running locally captures what the local computer displays.

Disconnect cleanly, set the intended Remote Desktop resolution or full-screen arrangement, reconnect, and then launch ShareX inside the final session. Avoid resizing or moving the remote client during the test. If capture works in a fresh, stable session but becomes offset after resizing, the session's display transition is the relevant trigger.

Audio devices, network throughput, upload authentication, and file destinations may affect recording sound or later uploads, but they do not normally shift region coordinates. Investigate them only if the region itself is correct and a later workflow stage fails.

4. Run a Clean Temporary Test With Minimal ShareX Settings

A minimal test determines whether the problem comes from the base capture operation or from a customized workflow. You do not need to erase your configuration or reinstall ShareX to perform this check.

4.1 Disable Extra Workflow Stages Temporarily

Record your current workflow before changing it. Then configure a temporary capture task that saves or previews the image without uploads, OCR, annotations, image effects, external commands, clipboard transformations, or custom actions. Trigger it directly from the ShareX interface if possible.

Use one monitor, preferably at 100 percent scaling, and restart ShareX before testing. Capture the same recognizable target three times. Consistent alignment across all three attempts is a successful baseline.

Next, restore your normal scale value and restart ShareX. If alignment remains correct, reconnect the second monitor. Then restore workflow stages one by one. This sequence changes only one variable at a time.

4.2 Avoid Reinstalling Until Scaling Is Isolated

A broad reinstall can consume time while leaving Windows scaling, monitor arrangement, compatibility overrides, and Remote Desktop behavior unchanged. It can also remove useful configuration evidence. Reinstallation is reasonable only after a minimal capture fails in a stable single-monitor setup, ShareX has been restarted, compatibility overrides have been checked, and the display driver is functioning normally.

Even then, preserve or export settings as appropriate before making destructive changes. The aim is to diagnose, not to replace configuration blindly.

5. Check Task History, Logs, and Recent Output

A pure coordinate mismatch may not create an error message because ShareX successfully completes the capture using the coordinates it received. Nevertheless, task history and output files can show whether the wrong image was captured initially or whether a later action transformed it.

5.1 Inspect the Earliest Available Image

Open the most recent task in ShareX and compare the initial screenshot with any edited, processed, uploaded, or copied result. Check the pixel dimensions. If the initial image is already shifted or incorrectly sized, stay focused on DPI, region selection, and monitor geometry.

If the initial image is correct but a later output is cropped, resized, or offset, inspect image effects, editor operations, custom commands, and destination-specific processing. That is a workflow problem rather than a ShareX region capture offset high DPI problem.

5.2 Use Logs for Errors, Not as Proof of Correct Scaling

Review ShareX logs when a task fails, produces no file, cannot access a destination, or reports an exception. Note the time, action, and full error text. Logs are useful for distinguishing a capture failure from an upload or automation failure.

The absence of an error does not rule out a scaling mismatch. If ShareX receives valid but inappropriate coordinates, the task can complete normally. Visual comparison remains the decisive test for this symptom.

6. Quick Fix Checklist

• Confirm that region capture is wrong while active-window capture is correct.
• Check whether Windows uses 125 percent, 150 percent, or mixed scaling.
• Exit ShareX completely and restart it after every display-layout change.
• Move ShareX and the target application onto the same monitor.
• Test without dragging a region across monitor boundaries.
• Temporarily set all displays to the same scale value.
• Disconnect extra displays and test one monitor at 100 percent.
• Remove unneeded high-DPI compatibility overrides and restart ShareX.
• Test a direct capture without OCR, uploads, effects, or custom commands.
• Stabilize the resolution before launching ShareX in Remote Desktop.
• Check official graphics drivers if other applications also show display errors.
• Inspect the earliest output to separate capture errors from later processing.

Stop troubleshooting as soon as repeated captures match the selected area under your normal working configuration. Once three or more tests succeed on the affected monitor, avoid changing additional settings. Extra changes can obscure which fix worked.

7. Frequently Asked Questions

7.1 Why Is My ShareX Region Capture Shifted?

The most likely cause is a mismatch between the coordinates used by the selection overlay and the physical pixels captured from the desktop. Windows scaling, mixed-DPI monitors, stale display information after a layout change, compatibility overrides, and Remote Desktop resizing can all contribute. Test one monitor at 100 percent and restart ShareX to confirm whether scaling is involved.

7.2 Does 125 Percent or 150 Percent Scaling Break ShareX?

Those are normal Windows scaling values and do not automatically break ShareX. They are relevant diagnostic conditions because coordinate conversion is more complex than at 100 percent. If the problem appears only at a higher scale, document the exact monitor, resolution, and scale combination rather than assuming ShareX is completely not working.

7.3 Why Does ShareX Work on One Monitor but Not Another?

The monitors may use different scale values, resolutions, orientations, or positions in the virtual desktop. Per-monitor DPI behavior also means an application can receive display-change notifications as it moves between screens. Put ShareX and the target window on the affected monitor, restart ShareX there, and test without crossing monitor boundaries.

7.4 Should I Change ShareX Upload or Recording Settings?

Not for a shifted screenshot. Upload destinations, network access, microphones, and recording audio do not normally determine where a still-image region is captured. Change those settings only if the selected image is correct and a later upload, recording, or automation step fails.

7.5 Should I Reinstall ShareX?

Not as the first step. A reinstall usually does not alter Windows display scaling, monitor geometry, Remote Desktop resolution, or graphics drivers. First test direct region capture on one monitor at 100 percent, restart ShareX, and check compatibility overrides. Consider reinstalling only if the minimal baseline still fails.

7.6 What Information Is Useful When Reporting the Problem?

Include the Windows version, each monitor's resolution and scale percentage, monitor arrangement, which display is primary, whether Remote Desktop is involved, and whether active-window capture works. Describe whether the error is a fixed shift or grows farther from the upper-left corner. Include a redacted example if it contains no private information, along with relevant ShareX task or error details.