ShareX Color Picker Shows the Wrong Color on High DPI: How to Fix It

If the ShareX color picker selects a pixel beside your cursor, reports an unexpected hex value, or disagrees with a browser or design tool, the cause usually falls into one of two categories. A coordinate problem makes ShareX sample the wrong physical pixel, often because of Windows scaling or mixed-DPI monitors. A color-management problem samples the intended location but produces a value that looks different because HDR, wide-gamut output, an ICC profile, or application-specific color conversion is involved. Identifying which category you have is the fastest route to a reliable fix.

1. Confirm the Symptom With a Simple Test

Before changing settings, determine whether the ShareX color picker is pointing at the wrong location or interpreting the intended pixel differently. These problems can look similar but require different troubleshooting steps.

1.1 Create a high-contrast coordinate test

Open Microsoft Paint or another simple application and create several large blocks of solid color. Use colors that are easy to distinguish, such as pure red, green, blue, black, and white. Make each block at least 100 pixels wide so that you can sample well away from its edges.

Activate the ShareX color picker and place the cursor near the center of each block. Then move slowly toward a boundary while watching the magnifier and reported color.

• If the magnifier or selected pixel is displaced from the cursor, treat the issue as a coordinate offset.
• If ShareX tracks the cursor correctly but its value differs from another tool, investigate color management.
• If the result changes only on one monitor, focus on that monitor's scaling, HDR setting, and color profile.
• If only browser content disagrees, test browser color management and the source image separately.

Success means the magnifier follows the exact pixel beneath the pointer and repeatedly reports the expected solid-color values. If this test works on every monitor, stop changing DPI-related settings. Your issue is more likely limited to a particular application, content type, or color-managed workflow.

1.2 Compare values rather than appearances

Do not rely only on how a swatch looks. Record the hexadecimal or RGB value reported by ShareX, then compare it with at least one other screen-sampling tool. If possible, also open the source image in an editor and inspect the pixel stored in the file.

These are three different observations: the color encoded in a file, the color produced on screen after color conversion, and the pixel value returned by a screen picker. They are not guaranteed to be identical. A color-managed application may transform an image through its embedded profile and the monitor profile before display. HDR rendering can introduce another conversion between standard dynamic range content and the displayed output.

If multiple screen pickers report the same value but the editor reports a different file value, ShareX is probably sampling the displayed result correctly. Stop changing ShareX settings and inspect the document profile, embedded image profile, browser behavior, HDR pipeline, or export settings instead.

2. Check the ShareX Settings Directly Related to the Problem

ShareX includes different capture and utility workflows, so first confirm that the behavior comes from the color picker itself rather than an image effect, editor operation, or post-capture task. Launch the color picker directly from ShareX and test without taking a screenshot or running an upload workflow.

2.1 Check the magnifier and selected pixel

The zoomed magnifier is the most useful diagnostic aid. Do not assume the center of a large zoomed grid is the selected pixel without checking its indicator. Move across a one-pixel or sharply defined edge and observe when the reported value changes.

If the magnifier image appears correct but the chosen pixel is consistently several pixels away, note the direction and approximate distance of the offset. A fixed or proportional offset that becomes larger farther across the screen strongly suggests a logical-coordinate versus physical-pixel scaling problem.

If zoom makes the preview look blurry, remember that magnification enlarges already rendered screen pixels. It does not reveal the original pixels in an image file. Browser zoom, application zoom, display scaling, and the picker magnifier are separate layers. Set browser or editor zoom to 100 percent during diagnosis so that only the picker magnification remains.

2.2 Restart ShareX after display changes

Completely exit ShareX from its notification-area menu, then reopen it after changing Windows scale, monitor arrangement, HDR, or docking configuration. Do not merely close the main window because ShareX commonly continues running in the notification area.

This matters because desktop coordinates and display information can change when a monitor is attached, removed, rotated, or assigned a different scale. Restarting gives the application a clean opportunity to detect the current display layout.

Success means the cursor, magnifier, and sampled pixel align after relaunching. If alignment is restored, stop there. You do not need to reset unrelated screenshot destinations, uploaders, hotkeys, OCR settings, or automation tasks.

2.3 Avoid forced compatibility scaling

Windows can apply compatibility overrides to an application's executable. Right-click the ShareX shortcut or executable, open Properties, and inspect the Compatibility tab. If Change high DPI settings contains a manually forced scaling override, record its current value and test with the override disabled.

A forced System or System Enhanced scaling mode can help an older application look larger, but it can also complicate coordinate mapping. Do not select random compatibility modes as a permanent solution. Test one controlled change, restart ShareX, and repeat the solid-color boundary test.

