Quick answer

My pick is off, with one caveat: a game’s motion blur is an effect drawn into the frame, and it is a different thing from the blur your eyes get from a sample-and-hold screen. If you like the cinematic look, a low setting is a matter of taste, not a fix. For blur you want less of, the levers are frame rate and refresh rate, or the monitor’s strobing or black frame insertion mode.

Contents

At a glance

Class
Gaming

Provenance

  • Nov 18, 2026Published

TL;DR · Motion blur on or off

  • My pick: off. That is judgment, not a measurement. Epic's and Unity's documentation define the effect and give you strength controls; neither says which way to set it.
  • Keep it on if you like the look, and keep it low. It is a style setting. It is not what fixes blur on your screen.
  • There is a second blur, and it is on the display, not in the game: Blur Busters calls it sample-and-hold blur, and it exists even on a 0 ms pixel-response panel.
  • To reduce that blur: raise frame rate and refresh rate together, or use the monitor's strobing or black frame insertion mode if it has one and you can tolerate the trade-offs.
  • Where it lives: the game's own graphics menu. I found no Windows or NVIDIA driver setting for it in the documentation I read.

There are two different blurs in this question, and the two are easy to mix up. One is an effect a game’s renderer draws into the picture. The other happens between your screen and your eyes whether the game draws any blur or not. This page covers both, with the definitions taken from the engine documentation and from Blur Busters, the site that has spent years on the display side. I have a 4K OLED on an RTX 5080 on this bench; I did not run any game for this page, so there is no “I tested it” anywhere below.

What the in-game setting is

Unity’s documentation describes its Motion Blur effect as simulating the blur that occurs in an image when a real-world camera films objects moving faster than the camera’s exposure time, usually from rapidly moving objects or a long exposure. Epic puts it in photography terms too: motion blur is the result of an object moving before the image has been captured, and how fast the object moves determines how much blur there is.

Two flavors show up in the documentation:

  • Camera motion blur. Unity’s Motion Blur override has a Mode with two options. Camera Only uses only the motion of the camera to blur the picture, does not use motion vectors, and Unity says it performs better than the other mode. Camera and Objects adds the motion of the objects in the scene, and per Unity the object motion vectors overwrite the camera motion vectors.
  • Per-object motion blur. Epic says Unreal’s motion blur uses a full-screen velocity map, and objects are blurred based on their contribution to that map. One of its controls, Per Object Size, sets the minimum projected screen radius an object needs to be drawn in the velocity pass, as a percentage of screen width; smaller radii cause more draw calls.

The strength controls are what you see in a game’s slider, if it has one. Unity’s are Intensity (0 to 1; higher values give a stronger blur and, depending on Clamp, can cost performance), Quality (lower presets perform better but risk visual artifacts) and Clamp, the maximum length the velocity from camera rotation can have, with a default of 0.05 and a range of 0 to 0.2. Epic’s are Amount (0 is off) and Max, the maximum distortion as a percentage of screen width (0 is off).

One Epic detail explains why the same slider can feel different at different frame rates. Its Target FPS setting makes the motion blur independent of the actual frame rate: relative to the specified target, shorter frames mean shorter shutter times and less blur, and lower FPS means more blur. A value of 0 makes it depend on the measured frame rate. Whether a particular game sets that value, I can’t tell you from documentation.

Why people turn it off, and why people turn it on

I’ll be plain about the limits here. Nothing I read from Epic or Unity says motion blur is meant to hide low frame rate, to help or hurt aiming, or to cause discomfort. I’m not going to repeat claims like those as fact.

What the sources do support is the display side, and that is where the frame-rate part of this question lives.

Sample-and-hold. Blur Busters says your eyes are always moving when you track a moving object on a screen, and that sample-and-hold means each frame is held statically until the next refresh. Your eyes are in a different position at the start of a refresh than at the end, so the frame is smeared across your retinas. It calls this blur from persistence, separate from pixel transition speed (GtG): even a 0 ms GtG panel can show a lot of motion blur this way, and it says plainly that most LCDs and OLEDs are sample-and-hold. A 60 Hz refresh, it notes, is displayed for a whole 1/60th of a second.

