GPU Colour Banding in Gradients? 8-bit vs 10-bit Colour Depth, Limited vs Full Dynamic Range & Panel Diagnosis

2026-10-21 ｜ GPU Repair ｜ About 10 minutes ｜ HK GPU Fix Editorial

Key Takeaways

Colour banding — visible steps or stripes in what should be a smooth gradient, such as a sky, a shadow, or a foggy scene — is usually a colour-depth or dynamic-range problem, not a dead graphics card. An 8-bit signal carries only 256 shades per colour channel, so a gentle gradient has to jump from one shade to the next in visible steps. A 10-bit signal carries 1,024 shades per channel, giving four times as many steps and far smoother transitions. A second, separate cause is a Limited versus Full dynamic-range mismatch: if the graphics card and the display disagree about whether black is level 0 or level 16, the whole picture looks washed out or crushed, and no change of colour depth will fix it. The diagnostic job is to separate these two causes, then find which link in the chain — content, driver setting, cable bandwidth, or the panel itself — is limiting the result.

What Colour Banding Looks Like

Banding shows up wherever brightness or colour changes very gradually across a large area. A sunset sky breaks into concentric bands instead of blending smoothly. A dark corridor in a game shows rings of grey rather than a continuous fall into black. A studio backdrop in a photo or video shows stripes where the light fades. Text and sharp edges usually still look fine, which is the first clue: banding is a problem of fine tonal steps, not of resolution or sharpness.

It helps to distinguish banding from three lookalikes. Backlight bleed and uneven panel lighting show as cloudy patches or glowing corners that stay in the same place regardless of what is on screen, and they are most visible on a fully black screen. Dithering noise, discussed below, looks like fine grain or shimmer rather than clean steps. Compression artefacts from a low-bitrate video look blocky and change from frame to frame, and they follow the video file rather than the display. True banding is stable: the same gradient shows the same steps every time it is displayed, and the steps move with the image rather than staying fixed to the screen.

A useful first check is the screenshot test. Take a screenshot of the banded gradient and open it on a different display, such as a phone or another monitor. If the bands are still there in the screenshot, the steps are already present in the rendered frame — the source content, the application, or the graphics pipeline produced them. If the screenshot looks smooth on the other display but banded on the original monitor, the steps are being introduced at or after the output stage: the driver setting, the cable, or the panel. This one test narrows the search by half before any setting is changed.

Colour Depth: 8-bit, 10-bit, and 8-bit Plus FRC

Colour depth is measured in bits per channel. Each channel — red, green, and blue — gets its own set of steps. An 8-bit channel has 2 to the power of 8, or 256, possible values, from 0 to 255. Three channels together give 256 × 256 × 256, about 16.7 million colours. A 10-bit channel has 2 to the power of 10, or 1,024 values, from 0 to 1023. Three channels together give about 1.07 billion colours. The jump from 8-bit to 10-bit does not make colours brighter or more saturated; it makes the steps between neighbouring colours four times finer, which is exactly what a smooth gradient needs.

Most everyday content — web pages, desktop applications, and much streaming video — is produced and delivered in 8-bit. On an 8-bit chain, that content is displayed as intended, and banding in such content usually comes from the source itself: a heavily compressed video or a gradient drawn with too few steps will band on any display. Higher-bit-depth content, such as 10-bit video files and some games and creative applications, only shows its advantage when every link in the chain preserves it. If any link truncates the signal to 8-bit, the extra steps are lost before they reach the panel, and the result looks the same as 8-bit content.

A true 10-bit panel, sometimes described as native 10-bit, can physically produce all 1,024 steps per channel. An 8-bit plus FRC panel cannot: its liquid-crystal cells still produce only 256 steps, but it adds Frame Rate Control, a form of temporal dithering. The panel rapidly alternates a pixel between two neighbouring 8-bit shades across successive frames, and the eye averages them into an intermediate shade. Done well, this simulates much of the 10-bit range and visibly reduces banding compared with plain 8-bit. It is not identical to native 10-bit, however. The simulation depends on frame timing, so it can be less effective in very dark tones, where the neighbouring steps are far apart in perceptual terms, and a small number of viewers notice flicker or grain in large flat areas. For gaming and general viewing, 8-bit plus FRC is a genuine improvement over plain 8-bit; for colour-critical work, where a shade must be exact rather than averaged, native 10-bit remains the reference.

