Defect log: mark each bad pixel and keep its position
Spotting a bad pixel is the easy bit. Finding it again is harder. You catch a faint dot on the white screen, glance away, and it's gone. Or you find three, and by the time you're in the support chat all you can say is "somewhere top left". The defect log is for that. In fullscreen, switch on mark mode and click right on each dot. A ring goes around it (the pixel itself stays uncovered in the middle) and the page writes down where it was.
Each entry holds the position in screen pixels, such as 1412, 308 on a 1920 by 1080 panel, the zone (top right, centre and so on) and the colour you were looking at. That last part matters more than it sounds. A bright dot on black is a stuck or hot pixel, a dark dot on white is a dead one, and a dot that only misbehaves on red, green or blue is a sub-pixel fault. The usual pixel policies, including the ISO 13406-2 classes, count those kinds separately, so "one bad pixel" isn't enough information for a return desk. "Dark pixel on white, 1412, 308, upper right" is.
It also settles the dust question. Mark the spot, wipe the screen with a dry microfibre cloth, run it again. If the dot is still at the same coordinates after cleaning, it's the panel.
- Clean the screen and set brightness high.
Then press "Start Test" and go through black and white first.
- Press M when you see a dot.
Or tap the ring button in the control bar. The cursor turns into a crosshair; clicking no longer changes the colour.
- Click the dot.
A numbered ring appears around it. Press U to undo a stray click, M again to go back to cycling colours.
- Exit fullscreen and read the log.
"Copy report" gives you plain text to paste into a warranty email.
The limits are real. The page can't find defects for you, your eyes still do that. Coordinates are only as precise as your pointer: on a 4K screen at 200% scaling one click is 2 by 2 physical pixels, so treat the numbers as "this spot" rather than a pixel ID. And it can't tell a pixel from a speck of dust on its own, which is what the clean-and-recheck step is for. Marking needs a mouse or touch, and phones whose browser won't go fullscreen can't use it.
