Color and dead pixels
Black, white, and RGB solids are the fastest way to catch dead pixels, bright pixels, dark pixels, and obvious tint imbalance.
Click to start fullscreen inspection
Inspect dead pixels, bright pixels, and dark pixels
Current: Pure black
#050505 · Press F for fullscreen
Device info
Screen width
--Device pixel ratio
0.0Color depth
--Refresh rate
--Controls
← →
Switch test colors F
Enter fullscreen Esc
Exit fullscreenShortcuts stay active outside input fields: use left/right arrows to switch patterns, F for fullscreen, and Esc to leave.
Color picker
Pure black
#050505Custom color
Fullscreen quick checksDead-pixel friendly patternsLive device info
Screen Overview Test
Bring the most common monitor checks into one page with fullscreen patterns, quick dead-pixel inspection, and browser-visible device information.
Grayscale and tonal range
Step ladders, gradients, and clipping views make it easier to catch banding, crushed shadows, and blown highlights.
Sharpness and refresh behavior
Resolution and refresh views help inspect scaling, thin-line rendering, browser-side smoothness, and timing consistency.
Core test entries
If the overview already reveals a likely issue, jump into a more focused page for a deeper pass.
Color Test
Use fullscreen solid colors and custom HEX values to inspect tint, dead pixels, bright pixels, and overall uniformity.
Grayscale Test
Use grayscale steps, smooth gradients, black clipping, white clipping, and banding patterns to inspect tonal transitions.
Burn-In Test
Use static solid colors and a manually started cycle mode to look for image retention, residual shadows, and obvious burn-in traces.
Resolution Test
Inspect current resolution, DPR, 1px lines, pixel grids, and sharpness samples to see how crisp the panel looks in the browser.
Refresh Rate Test
Estimate browser-side refresh rate with requestAnimationFrame and pair it with a simple motion scene to inspect smoothness and jitter.
Suggested test flow
This order mirrors how many people actually check a new monitor or troubleshoot a panel at their desk.
Start with solid colors
Use black, white, and RGB first to reveal dead pixels, bright pixels, glow, corner shading, and obvious tint shifts.
Move to grayscale next
If the panel looks washed out, crushed, or uneven in tone, switch to ladders and gradients for a more sensitive read.
Check sharpness after that
Use 1px lines, checker patterns, and text sharpness views to inspect scaling artifacts and rendering softness.
Use focused pages last
Once you know which direction to investigate, the dedicated color, grayscale, burn-in, resolution, or refresh pages will be more efficient.
Screen self-check guide
The reading path stays below the workbench so the first screen stays usable without hiding the deeper context.
Why solid colors come first
Solid-color patterns are the usual starting point for a quick display check because they are fast to read with the naked eye.
What grayscale and sharpness reveal
When solid colors look mostly fine, grayscale and fine-line views help dig deeper into tonal separation and rendering quality.
How to read each pattern
Each pattern is better at revealing a different class of display issue, so switching with intent saves time.
Quick checks
Pure black
Use black for dark-pixel checks, backlight glow observation, and basic panel uniformity.
Quick checks
Pure white
Use white for bright-pixel checks, dust spotting, and quick brightness uniformity viewing.
Quick checks
Red channel
Rotate to red to reveal stuck pixels and obvious tint imbalance.
Quick checks
Green channel
Green often makes dead or stuck pixels easier to isolate at a glance.
Quick checks
Blue channel
Blue helps reveal dark corners, stuck pixels, and some uniformity shifts.
Quick checks
Gray ladder
Quickly inspect whether tonal separation collapses between black and white.
Quick checks
Checker pattern
A fast sharpness pattern for scaling artifacts and edge clarity.
Screen self-check guide
The reading path stays below the workbench so the first screen stays usable without hiding the deeper context.
Why solid colors come first
Solid-color patterns are the usual starting point for a quick display check because they are fast to read with the naked eye.
Black surfaces expose dark issues
Pure black helps reveal dark pixels, backlight glow, gray corners, and dark-scene uniformity shifts.
White surfaces expose bright issues
Pure white makes bright pixels, dust, stains, and bright-area uniformity issues easier to notice.
What grayscale and sharpness reveal
When solid colors look mostly fine, grayscale and fine-line views help dig deeper into tonal separation and rendering quality.
Grayscale reveals tonal collapse
If neighboring tones merge too early or gradients band visibly, the display path is not separating tones smoothly enough.
1px lines reveal scaling behavior
Blurry or broken fine lines often point to system scaling, browser zoom, or rendering-path interpolation.
Where web testing stops
SPCBOX focuses on browser-reachable self-checks rather than pretending to expose low-level monitor truth.
The readings are browser-side
Resolution, DPR, color depth, and refresh estimates come from the current browser environment and should be read as practical hints.
Pro calibration still needs hardware
For absolute color accuracy, gamma curves, luminance calibration, or hardware response validation, dedicated physical instruments are still the right tool.
Common questions
These answers clarify what a browser-based screen test can help with and where its limits begin.
Q.
Can this replace professional display instruments?
No. It is best for fast dead-pixel, tint, grayscale, sharpness, and browser-side motion checks, not for replacing a calibrator or high-speed camera setup.
Q.
Why does fullscreen matter so much?
Fullscreen reduces browser chrome, nearby distractions, and layout edges, which makes glow, dead pixels, corner shading, and uniformity issues easier to spot.
Q.
Why is the refresh result not identical to my monitor spec?
Because this page estimates behavior through requestAnimationFrame, so the result is influenced by focus state, browser scheduling, and system load.
Q.
Do I need the dedicated subpages if the overview looks fine?
Not always. The overview is intentionally built for fast screening, and the focused pages are most useful once you already have a suspected direction.