MONITOR BLOOMING TEST

ADVERTISEMEANT
ADVERTISEMEANT

What this pattern reveals

High contrast makes local-dimming behavior visible

LCD local dimming cannot illuminate a bright object without affecting the surrounding zone. The amount and shape of the halo depend on zone count, algorithm, brightness, content, and viewing position.

OLED displays do not use a conventional backlight, but the pattern can still help reveal near-black glow, raised blacks, reflections, or image-processing changes.

How to run the test

  1. 01Dim the room, remove direct reflections, and let your eyes adapt for several minutes.
  2. 02Enable the local-dimming mode you normally use, then enter full screen.
  3. 03Compare the small targets in the corners and center with the larger central target.
  4. 04Move your head slightly and repeat at another brightness to separate fixed halos from off-axis glow.

How to read the result

  • A glow that follows the bright target usually reflects local-dimming zone behavior.
  • A fixed bright patch that remains without a nearby target may indicate backlight non-uniformity.
  • A halo that changes strongly with head position can be affected by panel viewing angle.

Interpretation guide

Judge halos as a local-dimming tradeoff, not a single number

Why bright objects on black reveal dimming behavior

An LCD needs a backlight, so a small bright object can require one or more lighting zones to turn on behind surrounding black pixels. If a zone covers a larger area than the object, scattered light creates a visible halo. More zones can improve spatial control, but zone count alone does not determine quality; the dimming algorithm, optical stack, panel contrast, zone transition speed, and chosen picture mode all matter. OLED and other self-emissive displays control light per pixel and therefore do not produce backlight-zone halos, although glare, lens flare in content, and eye scatter can still look halo-like.

Blooming and black crush pull in opposite directions

A local-dimming algorithm can reduce halos by dimming a zone aggressively, but that may erase faint stars, shadow texture, subtitles, or interface details near black. Preserving every small highlight may keep detail while lifting the surrounding black. Evaluate both sides of the tradeoff. Move the bright object across dark areas, compare small and larger objects, and check near-black detail. The best setting is the one that preserves intended information with the least distracting halo in the content and room lighting you actually use.

Position, motion, and viewing angle change the result

Edge-lit displays may form columns or broad clouds because their LEDs illuminate from the border, while full-array systems can show rectangular or circular zone structures. A moving target also reveals whether zones brighten late, dim late, flicker, or jump in visible steps. On VA and IPS LCDs, off-axis viewing can make a halo look larger or lighter, so first judge from the centered seating position. Subtitles and loading icons are useful real examples, but their antialiasing and the camera work in a scene can contain intentional glow; compare them with this clean geometric target.

SDR and HDR require separate observations

HDR typically asks the display to produce brighter highlights and may engage a different local-dimming algorithm, backlight level, or tone map. A setting that looks controlled in SDR can bloom more in HDR, while an HDR mode may also preserve more highlight detail. Test both modes only with a correctly configured signal and note the active preset. A browser observation cannot establish DisplayHDR compliance or peak luminance. VESA certification uses defined patterns, measurement positions, and instruments; this page is for seeing the spatial and temporal behavior that accompanies those measurements.

Reliable visual testing

Build a repeatable test before judging the display

A browser pattern is a controlled visual stimulus, not a measuring instrument. It is excellent for finding visible non-uniformity, clipped tones, scaling errors, halos, color shifts, and motion artifacts under the conditions in which you actually use the screen. It cannot, by itself, report luminance in candelas per square metre, a color difference value, a gamut percentage, or a response-time number. Those claims require a meter, defined test windows, timing equipment, and a documented procedure. Use this page first as a practical screening and comparison tool: it can tell you where to look, whether a change is repeatable, and whether one setting or one display looks better than another.

Treat the entire signal path as part of the experiment. The image passes through the page, browser, operating-system color management, graphics driver, cable or wireless link, monitor input mode, picture preset, and panel before it reaches your eyes. Browser zoom, system scaling, non-native resolution, night-light software, HDR conversion, an ICC profile, dynamic contrast, local dimming, sharpening, noise reduction, and variable refresh can each alter the result. A suspicious pattern therefore does not automatically prove a panel defect. Record the active resolution, refresh rate, browser, picture mode, brightness, contrast, color temperature, HDR state, and any adaptive features so that you can reproduce the observation.

Control the room before comparing results. Allow the display to reach a stable operating state, clean the screen with the method recommended by its manufacturer, and prevent direct reflections from crossing the test area. Use moderate, stable ambient light for general checks. Use a dim room only for near-black, black-uniformity, and blooming observations, because those artifacts are easily hidden by reflections and eye adaptation. Do not judge a dark screen immediately after looking at a bright white page; give your vision a short period to adapt. Keep your normal viewing distance and eye height unless the test specifically asks you to move off-axis.