Two further forms of dithering are worth knowing, because they explain why a setting change sometimes helps and sometimes does nothing. Spatial dithering mixes neighbouring pixels of different shades so the eye averages them across space rather than time; it is commonly used by drivers and applications when they must display a deeper image on a shallower output. Temporal dithering, the FRC method, averages across time. Both are approximations: they hide steps, they do not create new physical shades. If banding survives both a 10-bit output setting and the panel's own dithering, the limiting factor is likely the source content or the panel's native capability, not a missing toggle.

Limited Versus Full Dynamic Range

Dynamic range, in this context, is a separate setting from colour depth, and confusing the two is one of the most common diagnostic errors. Colour depth decides how many steps exist between black and white. Dynamic range decides which numeric values mean black and white in the first place.

Full range, the standard for PC monitors, uses the whole 8-bit scale: 0 is black and 255 is white. Limited range, the standard inherited from television and video equipment, uses a narrower slice: 16 is black and 235 is white, with values below 16 and above 235 reserved for signal headroom. Both are legitimate standards. The picture goes wrong only when the two ends disagree.

If the graphics card outputs Limited range but the display interprets the signal as Full range, the display treats level 16 as a dark grey rather than black. Every shadow lifts, contrast collapses, and the whole image looks washed out and flat. If the graphics card outputs Full range but the display interprets it as Limited, the opposite happens: values below 16 are crushed to dead black and values above 235 blow out to white, so shadow detail and highlight detail are both lost. The first case is by far the more commonly reported, because graphics drivers frequently default to Limited range on HDMI connections. HDMI was designed for televisions, and a driver that cannot confirm what is on the other end often assumes a television. DisplayPort connections, designed for monitors, usually default to Full range, which is why the same monitor can look fine on DisplayPort and washed out on HDMI.

The fix is agreement, not a universal preference for Full. On a PC monitor, set both ends to Full: in the NVIDIA Control Panel, Output dynamic range set to Full; in AMD Software, pixel format RGB 4:4:4 Full; in Intel Graphics settings, quantisation range Full (Intel wording varies by UI version; verify against the installed UI). Then check the display's own menu for a matching setting, often labelled black level, HDMI black level, or RGB range, and set it to Full, High, or Normal depending on the brand's wording. On a television, the television may genuinely expect Limited, in which case both ends should be Limited. Changing only one side leaves the mismatch in place and can make the picture worse, so always change the pair and re-check the result.

Note also that desktop settings and video playback settings are separate in some drivers. NVIDIA, for example, has a desktop output dynamic range under the resolution settings and a separate video colour setting for video playback. A desktop that looks correct can still show washed-out video if the video setting disagrees with the player, and vice versa. When the complaint is limited to video playback, check the video colour setting as well as the desktop setting.

The Full Chain: Where 10-bit Gets Lost

A 10-bit picture must survive four links: content, graphics output, cable, and panel. A break at any link returns the result to 8-bit, and the display will not warn about it.

Content comes first. If the game, video, or application renders in 8-bit, no output setting can invent the missing steps. Some applications need an explicit high-bit-depth or 10-bit option enabled, and some games only output 10-bit in specific modes, such as borderless versus exclusive fullscreen, or only when high dynamic range output is active. Checking the application's own settings before blaming the hardware saves a great deal of wasted effort.

