Motion comparison hub
Track synchronized objects at three speeds, switch edge structure, and use a compact browser-cadence status to name the symptom before choosing another test.
What did you notice?
Choose the closest visible symptom. You can change the selection before opening a test.
Suggested next checkStart with the Dead Pixel Test
Open the dead pixel checkCompare the fixed point on white, red, green, blue, and grey fields.
Choose by symptom, not by guesswork
Screen Test: Check Pixels, Uniformity and Screen Colors
This screen test hub matches a visible symptom with a focused browser workflow. Start with the smallest useful check, compare more than one field, and treat the result as a visual observation rather than an electronic measurement of the panel.
Motion
Compare cadence, trails, and motion discontinuities
Motion symptoms need animated references and stricter limits than solid fields. Start with the combined view, then use the focused workflow that matches what you see.
Refresh cadence
Estimate requestAnimationFrame cadence with a warmup, bounded interval window, median, recent range, and documented jitter formula. This is not a direct panel query.
Ghosting trails
Move original block, text, line, dark, and light patterns to inspect trailing, dark smearing, inverse ghosting, and persistence blur without calculating fake GtG values.
Tearing patterns
Move bars, a checkerboard, or a grid while accounting for synchronized browser compositing. Absence of a visible tear cannot certify VRR or its operating range.
Two scales of evidence
Is the symptom one point or a panel area?
The size and behavior of the mark determine which screen test is most useful.
Pixel-level behavior
A single fixed coordinate that stays dark, bright, or colored belongs in the dead-pixel or stuck-subpixel workflow. Compare that exact point on black, white, RGB, CMY, and grey fields. A point that moves with a reflection or changes after coating-safe cleaning is less consistent with a physical pixel defect.
Area-level panel behavior
A corner glow, bright edge, broad tint, vertical band, cloud, or dirty-screen effect is larger than one pixel. Neutral fields and a consistent viewing position help separate luminance or tint uniformity from angle-dependent panel behavior, backlight effects, and image processing.
Focused tools with different jobs
Screen testing fields organized by purpose
Black and near-black
Pure black can expose a bright or stuck point. Low grey levels add shadow-field context for LCD glow, OLED near-black behavior, and dark-scene irregularities without pretending to measure physical black luminance.
White and bright neutrals
White makes dark points and some surface specks easier to see. Bright neutral steps and optional zones also help compare tint or brightness across the panel at a comfortable device brightness.
Color and channel fields
RGB and CMY fields support channel comparisons; custom colors recreate a background where a mark was first noticed. Split fields and a simple ramp reveal obvious visual differences, not calibrated color accuracy.
Color & tone
Inspect tone steps, gradients, channels, and visible detail
These six tools separate different rendering questions. None substitutes for a colorimeter, luminance meter, or controlled calibration workflow.
Grayscale steps
Compare 4–64 grey patches, a smooth neutral ramp, uniform mid-grey, and focused near-black or near-white ranges.
Color banding
Scan neutral, RGB, and CMY transitions in smooth or deliberately stepped rendering modes without inferring panel bit depth.
Visual gamma
Match calculated solid neutral values with ordered-pixel fusion references for target responses from 1.8 through 2.4.
Shadow and highlight contrast
Inspect visible endpoint steps, checkerboards, alternating blocks, and subtle mid-tone shapes without claiming a measured ratio.
Near-black level
Concentrate adjustable steps, original PLUGE-style bars, and full fields within the first few percent above black.
RGB channels and mixes
Switch between primary fields, 0–255 channel ramps, known steps, and additive secondary color combinations.
A short first-day workflow
New screen quick check
Use normal settings first. Extreme conditions can make minor effects look more important than they are in use.
- Inspect the surface and native setup. Remove obvious reflections, confirm expected scaling and resolution where available, and use only cleaning guidance intended for the display coating.
- Run the main pixel sequence. Scan black, white, red, green, blue, and grey in a repeatable path. Keep any suspect point at the same coordinate as fields change.
- Compare bright and mid-grey uniformity. Look from your usual centered position for broad tint, banding, or brightness changes. Then shift your viewing angle to see whether the appearance moves.
- Check dark content at a realistic brightness. On a backlit LCD, compare black and near-black fields in a dim room. On OLED, use the dark fields for visual behavior, not a backlight bleed diagnosis.
- Compare motion at the display setting you plan to use. Open the motion comparison, then check browser cadence or moving-edge trails if smoothness is part of your new-screen evaluation. These visual tools do not measure physical response time or certify VRR.
- Document observations in ordinary use. A screen test is more informative when a suspected issue is also visible in normal content. Retailer and manufacturer policy, not this screen tester, determines return or warranty outcomes.
What the browser contributes
How an online screen test works
Normal images contain edges, texture, compression, and many colors. A browser screen test replaces that visual clutter with controlled CSS fields or simple patterns. Your eyes can then compare neighboring pixels or larger panel regions under repeatable conditions.
The requested color passes through the browser, operating system, GPU, color profile, cable or internal display link, and the panel’s own processing. That chain is exactly why this screen tester is useful for visible inspection but cannot report laboratory values. A colorimeter or imaging photometer is required to quantify white point, gamut, Delta E, luminance, contrast, or zone-to-zone deviation.
Continue by observation