HomeAll ToolsBadpoints.navTitle
What this tool helps you verify

Dead Pixel & Light Leakage Test

Use solid colors, gradients, and grids to examine screens for dead pixels, stuck pixels, and backlight bleeding. Essential for checking new monitors and phones.

Dead PixelsLight BleedMonitor VerifyColor CycleScreen Quality
Privacy

Avoids unrelated permissions and runs in your browser with the device APIs available on this device.

Supported platforms

Works best in current Chrome, Edge, Safari, and Firefox. Support depends on Canvas rendering checks, secure HTTPS, hardware availability, and browser policy.

Black (1/10)
Check for light bleed
control
solid color
grid assist
Automatic carousel
Tip: Carousels are more suitable for “quick scans”. To accurately check for bad pixels, it is recommended to stop and search slowly using monochrome.
other
Note: Some browsers/systems do not support this or need to activate the page in the foreground to take effect.

How to use this page to find problems faster

First click "Full Screen" and adjust the screen brightness to the level you want to compare (dark environment + medium-high brightness is recommended for light leakage).
Dead pixels/bright spots: use red/green/blue solid color full screen, scan along the grid frame by frame; dead pixels often appear as "always black/always bright/color deviation".
Light leakage/uneven backlight: Use a pure black or dark gray full screen, and observe whether there are shiny or cloudy patches on the edges/corners in a dark environment.
Uneven color/dirty screen/ribbon: Use white/light gray/medium gray full screen to observe whether there is color cast, dirt, streaks or uneven light and dark.
Tips: After full screen, you can "click the screen" to quickly switch colors; or use the space to start the automatic carousel and scan it quickly.

Inspection Guide

Use primary colors to find stuck pixels; Black/Grey for light leaks.

Step 1

Go to full screen and prepare the environment

about 10 seconds

Full-screen display with solid color background, it is recommended to select ambient light and brightness according to the target.

Click "Full Screen (F)" to enter full screen mode
Check for light leakage: dark environment + medium to high brightness recommended
Check for bad pixels: Moderate ambient light is enough to avoid interference from strong reflections
Step 2

Scan dead pixels and color casts with solid color

About 30–60 seconds

In solid colors such as red/green/blue, dead pixels are easier to identify.

Start with "red/green/blue", sweep one color and then change to the next one
Turn on the grid (G) and scan along the grid frame by frame to make it easier to miss.
After discovering an abnormality, pause the carousel and stop at the color recording position (such as the upper left/middle/lower right of the screen)
Tip: Some "bad pixels" are only noticeable under certain colors (for example, they are only dark under blue).
Step 3

Use black/grey/white to observe light leakage and uniformity

About 20–40 seconds

Black/grey is more suitable for seeing light leakage and uneven backlight; white/light gray is more suitable for seeing dirty screens and color temperature shifts.

Pure black: focus on the four corners and edges to see if there are obvious shiny/cloudy patches
Dark gray/medium gray: It is easier to see large-area uneven brightness, streaks, and vignetting
Pure white/light gray: Check whether there is a "dirty feeling", yellowish/blueish color, partial darkness or brightness

What this tool checks

This page helps you inspect the screen visually for dead pixels, stuck pixels, light bleed, and other easy-to-miss panel issues.

solid-color inspection

Lets you scan the panel against uniform backgrounds where dead or stuck pixels stand out more clearly.

bright and dark defect clues

Helps reveal pixels that stay black, white, or a fixed color when they should change.

gradient visibility

Useful for noticing obvious banding, unevenness, or panel artifacts.

edge glow and bleed check

Makes backlight bleed or corner glow more visible on dark full-screen backgrounds.

grid / alignment aid

Provides structured patterns that help reveal scaling and uniformity oddities.

manual screen scan workflow

Supports a deliberate user inspection before you accept a new monitor or phone screen.

What this tool cannot confirm

This is a visual inspection tool, so the result depends on your own observation and the room you are viewing the display in.

not automatic pixel counting

The page does not programmatically detect every faulty pixel for you; you still need to inspect the screen.

ambient light matters a lot

Light bleed, uniformity issues, and subtle defects are easier or harder to notice depending on room lighting.

panel technology affects expectations

IPS glow, OLED mura, and mini-LED blooming can look different without necessarily meaning the same defect.

cannot judge warranty policy

A visible defect does not automatically mean the manufacturer will replace the panel under their policy.

How the result is generated

The result is generated by rendering full-screen colors, gradients, and grids locally so that you can inspect the panel yourself.

01

pattern rendering

The page displays solid colors, gradients, or grids directly in the browser.

02

fullscreen viewing

You can inspect the panel more clearly when the test fills as much of the screen as possible.

03

visual scan

You move your eyes across the display to look for fixed dots, glow, or uneven regions.

04

pattern switching

Changing colors helps reveal whether a suspicious pixel remains fixed across different backgrounds.

05

manual conclusion

The final result depends on what you observed while viewing the rendered patterns.

Interpret your results

Use the observed defect pattern to decide whether you are seeing a stuck pixel, a dead pixel, bleed, or just normal panel behavior.

