Dead pixel
- What it looks like
- The same point stays black on every core pattern.
- What it usually means
- This usually points to hardware failure, not a recoverable stuck state.
Pixel Diagnostics
Dead Pixel Test
Run the fullscreen test, tell dead vs stuck vs hot pixels apart, and decide whether to retest, repair, or file a claim.
Noticed a dot that stays black, bright white, or the wrong color?
Check whether it is a real pixel defect before you retest, repair, or file a claim.
If a point on your screen refuses to change with the rest of the panel, use this test to see whether it behaves like a true dead pixel, a stuck or hot pixel, or a look-alike such as burn-in, backlight bleed, dust, or an overlay.
- You are checking
- Whether the same point stays black, stays lit, or only looks defective under certain conditions.
- You will learn
- How to confirm the result, what can be mistaken for a dead pixel, and what the result usually means.
- Then you can
- Retest with confidence, open the right repair workflow, or document the issue for return or warranty support.
Start the test in fullscreen
Open the color patterns, scan slowly, and mark any point that stays black, bright, or stuck on the wrong color across repeated passes.
- Clean the screen so dust and smudges do not mimic a pixel defect.
- Raise brightness and disable night mode or adaptive color filters.
- Use fullscreen so overlays and browser chrome do not hide the point.
- Re-check the same location on black, white, red, green, and blue.
Run the test in fullscreen
Clean viewing conditions matter more than anything else. Set the screen up properly, then check the same point across the five core colors before you decide the defect is real.
- Step 01
Prep the panel
Wipe the screen, raise brightness, disable night mode or adaptive filters, and remove anything that could mimic a tiny defect.
- Step 02
Open fullscreen mode
Use fullscreen so browser chrome, app bars, and reflections do not create fake edge defects or hide a small point.
- Step 03
Run the five core colors
Start with black, white, red, green, and blue. Those five patterns reveal whether the same point stays black, bright, or fixed in one color.
- Step 04
Scan slowly, then re-check
Move by quadrants, not random sweeps. When you find a suspect point, re-check the exact same location on multiple patterns before you classify it.
How to tell a dead pixel from a stuck or hot pixel
The biggest mistake people make is calling every stubborn point a dead pixel. If the point still emits light, it is usually stuck or hot. If it stays black across every core color, the dead-pixel case gets much stronger.
Stuck pixel
- What it looks like
- The point stays one color, usually red, green, or blue.
- What it usually means
- The pixel still emits light, which keeps software repair on the table.
Hot pixel
- What it looks like
- The point stays bright white or nearly white.
- What it usually means
- One or more sub-pixels are stuck on at full output.
When the result is still unconfirmed
- Call it dead only after the same point stays black on black, white, red, green, and blue.
- Call it stuck or hot only when the same point keeps emitting light in a stable way across repeated passes.
- If the point changes with angle, brightness, app state, or cleaning, keep the result provisional and rule out false positives first.
What can look like a dead pixel but isn’t
A single stubborn spot is not always a failed pixel. These are the most common look-alikes to rule out before you classify the result or open a claim.
False positiveWhy it fools peopleHow to rule it out
False positive
Dust, smudges, or protector debris
Why it fools people
Small dirt spots and protector flaws can look like dead pixels at a glance.
How to rule it out
Clean the panel, remove the protector if possible, and check whether the mark changes shape or disappears.
False positive
OLED retention or burn-in
Why it fools people
Ghosted logos or UI shadows can be mistaken for clusters of dead pixels, especially on dark or saturated patterns.
How to rule it out
If the artifact follows interface shapes instead of a single point, compare it with the burn-in workflow.
Check with the burn-in testFalse positive
Backlight bleed, IPS glow, or corner haze
Why it fools people
Uneven light near edges and corners can look like panel failure, but it is not a single pixel defect.
How to rule it out
If the issue spreads across an area instead of one point, compare it with the bleed test in a dark room.
Compare with the backlight bleed testFalse positive
Pressure marks, reflections, or UI overlays
Why it fools people
Pressure damage and overlay elements can mimic a tiny point defect until fullscreen mode removes the distraction.
How to rule it out
Change angle, dismiss overlays, and re-check the exact same point in fullscreen before you classify the result.
What your result means
The result matters only if you can turn it into the right label and the right decision. Use the pattern below to match what you saw to the most likely interpretation.
What you observedWhat it usually meansConfidenceBest next step
What you observed
The same point stays black on every core pattern
What it usually means
Highest-confidence dead-pixel signal. The pixel is likely no longer responding.
Confidence
High after repeat checks
Best next step
Stop treating it like a repair candidate and document it for return or warranty.
What you observed
The same point stays one color
What it usually means
Strong stuck-pixel signal. The pixel still emits light in a fixed state.
Confidence
High after repeat checks
Best next step
Move to the stuck-pixel repair page and reassess after short, controlled sessions.
What you observed
The same point stays bright white
What it usually means
Typical hot-pixel behavior. One or more sub-pixels appear locked on.
Confidence
High after repeat checks
Best next step
Treat it like a stuck pixel first, then escalate only if it remains unchanged.
What you observed
The point is inconsistent or you cannot reproduce it
What it usually means
The result is still provisional. Misreads, overlays, pressure marks, or transient artifacts are still in play.
Confidence
Low
Best next step
Retest under cleaner conditions before you classify it or open support.
What you observed
The issue appears as a shape, streak, or wider area instead of a point
What it usually means
This is likely not a single-pixel defect at all.
Confidence
Moderate to high
Best next step
Compare it with burn-in or backlight bleed before you keep using the pixel label.
What to do next
Once the result is clear, stop repeating the same test and move into the right next action. The best path depends on whether the point is truly dead, still emitting light, or no longer looks like a pixel defect at all.
Confirmed stuck or hot pixel
The same point keeps emitting a stable color or bright white output.
Move into the repair workflow and reassess after short sessions instead of guessing from the test page.
Confirmed dead pixel
The same point stays black on every core pattern after repeated checks.
Skip repair-first behavior and switch to evidence, return timing, or warranty thresholds.
Looks more like retention or ghosting
The problem follows UI shapes, logos, or larger image remnants instead of one point.
Use the burn-in test before you keep using the dead-pixel label.
Looks more like glow, bleed, or haze
The issue spreads across an area, edge, or corner instead of a single point.
Use the bleed test in a dark room so you do not escalate the wrong defect class.
If you need return or warranty evidence
Once the defect is repeatable, document it while return and exchange options are still simple. Keep the evidence clear, specific, and matched to the exact behavior you confirmed.
- Photograph the confirmed defect on at least two core patterns after you reproduce the same point.
- Capture one close-up image and one normal-use image so support can judge both existence and impact.
- Record the device model, purchase date, serial number, and whether you are still inside the retailer return window.
- Write down whether the issue is dead, stuck, hot, or still provisional instead of calling every defect “dead.”
SignalStronger evidenceWeaker evidence
Signal
Reproducibility
Stronger evidence
The same point behaves the same way across repeat checks.
Weaker evidence
The issue appears once and cannot be reproduced cleanly.
Signal
Visual proof
Stronger evidence
Photos show the defect clearly on fullscreen patterns and in normal use.
Weaker evidence
Photos are dim, blurry, or only show an unclear close-up.
Signal
Timing
Stronger evidence
Evidence is captured inside the retailer return period or early in warranty coverage.
Weaker evidence
The issue is raised late with little documentation.
Signal
Policy fit
Stronger evidence
You checked the current model-specific threshold before filing the claim.
Weaker evidence
You are relying on a generic forum rule instead of current policy wording.
FAQ
Dead pixel test FAQs
Short answers on trust, false positives, and what to do when the result is still unclear.
Reviewed and maintained by Jacob Dymond
Founder, ScreenDetect
Last reviewed March 28, 2026
ScreenDetect maintains this page as a conservative pixel-classification workflow. The guidance is written to help users confirm what they are seeing, avoid overcalling a defect too early, and document the result clearly enough for the right repair, return, or support decision.
Source basis
- ScreenDetect testing methodology · ScreenDetect
- Display pixel policies and thresholds · ScreenDetect
- Display Pixel Guidelines · Dell Support
- ISO 9241-302/303/305/307 (standards family reference) · ISO