The graphics driver is the second link. In the NVIDIA Control Panel, the relevant controls sit under Change Resolution: output colour depth, output colour format, and output dynamic range. In AMD Software, the equivalents are under display settings as colour depth and pixel format. In Intel Graphics settings, they appear as colour depth and quantisation range (Intel wording varies by UI version; verify against the installed UI). A driver update, a clean driver installation, or a switch from DisplayPort to HDMI can reset these values, so a picture that changed after a driver update or a cable change should have these settings re-checked first. Also note that the driver only offers the depths the display reports through EDID, the identification data the monitor sends on connection. If a monitor's EDID advertises 10-bit support because its scaler accepts a 10-bit signal for FRC processing, the driver will offer 10-bit even though the panel is 8-bit plus FRC. That is normal behaviour, not a fault: sending 10-bit to such a panel lets its FRC engine work from the full data rather than from data already truncated to 8-bit, which generally gives the better result.

The cable is the third link, and it is governed by bandwidth. Higher resolution, higher refresh rate, wider colour format, and higher bit depth all demand more data per second. When the total exceeds what the cable and port combination can carry, the driver may silently fall back: dropping to a lower refresh rate, switching colour format from RGB to YCbCr 4:2:2 or 4:2:0, or dropping depth back to 8-bit. Chroma subsampling — sending full detail for brightness but reduced detail for colour — preserves bandwidth, but 4:2:2 and especially 4:2:0 visibly soften coloured text and fine colour edges, and can make gradients look coarser even though the headline resolution is unchanged. If enabling 10-bit causes the colour format to change from RGB to YCbCr 4:2:2, the trade is usually not worth it for desktop use: an 8-bit RGB signal generally looks cleaner than a 10-bit subsampled one. The remedy is a cable and port combination with enough bandwidth for the desired mode, or a lower refresh rate at the same resolution to free bandwidth for depth.

The panel is the final link. Its native depth is fixed at manufacture and is found in the manufacturer's detailed specifications, not in the marketing headline. A specification that lists 1.07 billion colours without the word native, or that writes 10-bit (8-bit plus FRC), describes an FRC panel. A specification that lists 16.7 million colours describes an 8-bit panel. No driver setting changes either figure. What settings can change is whether the panel receives the best signal it is capable of displaying.

Panel Diagnosis: Is the Panel Itself at Fault?

Once settings and cable are ruled out, the question becomes whether the panel is faulty or simply limited. A limited panel is not broken: it displays everything it was designed to display, and banding in gentle gradients is its expected behaviour at 8-bit. A faulty panel shows something additional — banding that appears suddenly after previously smooth performance, banding confined to one region of the screen, bands that change with panel temperature or with flexing the display, flicker that accompanies the bands, or colour shifts that affect solid colours as well as gradients.

A structured sequence separates these cases:

1. Run the screenshot test described above to decide whether the steps are in the frame or in the output chain.
2. Display a known gradient test image at the panel's native resolution, with no scaling. Scaling a test image up or down introduces its own steps and invalidates the result. Use a full-screen gradient rather than a small window, so compression and window effects do not interfere.
3. Check the black-level test: on a black-level chart, each dark square should remain distinct and visible against the background. If the background looks grey, suspect a Limited versus Full mismatch. If the first few dark squares merge into one black block, suspect crushing from the opposite mismatch.
4. Change one variable at a time: driver depth setting, then dynamic range, then cable, then port, then a second monitor on the same output. If the banding follows the monitor to a different computer, the monitor is the limiting factor. If it follows the graphics card to a different monitor, the card's output or its settings are the limiting factor. If it appears on every combination, the source content is the limiting factor.
5. Test at a lower refresh rate and at the native resolution. If banding disappears at a lower refresh rate, the cause was a bandwidth fallback — the driver was dropping depth or subsampling colour to hold the higher refresh rate.
6. Check for a colour profile problem. A corrupted or incorrect ICC profile can remap tones and create steps that look exactly like depth banding. Temporarily removing custom profiles and returning to the system default, then re-testing the same gradient, isolates this cause quickly.

