Why did my monitor suddenly turn red over HDMI?

The most common cause is a dynamic-range mismatch: NVIDIA and AMD graphics drivers can default an HDMI connection to a Limited (16-235) color range instead of Full (0-255), which the monitor then displays as oversaturated, red-shifted color rather than the washed-out look you'd expect. NVIDIA's own Control Panel documentation covers this directly — opening Display > Change Resolution > Output Dynamic Range and setting it to Full (or checking the monitor's own 'HDMI Black Level'/'RGB Range' OSD setting) clears it in most cases without touching a cable or driver reinstall.

Is a red tint a GPU problem or a monitor problem?

It can be either, which makes red tint less predictable than other color casts. Start with the dynamic-range setting in your GPU control panel, since that's the single most common cause and costs nothing to check. If that's already correct, work through the monitor's OSD color-temperature preset, a cable swap, and a driver reinstall next. A failing graphics card is the least common cause but is real — a documented Tom's Hardware forum case traced a persistent red tint to a defective RTX 2060 that produced the same artifact on a second PC, confirming the GPU rather than the monitor was at fault.

How do I fix the HDMI dynamic-range red tint on NVIDIA or AMD?

On NVIDIA: open NVIDIA Control Panel > Display > Change Resolution, scroll to Output Dynamic Range, and select Full. On AMD: open AMD Software > Display and set the Color Depth/Pixel Format's RGB range to Full. Then check the monitor's own OSD menu for a setting often labeled 'HDMI Black Level,' 'RGB Range,' or 'RGB PC Range' and set it to Full/High/Normal (0-255) rather than Limited/Low (16-235) — both ends of the cable need to agree, or the mismatch persists.

Can a bad cable cause a monitor to look red?

Yes, most often on VGA. A VGA connector carries red, green, and blue on three separate analog pins, so corrosion or a bent pin on the green or blue pin specifically can leave red relatively dominant even though nothing about the red channel itself changed. HDMI and DisplayPort are digital and fail less often this way, but a damaged connector or failing shielding can still corrupt color data enough to produce a reddish cast, especially if the tint changes when the cable is flexed or reseated.

Is a red tint a sign my monitor is dying?

Rarely — check the dynamic-range setting, the OSD color-temperature preset, a different cable, and an updated GPU driver first, since all four are free and cover the large majority of cases. If the tint survives every one of those checks, and especially if it's present from a cold boot on the monitor's own factory picture mode across multiple source devices, the remaining causes are a failing GPU or an aging backlight/color-processing component in the panel itself, and replacement is usually more practical than a component-level repair.

Monitor Screen Turned Red? How to Fix It (2026)

Quick Answer: A monitor that suddenly looks red or oversaturated is, in most cases, an HDMI dynamic-range mismatch — NVIDIA and AMD drivers can default HDMI to a Limited (16-235) color range instead of Full (0-255), which displays as red-shifted, oversaturated color rather than the washed-out look that mismatch usually causes on other connections. Per NVIDIA’s own Control Panel documentation, switching Output Dynamic Range to Full in Display > Change Resolution clears it in most cases; a monitor color-temperature preset stuck on Warm, a damaged cable, or an outdated GPU driver account for nearly all the rest. A failing graphics card is rare but real — a documented Tom’s Hardware forum case traced a persistent red tint to a defective RTX 2060, confirmed when the same card produced the same artifact on a second PC.

A red or oversaturated cast is one of the less predictable monitor color problems because, unlike a tint that’s purely a monitor or cable issue, red is one of the few casts that a genuinely failing graphics card can also cause. The color model behind every image a monitor builds is just red, green, and blue light combined, so red dominance means either red is being pushed too hard or green and blue are being suppressed — and the fix depends entirely on which layer of the signal chain that’s happening in: the GPU’s dynamic-range setting, the cable, the driver, or the monitor’s own OSD.

Red tint causes and fixes, ranked by likelihood

Cause	How to tell	Fix
HDMI dynamic-range mismatch (Limited vs Full)	Only happens over HDMI, not DisplayPort; colors look oversaturated, not washed out	Set Output Dynamic Range to Full in NVIDIA/AMD settings, match the monitor's OSD RGB-range setting
Monitor color-temperature preset	Tint is present at all hours, on every input device	Open the OSD and switch color temperature from Warm to Normal/6500K
Outdated or corrupted GPU driver	Started right after a driver or Windows update	Update the graphics driver, or roll back to the prior version
Loose or damaged cable	Tint worsens when the cable is touched, or clears on a different cable/port	Reseat firmly, or swap to a new cable — especially on VGA
Failing GPU or aging backlight/panel	Tint survives every check above, on a different PC or monitor it also appears	Test on a second PC/monitor to isolate which component is at fault, then replace it

Why it happens: the HDMI dynamic-range mismatch is the current top cause

NVIDIA’s own Control Panel help documentation describes an “Output Dynamic Range” setting with two options — Limited (16-235) and Full (0-255) — and notes that HDMI connections in particular can default to Limited even when the monitor expects Full. The two color ranges compress or expand where black and white sit within the 0-255 scale, and when the GPU and monitor disagree about which range is in use, the mismatch shows up as oversaturated, often red-shifted color rather than the flatter, washed-out look you’d expect from a range error. This is why the fix lives on both ends of the cable: the GPU’s own dynamic-range setting (NVIDIA Control Panel > Display > Change Resolution, or AMD Software > Display) has to match whatever the monitor’s OSD calls its “HDMI Black Level” or “RGB Range” setting, and DisplayPort connections are rarely affected by this specific mismatch at all.

Samsung ViewFinity S8 (S80UD) — Best Replacement If It's the Panel

Best if hardware is confirmed · 27" 4K IPS, 3-side slim bezel · USB-C 90W + KVM · about $449.99

Factory-calibrated color out of the box, so a fresh unit doesn't inherit a drifted OSD color-temperature preset the way a years-old monitor can.
USB-C with 90W charging and a built-in KVM makes it a clean single-cable replacement if you're swapping out a monitor rather than chasing a GPU or cable fault.
The right pick once the dynamic-range setting, OSD preset, drivers, and a cable swap have all ruled out an easy fix and the tint is confirmed to be a hardware fault in the panel.

If it’s not the dynamic-range setting

Check the GPU’s Output Dynamic Range first. NVIDIA: Control Panel > Display > Change Resolution > Output Dynamic Range > Full. AMD: Software > Display > set the RGB/pixel format range to Full. This clears the single most common cause of a red-over-HDMI tint in seconds.
Match the monitor’s own RGB-range OSD setting. Look for “HDMI Black Level,” “RGB Range,” or “RGB PC Range” in the monitor’s menu and set it to Full/High/Normal, not Limited/Low — both the GPU and the monitor need to agree.
Open the OSD and check color temperature. Switch out of any “Warm” or “Reading” preset to Normal, User, or a stated 6500K/D65 option.
Update the graphics driver. A corrupted or outdated NVIDIA, AMD, or Intel driver can shift color-channel output; updating (or rolling back a driver installed right before the tint appeared) resolves driver-side causes.
Try a different cable and port, and a different input (DisplayPort instead of HDMI, if available) to isolate whether the cable or connection type is involved.
Test the monitor on a second PC, and the GPU on a second monitor, if the tint persists. This is the only reliable way to tell a failing graphics card from a failing panel — swap one variable at a time rather than replacing both at once.

Red tint by the numbers

16-235 vs. 0-255. The two dynamic-range scales NVIDIA’s own Control Panel documentation names for HDMI output — Limited and Full, respectively — and the source of the mismatch that causes most reported cases of a sudden, oversaturated red or reddish cast over HDMI specifically, not DisplayPort.
A defective GPU, confirmed on a second PC. A documented Tom’s Hardware forum troubleshooting case traced a persistent red tint to a failing RTX 2060 rather than the monitor — the same graphics card produced the identical artifact when moved to a different computer, which is the diagnostic step that actually separates a GPU fault from a display fault.

The bottom line

Check the GPU’s Output Dynamic Range setting first if you’re on HDMI — it’s the fastest fix and covers the single most common cause of a sudden red or oversaturated cast. If that’s already set to Full, work through the monitor’s own RGB-range OSD setting, its color-temperature preset, a driver update, and a cable swap in order. A tint that survives all of those, and reproduces on a second PC or a second monitor, has crossed into genuine hardware failure, and a factory-calibrated panel like the Samsung ViewFinity S8 removes the drifted-preset failure mode for good. Same setting, opposite symptom: on most panels this dynamic-range mismatch produces a flat, faded look rather than red — see our monitor colors washed out guide for that more common case. Chasing a different color symptom instead? Our monitor yellow tint, monitor pink tint, and monitor blue tint guides cover the other common color casts with an overlapping but distinct set of causes, and our monitor color calibration guide covers getting a panel to genuinely accurate color once any cast is already resolved.