Blur Busters’ one rule for fixing it: the only way to reduce sample-and-hold blur is to shorten the time a frame is displayed, with extra refreshes (higher Hz) or black periods between refreshes (flicker). A guest article by William Sokol Erhard that Blur Busters published in May 2025 puts a number on the first route: doubling the frame rate will halve display motion blur and quadrupling it eliminates 75 percent, assuming enough refresh rate and instant pixel response (GtG of 0).

That is the “low frame rate” connection I can actually source: that 2025 piece ties frame rate directly to the amount of display blur. Whether a game’s drawn blur makes a 60 fps game look smoother to you is something I haven’t found a source for, and I won’t pretend otherwise. Try it in the game and judge it with your own eyes. If it looks better to you, that is a fine reason to leave it on.

OLED does not escape it. Blur Busters’ OLED page makes the point that OLED’s near-instant pixel response does not shorten persistence. Their examples are older handheld and phone OLEDs, so I read it as a statement about the mechanism, and the same page says some OLEDs use strobing to lower persistence and not all do.

Display-side blur reduction

This is the part of the question the in-game slider can’t touch. Blur Busters’ motion blur reduction FAQ describes backlight strobing, sold under names like ULMB, LightBoost, DyAc and ELMB, as flashing a backlight synchronized to the refresh rate. The backlight is off while the LCD pixels are changing and flashes only on fully refreshed frames; the flash can be shorter than the pixel transition. NVIDIA’s own words for ULMB in its driver help are “Ultra Low Motion Blur” for people who prefer to improve motion blur instead of using G-SYNC, and NVIDIA app’s text describes it as backlight pulsing at a fixed refresh rate to minimize blur, best for games with consistently high FPS.

The trade-offs, all from Blur Busters:

  • Quality varies by monitor. It says blur reduction sometimes looks very good, with CRT-style motion clarity, and sometimes very bad, with double images (strobe crosstalk), poor colors, dimness, microstutter or flicker.
  • Frame rate must match. Frame rates lower than the strobe rate produce multiple-image artifacts: 30 fps at 60 Hz is a double image, 60 fps at 120 Hz is a double image and 30 fps at 120 Hz is four. Its advice is to match frame rate, refresh rate and strobe rate.
  • Brightness versus clarity. Some backlights have an adjustable pulse width, and the shorter the flash, the clearer the motion and the dimmer the picture.
  • Input lag. It says blur reduction modes by several vendors may add input lag.
  • Flicker. Erhard’s 2025 guest article puts the flicker fusion threshold for most people at roughly 90 to 120 Hz, and says strobing below it can cause significant discomfort and fatigue. NVIDIA’s app text for G-SYNC Pulsar, its variable-frequency strobing feature, says it runs at 90 to 360 Hz by default, that the minimum can be set between 75 and 120 Hz based on personal flicker tolerance, and that some users might perceive flickering below 90.

Black frame insertion (BFI). Same idea at the signal level: individual refresh cycles are blacked out. Erhard’s article lists BFI, ULMB, ELMB, DyAc, OLED Motion and G-Sync Pulsar as names for the family, and says modern TVs like LG OLEDs and OLED gaming monitors often offer BFI with limited controls, a moderate amount of added latency, and often a single mode at half the maximum refresh rate with a 50 percent duty cycle. Duty cycle there means the fraction of each refresh the image is visible; the lower it is, the lower the brightness and the lower the motion blur. Which of your monitor’s modes are which is a question for your monitor’s manual.

On my own screen, the one thing I can tell you comes from my AORUS FO48U review: it has a feature called Aim Stabilizer that is supposed to reduce motion blur, and I wrote there that enabling FreeSync disables most of the monitor’s gamer features. Blur Busters’ FAQ lists Aim Stabilizer, by AORUS/Gigabyte, among the monitor brand names for blur reduction. I have no measurement of it. That interaction between adaptive sync and strobing is also in the sources: Erhard’s article says some strobing implementations offer configurable refresh rates but not with variable refresh rates (NVIDIA markets G-SYNC Pulsar as variable-frequency strobing, so check what your monitor supports).

