ShareX Screenshots Are Too Dark or Washed Out: How to Fix Color Problems

If ShareX screenshots look too dark, too bright, flat, washed out, or noticeably different from what you see on the screen, the capture itself may not be the only factor involved. The most common causes are Windows HDR-to-SDR tone mapping, an ICC color profile or wide-gamut display, an image effect applied by ShareX after capture, or a difference in how the resulting file is displayed by browsers and image viewers. Follow the tests below in order. Once the same screenshot looks correct in several color-managed applications, stop changing settings, even if a particular thumbnail or non-color-managed viewer still looks different.

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

Start by determining whether ShareX is creating an incorrect image or another application is displaying a correct image incorrectly. This distinction prevents you from changing capture settings when the real issue is HDR, color management, or a viewer.

1.1 Capture a controlled color chart

Open a simple test image containing white, black, neutral gray, saturated red, green, and blue. A basic color chart is more useful than a game, video, or photograph because you can identify brightness and color shifts without subjective details getting in the way.

1. Place the color chart in a normal desktop application on the monitor being tested.
2. Use ShareX to capture the same fixed region twice.
3. Save the image locally without editing, uploading, resizing, or converting it.
4. Open the saved file in at least two applications, such as Microsoft Paint and a modern browser.
5. Compare the full-size file rather than a small thumbnail.

If neutral gray becomes tinted, investigate color profiles and wide-gamut behavior. If highlights become dull while shadows look heavy, HDR tone mapping is a stronger suspect. If the saved file looks normal in one application but wrong in another, the viewer is more likely responsible than ShareX.

1.2 Compare the thumbnail with the actual file

A thumbnail in ShareX history, File Explorer, an upload service, or a messaging application may be resized, compressed, or rendered through a different color pipeline. Open the original local file at 100 percent zoom before deciding that the capture is defective.

Success means the original image has the expected white, black, and gray levels when opened full size. If only the thumbnail is washed out, there is usually no reason to alter ShareX capture settings.

1.3 Check whether only one monitor is affected

Move the same test chart to each monitor and repeat the capture. Record whether HDR is enabled, whether the monitors use different ICC profiles, and whether one is a wide-gamut display. Mixed-monitor systems commonly expose inconsistencies because Windows can apply different display transformations to each screen.

If captures from one monitor are wrong and captures from another are normal, concentrate on that monitor's HDR mode, color profile, graphics configuration, and calibration. Stop changing global ShareX settings until the monitor-specific difference is understood.

2. Check the ShareX Settings Directly Related to This Problem

ShareX usually captures the pixels supplied through the Windows capture path. It does not automatically guarantee that HDR content, an ICC-managed application, and every destination viewer will all use identical color interpretation. However, ShareX can modify an image after capture through task settings, effects, resizing, or workflow automation.

2.1 Disable image effects temporarily

Review the active after-capture tasks and image effects. Look for brightness, contrast, gamma, color adjustment, grayscale, transparency, border, watermark, resize, or other processing. An effect may have been enabled intentionally for an older workflow and then left active for every capture.

1. Open ShareX and review the current after-capture tasks.
2. Disable image effects and any automatic image editor action for the test.
3. Disable resizing or conversion tasks that create a second output file.
4. Capture the color chart again and save it directly.

Success means the new unprocessed file matches the screen more closely than the previous file. If so, re-enable tasks one at a time until the color change returns. Keep the useful tasks and remove only the effect responsible for the shift.

2.2 Check task-specific settings and hotkey workflows

ShareX can assign different task settings to different hotkeys. A region-capture hotkey may therefore process an image differently from a full-screen capture or a toolbar command. Test the exact hotkey that produces the problem, then compare it with a plain capture launched from the main ShareX window.

If the main-window capture is correct but the hotkey result is wrong, inspect that hotkey's task configuration. Success means both methods save visually equivalent files once their post-capture actions are aligned.

2.3 Avoid assuming the export format is the cause

PNG and JPEG can look different around fine details because JPEG uses lossy compression, but ordinary JPEG compression does not normally explain a major whole-image shift from correct color to severely dark or washed-out color. PNG is the better diagnostic format because it avoids lossy artifacts and preserves sharp color-chart boundaries.

Use PNG for the controlled test. If PNG and high-quality JPEG have the same brightness shift, changing compression quality repeatedly will not solve the underlying HDR or color-management problem. Stop adjusting quality settings and continue with the Windows checks.