Observed panel signLikely meaning
Fixed black dotA likely dead pixel or permanently non-lighting subpixel cluster.
Fixed bright or colored dotA likely stuck pixel that is staying on one state or color.
Corner glow on dark screensBacklight bleed or panel glow that may be normal to a degree depending on panel type.
Visible banding in gradientsLimited smoothness, panel processing issues, or expected panel characteristics.
No obvious defect seenThe panel appears visually normal in the conditions you tested.

Supported browsers and known limitations

This tool mainly depends on the browser rendering full-screen colors cleanly, so support is generally broad.

browserfullscreen color patternsgradient / grid supportmanual inspection flowknown limitations
ChromeStrongStrongStrongBrowser UI chrome may still interfere unless fullscreen is used.
EdgeStrongStrongStrongDisplay scaling can slightly affect how small patterns look.
FirefoxStrongStrongStrongColor management differences may slightly change gradients.
SafariStrongStrongStrongAuto-brightness and True Tone style features can influence perception.
iOS SafariStrongGoodGoodSystem gestures and brightness control can interfere with edge inspection.
Android ChromeStrongGoodGoodMobile brightness and OLED behavior can alter what you notice.

Use cases

This test is most useful when you need a deliberate visual inspection workflow for a display before relying on it.

after buying a new monitor

Inspect the screen for pixel defects or bleed before the return window closes.

after buying a new phone

Quickly scan for stuck pixels or uneven display areas on a fresh device.

when you notice a suspicious dot

Switch colors to confirm whether the defect remains fixed across patterns.

before accepting office hardware

Run a quick visual screen check before taking a monitor into daily use.

after transport or repair

Re-check the panel if the device was shipped, moved, or recently serviced.

FAQ

A collection of frequently asked questions about dead pixels/light leakage/color uniformity inspection.

1.

What are dead pixels/bright pixels/dark pixels?

Bad pixels usually refer to pixels or sub-pixels working abnormally: bright spots (always bright), dark spots (always dark), or color casts (a sub-pixel failure causes abnormal color). The performance will be different under different solid colors, so it is recommended to use red/green/blue to check separately.

2.

Why use solid color full screen?

Solid colors can maximize the emphasis on "abnormal points" and "regional unevenness" on the screen. For example, black screens are most likely to see light leakage, white/grey screens are most likely to see dirty screens and uneven brightness, and RGB solid colors are most likely to see bad pixels and color casts.

3.

What is the grid used for?

The grid can divide the screen into regular areas, helping you scan in the order of "left to right/top to bottom" to reduce omissions; it also makes it easy to locate and record the location of the problem.

4.

How to measure light leakage more accurately?

It is recommended to use a pure black or dark gray full screen in a dark environment, and adjust the screen brightness to the mid-to-high range you usually use (or the level you want to compare). Be careful to differentiate between "normal IPS grey/glow" and distinct edge light leaks/cloudy patches.

5.

Full screen may fail on mobile phone/tablet, what should I do?

Some mobile browsers have limitations on the Fullscreen API (especially iOS Safari). You can still scroll the page to the maximum display area and manually hide the browser UI; or switch to a browser/desktop with better support and test again.

6.

Does this page collect my screen data?

Won't. The essence of "detection" here is to display a specific color/grid pattern to help you see it with the naked eye. All rendering is done locally in the browser, with no need to upload any images or device data.

7.

What to do after discovering bad pixels?

It is recommended to record the location (grid assist), review it in different colors, and take photos as evidence (be careful to avoid the influence of the camera's automatic exposure). If it is within the warranty/return period, you can communicate with after-sales accordingly.

Related guides

Read a few practical guides for setup, browser compatibility, and troubleshooting around this test.

The Hidden Flaws in Your Display: A Complete Guide to Dead Pixel and Light Leakage Testing

Discovering a dead pixel or severe light leakage on a brand-new monitor can be frustrating, but catching these issues early is crucial for warranty claims and visual comfort. This practical guide explores why screen quality verification matters for everyone from gamers to graphic designers. We break down the science behind stuck pixels and backlight bleeding, explaining how solid color cycles and gradient tests reveal hidden defects that standard usage might miss. Step-by-step, you will learn how to utilize online testing tools to inspect new purchases, verify post-repair quality, or evaluate second-hand devices. Whether you are setting up a professional design station or simply ensuring your home entertainment setup is flawless, this article provides the essential workflow to identify screen anomalies, document evidence for returns, and ensure you are getting the display quality you paid for.

The Hidden Flaws in Your Display: A Complete Guide to Dead Pixel and Light Leakage Testing

Discovering a defect in a brand-new monitor or smartphone screen can be frustrating. This practical guide explores the critical importance of performing dead pixel and light leakage tests immediately after purchasing a device or completing a repair. We break down how solid color cycles, gradients, and grid patterns reveal hidden issues like stuck pixels and backlight bleeding that often go unnoticed during casual use. Whether you are a graphic designer requiring perfect color uniformity, a gamer checking for distractions in dark scenes, or a consumer verifying a second-hand purchase, this article provides step-by-step instructions on using online tools to validate screen quality. Learn how to document these flaws effectively to ensure you can claim warranties or negotiate returns before it's too late.

Feedback / report a bug

Tell us your browser, device, and what happened.

Did this result look wrong?

Comments(0)

5
0