When a display looks wrong, useful evidence is a clear record of what you saw and how you reproduced it. A photo or browser test does not prove a hardware failure, but a careful description can help a seller or support team choose the next diagnostic step. Keep the evidence factual: record the symptom, not a diagnosis you cannot confirm.
1. Repeat the same observation
Return to the pattern, app or scene where the problem appeared. Check whether the mark stays in one physical location as the image changes, moves with the content, or changes when you shift your viewing angle. If the display has a visible smudge, follow the manufacturer’s cleaning guidance before treating it as a pixel problem. Repeat the check once under the same settings so you know the observation is reproducible.
For fixed dots, ScreenBlack’s Dead Pixel Test lets you compare several colors. For a broad patch or tint, the Uniformity Test gives you consistent fields. Note the exact color or pattern that makes the symptom easiest to see.
2. Separate the display from the source
If possible, try another cable, input or source device, changing one thing at a time. If the issue only appears in one app or on one computer, it may be related to the software or signal path rather than the panel. If it also appears on the monitor’s own menu or a manufacturer-provided self-test, record that observation. Some displays offer built-in diagnostics, but their procedures vary by model. Dell’s support documentation, for example, directs users to the model manual for the correct diagnostic steps; do not copy a button sequence meant for a different device.
3. Take two useful camera photos
Take one photo that shows the full display and one closer view of the area. Keep the phone steady, frame the same location, and avoid digital zoom if it makes the picture blurry. If your camera allows it, lock focus and exposure; otherwise take a few ordinary photos and keep the unedited originals. Do not apply filters, artificial sharpening, recoloring or brightness changes to the evidence file. If you annotate a copy to point out a location, retain the original too.
Camera exposure can make a dim screen look brighter than it seemed in person, and reflections or autofocus can hide a faint spot. Include a short note about room lighting and display brightness rather than relying on a photo to communicate severity. A photo is context, not a measurement.
4. Know when a screenshot helps
A screenshot records the digital image generated by software. It can help show a problem in a page, video or application, but it normally cannot record a physical panel issue such as a fixed bright pixel, surface scratch, reflection, backlight patch or viewing-angle change. For those, take a camera photo of the physical screen. If you suspect a software-rendering issue, preserve both the screenshot and a camera photo and say which one shows the problem.
5. Record the conditions
| What to note | Example |
|---|---|
| Device | Exact monitor, laptop, phone or TV model; purchase date if relevant. |
| Signal path | Source device, cable, dock and input used. |
| Display settings | Picture mode, brightness, HDR state and resolution. |
| Test conditions | Pattern or app, room light, viewing angle and approximate distance. |
| Observation | Location, color, whether it stays fixed, and whether it repeats. |
You do not need a laboratory log. A few specific notes are enough to make your report more useful than “the screen is faulty.”
6. Contact the right support channel
Use the seller’s or manufacturer’s official contact method. Describe the issue in one or two sentences, attach original photos if requested, and ask what model-specific diagnostic they recommend. Pixel thresholds and warranty procedures differ between product lines and countries. Dell’s published pixel guidelines illustrate that even one manufacturer can have different terms across its product categories. Check the current policy for the exact model; do not assume a general threshold applies.
Protect personal information in your evidence
Do not post a serial number, receipt, address or order number publicly. Share those details only through a verified support channel when needed. Before sending a photo, check that reflections, open windows or objects in the frame do not reveal information you did not intend to share. Avoid uploading pictures or diagnostic files to unknown sites promising an instant repair diagnosis.
A support message template
“My [exact model] shows [plain description] near [location] when I display [pattern/content]. I repeated it using [source/input] with [settings]. The issue [does/does not] also appear with [another source or built-in test, if checked]. I have attached an original full-screen photo and close-up. Which diagnostic or warranty step applies to this model?” Edit the brackets and remove anything you did not actually test.
References: Dell monitor diagnostic instructions and Dell Display Pixel Guidelines. These are manufacturer-specific examples, not a policy for every brand.
Use a repeatable sentence for the observation
A useful report includes four things: what you saw, where it appeared, which pattern or content was on screen, and whether it remained after you repeated the check. For example: “A small bright point stays near the upper-left edge on black and blue fields; it is visible again after refreshing the page.” This does not name a cause, but it gives support a clear starting point. If it only appears on a dark movie scene, say that rather than calling it a dead pixel.
Do not ask a photo to prove what it cannot capture
Photos are especially unreliable for judging subtle glow because phone cameras may use a long exposure, automatic night mode, HDR processing or noise reduction. A long exposure can make a dark room and screen look much brighter than they appeared to your eyes. If you want a comparison, keep the phone and display settings consistent and mention that the photo is illustrative. Do not edit the original file or claim that the camera reproduces the exact brightness of the defect.
For a moving flicker, a short video may show the timing better than a still photo, but video compression and rolling shutter can create artifacts of their own. Include a plain description of what you saw in person and let support decide whether a different diagnostic is needed.
Keep an organized private record
Save the original photos, notes and support correspondence in one folder using the model and date in the folder name. Keep the original file metadata where possible; do not replace originals with edited versions. If the issue changes, add a new dated note instead of overwriting the old one. A timeline can help support staff understand whether the behavior is stable, intermittent or linked to a setting change.