ULMB 2 is Nvidia’s second-generation Ultra Low Motion Blur mode, a backlight-strobing technique that flashes the backlight in sync with each frame to sharpen fast motion. If you have ever chased a flick target and watched it smear into a blurry ribbon, motion blur reduction is the feature aimed squarely at that problem. This guide explains what ULMB 2 actually does, how it differs from ordinary strobing, and whether it belongs on your shortlist.
Why sample-and-hold blur exists
An LCD or OLED holds each frame on screen until the next one arrives. Your eyes track moving objects smoothly, but the image sits still for the whole frame, so the object appears to blur across the distance it travelled. At 60Hz a frame is held for about 16.7ms; at 240Hz it is roughly 4.2ms. Raising refresh rate shrinks the hold time and therefore the blur, which is why a 240Hz panel looks clearer in motion than a 60Hz one even with identical response times.
What strobing does differently
Backlight strobing attacks the same problem from another angle: instead of leaving the image lit for the full frame, it blacks out the backlight for most of the frame and flashes it briefly. That short pulse means your eye sees the image for only a fraction of the hold time, so perceived blur collapses. The trade-offs are lower brightness (the backlight is off most of the time) and a risk of “strobe crosstalk,” a faint double-image where the panel had not finished transitioning when the flash fired.
Where ULMB 2 improves the formula
First-generation ULMB and most strobing modes locked you to a fixed refresh (often 120Hz) and left brightness painfully dim, sometimes under 200 nits. ULMB 2 targets much higher effective motion clarity, with Nvidia quoting figures around 1000Hz to 1440Hz of equivalent motion resolution on supported panels, while keeping full brightness closer to 250 to 300 nits. It also tunes overdrive per-pixel across the refresh window to crush crosstalk, and runs at high native rates like 240Hz rather than dropping you to 120Hz.
ULMB 2 vs generic strobing at a glance
| Attribute | Higher refresh only | Generic strobing | ULMB 2 |
|---|---|---|---|
| Typical motion clarity (equiv. Hz) | 240-360 | ~700-900 | ~1000-1440 |
| Brightness during mode | Full (300-600 nits) | Low (100-200 nits) | ~250-300 nits |
| Works with VRR at same time | Yes | Rarely | No (fixed refresh) |
| Crosstalk / double image | None | Often visible | Heavily reduced |
| Refresh it runs at | Native | Often 120Hz | Native high (e.g. 240Hz) |
The catch: you cannot strobe and use VRR together
Strobing needs a fixed, predictable frame cadence, so ULMB 2 cannot run at the same time as G-Sync or FreeSync variable refresh. That forces a choice: tear-free adaptive sync for single-player games where framerate swings, or ULMB 2 for competitive shooters where you can hold a stable framerate at or near the panel’s refresh. Most players keep VRR on for campaigns and flip ULMB 2 on only for esports titles their GPU can pin at 240fps.
Do you need it?
If you play Valorant, CS2, or Overwatch and can sustain high, stable framerates, ULMB 2 delivers a genuinely visible clarity jump that plain 240Hz cannot. If you mostly play story-driven or open-world games with variable framerates, you will get more value from VRR and simply won’t benefit. It is a competitive-first feature, not a universal upgrade.
How to get the most out of ULMB 2
Turning the mode on is only half the job; feeding it correctly is what makes the clarity appear. Because strobing samples each frame for a sliver of time, you want your framerate to sit right at the panel’s strobed refresh, commonly 240Hz, so every strobe lands on a fresh, complete frame. If your framerate falls well below that, you will see stutter and duplicated images instead of the crisp motion the mode promises.
Framerate discipline
In practice, that means picking games and settings your GPU can pin near 240fps. Competitive shooters like CS2, Valorant, and Overwatch are ideal because they run at very high framerates on modern hardware even at reduced settings. Cap your framerate slightly below the refresh to keep it stable, and avoid demanding graphics options that cause dips into the low hundreds where strobing starts to fall apart.
Tuning the pulse
Many ULMB 2 implementations expose a pulse-width or strobe-length control that trades brightness against clarity: a shorter pulse sharpens motion further but dims the picture, while a longer pulse brightens it at the cost of a little blur. Start in the middle, then adjust based on your room lighting and how much clarity you actually need. In a bright room you may prefer a longer pulse; in a dim battlestation you can chase maximum sharpness.
FAQ
Does ULMB 2 add input lag?
The strobing itself adds only a negligible fraction of a millisecond because the flash is timed to the frame. The bigger latency factor is that you must disable VRR and typically cap framerate, but the mode is not meaningfully “slower” than running the same fixed refresh without strobing.
Will ULMB 2 work on any 240Hz monitor?
No. It requires specific hardware certification and a supported G-Sync module or panel controller, plus a compatible GPU and DisplayPort connection. Check the monitor’s spec sheet for explicit ULMB 2 support rather than assuming a high refresh rate implies it.
Bottom line
ULMB 2 is the most refined take yet on backlight strobing: near-CRT motion clarity at usable brightness and high native refresh, with crosstalk largely engineered out. The price is losing adaptive sync while it runs and needing a framerate high enough to feed it. For competitive players it is a standout feature; for everyone else, a high native refresh with VRR remains the smarter default.
