James Bentley, a hardware writer at PC Gamer, says motion blur has become the “default” in games for so long that nobody bothered to fix it, and he is done. In his recent testing, he noticed Halo: Campaign Evolved uses one of the worst motion blur implementations he has seen, including the audacity of having it turned on by default.

Bentley’s core claim is immediate and simple: motion blur makes captured gameplay look significantly worse with it enabled, and it does not feel more immersive even when the game is running well. He says the blur is at its worst below 60 fps, but it still looks bad at around 100 fps too. His practical takeaway is also blunt: one of the first things he does when he plays a game is turn motion blur off.

To understand why this matters beyond taste, Bentley walks through the two reasons motion blur historically made sense. In big-budget, cinematic games, motion blur has been used to make visuals feel closer to film, rather than real life. He points to an older example from the filmmaking world: the 1933 King Kong reportedly looked weird in part because the titular ape was animated with still photos while the background shots were filmed, and cameras introduce motion blur. Modern stop motion animators add artificial blur for a similar reason, to make pictures feel more like a movie.

The second classic reason is performance camouflage. Bentley notes that motion blur can add a sense of speed and realism, and it can reduce the perception of artifacts. That makes it effective at obscuring faults at lower frame rates too, which is why it largely came about in the early 2000s, when 3D games were becoming popular but hardware struggled to keep up. In other words, motion blur was a tool to hide the mess that weaker frame rates used to make more obvious.

But Bentley’s argument pivots on 2026-era rendering. He says modern hardware, especially innovations like upscaling and frame generation, can get average fps into the hundreds even for modern titles. If that is true for the average experience, then the original justification for motion blur as a workaround weakens. His central question is the one that will annoy anyone who has ever accepted “default settings” as gospel: if we can cover up low frame rates with better tools now, why is motion blur still the native way we are supposed to play?

He also brings in the counterbalance that regulators and researchers love, data. Bentley cites a study from 2013 stating that even in racing games, players could reliably detect motion blur but did not report it having a positive effect on the game. The study concludes: “motion blur effects, while useful for reducing artifacts and achieving a realistic 'look', do not significantly enhance the player experience.” That framing matters because it separates two things developers can accidentally conflate: visual smoothing (less obvious artifacts) versus player-perceived benefit (fun, immersion, comfort).

There is also a distribution and capture angle hidden in the complaint. Bentley says that while playing Halo: Campaign Evolved, he realized game capture looked significantly worse with motion blur on, regardless of the game’s fps. This matters in an era where “what the game looks like” is increasingly mediated by screenshots, clips, and streams, not just personal eyeballing at your desk. When motion blur degrades captured footage, it can distort the feedback loop. The community sees a different reality than the game might present with cleaner motion settings, and that can influence what players expect from future titles.

The big strategic point in Bentley’s piece is about incentives, not just aesthetics. He argues motion blur may persist because it was the default, and if it “ain’t broke,” there is no reason to fix it. He also flags a subtle but powerful second-order issue: tools that mask performance issues being the expected way to play games can set the wrong baseline for quality. His metaphor is colorful but the idea is practical: he wants his first taste of a game as “untreated as possible,” then he can add “salt and pepper” via settings he chooses, not via a built-in smear that some players never asked for.

For executives, the stake is straightforward. Motion blur might still be defensible in specific contexts, Bentley even nods to defenders in high-speed sequences like racing games. But if research suggests it does not significantly enhance player experience, and if modern tech can maintain fluidity without relying on blur, then keeping it on by default becomes a product-quality decision with measurable downstream effects. Teams should treat “default visual settings” like a commitment to player experience, not a legacy checkbox. If you are building for 2026 audiences, the question is not whether motion blur can look cinematic. It is whether shipping it by default is worth the immersion tax, especially when better options like upscaling and frame generation can do the job without smearing the whole screen.