WHITE SATURATION TEST

ADVERTISEMEANT
ADVERTISEMEANT

What this pattern reveals

Near-white steps expose highlight clipping

Excessive contrast, mismatched video range, or picture enhancement can merge bright tones. This pattern places values 235 through 254 against white so you can compare their separation.

The highest values are supposed to be subtle. Lowering contrast too far just to reveal every box can reduce useful image brightness.

How to run the test

  1. 01Use the display preset and signal path you normally use for SDR content.
  2. 02Enter full screen and view the pattern from your normal distance.
  3. 03Look for a gradual reduction in contrast as the numbered patches approach white.
  4. 04If most patches disappear, reduce excessive contrast and confirm the GPU output range.

How to read the result

  • Several patches below white should remain distinguishable without making white look gray.
  • Many identical patches can indicate highlight clipping or a limited/full range mismatch.
  • Tinted near-white patches may point to channel clipping or an aggressive color-temperature setting.

Interpretation guide

Recover bright detail without flattening the image

What near-white separation actually tests

The lightest patches differ only slightly from the white background. If high input values are clipped or compressed too aggressively, several patches merge into one flat white. If contrast is reduced too far, every patch becomes obvious but the display may lose useful brightness and tonal impact. Look for an orderly progression in which intended near-white differences remain visible without adding colored outlines or artificial texture. This is a tone-separation check, not a demand that the screen reach a particular peak luminance.

Contrast controls can clip individual color channels

A global contrast setting may drive red, green, or blue to its maximum before the other channels. The result can be a colored cast in the brightest neutrals even when lower grays look balanced. Dynamic contrast, vivid presets, and channel gains can do the same. Reduce the responsible control until detail and neutrality return, then confirm on natural content such as clouds, white clothing, paper, and specular reflections. Do not compensate for clipped highlights by changing black level, because that shifts a different part of the tone curve.

HDR highlights are governed by tone mapping

In HDR, content can describe highlights brighter than the display can reproduce. The display or operating system must map that range to its capabilities. Some modes preserve highlight detail by rolling off gradually; others maintain more midtone brightness and clip the brightest information. Browser HDR support, operating-system calibration, page color space, and monitor metadata all influence the path. Run this simple page as an SDR visual check unless the tool explicitly identifies an HDR pattern. Formal HDR peak-brightness tests use defined window sizes, sustained durations, and measuring instruments.

Glare and vision can hide subtle bright differences

Strong room light does not wash out white the way it washes out black, but reflections, screen coating sparkle, and excessive luminance can still make small differences uncomfortable to inspect. Use a sustainable working brightness rather than maximizing the backlight. Squinting or moving extremely close changes perceived contrast and is not representative. If one side of the panel loses the patches before the other, repeat the uniformity and viewing-angle tests; the issue may be spatial consistency rather than a single contrast setting.

Reliable visual testing

Build a repeatable test before judging the display

A browser pattern is a controlled visual stimulus, not a measuring instrument. It is excellent for finding visible non-uniformity, clipped tones, scaling errors, halos, color shifts, and motion artifacts under the conditions in which you actually use the screen. It cannot, by itself, report luminance in candelas per square metre, a color difference value, a gamut percentage, or a response-time number. Those claims require a meter, defined test windows, timing equipment, and a documented procedure. Use this page first as a practical screening and comparison tool: it can tell you where to look, whether a change is repeatable, and whether one setting or one display looks better than another.

Treat the entire signal path as part of the experiment. The image passes through the page, browser, operating-system color management, graphics driver, cable or wireless link, monitor input mode, picture preset, and panel before it reaches your eyes. Browser zoom, system scaling, non-native resolution, night-light software, HDR conversion, an ICC profile, dynamic contrast, local dimming, sharpening, noise reduction, and variable refresh can each alter the result. A suspicious pattern therefore does not automatically prove a panel defect. Record the active resolution, refresh rate, browser, picture mode, brightness, contrast, color temperature, HDR state, and any adaptive features so that you can reproduce the observation.

Control the room before comparing results. Allow the display to reach a stable operating state, clean the screen with the method recommended by its manufacturer, and prevent direct reflections from crossing the test area. Use moderate, stable ambient light for general checks. Use a dim room only for near-black, black-uniformity, and blooming observations, because those artifacts are easily hidden by reflections and eye adaptation. Do not judge a dark screen immediately after looking at a bright white page; give your vision a short period to adapt. Keep your normal viewing distance and eye height unless the test specifically asks you to move off-axis.

