A clear view of every pixel. Choose a color below, go fullscreen, and take a closer look at your display.
Choose a clean field of color, expand Screen Tester to fullscreen, and inspect the panel at your normal viewing distance.
A plain field removes the distractions of a photo or desktop. Use it to locate an observation, then compare several references before deciding what it means.
A small dark point may stand out on white, while a bright or colored point may be easier to see on black or another solid color. Check the same location on red, green, and blue. A visual screen test helps you find the point; it does not automatically classify the pixel or repair it.
White and gray fields can reveal a broad tinted area, a darker strip, or uneven brightness. Look from your normal centered position and compare the screen at an ordinary viewing distance. A reflection, viewing angle, or the display coating can influence what appears to be a panel issue.
Solid colors are useful when checking a new monitor, comparing a laptop with an external display, or documenting a change in a familiar screen. Keep the brightness and picture mode consistent between passes. A repeatable observation is more useful than a single impression from a busy image.
The tool is ready in your browser. Begin with a clean screen and familiar settings, then move through the references deliberately.
Remove visible dust using the screen maker’s cleaning guidance. Use the intended resolution and your usual brightness. Start with comfortable room lighting and sit at the distance you normally use. If you are comparing screens, keep each on the same kind of content rather than comparing a dark field with a desktop.
Select a preset or enter a six-digit HEX value for a custom field. Click the preview or press F while the tester is focused to request fullscreen. Use the arrow keys or fullscreen swatches to change colors, and Escape to leave. Fullscreen availability depends on the browser and device.
Scan the center, edges, and corners without changing several settings at once. If you find a dot or patch, return to it on another color and at a normal viewing angle. Note the color, location, and conditions. This makes a later comparison or a support report easier to reproduce.
The twelve presets cover bright, dark, primary, and neutral fields. They are rendered references, not measurements of the light your panel produces.
Use white to look for dark points and broad differences in tint or brightness. Other bright fields can help confirm whether the same feature remains visible. If a mark changes when you clean the surface or move your head, compare that behavior before deciding that it is a faulty pixel.
The primary-color fields help you compare a suspicious point across different channel outputs. Cyan, magenta, and yellow provide additional combinations. A point that is obvious on only some fields needs careful comparison; the browser cannot inspect its electronics or decide whether it meets a manufacturer’s pixel policy.
Use black to look for bright points and compare the appearance of dark areas. For a more focused corner or edge check, open the dedicated backlight bleed test. Keep normal-use brightness in mind: a dark room can make small differences much more conspicuous than they are during ordinary viewing.
The gray presets are useful for comparing neutral shading and large uniformity changes. A custom HEX field lets you repeat a specific RGB reference. Its code describes the browser’s requested color; it is not a measured brightness, color temperature, or calibrated output value from the display.
A useful display check separates the observation from the cause. The next step depends on whether the issue follows the screen, the content, or the setup.
Repeat a suspicious result at the same location on multiple fields. Then compare a familiar photo, a document, or the content that first showed the problem. This helps distinguish a visible everyday issue from an effect that appears only under a particularly revealing test condition.
A solid field is good for locating a point or patch, but it cannot answer every display question. Fine lines and a geometry grid are better for shape and detail. Gray steps and gradients show different tonal behavior. Use the dedicated tools below to continue the same investigation.
This screen tester does not read light from the panel, change hardware settings, measure color accuracy, or issue a pass/fail certificate. If an observation matters for a return or service decision, compare your model’s published guidance and provide repeatable details rather than relying on the browser view alone.
Practical answers about solid-color checks, fullscreen, and what the browser can tell you.
No. It displays reference colors for you to inspect visually. A dark point on a bright field or a bright point on black can be a reason to look more closely, but the page cannot see your panel, count defective pixels, or confirm a hardware diagnosis.
Compare the exact spot on several colors after cleaning the screen according to the manufacturer’s instructions. A surface mark, reflection, or viewing-angle effect can look different from a fixed point in the image. Repeat the observation before assigning a cause; the browser cannot make that distinction for you.
Fullscreen gives the reference more of the visible display and removes much of the browser interface. It is useful for inspecting edges and corners. Entering it still requires an explicit user action, and some mobile browsers do not support the same fullscreen behavior as a desktop browser.
No. Resolution, pixel ratio, and color depth are the values available to the browser. The refresh figure is an estimate based on browser frame timing. Scaling, browser behavior, power settings, and the active display can affect those values; use the dedicated refresh-rate page for a longer live comparison.
You can open it in a compatible browser on a phone, tablet, laptop, or a computer connected to a TV. A TV without a suitable browser needs a connected source device. Use the intended output resolution, and remember that browser fullscreen and keyboard controls vary between devices.
Use the reference that matches the question you want to answer.