Success means the selected pixel no longer drifts from the pointer. If disabling an override fixes the offset, leave that override disabled. If it changes only text sharpness and not sampling alignment, restore the original setting and continue.

3. Check Windows Scaling and Display Color Factors

For this symptom, display configuration is more relevant than audio, network, upload destination, or microphone settings. Permissions can affect capture in some protected applications, but they do not normally explain a repeatable color-picker offset across ordinary desktop windows.

3.1 Test one monitor at 100 percent scale

The clearest mixed-DPI test is temporary and reversible:

1. Disconnect or disable secondary monitors in Windows display settings.
2. Use the remaining monitor at its recommended resolution.
3. Temporarily set Scale to 100 percent.
4. Sign out and back in if Windows indicates that an application needs to restart.
5. Start ShareX again and repeat the high-contrast test.

If the picker becomes accurate, the fault is related to scaling or the transition between monitors rather than the underlying color value. Reconnect the other displays one at a time. Test with ShareX and the target application fully contained on each display. Avoid placing either window across a monitor boundary during testing.

Mixed-DPI arrangements, such as a laptop at 150 percent beside a desktop monitor at 100 percent, are especially useful for reproducing coordinate errors. Also verify that Windows shows the monitors in their correct relative positions. Misaligned virtual monitor edges can make pointer movement and capture regions feel inconsistent.

Success means sampling remains aligned on each monitor at the scale you intend to use. Once you identify a stable arrangement, stop changing scale values. Keeping every monitor at 100 percent can be a diagnostic workaround, but it is not always a practical permanent requirement.

3.2 Separate HDR behavior from cursor offset

HDR generally affects color and brightness interpretation, not where the cursor points. If the picker targets the correct location but a sampled color appears brighter, duller, or numerically different from an SDR reference, test with HDR temporarily turned off in Windows.

After switching HDR, close and reopen ShareX and the application containing the test content. Compare the same flat swatches again. If the values agree in SDR but not HDR, you have identified a display-pipeline or tone-mapping difference rather than a DPI coordinate bug.

Success does not necessarily mean HDR must remain disabled. It means you now know that an SDR screen picker may not provide the original file value from HDR-composited output. For exact asset colors, inspect the source file in a color-aware editor instead of treating the final displayed pixel as the authoritative value.

3.3 Review wide-gamut displays and ICC profiles

A wide-gamut monitor can display colors outside the usual sRGB range, while many web assets and interface colors are authored with sRGB assumptions. Windows color management and color-aware applications may use the monitor's ICC profile to convert content for that display.

Open Windows Color Management and identify the profile assigned to the affected monitor. Do not delete a manufacturer or calibration profile merely because two tools disagree. First test whether the disagreement occurs only in color-managed applications. If you suspect a damaged or incorrect profile, note the existing configuration before temporarily testing a known appropriate profile or the monitor manufacturer's current profile.

Success means applications that are expected to use the same color space report or render consistently. If the profile is valid and only ShareX differs from a document editor, use the editor's document-color readout for file values. A screen picker answers what is on the composed desktop, not necessarily what is encoded in the document.

3.4 Test browser content carefully

Browsers may color-manage tagged images, CSS colors, canvas output, video, and HDR media differently. Browser zoom and operating-system scaling can also combine to make a visual comparison confusing.

Set browser zoom to 100 percent and create a basic test using a CSS color with a known hex value. Compare a large CSS background with a separately loaded image containing the same nominal RGB value. If ShareX samples the CSS block consistently but the image differs, inspect the image's embedded color profile. If two browsers render or sample the asset differently, the issue is not necessarily ShareX.

Also remember that antialiasing, transparency, shadows, gradients, filters, and subpixel text rendering alter displayed pixels. Sample the center of a large opaque area rather than an edge. Success means ShareX matches another screen picker on the same rendered pixel. The HTML or source-image value can still differ for legitimate color-management reasons.

4. Run a Clean Temporary ShareX Test

If the result remains inconsistent, isolate the color picker from your established ShareX workflow. Back up or note your current configuration before making changes. The objective is not to erase years of hotkeys and destinations, but to determine whether a local preference or compatibility choice is involved.

4.1 Minimize the variables

For the temporary test, use one monitor, 100 percent Windows scaling, SDR mode, browser or editor zoom at 100 percent, and a simple opaque test image. Exit overlays, screen magnifiers, remote-desktop sessions, GPU color filters, night-light utilities, and third-party display enhancement tools when practical.

Open ShareX normally and invoke only its color picker. Do not run image effects, capture transformations, OCR, uploads, or after-capture tasks. Compare several known solid colors and save the reported values in a text file.