Run the first pass at the panel's native resolution with browser zoom at 100 percent. Full screen reduces distractions, but it does not cancel operating-system scaling or color processing. Inspect once from your normal position, then move closer only to identify the structure of an artifact. Change one control at a time and repeat the same pattern after every change. If several settings move together, you lose the ability to say which one helped. A useful comparison is A/B/A: observe the baseline, apply one change, then return to the baseline. If the effect disappears and returns with the setting, the relationship is more credible than a single impression.

Look for repeatability across content, positions, and inputs. Rotate or move the pattern when the tool allows it. Test a second browser, input, cable, refresh rate, or computer if the finding matters. A mark that stays in the same physical place on the panel is more likely to be display-related; a mark that follows a browser window or screenshot may originate earlier in the signal chain. Photographing the screen can help document location and severity, but a camera introduces exposure, focus, lens shading, moiré, rolling shutter, tone mapping, and white-balance errors. A photograph is evidence of what the camera captured, not a substitute for a calibrated reading.

A compact pre-test checklist

01Stabilize the display

Let brightness and temperature settle, disable screen savers, and avoid testing while the device is rapidly changing power or thermal state.

02Confirm the signal

Use native resolution, verify the intended refresh rate and RGB range, set browser zoom to 100 percent, and note whether SDR or HDR is active.

03Neutralize temporary processing

Pause night light, automatic brightness, dynamic contrast, content-adaptive brightness, and vendor enhancement modes unless one of them is the feature being tested.

04Control the environment

Remove glare, keep ambient light stable, sit square to the screen, and use a darker room only when the test calls for near-black observation.

05Make one change

Adjust only one setting between runs, return to the original value for confirmation, and write down values instead of relying on memory.

06Repeat before concluding

Reopen the pattern, try representative real content, and check another browser or input when the consequence of a wrong conclusion would be costly.

How to turn an impression into useful evidence

Describe what you see without jumping directly to a diagnosis. Record the pattern, color or tone, screen region, viewing distance, room lighting, time after power-on, and whether the artifact changes with angle or settings. Terms such as “a pale vertical band in the left third on 30–50 percent gray” are more useful than “the panel is bad.” Severity should be tied to normal work: state whether the effect is visible only in a dark test room, during ordinary desktop use, or in real video and games. This makes comparisons between presets, firmware versions, and replacement units much more meaningful.

Escalate the method when the decision requires numbers. Photographers and designers may need a colorimeter or spectrophotometer for white point, gamma, tone response, color accuracy, and uniformity. HDR evaluation needs defined test windows and an instrument that can measure bright highlights and dark levels. Motion measurements need synchronized capture or a validated pursuit-camera method. Warranty decisions should follow the manufacturer's pixel, uniformity, and return policies rather than an unofficial universal threshold. The visual test remains valuable: it identifies the question that a formal measurement needs to answer.

What a visible symptom may mean

Top patches merge into one white field

Lower contrast or channel gain and disable vivid or dynamic modes. Confirm that the source is not being tone-mapped by an unintended HDR conversion.

Bright grays turn pink, green, or yellow

One or more channels may be clipping early. Compare a neutral color-temperature preset and undo per-channel gain changes before judging the panel.

All patches are very dark and obvious

Contrast may be unnecessarily low or the page may be rendered through an altered gamma curve. Restore a neutral baseline and judge with real highlights.

Separation differs across the screen

Check viewing position, white uniformity, and local-dimming behavior. A spatial difference cannot be corrected reliably with a single global contrast control.

What this browser test cannot measure

It cannot measure peak luminance, HDR tone mapping, color temperature, or grayscale accuracy. Results depend on the active SDR image path.

White saturation questions

Do I need to see every box?+

No. The highest levels can be extremely close to white. Aim for a gradual transition and preserve a clean white background.

Which setting should I adjust first?+

Check the GPU and display range first, then adjust the monitor contrast control in small steps. Avoid changing several controls at once.

Methodology and further reading

Lagom's combined LCD test describes near-white squares that should remain distinguishable, while EIZO's gradient guidance provides the broader expectation of steady tonal transitions. RTINGS' peak-brightness methodology demonstrates why actual SDR and HDR luminance claims require warm-up, defined window sizes, and instruments.

Lagom LCD Test Pages — White SaturationLagom
EIZO Monitor Test — GradientsEIZO
Our Monitor Peak Brightness TestsRTINGS

Continue testing

Related monitor tests