3. Check Windows, Displays, and Application Rendering

For this symptom, display and rendering factors matter more than audio, network, upload permissions, or destination credentials. Those other factors can break recording or uploading, but they do not normally make a locally saved screenshot uniformly darker or more washed out.

3.1 Test Windows HDR and SDR tone mapping

HDR is a frequent cause of mismatches between the visible screen and an SDR screenshot. An HDR display can show brightness and color values beyond the range expected by a conventional SDR image. Windows, the graphics driver, the capture method, and the viewing application may each participate in tone mapping that content into an SDR file or SDR-looking preview.

Run a reversible test rather than permanently disabling HDR immediately:

1. Save your work and note the current HDR setting.
2. Open Windows display settings and select the affected monitor.
3. Temporarily turn off HDR for that monitor.
4. Close and reopen the test application so it redraws in SDR.
5. Capture the color chart again and compare the saved PNG.

If the SDR capture matches the screen while the HDR capture does not, ShareX is probably not applying a random brightness effect. The mismatch is in the HDR capture and tone-mapping path. You can leave HDR off during color-critical captures, adjust Windows HDR and SDR content brightness controls, or use a capture method designed for the specific HDR application.

Success means neutral tones, highlights, and shadows survive the capture without an obvious global shift. Once that happens consistently, stop changing unrelated ShareX options.

3.2 Review ICC profiles and wide-gamut behavior

An ICC profile describes how a device represents color. Wide-gamut monitors can display colors outside the typical sRGB range, but applications do not all use profiles in the same way. A color-managed application may transform colors correctly for the monitor, while a non-color-managed thumbnail or older viewer may treat the same RGB values as if they were standard sRGB.

Open Windows Color Management and check which profile is associated with the affected display. Do not delete a manufacturer profile or a calibration profile without recording the current configuration. Instead, compare the image in modern color-aware software and, if appropriate, temporarily test the standard display configuration recommended by the monitor manufacturer.

A strong clue is that the saved file looks correct in one color-managed application but oversaturated, flat, or tinted in another. In that case, the file may be valid. The applications are interpreting it differently. Success means the image looks consistent in the applications and publishing destinations that matter to your workflow, not necessarily in every legacy viewer.

3.3 Test browser and media player hardware acceleration

If the problem occurs only when capturing browser video, streaming content, or a hardware-accelerated media player, compare it with a static webpage and a normal desktop window. Hardware overlays, protected video paths, HDR video, and GPU rendering can produce results that differ from ordinary desktop capture.

1. Pause the video on a representative frame.
2. Capture it with the application's hardware acceleration enabled.
3. Temporarily disable hardware acceleration in that browser or player and restart it.
4. Capture the same frame again.
5. Compare both original PNG files in the same viewer.

If only accelerated video is affected, keep ShareX's general settings unchanged. Use the application's non-accelerated mode when practical, switch its video or HDR setting, or use an application-supported frame export feature. Protected content may intentionally block capture and can appear black rather than merely dark.

3.4 Check Night Light and vendor display enhancements

Windows Night Light, monitor presets, dynamic contrast, blue-light filters, and graphics-driver color enhancements can alter what your eyes see without necessarily becoming part of the screenshot. A screen may therefore look warm or brighter while the captured file contains the underlying unmodified pixel values.

Temporarily turn off Night Light and monitor or GPU enhancements, then repeat the controlled test. If the screenshot and screen now match, the difference came from a display-only adjustment. Decide whether to keep that adjustment for comfort or disable it during color-sensitive work.

4. Run a Clean Temporary Test With Minimal ShareX Settings

A minimal test separates ShareX itself from a complicated automation workflow. It is especially useful when several hotkeys, custom actions, uploads, image effects, or destination-specific conversions are configured.

1. Record or export any settings you may need to restore.
2. Choose a basic region or full-screen image capture from the ShareX interface.
3. Disable after-capture image effects, annotation, resizing, conversion, and automatic upload for the test.
4. Save directly to a local folder as PNG.
5. Capture a static color chart on an SDR desktop.
6. Open the local file in two current applications at full size.

Do not add OCR, screen recording, upload destinations, custom commands, or editor steps until the basic PNG is correct. Those features are valuable, but they introduce extra outputs and make comparison harder.

