Dead Pixel Test
A guided fullscreen dead-pixel checker for monitors, laptops, tablets, and phones with manual and timed navigation.
Related tools
Practical uses for Dead Pixel Test
- Inspect a newly purchased display before the return window closes.
- Differentiate always-dark, always-bright, and color-stuck pixels.
- Repeat the same sequence across multiple displays.
A careful three-step workflow
- 1
Clean the screen and dim distracting room light.
- 2
Start the test and inspect every color at a comfortable distance.
- 3
Use arrows or swipe to advance; note a mark only if it stays in exactly the same physical location.
Interpret the result in context
- Dust and reflections can resemble defective pixels.
- This tool identifies visible symptoms; it cannot safely repair a pixel or determine warranty coverage.
- State for Dead Pixel Test is processed locally and resets from the normal page view.
Check every part of a display with solid colors
A pixel defect is easiest to notice when the rest of the display shows one uninterrupted color. This test cycles through white, black, red, green, blue, cyan, magenta, yellow, and gray so that dark pixels, bright pixels, and incorrect color components have fewer places to hide. The patterns are generated by the browser; the test does not inspect the device, read display data, or upload a result.
How to run a careful dead pixel check
- Wipe dust from the panel using the manufacturer’s cleaning instructions, then open the test in a room without strong reflections.
- Use the display’s normal picture mode and native resolution. Avoid changing brightness or zoom during the sequence.
- Enter fullscreen deliberately and inspect the panel from your usual viewing distance. Use the arrow keys, swipe, or the on-screen controls to move between colors.
- If a dot looks suspicious, change colors. A speck of dust or reflection usually changes with viewing angle; a pixel symptom remains fixed at the same screen coordinate.
- Record the location and colors on which it appears. Warranty definitions and allowable pixel counts differ, so consult the manufacturer before drawing a conclusion.
Dead, stuck, and bright pixel symptoms
An always-dark point can be consistent with a non-emitting pixel or subpixel. A point that remains red, green, blue, cyan, magenta, or yellow may indicate one or more components that are stuck. A point that remains conspicuously bright is a different visible symptom again. This browser test can help describe what you see, but it cannot determine the electrical cause or certify a panel as defective.
| Visible symptom | Fields that make it easier to see | Next check |
|---|---|---|
| Point stays black | White, gray, red, green, and blue | Confirm it stays at one physical panel location |
| Point stays bright | Black and low gray | Compare normal dark content from working distance |
| Point stays one color | RGB and secondary colors | Record exactly which requested colors change it |
| Line, patch, or retained shape | Several gray levels | Use the uniformity or OLED gray test instead |
Phone, tablet, laptop, and desktop procedure
On a phone or tablet, rotate once before starting and keep the chosen orientation fixed; browser bars and camera cutouts reduce the usable area. On a laptop, use the built-in panel at its native resolution and disconnect display mirroring if it changes scaling. For a desktop monitor, test the input and refresh configuration you normally use. A touchscreen mark that follows a finger swipe is more likely to be surface residue than a fixed pixel symptom.
Use a screenshot to separate software from the panel
Take an operating-system screenshot while the suspicious point is visible, then view that file on a different known-good display. A physical panel defect is not encoded in a screenshot. If the point appears in the file elsewhere, investigate the source image, application, overlay, GPU path, or signal rather than classifying it as a dead pixel. If it stays fixed relative to the bezel across different sources, record that repeatable observation for the manufacturer.
What this test cannot do
ScreenOrbit does not flash the screen rapidly, press the panel, or claim to repair pixels. Those actions can be uncomfortable or may damage a display. A mark that appears only in one application can also come from software, scaling, or the source image. Compare with the Monitor Test, and use the Screen Uniformity Test when the issue is a patch, tint, or uneven region rather than one fixed point.
For a repeatable purchase check, follow the 15-minute new-monitor inspection checklist and read Dead vs. Stuck Pixels.
Plan a useful session with Dead Pixel Test
Dead Pixel Test works best when you start with one question. Decide what you need to view, compare, create, record, or demonstrate. Keep the first run at the default state. Change one control after you understand the starting result. This approach gives you a clear baseline and a useful reason for every adjustment.
A guided fullscreen dead-pixel checker for monitors, laptops, tablets, and phones with manual and timed navigation. Use the normal page view to prepare the settings. Enter fullscreen only after you review the exit control. Write down the mode and key values when you need to repeat the result on another device.
Choose controls by outcome
The available modes include white, black, red, green, blue, cyan, magenta, yellow, gray. The control set includes fullscreen, auto cycle, keyboard, swipe, wake lock, quick download, reset. Start with the option closest to your task. Avoid changing every value at once. A single change gives you a direct before-and-after comparison and makes a saved result easier to explain.
- Inspect a newly purchased display before the return window closes. Set a clear finish point before you begin.
- Differentiate always-dark, always-bright, and color-stuck pixels. Set a clear finish point before you begin.
- Repeat the same sequence across multiple displays. Set a clear finish point before you begin.
Run a repeatable workflow
- Stage 1. Clean the screen and dim distracting room light. Record the starting environment and state.
- Stage 2. Start the test and inspect every color at a comfortable distance. Keep the first comparison short and controlled.
- Stage 3. Use arrows or swipe to advance; note a mark only if it stays in exactly the same physical location. Reset the page when the session ends.
For a device comparison, use the same browser family, viewport, room light, physical brightness, and viewing distance where practical. Run the same order on both devices. Change one environmental factor only after the matched pass is complete. Keep this route focused on this use: Inspect a newly purchased display before the return window closes.
Keep a useful record
A useful record names the page, mode, control values, browser, device, viewport, date, and viewing condition. For a visual observation, describe the location and the fields where the effect appears. For a generated asset, record dimensions, format, color values, and the downloaded file name. For a simulation, record the duration, custom text, disclosure, and exit method. The starting reference for this page is white.
- Dust and reflections can resemble defective pixels.
- This tool identifies visible symptoms; it cannot safely repair a pixel or determine warranty coverage.
Avoid common setup errors
- For this use, do not treat a browser view as a hardware measurement or system action: Inspect a newly purchased display before the return window closes.
- Do not change several settings before you record the baseline. Begin with white.
- Do not rely on a phone photograph as the only evidence. Keep this route limit in view: Dust and reflections can resemble defective pixels.
- Do not leave route features active after the task ends. The main controls include fullscreen, auto cycle, keyboard, swipe.
- Do not add private data, credentials, payment details, or confidential text. Keep the second listed use in scope: Differentiate always-dark, always-bright, and color-stuck pixels.
Continue with the closest comparison
Open a related route when the first page reveals a new question. Keep the same environment and repeat only the part needed for comparison. The closest listed routes are Monitor Test, Black Screen, White Screen. Keep this final use in mind: Repeat the same sequence across multiple displays.
- Monitor Test. A complete guided sequence for pixels, levels, gradients, sharpness, geometry, and motion.
- Black Screen. A pure black fullscreen surface for dark-room checks and distraction-free secondary displays.
- White Screen. A clean fullscreen white display for light, cleaning, tracing, and visual checks.
Recommended guides
Questions about Dead Pixel Test
What does Dead Pixel Test do?
A guided fullscreen dead-pixel checker for monitors, laptops, tablets, and phones with manual and timed navigation. Inspect a newly purchased display before the return window closes. Differentiate always-dark, always-bright, and color-stuck pixels.
Who gets the most value from this page?
Use this page when your task matches the listed purpose. Inspect a newly purchased display before the return window closes. Differentiate always-dark, always-bright, and color-stuck pixels. Start with a clear goal and stop once the page answers that goal.
Which Dead Pixel Test setting should you choose first?
Start with white, black, red, green, blue, cyan, magenta, yellow, gray. Keep the default state for the first pass. Change one control, review the result, then record the setting before another change.
What should you prepare before fullscreen?
Use native resolution where practical. Record scaling, HDR state, picture mode, room light, and viewing distance before starting the test. Clean the screen and dim distracting room light. Start the test and inspect every color at a comfortable distance.
Does this page change hardware or system settings?
The browser shows controlled patterns or generates local output. The page does not inspect panel electronics, certify calibration, provide medical advice, or decide warranty status. The white mode and Reset affect local page state only.
How should you judge the result?
Repeat the observation at another relevant level. Change one variable at a time. Confirm a pattern result in ordinary work, video, or games before assigning practical weight. Dust and reflections can resemble defective pixels. This tool identifies visible symptoms; it cannot safely repair a pixel or determine warranty coverage.
Does the page upload files or settings?
No tool state is uploaded by ScreenOrbit. Supported local files stay in the current browser tab. Generated files are assembled in browser memory and download to your device. The starting mode is white. The first use is: Inspect a newly purchased display before the return window closes.
Which phones, tablets, and computers support the tool?
Current desktop and mobile browsers support the core page. Fullscreen, Wake Lock, downloads, audio, and local file access depend on browser and operating system support. The visible control set starts with fullscreen. The first use is: Inspect a newly purchased display before the return window closes.
What mistakes reduce the value of the page?
Avoid changing brightness, picture mode, viewing angle, and room light at the same time. Multiple changes make the result hard to reproduce. Keep the goal, settings, environment, and exit plan clear. The first listed use is: Inspect a newly purchased display before the return window closes.
Which ScreenOrbit tool should you open after Dead Pixel Test?
Continue with Monitor Test, Black Screen, White Screen. The related links preserve the same task area while giving you another field, pattern, or workflow for comparison.