Success means each color is repeatable and the selected location follows the cursor. Add complexity back one item at a time: the second monitor, normal scale, HDR, the ICC profile, then the real browser or design application. The first change that brings back the problem identifies the relevant layer.

4.2 Distinguish local display output from remote output

Remote Desktop, virtual machines, streaming software, and GPU overlays can create an additional rendered surface. A picker running on the local computer may sample the final streamed or converted image rather than the pixels represented inside the remote application.

If the issue happens only in a remote session, run the comparison tool in the same environment as ShareX. Do not compare a file value measured inside a remote machine with a displayed pixel sampled after compression and color conversion on the local machine.

5. Check Logs and Recent Output Only When Useful

ShareX task history and logs are valuable for failed captures, uploads, OCR operations, destination errors, and automation problems. They are less likely to explain a color picker that opens normally but samples the wrong coordinate or returns a color affected by the display pipeline.

Review task history if the value changes after the screenshot is saved or edited. Compare the live picker value, the captured screenshot, the file opened in an editor, and the uploaded result. This sequence reveals whether a conversion occurred during capture, image processing, encoding, or upload.

• If the live picker is wrong before capture, focus on DPI, coordinates, HDR, and color management.
• If the picker is correct but the saved screenshot differs, inspect capture and image-processing steps.
• If the local file is correct but an uploaded preview differs, investigate the destination's image processing or browser rendering.
• If an error message appears, record its exact wording before changing settings.

Success means you can identify the first stage where the value or appearance changes. Stop troubleshooting earlier stages once they have produced a verified correct result.

6. Quick Fix Checklist

1. Use large, opaque, solid-color blocks to distinguish pixel offset from color disagreement.
2. Confirm whether the ShareX magnifier follows the precise cursor location.
3. Compare hexadecimal values in ShareX, another screen picker, and the source editor.
4. Restart ShareX fully after changing monitors, scale, HDR, or display arrangement.
5. Disable any manually forced high-DPI compatibility override and retest.
6. Test with one monitor at 100 percent scale and its recommended resolution.
7. Reconnect mixed-DPI monitors one at a time and test each screen separately.
8. Turn HDR off temporarily to identify tone mapping or advanced-color behavior.
9. Check whether disagreement is limited to a wide-gamut monitor or color-managed application.
10. Review the affected monitor's ICC profile without deleting a valid calibration profile.
11. Set browser and editor zoom to 100 percent during comparison.
12. Sample away from text, transparency, gradients, shadows, and antialiased edges.
13. Use the source editor, not a screen picker, when you need the color encoded in a file.

7. Frequently Asked Questions

7.1 Why does ShareX select a pixel beside my cursor?

A repeatable displacement usually indicates coordinate scaling rather than incorrect color interpretation. Mixed-DPI monitors, a forced Windows compatibility override, or a display-layout transition can cause logical and physical coordinates to diverge. Test on one monitor at 100 percent scale, restart ShareX, and check compatibility settings.

7.2 Why does ShareX show a different hex value from Photoshop or another editor?

The editor may be reporting the RGB value stored in the document, while ShareX is sampling the rendered desktop after profile conversion, blending, HDR processing, or tone mapping. Compare ShareX with another screen picker first. If the screen pickers agree, use the editor's value when the file's encoded color is what matters.

7.3 Can an ICC monitor profile change sampled colors?

An ICC profile can affect how a color-managed application converts document colors for a particular monitor. Whether a screen picker returns pre-conversion or displayed values depends on the rendering and capture path. An ICC-related difference generally does not create cursor offset, so keep profile troubleshooting separate from coordinate troubleshooting.

7.4 Does HDR make the ShareX color picker inaccurate?

HDR can make a straightforward SDR hex comparison unreliable because Windows and applications may map content into an advanced-color output space. This does not automatically mean ShareX is malfunctioning. Turn HDR off temporarily and compare again. For exact asset values, inspect the original file in a suitable editor.

7.5 Why is browser content different from the CSS or image value?

The browser may apply color management to profiled images, composite transparent layers, render antialiased edges, or process HDR media. Browser zoom and display scaling can further complicate location comparisons. Test an opaque CSS block at 100 percent browser zoom and sample its center.

7.6 When should I stop changing ShareX settings?

Stop when the magnifier follows the cursor and ShareX agrees with another screen picker on a flat, opaque test area. At that point, a remaining disagreement with a source file or design tool is probably about color spaces, profiles, HDR, or rendered versus stored color. Continuing to reset hotkeys, uploaders, OCR options, or destinations will not address that distinction.