Run the first pass at the panel's native resolution with browser zoom at 100 percent. Full screen reduces distractions, but it does not cancel operating-system scaling or color processing. Inspect once from your normal position, then move closer only to identify the structure of an artifact. Change one control at a time and repeat the same pattern after every change. If several settings move together, you lose the ability to say which one helped. A useful comparison is A/B/A: observe the baseline, apply one change, then return to the baseline. If the effect disappears and returns with the setting, the relationship is more credible than a single impression.

Look for repeatability across content, positions, and inputs. Rotate or move the pattern when the tool allows it. Test a second browser, input, cable, refresh rate, or computer if the finding matters. A mark that stays in the same physical place on the panel is more likely to be display-related; a mark that follows a browser window or screenshot may originate earlier in the signal chain. Photographing the screen can help document location and severity, but a camera introduces exposure, focus, lens shading, moiré, rolling shutter, tone mapping, and white-balance errors. A photograph is evidence of what the camera captured, not a substitute for a calibrated reading.

A compact pre-test checklist

01Stabilize the display

Let brightness and temperature settle, disable screen savers, and avoid testing while the device is rapidly changing power or thermal state.

02Confirm the signal

Use native resolution, verify the intended refresh rate and RGB range, set browser zoom to 100 percent, and note whether SDR or HDR is active.

03Neutralize temporary processing

Pause night light, automatic brightness, dynamic contrast, content-adaptive brightness, and vendor enhancement modes unless one of them is the feature being tested.

04Control the environment

Remove glare, keep ambient light stable, sit square to the screen, and use a darker room only when the test calls for near-black observation.

05Make one change

Adjust only one setting between runs, return to the original value for confirmation, and write down values instead of relying on memory.

06Repeat before concluding

Reopen the pattern, try representative real content, and check another browser or input when the consequence of a wrong conclusion would be costly.

How to turn an impression into useful evidence

Describe what you see without jumping directly to a diagnosis. Record the pattern, color or tone, screen region, viewing distance, room lighting, time after power-on, and whether the artifact changes with angle or settings. Terms such as “a pale vertical band in the left third on 30–50 percent gray” are more useful than “the panel is bad.” Severity should be tied to normal work: state whether the effect is visible only in a dark test room, during ordinary desktop use, or in real video and games. This makes comparisons between presets, firmware versions, and replacement units much more meaningful.

Escalate the method when the decision requires numbers. Photographers and designers may need a colorimeter or spectrophotometer for white point, gamma, tone response, color accuracy, and uniformity. HDR evaluation needs defined test windows and an instrument that can measure bright highlights and dark levels. Motion measurements need synchronized capture or a validated pursuit-camera method. Warranty decisions should follow the manufacturer's pixel, uniformity, and return policies rather than an unofficial universal threshold. The visual test remains valuable: it identifies the question that a formal measurement needs to answer.

What a visible symptom may mean

A rectangular glow follows the target

This is consistent with a dimming zone being larger than the bright object. Compare local-dimming levels and centered versus off-axis viewing.

Dim trail behind a moving object

The zone algorithm may be releasing slowly. Change motion speed and refresh rate, then verify with ordinary dark scenes before rating its impact.

Faint objects disappear near highlights

Aggressive dimming may be suppressing shadow detail or small highlights. Compare a less aggressive mode and inspect whether blooming increases as detail returns.

Halo exists with local dimming off

Check panel glow, backlight bleed, reflections, and eye scatter. Not every bright area around an object is generated by the zone algorithm.

What this browser test cannot measure

It does not measure black level, contrast ratio, zone count, HDR peak brightness, or blooming area. A camera often exaggerates halos and should not replace direct observation.

Blooming test questions

Is blooming normal on a mini-LED monitor?+

Some blooming is expected because one dimming zone controls more than one pixel. Visibility varies with zone count, algorithm, brightness, viewing angle, and content.

Why does blooming look worse in photos?+

Phone cameras raise exposure, apply sharpening, and capture lens flare. Use photos for location records, not as a calibrated representation of what your eyes see.

Methodology and further reading

RTINGS' published local-dimming method evaluates haloing, black crush, zone transitions, flicker, and real content rather than reducing performance to zone count. VESA's DisplayHDR material shows why formal HDR and black-level claims use prescribed patterns and colorimetric instruments. This page adapts those questions for unaided visual comparison.

Our Monitor Local Dimming TestsRTINGS
DisplayHDR True Black Standard OverviewVESA
DisplayHDR Standard Update and Test MethodsVESA

Continue testing

Related monitor tests