RGB Full vs Limited Range on a PC Monitor or TV

RGB Full and RGB Limited describe which numerical code values represent the normal black-to-white range in an RGB signal. Intel documents Full Range as 0–255 for each red, green, and blue channel in 8-bit mode, while Limited Range typically maps black to 16 and white to 235. AMD exposes the same distinction as RGB 4:4:4 PC Standard (Full RGB) and RGB 4:4:4 Studio (Limited RGB).

The important word is range. Full versus Limited is not a monitor contrast specification, a wider color gamut, a higher bit depth, or a different resolution. A correctly matched Full path and a correctly matched Limited path can both represent black and white correctly because the display interprets the incoming code values according to the same range convention used by the source.

Problems appear when the source and display use different assumptions. If a GPU sends Limited RGB but the display interprets the signal as Full, encoded black at 16 is no longer mapped to the display’s black endpoint and the picture can look gray or washed out. AMD explicitly warns that an unsuitable display picture mode or color-format combination can produce washed-out color.

The opposite mismatch can clip information. If the GPU sends Full RGB while the display treats the signal as Limited, low code values can fall below the display’s expected black endpoint and high values above its expected white endpoint. The visible symptom is often described as crushed blacks or clipped whites. These symptoms are useful clues, but they do not prove which device is misconfigured without checking both ends of the link.

The familiar 0–255 Full and 16–235 Limited numbers describe the conventional 8-bit case. Intel explicitly qualifies its Limited values as typical in 8-bit mode. Higher-bit-depth signals have more code values, so the numeric endpoints scale with precision even though the conceptual distinction between a full-range and a narrower video-range encoding remains.

Do not confuse this with the separate 8-bit versus 10-bit monitor question. Bit depth controls how many numerical levels are available per component. Quantization range controls which portion of those levels represents the normal image range. A path can therefore be 8-bit Full, 8-bit Limited, 10-bit with a full-range convention, or 10-bit with a limited/video-range convention when the devices and format support it.

AMD lists RGB Full and Limited alongside YCbCr pixel formats, while its documentation treats RGB/YCbCr format selection separately from color depth. Chroma subsampling such as 4:4:4, 4:2:2, or 4:2:0 describes the spatial sampling of color-difference information; Full versus Limited describes the encoded level range. One setting does not determine the other.

This distinction is especially useful when a TV is connected to a PC. A display can accept several RGB and YCbCr modes and may apply different processing or range assumptions to different inputs or picture modes. Changing from RGB to YCbCr just to fix a black-level mismatch can hide the underlying configuration problem and can also change chroma behavior. Check the range controls first when the symptom is specifically elevated blacks or clipped dark detail.

Intel notes that Limited Range is commonly associated with TV use while Full Range is its recommended setting, but that is not a rule that every television must use Limited or every monitor must use Full. Modern displays can support multiple formats and may switch behavior with input labels, HDMI black-level controls, picture modes, EDID information, HDR state, or source negotiation.

On AMD Radeon systems, current Adrenalin software exposes supported pixel formats per active display for direct DisplayPort or HDMI connections. Intel Graphics Software exposes Quantization Range under Display on supported configurations. Exact control names and availability remain hardware-, driver-, connection-, and display-dependent, so a missing option should not be replaced with a guessed registry tweak.

After changing a range setting, verify the complete path with a known black-level or grayscale test pattern. The goal is not to make black look subjectively darker; it is to preserve the intended distinction between reference black and near-black steps while keeping white and near-white information where the test pattern expects it. Room lighting, panel black level, local dimming, OLED behavior, gamma or EOTF, and display processing can still affect what you see.

If the image is washed out only in one application or only during video playback, do not assume the global GPU output range is wrong. Applications, video renderers, HDR/SDR conversion, and content itself can use their own color-management and range paths. First establish whether the Windows desktop and a known test pattern are wrong globally, then narrow the problem to the application or media pipeline if the desktop path is correct.

For a conventional PC desktop connected directly to a monitor that supports Full RGB, Full is a straightforward way to use the complete RGB code range and matches the terminology GPU vendors use for PC output. A TV or video workflow may legitimately use Limited when the source and display agree on that convention. The technical objective is matching the source encoding to the display interpretation.

Range selection also cannot tell you whether a display has good contrast, accurate color, a wide gamut, true 10-bit panel hardware, correct HDR tone mapping, full 4:4:4 chroma, or low latency. Those are separate properties. Keeping them separate prevents a black-level configuration setting from being turned into a broad image-quality verdict.