Screen Gradient Test

Choose a gradient pattern and fullscreen the test area to inspect smooth tonal transitions.

Gradient

Direction

Visible banding can come from the display, GPU output format, browser composition, image processing, or viewing conditions. This is a visual inspection pattern rather than a colorimeter measurement.

What the browser can measure

Start with a functional check, measure only what the browser can actually expose, then retest after one change.

ConnectChoose the actual browser-visible device or grant permission when required.

TestConfirm basic signal, input, output, preview or display behavior.

MeasureUse browser-exposed levels, timing, resolution, FPS, axes or event data.

DiagnoseCompare the symptom with the specific diagnostic instead of relying on one number.

RetestRepeat after changing the device, cable, permission, browser or system setting.

Pre-call Mic Webcam Keyboard Mouse Gamepad Display Permissions

Browser boundary
These tools observe browser APIs and local media/event streams. They cannot certify hardware condition, bypass denied permissions, or expose measurements the browser/OS does not provide.

Banding lab: dark range, RGB, radial & stepped reference

Compare controlled browser-generated patterns without claiming to measure native panel bit depth.

PatternReferenceDirection

—Browser colorDepth

—Device pixel ratio

—Screen CSS px

—Pattern

Browser colorDepth reports environment context, not verified native panel depth. Compare browsers and inputs before diagnosing hardware.

Browser-local does not mean laboratory measurement

These pages can report Web API data such as events, stream settings, frame timing and audio samples. They do not certify hardware condition or bypass browser and operating-system limits.

Gradient inspection is explicitly a visual banding reference

Browser rendering, ICC/color management, bit depth, dithering and display processing can affect what is seen. The test does not claim to measure native panel bit depth or calibrated gamma.

Practical guide and verification

Use the product first, then apply these tool-specific checks to verify assumptions, interpret the result, and hand it off safely without moving the primary workflow below generic content.

Banding is a symptom, not a direct bit-depth measurement

Visible steps can come from the panel, GPU output, browser composition, ICC transforms, limited-range signaling, image processing, or the generated content itself. A smooth browser ramp cannot prove true 10-bit panel depth, and visible banding does not automatically prove a defective display. Use this page as a controlled visual reference.

Inspect dark gradients separately

Quantization is often easiest to notice near black because adjacent encoded levels represent a larger relative brightness change. Test a full grayscale ramp first, then a dark-range ramp without changing brightness or picture mode. If the result changes between browsers or inputs, investigate the signal path before blaming the panel hardware.

Use stepped references to calibrate your eyes

A deliberately quantized 16-, 32-, or 64-step reference shows what actual discrete transitions look like. Compare it with the smooth ramp from normal viewing distance, then move closer only to inspect a suspected boundary. The goal is to distinguish real repeated contours from texture, glare, compression, or browser scaling artifacts.

Control the viewing setup before comparing results

Set browser zoom to 100%, use native display resolution, disable temporary night-light or dynamic-contrast modes, and keep the same room lighting for comparisons. Fullscreen reduces interface distractions but does not bypass operating-system color management. Record the browser, connection, picture mode, and output format when documenting a repeatable issue.