If the clean test works, re-enable one workflow stage at a time. Capture a new file after each change. The first stage that reintroduces the shift identifies the area to fix. If the clean test fails only with HDR enabled or only on one monitor, focus on Windows and display handling rather than rebuilding every ShareX preference.

5. Check History, Logs, and Recent Workflow Output

Color differences do not always generate an error message, but ShareX history can reveal whether you are inspecting the same file that was originally captured. An automated workflow may save a PNG locally, convert a copy to JPEG, upload the converted copy, and show a service-generated thumbnail. Comparing those different outputs can look like a capture failure.

5.1 Trace the exact file path

Use ShareX history to locate the original output. Confirm its filename, extension, dimensions, and modification time. Then compare it with the uploaded or edited version. If dimensions changed, a secondary processing step occurred. If the extensions differ, conversion occurred.

Success means you can identify precisely where the appearance changes: at capture, during post-processing, after upload, or only during display. Once the stage is known, avoid changing components earlier in the workflow that produce a correct file.

5.2 Use logs for workflow failures, not subjective color alone

Logs are useful when a custom action fails, an image processor reports an error, or the wrong destination file is used. They may not report HDR tone mapping or a viewer's color-management behavior as an error. Check logs when the expected PNG is missing, a conversion command ran unexpectedly, or an upload returned a different file.

If ShareX is otherwise not working, such as failing to save or upload, resolve that operational error separately. Network and destination errors can change which preview you see, but they do not normally alter the colors in an already verified local PNG.

6. Quick Fix Checklist

• Open the original local file at 100 percent instead of judging a thumbnail.
• Capture a simple color chart and compare it in two modern applications.
• Save the diagnostic capture as PNG without resizing, editing, or uploading.
• Disable ShareX image effects and check task-specific hotkey settings.
• Test the affected monitor with Windows HDR temporarily disabled.
• Compare every monitor separately, especially in mixed HDR and SDR setups.
• Review the affected display's ICC profile and wide-gamut configuration.
• Test browser or media-player hardware acceleration when only video is affected.
• Disable Night Light and vendor display enhancements during the comparison.
• Trace the original file through ShareX history before evaluating uploaded copies.

Stop troubleshooting when the original PNG has stable neutral tones and acceptable brightness in the applications and destinations you actually use. Chasing identical previews across every thumbnail generator, legacy viewer, HDR display, and color-managed application may not be realistic because those programs can render the same file differently.

7. Frequently Asked Questions

7.1 Why are ShareX screenshots darker when HDR is on?

HDR content has a wider brightness range than an ordinary SDR screenshot can represent. Capturing or viewing that content may require tone mapping, and different parts of the Windows graphics pipeline can map it differently. If switching the affected monitor to SDR fixes the test capture, use SDR for color-critical screenshots or adjust the HDR workflow rather than applying a permanent brightness effect to every image.

7.2 Why does the screenshot look correct in Paint but washed out in another viewer?

The applications may use different color-management and rendering paths. ICC profiles, embedded color information, wide-gamut displays, and HDR handling can all affect the result. Evaluate the original file in multiple current applications and prioritize the viewer or publishing destination used by your audience.

7.3 Can JPEG compression make the entire screenshot too dark?

Normal JPEG compression mainly introduces detail loss, ringing, and block artifacts. It is not the leading explanation for a severe global brightness or saturation shift. Test with a direct PNG capture. If both formats have the same shift, investigate HDR, ICC profiles, image effects, or viewer behavior.

7.4 Why are only browser videos captured with incorrect colors?

The browser may use GPU hardware acceleration, HDR video processing, an overlay surface, or a protected content path. Test a static webpage, restart the browser with hardware acceleration disabled, and compare the results. If only video changes, the issue is specific to video rendering rather than all ShareX captures.

7.5 Should I reset all ShareX settings?

Not initially. First disable image effects and run a direct local PNG capture with minimal tasks. A full reset can erase useful hotkeys and automation without changing Windows HDR or ICC behavior. Reset settings only after preserving your configuration and confirming that a clean test still points to ShareX.

7.6 How do I know whether the problem is fixed?

The fix is successful when a repeatable color-chart capture preserves neutral gray, readable shadow detail, and reasonable highlights in the original local file, and when that file looks correct in your primary viewer or destination. If only a generated thumbnail remains different, treat that as a preview-rendering issue and stop modifying the capture workflow.