Cycle repeatable solid-color fields in fullscreen to look for dead, stuck, bright or wrong-color pixels. This page now stays focused on pixel-defect inspection; gradients, sharpness, refresh rate and motion behavior remain in their own dedicated display diagnostics so the tests do not duplicate each other.
Visual test suite
Fullscreen solid-color pixel inspection
BLACK • click / → next • ← previous • H hides hint • Esc exits fullscreen
How to run a complete dead pixel inspection
Clean the panel gently and let it reach normal operating temperature. Dust, reflections and fingerprints can imitate a fixed point.
Select the display's native resolution, use 100% browser zoom where practical and disable any browser color-filter extension.
Open fullscreen, start on black, and scan the panel in overlapping rows at your normal viewing distance.
Repeat on white, red, green and blue, then use cyan, magenta, yellow and all three gray fields.
For any suspicious point, note its screen location and compare the same location in another app.
Repeat after exiting fullscreen. Record only a defect that stays at one physical screen location across repeated checks.
Why eleven solid colors matter
A display pixel is built from color components. A dark point on white, a colored point on a primary field and a bright point on black describe different visible behaviors. Complementary cyan, magenta and yellow fields request two channels together; the gray fields make brightness differences easier to compare.
The fields are deliberately static. This is a visual inspection tool, not a flashing repair routine, colorimeter or electrical panel analyzer.
Interpret the result without overclaiming
Label
What you observed
What to do next
PASS
No repeatable fixed point is visible across the full set of fields under the conditions you checked.
Record this as “no visible defect found,” not proof that every subpixel and transition is fault-free.
WARNING
A mark appears on one field, changes with viewing angle, disappears after cleaning, or moves with page content.
Repeat in another app, inspect for dust/reflections and verify resolution, zoom and cable/GPU behavior before blaming the panel.
FAIL
The same point remains fixed at one physical screen location and behaves incorrectly on multiple relevant fields.
Document the fields, location and conditions, then compare the exact seller or manufacturer pixel policy. This label describes a repeatable visible symptom, not the failed component.
Troubleshoot by symptom
Dark on every bright field: repeat on white and the primary colors, then confirm the point stays fixed in another app.
Bright on black: lower room reflections, check black again and compare the same location outside the browser.
Wrong color on selected fields: note exactly which fields expose it; this can be consistent with a subpixel symptom without proving the circuit failure.
Mark moves with content: investigate the source image, app, browser or graphics path rather than the physical pixel.
Whole line or large region changes: reconnect the cable, try another input/device and inspect monitor settings; that pattern is broader than a single-pixel check.
Browser, panel and capture limitations
CSS pixels do not always map one-to-one to physical pixels because browser zoom, operating-system scaling, devicePixelRatio and monitor scaling intervene.
A browser cannot inspect subpixel electronics, identify the failed component or certify a display.
A screenshot cannot capture a physical panel defect because it records rendered image data before the panel.
A phone photo can help document a location, but focus, exposure, moiré and sensor pixels can exaggerate or hide it.
Use this test to establish a repeatable visual observation. Do not treat “nothing noticed” as a laboratory measurement or a guarantee.
Warranty and evidence workflow
Write down the field colors that expose the point.
Describe its location relative to a corner or edge; avoid adding markers over the suspected pixel.
If requested, photograph the whole display and then a closer view while noting that the photo is supporting evidence, not a calibrated measurement.
Check the policy for the exact model, seller, region and purchase date. Policies can distinguish dark, bright and clustered defects.
Use the focused test for the focused question
This page isolates fixed-pixel symptoms. Use the refresh-rate test for browser cadence, the ghosting test for moving trails and overdrive comparison, and the full display test for gradients, sharpness and broader screen patterns.
Keeping these workflows separate makes the result easier to interpret and prevents a visual pixel check from masquerading as a measurement it cannot perform.
Dead pixel test FAQ
Can this dead pixel test repair a stuck pixel?
No. The tool uses static inspection fields and does not claim to repair pixels. It intentionally avoids rapid flashing or color-cycling repair claims.
Which colors should I use first?
Start with black, white, red, green and blue, then check cyan, magenta, yellow and the three gray fields. A repeatable point can look different as different subpixel combinations are requested.
What if the suspicious mark moves with the page?
A physical panel defect stays at the same screen location. A mark that moves with content points instead to the image, browser, application or graphics path.
Can a screenshot prove that a physical pixel is defective?
Usually no. A screenshot records rendered image data, not the physical panel. A phone photo can document the location, but focus, exposure, moiré and the camera sensor can alter its appearance.
Does one bad pixel guarantee a monitor replacement?
No. Seller and manufacturer policies vary by defect type, count, location, model and purchase terms. Record the repeatable symptom and check the policy that applies to your display.
Why should I test at the display's native resolution?
Native resolution avoids extra monitor scaling, while 100% browser zoom reduces additional CSS-to-device-pixel mapping changes. Operating-system scaling and devicePixelRatio can still prevent a one-to-one mapping.