Graphics-card hardware faults rarely present as pure banding. A failing card more typically shows artefacts that move or change with load — speckles, stray polygons, flashing textures, or crashes — and those artefacts appear on every monitor connected to it. Banding that is identical on two monitors and in screenshots points to content or rendering; banding confined to one monitor points to that monitor's settings, cable, or panel; banding that appears only in one application points to that application's output settings.

This article deals with colour depth, dynamic range, and panel behaviour in ordinary desktop and gaming use. It is distinct from high-dynamic-range tone-mapping problems, where a display's brightness mapping and metadata handling are the issue: if the picture is wrong only when HDR mode is active and correct in standard mode, the HDR pipeline, not the depth or range settings described here, is the place to investigate.

Prevention and Sensible Settings

For a PC monitor, the sensible default is RGB format, Full dynamic range on both ends, and the highest colour depth the combination sustains without forcing chroma subsampling. After any driver update, cable change, or monitor swap, re-check the three driver controls, because defaults can silently revert, particularly on HDMI. Keep the display at its native resolution for gradient-critical work, since scaling adds its own artefacts. When buying a monitor for gradient-critical work, read the detailed specification for native depth rather than the headline colour count, and treat 8-bit plus FRC as a good general-purpose choice and native 10-bit as the choice for colour-critical work.

If banding persists after every setting, cable, and monitor substitution has been tried, and it is accompanied by other symptoms — artefacts, crashes, or output failures — the graphics card's output path or memory may need inspection. A workshop inspection can test the card's outputs against known-good displays and cables and check whether the fault follows the card, which is the decisive test that substitution at home sometimes cannot complete.

For inspection and advice, the workshop is at Dali Plaza Room 1209, Shek Mun. Telephone 2186 8010, WhatsApp 6558 6806. Any repair quotation is given as a final quote after inspection.

Frequently Asked Questions

Why does a gradient band on my monitor but look smooth on my phone?

The two displays differ in colour depth, dynamic range setting, or panel type, or the screenshot and the live output differ. Open the same gradient file, not a screenshot, on both displays at native resolution. If the phone is smooth and the monitor bands, the monitor's chain — setting, cable, or panel — is the limiting factor, and the diagnostic sequence above isolates which link.

Should I set 10-bit output on an 8-bit plus FRC monitor?

Generally yes, provided the colour format stays RGB and the refresh rate does not drop. Sending 10-bit lets the panel's FRC engine work from the full data instead of data already truncated to 8-bit. If enabling 10-bit forces YCbCr 4:2:2 subsampling or a lower refresh rate, revert to 8-bit RGB and compare the two results on the same gradient before deciding.

Is 8-bit plus FRC the same as true 10-bit?

No. A native 10-bit panel produces all 1,024 steps per channel directly. An 8-bit plus FRC panel produces 256 steps and simulates the intermediate shades by rapidly alternating neighbouring shades across frames. The simulation is effective for most viewing and visibly better than plain 8-bit, but it is an approximation, and it can show grain or flicker in large flat areas where native 10-bit stays clean.

Why did my picture turn washed out after a driver update?

Driver updates and clean installations commonly reset the HDMI output dynamic range to Limited. Check the output dynamic range setting and the display's black-level setting, and set both to Full for a PC monitor. Also check the separate video colour setting if only video playback looks washed out while the desktop looks correct.

Can a cable cause banding?

Indirectly, yes. A cable that cannot carry the bandwidth of the requested mode — resolution plus refresh rate plus colour depth plus colour format — forces the driver to fall back to a lower depth or to chroma subsampling, and both make gradients coarser. The cable does not add steps itself; it removes the bandwidth that depth needs. Testing with a known-good cable rated for the mode, or testing at a lower refresh rate, separates a cable bandwidth limit from a panel limit.

Does banding mean my graphics card is failing?

Not on its own. Pure, stable banding in gradients with no artefacts, no crashes, and no output failures points to content, settings, cable bandwidth, or panel depth. A failing card usually adds other symptoms: artefacts that change with load, driver crashes, or failures that follow the card to another monitor. If banding is accompanied by those symptoms, the card should be inspected rather than assumed healthy.