Phone Dead pixel, stuck pixel or persistent display mark?
Compare a visible mark across colours and content without promising that a website can diagnose or repair it.
Published 24 October 2026 · English · Our method & limitations
Check the surface first
Inspect the glass with the screen off in normal light. Dust, a scratch or a protector defect can look like a display defect. Clean gently using the device manufacturer’s care guidance and avoid pressure on the mark.
Compare solid backgrounds
Use the screen test to display several colours at comfortable brightness. Note whether the mark is a tiny point, a larger patch or a recognisable outline. Record whether its colour or visibility changes with the background. The test supplies patterns; it does not scan the panel or automatically classify the mark.
Compare with normal content
Open unrelated content and look at the same physical area. If practical, inspect a screenshot on a different display: a mark captured in that image may be in the content or rendering path. A screenshot viewed only on the same screen cannot make that comparison.
Describe before you diagnose
A fixed dark point can be consistent with a non-emitting pixel; a coloured point or persistent outline suggests a different observation. These descriptions alone cannot establish the underlying cause. Note its size, position, background and persistence for further assessment.
Do not promise a fix
Phone Test does not repair dead pixels, reverse burn-in or certify a replacement panel. Avoid rapid-flashing repair routines or pressing the screen. If the mark persists across independent checks, use a manufacturer or repair assessment rather than treating a web pattern as proof.
Continue learning
How to check a phone screen and touchscreen
Inspect solid colours, touch coverage and simultaneous contacts, then distinguish repeatable symptoms from browser limits.
Read guide →Display & touchPhone refresh-rate test: understand your result
Understand estimated browser frame rate, why a 120 Hz screen can show a lower reading, and how to repeat a useful test.
Read guide →Found an error? Send a correction with this guide’s title and the behaviour you observed.