What I’d do

  1. Pick the in-game setting by taste, starting at off. It’s drawn into the image by the game; the documentation gives you strength controls and nothing more.
  2. If your complaint is that moving objects smear on your screen, that’s the display’s persistence. Raise frame rate and refresh rate together; the VSync and frame generation pages cover the sync and frame-rate settings. If frames are inconsistent rather than low, the stuttering guide is the place to start. The FPS calculator helps with the budget.
  3. Then look at your monitor’s strobing or BFI mode, and treat it as a trade: brightness, flicker, crosstalk and latency in return for clarity.
  4. Softness that isn’t motion (a static image that looks smeared) is an anti-aliasing question, covered in the anti-aliasing guide.

Frequently asked questions

Should motion blur be on or off in games?
Neither Epic’s nor Unity’s documentation recommends a setting; both describe it as an effect with strength controls. My pick is off, because it is blur drawn into the image on top of whatever your display already does, and I read nothing that says one cancels the other. If you like the look, keep it low. It is a taste setting.
What is the difference between camera and per-object motion blur?
Unity’s URP Motion Blur override has a Camera Only mode, which uses only the motion of the camera, and a Camera and Objects mode, which adds the motion of GameObjects. Unity says Camera Only has better performance. Epic’s Unreal documentation describes the engine blurring objects by their contribution to a full-screen velocity map.
Does motion blur lower FPS?
It can. Unity says higher intensity values give a stronger blur but can cause lower performance depending on the Clamp setting, and that the Camera Only mode performs better than Camera and Objects. Epic says a smaller Per Object Size radius means more draw calls. Neither gives a frame-rate figure, and I won’t invent one.
Why does my monitor look blurry in motion even with motion blur off?
Blur Busters explains that a sample-and-hold display shows each frame for the whole refresh while your eyes keep tracking the moving object, which smears it across your retina, and that this is separate from pixel response time. It says even a 0 ms GtG panel can show a lot of motion blur this way.
Does a higher refresh rate reduce motion blur?
Per a Blur Busters guest article by William Sokol Erhard (May 2025), yes: doubling the frame rate halves display motion blur and quadrupling it removes 75 percent, assuming enough refresh rate and instant pixel response. That means the frame rate has to rise too, not only the refresh rate.
What is black frame insertion, and should I use it?
It blacks out some refresh cycles to shorten how long each image is visible. A Blur Busters guest article by William Sokol Erhard (May 2025) says strobing very effectively reduces motion blur but often causes flicker, needs the refresh rate above roughly 90 to 120 Hz to avoid it, and that built-in modes on LG OLEDs and OLED gaming monitors often have limited controls, add a moderate amount of latency and often allow a 50 percent duty cycle at half the maximum refresh rate. Try it, and turn it off if it flickers or costs you too much brightness.

Sources and corrections

Last updated
Methodology
See our methodology for research and review standards. It draws on 6 cited sources, listed below, each checked against the original page on 2026-11-17. First-hand reads on the bench machine, all read-only, on 2026-11-17. Windows 11 Home build 26200 (the registry’s ProductName still reads ‘Windows 10 Home’; DisplayVersion 25H2, UBR 9974, from Get-ItemProperty on HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion). nvidia-smi –query-gpu=name,driver_version returned ‘NVIDIA GeForce RTX 5080, 621.24’. Get-CimInstance Win32_VideoController returned a 3840x2160 current mode at CurrentRefreshRate 119 and driver version 32.0.16.2124, and WmiMonitorID returned a monitor named AORUS FO48U. NVIDIA app version 11.0.9.585 from reg query HKLM\SOFTWARE\NVIDIA Corporation\Global\NVApp. I read NVIDIA’s descriptions of ULMB and G-SYNC Pulsar from the app’s own English string table, C:\Program Files\NVIDIA Corporation\NVIDIA App\www\assets\i18n\en_US.json; that tells me NVIDIA’s wording, not whether my monitor supports either feature, and I did not open the app. I did not measure motion blur, persistence or input latency and did not run any game, so every statement about blur on this page belongs to the engine documentation or to Blur Busters, named where it appears. The Blur Busters FAQ and OLED pages are old pages that still carry the site’s definitions; the 2025 strobing-versus-frame-generation article is a guest piece by William Sokol Erhard, who also makes the Vint software it discusses, and I attribute its claims to him.
Corrections
Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.

About the author

I am Lowell K. Wood IV. I research, write and maintain everything on TechFuelHQ from St. Louis County, Missouri.