How do solid RGB colors distinguish dead pixels vs stuck subpixels?
Every color on an LCD or OLED panel comes from three tiny red, green, and blue subpixels blended side by side. This screen test drives calibrated single-channel hex frames edge to edge inside your browser tab so you can perform a stuck subpixel check without downloading software or sending device details anywhere.
Isolating primary red, green, and blue subpixel defects
A true dead pixel fails across every channel and appears as an unlit black dot on Pure white (#FFFFFF) as well as on Red (#FF0000), Green (#00FF00), and Blue (#0000FF). Conversely, a hot pixel locks all three subpixels open and glows bright white against Pure black (#000000).
Single-channel primary fills catch subtle subpixel faults that white backgrounds hide. For example, a dead blue subpixel looks black only on Blue, whereas on Pure white it appears as a faint yellow dot because red and green still light normally.
Verifying CMYK secondary fills on LCD and OLED panels
Secondary patterns combine two subpixel channels at 100% intensity while turning the third channel completely off. Cyan (#00FFFF) pairs green and blue, Magenta (#FF00FF) pairs red and blue, and Yellow (#FFFF00) pairs red and green.
- Two-channel contrast: A stuck green subpixel stands out cleanly on Magenta because green should remain dark while red and blue emit full light.
- Fullscreen activation: Clicking Start fullscreen test triggers
requestFullscreen()inside the click handler, matching the transient user activation rule in the W3C Fullscreen API Specification.
If you are checking a new phone, tablet, or 2-in-1 laptop, confirm the display matrix looks uniform first. You can then sweep touch panel zones after inspecting display pixels in the next tab.
Running fullscreen test patterns with keyboard and auto-cycle timers
Browser toolbars, scrollbars, and dark theme margins hide defects along monitor corners where backlight bleed and edge pressure occur. Entering fullscreen removes browser chrome so every row from pixel zero to the outer bezel displays a clean reference fill.
Hiding the floating HUD and setting 2 to 8 second timers
Inside fullscreen mode, a compact floating bar displays the active pattern index (for example 1/12: Pure black) alongside Previous, Next, Hide bar (H), and Exit test (Esc) buttons. Pressing H hides the floating bar completely so no interface box blocks the bottom center of your monitor.
Use ArrowRight or Space to advance, ArrowLeft to step back, or tap anywhere directly on the canvas on mobile screens. When inspecting monitors from across a desk, set Auto-cycle interval in fullscreen to Every 2 seconds, Every 4 seconds, or Every 8 seconds so patterns rotate automatically.
Handling Fullscreen API blocks with a viewport fallback
Under the MDN Fullscreen API Documentation, Element.requestFullscreen() returns a promise that can reject inside restricted embedded frames or locked kiosk policies. If that call is declined, the tester retains a fixed inset-0 z-50 overlay covering 100% of the browser viewport.
Pressing Escape or clicking Exit test (Esc) calls document.exitFullscreen() when active and clears the viewport overlay cleanly. Once your panel passes inspection before a video call or hardware unboxing, check camera clarity with our browser webcam FPS and framing monitor.
Checking 50% gray uniformity, backlight bleed, and all 12 test patterns
Uniformity defects rarely affect a single pixel dot; instead they appear as cloudy corner glow on IPS monitors or vertical curtains on large OLED screens. Stepping through all 12 Test patterns covers subpixel faults, uniformity, scaling, and motion overdrive in one sequence.
| Pattern label | Color or canvas spec | Target display defect | Best viewing condition |
|---|---|---|---|
| Pure black | Solid #000000 |
Stuck bright subpixels, IPS backlight bleed, corner glow | Dim room, full panel brightness |
| Pure white | Solid #FFFFFF |
Dead black pixels, surface dust, warm/cool tint shifts | Normal room light |
| Red / Green / Blue | #FF0000, #00FF00, #0000FF |
Dead or stuck single-channel subpixels | Close viewing distance |
| Cyan / Magenta / Yellow | #00FFFF, #FF00FF, #FFFF00 |
Paired subpixel cross-talk and dark-channel leaks | Close viewing distance |
| 50% gray | Solid #808080 |
Dirty-screen effect, clouding, vertical OLED banding | Dim room, perpendicular angle |
| Pixel checkerboard | 1 px alternating #000000 / #FFFFFF |
Pixel inversion flicker, LCD overdrive artifacts | Static 100% browser zoom |
| Grayscale ramp | 256-step #000000 to #ffffff ramp |
6-bit FRC dithering shimmer and contour banding | Neutral gamma mode |
| Subpixel grid | 24 px #3a3a3a grid, 1 px #ffffff border |
Non-native OS scaling blur and bezel overscan clipping | 100% zoom, edge-to-edge |
Notice how 50% gray isolates uniform mid-tone brightness across the entire matrix where Pure white tends to clip differences. On new OLED panels showing faint vertical bands, running 4 or more hours of normal playback allows standby compensation cycles to even out near-gray voltage.
If you are setting up a new living room TV or gaming desk monitor for console play, test panel uniformity before connecting peripherals. Follow that visual sweep with a quick run to confirm analog stick drift before console setup.
Reading devicePixelRatio, OLED banding, and 8-bit grayscale ramps
Besides solid colors, the sidebar Display measurements readout helps verify whether your operating system is driving the monitor at true native sharpness. When scaling or display cable settings drop below native pixels, 1-pixel lines in Pixel checkerboard and Subpixel grid turn blurry or display interference bands.
Calculating estimated native pixels from CSS display scaling
The sidebar reads window.screen.width, window.screen.height, window.devicePixelRatio, and window.screen.colorDepth (24-bit on standard SDR displays). As documented in the MDN Window devicePixelRatio Reference, devicePixelRatio equals the count of physical panel pixels packed into one CSS layout pixel.
On a 3840 × 2160 monitor running at 2.00× OS display scaling, Screen resolution reports 1920 × 1080 CSS px while Estimated native multiplies by 2.00× to restore 3840 × 2160 px. Note that browser page zoom (Ctrl/Cmd plus + or -) alters devicePixelRatio temporarily, so reset zoom to 100% before judging Pixel checkerboard or Subpixel grid sharpness.
Spotting 6-bit FRC banding, pixel inversion, and surface dust
The Grayscale ramp paints a smooth horizontal gradient across 256 grayscale steps from #000000 to #ffffff. Budget 6-bit+FRC panels can show faint stepped vertical bands or subtle shimmering crawl along dark gray transitions, whereas clean 8-bit and 10-bit panels blend smoothly.
Tip: Before reporting a warranty defect on Pure white, gently tilt your head left and right over any dark dot: dust resting on top of an anti-glare coating shifts parallax relative to the glowing subpixels underneath, whereas a true dead pixel stays locked to the matrix.
To finish verifying a newly arrived monitor that includes built-in speakers or a 3.5 mm audio pass-through jack, test left and right audio channels next. Pair your visual check with the Online audio tone generator to confirm clean playback.