This week I’ve been: recovering from testing Halo: Campaign Evolved and playing far too much The Binding of Isaac.
I have an experiment for you. Right now, as you stare at this article on a phone, monitor, PS Vita, whatever, spin your head around. Oh, probably don’t do that in public or while walking. Or do. I don’t know, I’m not your dad.
But you will probably spot that the entire world doesn’t go blurry as you spin. Now, a second experiment: wave your hand in front of you and tell me if your hand goes blurry. As you’ll likely deduce from that very scientific experiment, motion blur (ie the entire world going blurry around you as you wiggle your head) is not a ‘realistic’ game setting.
One of the first things I do when I play a game is turn motion blur off. Given you are reading this on PC Gamer dot com, the likelihood is that you do the same. Recently, while playing Halo: Campaign Evolved, I realised it has one of the worst implementations of motion blur I’ve ever seen, and it even has the audacity to be on by default.
Now, I do acknowledge that motion blur serves a purpose. Calling it a “cure worse than the disease” back in 2023, we noted that motion blur can not only add a sense of speed and realism but can reduce the perception of artifacts. As you might be able to guess, that means motion blur is effective at obscuring faults at lower frame rates too.
And as such, it makes sense that it largely came about in the early 2000s. As 3D games became more popular, and hardware ramped up to attempt to keep pace with that innovation, motion blur helped to obscure low frame rates.
There is another purpose for motion blur. As pointed out back in 1999, Kong looks a bit weird in the 1933 King Kong movie, because the background shots are shot on camera and the titular great ape was animated with still photos. Cameras introduce motion blur, and many games attempt to mimic film, rather than real life. Nowadays, stop motion animators add artificial blur to make their pictures feel more like a movie.
So, in big-budget cinematic games, there are two built-in reasons for motion blur: to feel closer to a movie than real life, and to make up for poor performance.
But it’s 2026, and modern hardware, especially with innovations like upscaling and frame generation, can get the average fps up into the hundreds for even modern titles. So my question is, ‘why is motion blur the default?’ Why is it the native way we are supposed to play games?
Now, motion blur absolutely has its defenders, and I can see the argument for it in sequences that are played at high speeds (like racing games). But, a study from back in 2013 shows that, even in racing games, players could reliably detect motion blur but did not report it having a positive effect on the game. It concludes, “motion blur effects, while useful for reducing artifacts and achieving a realistic ‘look’, do not significantly enhance the player experience.”
While playing Halo: Campaign Evolved, I realised game capture looked significantly worse with motion blur on, regardless of the fps of the game. The blur tends to be at its worst below 60 fps, but it’s not exactly pretty at 100 fps either. The game ultimately feels less immersive to me with motion blur on.
The thing is, motion blur’s benefits, aesthetically speaking, are subjective. I hate it, and wish I’d never have to see it in a game again, but others like it. And that’s part of the problem here. It has become the default, I think, in part because it was the default, and there’s no point fixing it if it ain’t broke.
But we have tools that are much better at making up for lower frame rates now. I’d opt for a little upscaling pretty much any day over motion blur, but I also don’t expect that to be the default. There’s also a little part of my brain that doesn’t like tools that are used to mask performance issues being the expected way to play games. I want my first taste of a game to be as untreated as possible, where I then season it with as much salt and pepper as I like. And motion blur is simply too spicy for a first bite.