sRGB Test

How this test works

Use standard sRGB CSS colors as a visual reference for clipping, neutrality, and tonal separation.

1. Prepare the display using the checklist below.
2. Select Start test and allow fullscreen mode if your browser asks.
3. Use the arrow keys, on-screen controls, or click the pattern to move through the test.
4. Exit the runner and save a local observation if useful.

Before you begin

• Select an sRGB or standard display mode
• Disable vivid and wide-gamut enhancement
• Enable the correct ICC profile

What to look for

• Distinct saturation steps
• Neutral gray without a strong tint
• Smooth gradients without abrupt clipping

Treat sRGB as a defined content space

sRGB is the reference color space for much ordinary web imagery and interface content. This runner uses sRGB-defined browser colors, neutral tones, gradients, and saturation steps as visual references. Select the display’s sRGB or standard mode if it has one, use the correct system profile, and disable temporary vivid or night-light effects for a controlled comparison. Look for a strong gray cast, clipped saturation steps, or abrupt bands. The question is whether the active path behaves plausibly with standard content, not whether your eyes can certify a numerical sRGB result.

A wide-gamut display in an unmanaged or vivid mode can make standard content look more saturated than intended. A correct sRGB mode may initially appear less dramatic, especially if you are accustomed to a wide-gamut preset. That change alone does not establish calibration quality. Compare the same page under one mode at a time and keep brightness similar. If neutral gray is tinted across only part of the panel, uniformity may be the better follow-up; if the issue is isolated to one channel, use the RGB page.

Understand the browser-to-display path

A CSS sRGB value begins as a defined digital color, but the browser and operating system may transform it using a display profile before output. The graphics driver, display electronics, and panel then determine the physical light you see. Differences between browsers or apps can arise from color-management behavior rather than a defect in the panel. Record the browser, profile, picture mode, and whether the same content looks different elsewhere. Do not assume that a screenshot taken on one screen preserves the physical appearance seen on another.

The test cannot measure sRGB coverage, white-point error, or Delta E because it has no calibrated light sensor. It also cannot determine whether your system profile accurately represents your particular display. Use a colorimeter or spectrophotometer with suitable software for that. The value of this browser pattern is practical: it lets you inspect whether standard colors and tone steps show obvious clipping, tint, or inconsistent behavior while keeping the content itself controlled.

Use focused comparisons for the next question

If you need to know whether the browser can distinguish Display P3 values from sRGB fallbacks, use the Display P3 page. If you want a broader explanation of color-space mapping and clipping, use the color gamut page. This sRGB page stays centered on standard web-color rendering. A visible difference between two modes does not tell you which is objectively accurate. First ask which mode you intend for your workflow, then compare with familiar images and, if accuracy matters, measured calibration results.

Write down the exact field or step that looked unusual, and repeat with the same window, browser, and room light. Avoid treating maximum saturation as success. A restrained mode may better preserve intended relationships among colors, while an oversaturated one may make skin, logos, or gradients look wrong. This page offers visual clues for troubleshooting a standard-color workflow, not a score or percentage coverage. It does not change your system profile or calibrate the screen for you.

Frequently asked questions