MONITOR GRADIENT TEST

ADVERTISEMEANT
ADVERTISEMEANT

What this pattern reveals

A gradient exposes breaks in the image pipeline

Smooth ramps make quantization, limited-range mismatches, aggressive picture processing, and low-bit-depth content easier to notice. The upper ramp checks neutral tones while the lower ramp checks hue transitions.

Banding can originate in the browser, graphics driver, cable range, display processing, or the panel. Use the pattern to locate a symptom, then compare another browser and source.

How to run the test

  1. 01Set browser zoom to 100% and disable temporary contrast, night-light, or color-filter features.
  2. 02Enter full screen and inspect both ramps from your normal viewing distance.
  3. 03Look for hard vertical boundaries, repeated bands, crushed ends, or tinted sections.
  4. 04Compare SDR and HDR modes separately and repeat in another browser before changing the monitor.

How to read the result

  • A good result appears continuous, although very faint steps may still be visible on an 8-bit path.
  • A large flat region near black or white suggests clipping or a range mismatch.
  • Bands that move or change in another browser are more likely caused by software or color management than the panel.

Interpretation guide

Separate true banding from the steps built into a signal

What a smooth gradient should communicate

A continuous grayscale ramp should progress steadily from dark to light without abrupt plateaus, colored streaks, reversals, or isolated contour lines. Perfect visual smoothness is not guaranteed: the source has finite code values, the browser composites the page, the graphics pipeline may dither, and the panel has its own bit depth and temporal processing. The practical question is whether transitions are unobtrusive at normal distance and whether obvious bands also appear in well-mastered photographs, games, or video. Inspect the whole ramp, then pay special attention to the darker end where equal numeric steps can be harder to display.

Bit depth, dithering, and compression leave different clues

Insufficient tonal precision tends to produce broad contours that follow equal-tone regions. Dithering replaces a missing intermediate tone with fine spatial or temporal noise; from normal distance it may look smoother, while close inspection can reveal a texture. Image or video compression may create block-shaped boundaries or ringing that changes with the source. This page is generated in the browser and avoids video compression, which helps isolate the display path, but screenshots, remote desktops, color profiles, and GPU output settings can still modify the ramp.

Recent setting changes can create the artifact

Strong contrast, black equalizer, gamma, color-channel curves, HDR-to-SDR conversion, and calibration corrections can compress or stretch parts of the tone range. When adjacent input values are mapped to the same output, bands or clipped areas appear even if the panel can show finer steps in another mode. Return to a neutral preset and compare before assuming a hardware limit. If a custom ICC profile or graphics-card correction is active, repeat in a color-managed application and with the correction temporarily removed, while preserving the original configuration so it can be restored.

Use distance and multiple colors deliberately

Evaluate smoothness from normal viewing distance first; sitting inches from the panel overemphasizes pixel structure and dithering that merge during real use. A neutral gray ramp is sensitive to both tone discontinuities and RGB imbalance, because unequal channels create colored bands. Separate red, green, and blue ramps can help identify whether one channel clips or steps differently, but they still do not measure gamma or color accuracy. For production decisions, use calibrated software and instruments in addition to the visual screen.

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

Wide, stable contour bands

Reset aggressive contrast or gamma controls and compare SDR with HDR. Persistent contours may reflect limited precision or a tone curve that collapses adjacent values.

Fine sparkling or crawling texture

This may be spatial or temporal dithering rather than banding. Step back to normal distance and check whether the texture resolves into a smoother tone.

Colored stripes in a gray ramp

Disable color-temperature enhancements and inspect each channel. Unequal channel mapping, a profile, or panel color non-uniformity can turn a neutral transition into tinted bands.

Bands appear only in one browser

Compare browser color management, hardware acceleration, HDR behavior, and extensions. A browser-specific result should not be assigned to the panel without another controlled check.

What this browser test cannot measure

The pattern cannot certify bit depth, gamma accuracy, HDR performance, or color calibration. Browser rendering and screenshots may introduce their own banding.

Gradient test questions

Does visible banding mean my monitor is defective?+

Not necessarily. Banding can come from compressed content, an 8-bit signal, GPU settings, browser color handling, or monitor processing. Compare multiple sources first.

Should I enable dithering?+

Dithering can make steps less visible, but support depends on the graphics path and display. Test the normal configuration you actually use before adjusting advanced settings.

Methodology and further reading

EIZO and Lagom both use smooth grayscale transitions as a visual check and caution that abrupt breaks or colors are undesirable. Lagom additionally explains that dithering and earlier display-setting changes can affect the result. The native-resolution and signal-path guidance comes from Lagom's display-settings documentation.

EIZO Monitor Test — GradientsEIZO
LCD Gradient TestLagom
Display Settings for LCD TestsLagom

Continue testing

Related monitor tests