Motion Blur in Blender Cycles: A Settings Guide for Architectural Animation

Blender’s official manual explains how to control motion blur in Cycles render settings using Position, Shutter, and Rolling Shutter options. The feature simulates the motion trails visible when moving objects are captured in an animation frame or a real photograph. The manual pages do not specify a particular Blender version, so the steps below are limited to the documented interface and options.

When is motion blur useful?

Blender animations are normally captured as completely static images, one frame at a time. In real camera footage, however, fast-moving objects can appear blurred in the direction of motion. Motion blur in Cycles recreates this visual effect in animations. It can be useful in architectural presentations featuring sequences with a moving camera, vehicle, person, or other moving object; in still images, the feature has no motion trail to create.

The settings are in the Render › Motion Blur panel. Each object also has its own motion blur controls in the Object tab of Properties. Reviewing the scene-wide settings alongside the object-level controls can make it easier to identify the source of an unwanted effect.

1. Choose the shutter position within the frame

The Position setting determines when the shutter opens relative to the current frame. With Start on Frame, it begins opening at the current frame. With Center on Frame, the shutter is fully open at the current frame. End on Frame means the shutter is fully closed at the current frame.

These options affect where the blur falls on the animation timeline. If it matters which frame a movement is associated with, it is useful to compare all three positions in a quick test render. The manual does not recommend a single position for a specific scene type; the choice depends on the desired timing effect.

2. Set the Shutter duration according to the amount of motion

Shutter specifies the duration, in frames, from when the shutter starts opening until it is fully closed. In the example in the official manual, a value of 1.0 produces blur over one frame of motion. Since the manual does not recommend a universal value for shorter or longer durations, test settings according to the speed of the architectural animation and the intended image.

The values and options in the table are examples described in the manual; they should not be treated as presets recommended for every scene. In particular, when changing the Shutter duration, reviewing several consecutive frames—not just a single frame—can help you check that the effect remains consistent over time.

3. Interpret Rolling Shutter and the curve correctly

In the Rolling Shutter setting, None means the effect is disabled. Top-Bottom applies the rolling shutter effect from the top of the image to the bottom. Rolling Shutter Duration determines the balance between pure rolling shutter and pure motion blur: a value of 0 gives pure rolling shutter, while 1 gives pure motion blur. The manual does not define specific visual results for intermediate values, so they need to be tested in the project.

Shutter Curve uses a curve to define how the shutter opens and closes. The X axis represents time; on the Y axis, 0 means the shutter is fully closed and 1 means it is fully open. The default mapping is set so that opening and closing happen instantaneously. When adjusting the curve, understanding what the axes represent helps you make controlled changes to the timing.

4. Pre-render checklist and limitations

In scenes with particles or other physics systems, bake the simulations before rendering. The manual notes that motion blur may not produce correct or consistent results if the simulations have not been baked. It also states that camera motion blur does not work with Orthographic Cameras. Motion of lights in world space is not taken into account either; lights are treated as stationary during rendering. Moving lights along with the camera can therefore produce incorrect blur.

Choosing a render device is also part of the Cycles workflow. CPU supports all Cycles features. GPU Compute may be faster in many cases, but feature support can be limited by the backend in use. The manual says that some backends may allow GPU and CPU devices to be used at the same time, with the details depending on compatibility and limitations. OSL is supported only on the CPU or the OptiX GPU Compute backend; compiling and interpreting custom shaders can reduce performance.

Impact on architectural visualization workflows

In archviz sequences featuring a moving camera and animated elements, blur can change how motion between frames is perceived. The safest approach is to compare Position and Shutter options with low-cost test frames first, then verify the final settings in the production sequence. In static presentations, the effect is only relevant if the output includes motion.

When making hardware decisions, offices should consider more than the potential speed advantage of a GPU: they should also check that the selected Cycles backend supports the required features. Baking physics simulations, verifying the camera type, and assessing camera and light movement separately are all essential pre-render checks. The manual does not provide licensing or pricing information, so no conclusions can be drawn on those topics.