Full RGB vs. Limited RGB: Quantifying the Display Mismatch That Ruins Shadow Detail

If your game looks washed out or the shadows are crushed into pure black, your source and display are speaking different color languages. A PC outputting Full RGB (0-255) to a screen expecting Limited RGB (16-235) physically deletes the darkest and lightest details, while the reverse turns true black into a milky gray.[1][4]

The stakes are immediate for anyone upgrading their setup in 2026. You can spend $800 on a high-end OLED gaming monitor or a premium LG television, but a single toggle in the Nvidia Control Panel or PlayStation 5 settings dictates whether you actually see the contrast you paid for. The hardware cannot out-render a broken digital handshake.[3][7]

The math begins with the standard 8-bit color space. Full RGB uses 256 steps per color channel—Red, Green, and Blue—creating 16.7 million possible combinations. In this pipeline, zero is absolute black, and 255 is absolute white. PC monitors natively speak this language, expecting the full spectrum of data from the graphics card.[1][2]

Limited RGB operates on a narrower band. Broadcast television established the 16-235 standard decades ago to leave headroom and footroom for signal overshoot over analog cables. Here, 16 is absolute black and 235 is absolute white, leaving 220 steps per channel and roughly 10.6 million total colors.[3][8]

The "Crushed Black" scenario occurs when a Full RGB source feeds a Limited RGB display. The PC sends a luminance value of 5, intending to render a dark gray shadow in a competitive shooter. The TV, however, treats anything 16 or below as pure black, instantly erasing the gradient.[1][7]

The result is catastrophic for competitive gaming and visual fidelity alike. "Video range (16-235) is the standard for consumer video," notes calibration software developer Portrait Displays, but forcing a 0-255 signal into that container clips 14% of the total luminance data. Enemies hiding in dark corners disappear entirely into a wall of crushed black pixels.[8][9]

The "Washed Out" scenario is the exact inverse. A console sends a value of 16, intending to display absolute black during a loading screen or a dark cinematic. The PC monitor, expecting 0 for black, renders that 16 as a highly visible dark gray.[4][6]

This mismatch artificially compresses the contrast ratio, raising the black floor by 6.2%. The entire image looks as though a white film has been placed over the screen, a common complaint when connecting a PlayStation 5 or Xbox Series X to a PC monitor without adjusting the console's video output settings.[4][9]

The fix requires parity, not necessarily forcing Full RGB everywhere. If the source sends Limited, the display must expect Limited. If the source sends Full, the display must expect Full. The visual output of a properly matched 16-235 signal is virtually indistinguishable from a 0-255 signal on a standard television.[2][3]

Consoles connected to televisions should generally remain on Limited, which is often labeled "Automatic" or "Low" black level in the TV settings. Sony and Microsoft designed their operating systems around the assumption that they will be plugged into living room displays, which default to the 16-235 broadcast standard.[3][7]

PCs connected to monitors should use Full RGB. However, when routing a PC to a television via HDMI, users must manually verify the handshake. Nvidia and AMD drivers often detect a TV and default to Limited RGB, requiring a manual override in the control panel to restore the 0-255 range.[6][7]

Hardware intermediaries frequently break this chain without warning. As monitor manufacturer KTC documents, HDMI splitters and capture cards can strip EDID (Extended Display Identification Data), causing the source to default to Limited RGB while the monitor still expects Full, instantly washing out the image.[5]

The hardware does not auto-correct a forced mismatch. Until display handshakes become universally foolproof across all HDMI 2.1 and DisplayPort 2.1 devices, verifying the 0-255 or 16-235 alignment remains the only way to ensure the image on the screen matches the code in the engine.[5][9]