Self-emissive pixels
OLED pixels emit light rather than modulating a shared backlight. A black request can turn pixels off in an appropriate signal path, while individual bright or colored points may remain conspicuous on dark fields.
Device inspection workflowSelf-emissive OLED inspection sequence
0 of 7 complete
Use practical brightness and short manual comparisons. Move from point defects to residual shapes, low grey, uniformity, tint, black, and optional motion; the checklist does not grade the panel.
An OLED screen test should focus on self-emissive pixel behavior, residual static shapes, low-grey uniformity, and tint. There is no LCD backlight bleed step because OLED has no separate LCD backlight.
- Run pixel fieldsEssential
Check dark, bright, and colored points
Black, white, RGB, and grey provide different backgrounds for pixel and subpixel observations on a self-emissive panel.
How to run and read this step
Run it: Scan methodically at a comfortable brightness and keep any suspect location fixed as fields change.
Look for: Note whether a point stays off, stays lit on black, or responds differently to individual color channels.
- Open retention checkEssential
Look for retention or differential aging
Low and middle grey plus selected color fields can expose faint outlines left by static interface regions.
How to run and read this step
Run it: Use manual fields first and inspect status-bar, logo, taskbar, scoreboard, and keyboard-shaped areas relevant to the device.
Look for: A persistent outline may be temporary retention or permanent differential aging; interpretation requires time and context.
Keep in mind: The page cannot read compensation-cycle status and does not recommend repeatedly forcing maintenance cycles.
- Open low-grey patternsEssential
Compare near-black detail
Very low grey levels help reveal black crush, lifted dark tones, tint, flashing, or OLED mura-like non-uniformity.
How to run and read this step
Run it: Use low ambient light and compare 0.5%, 1%, 2%, 5%, and the low-grey ramp without assuming every code is visible.
Look for: Look for broad fixed regions and missing adjacent tones; panel processing and browser color handling can affect the view.
- Compare grey fieldsRecommended
Inspect grey uniformity at several levels
Low, middle, and bright neutral fields can reveal vertical bands, patches, or a broad color cast.
How to run and read this step
Run it: View low grey in dim light and mid-grey in normal light from a stable centered position.
Look for: Record where an area appears and whether its visibility changes strongly with brightness or warm-up time.
- Open RGB channelsRecommended
Compare RGB tint and uniformity
Primary fields and ramps can reveal channel-specific tint or area differences without claiming gamut coverage.
How to run and read this step
Run it: Compare red, green, blue, white, and secondary mixes briefly at a practical brightness.
Look for: Look for a fixed broad tint or channel-specific patch, accounting for viewing angle and device color modes.
- Open black fieldRecommended
Observe the black field
A pure black request provides a visual reference for stuck-on points and unexpected lifted areas.
How to run and read this step
Run it: Inspect in low ambient light, then compare 1% and 2% fields so pure black is not judged in isolation.
Look for: Reflections, browser overlays, near-black processing, and raised blacks in the signal path can alter the result.
Keep in mind: The browser does not measure emitted black luminance or exact contrast.
- Open motion lanesOptional
Optionally compare motion cadence and trails
Self-emissive response does not eliminate sample-and-hold blur, browser cadence limits, or motion-processing effects.
How to run and read this step
Run it: Compare the synchronized lanes and use focused refresh or ghosting tools only if a symptom is visible.
Look for: Name the visible effect without converting it into an invented response-time value.
Self-emissive panel workflow
OLED Screen Test
An OLED screen test should reflect how the panel works: each pixel produces its own light, so pixel points, residual static shapes, near-black rendering, low-grey uniformity, and RGB tint deserve attention. LCD backlight bleed does not apply to OLED.
Mechanism matters
Why an OLED workflow does not include LCD backlight bleed
Differential aging
Repeated static regions can age differently from surrounding pixels. Grey and selected colors may reveal an old interface outline, but a visual field alone cannot establish permanence, cause, or remaining lifespan.
Near-black complexity
Very low grey can expose black crush, tint, flashing, banding, or mura-like variation. Browser color management, device processing, ambient light, and eye adaptation all influence the observation.
Interpretation sequence
Classify the shape before discussing burn-in
- Locate it. Is the observation one pixel-sized point, a broad vertical area, or a recognizable interface shape such as a taskbar, status region, keyboard, logo, or scoreboard?
- Change the field. Compare low grey, middle grey, white, and selected RGB fields. Record where the shape is strongest rather than assuming one grey value is universally best.
- Change ordinary content. Confirm that the shape stays at the same physical panel location and is not part of the page, a reflection, image compression, or an application overlay.
- Allow normal device behavior. Do not repeatedly force maintenance or compensation cycles. Follow manufacturer guidance and reassess through normal use when temporary retention is plausible.
Low-grey observation
Use more than one near-black level
Pure black, 0.5%, 1%, 2%, 5%, and 10% grey answer different questions. Pure black can reveal an unexpected lit point or raised black in the signal path. Very low grey can show whether adjacent dark values separate, while low and middle grey make broad uniformity and residual shapes easier to compare. Not every mathematically requested level must be visible on every browser and display path.
Black level is an observation, not a contrast measurement
The black field can look completely dark in a dim room, but that does not let the site calculate infinite or exact contrast. Reflections, browser overlays, video range, color modes, near-black processing, and surrounding light remain relevant. A meter and controlled signal path are needed for physical luminance or contrast data.
Keep the OLED screen test short and repeatable
Use comfortable brightness, manual fields, and a written observation. Avoid leaving static high-brightness patterns displayed longer than necessary. The workflow does not flash rapidly, promise a repair, or advise pressing the screen. Warranty and service decisions belong with the relevant manufacturer, retailer, or qualified provider.