Blender Cycles Motion Blur for Animation (2026): Shutter, Deformation Steps and Consistent Frames
Cycles renders true 3D motion blur from Render › Motion Blur: Position sets when the shutter opens relative to the frame and Shutter sets how long it stays open in frames. Each object also has Deformation blur and Steps; the Manual notes more steps use more memory. For frames rendered on several GPUs or machines, bake simulations first so every frame sees the same motion.
- Shutter: in frames; 1.0 blurs over one full frame.
- Position: Start, Center or End on Frame.
- Deformation: per object; Steps raise memory.
- Consistency: bake physics and particles before splitting frames.
Cycles motion blur is computed in the render, not faked afterwards, so it is accurate but adds render time and memory. It is also where a sequence split across GPUs most often shows a jump, when one frame sees different motion than its neighbour.
This guide covers the scene and object settings, what they cost, and the checks that keep motion blur consistent when frames are rendered in parallel.
Checked against the Blender Manual (Motion Blur, Object Settings), November 2026.
1. The scene settings: position and shutter
In Render › Motion Blur, Position controls at what point the shutter opens in relation to the current frame: Start on Frame, Center on Frame or End on Frame. Shutter is the time in frames between the shutter opening and closing; 1.0 blurs over the length of one frame (Blender Manual: Motion Blur). Rolling Shutter imitates CMOS cameras that read the sensor in scanlines, and Shutter Curve defines how the shutter opens and closes.
2. Object settings: deformation and steps
Each object has its own motion blur settings. Deformation enables blur for deforming meshes such as animated characters and hair. Steps controls the accuracy of deformation blur; the actual number of time steps is 2^(steps-1), and more steps use more memory (Blender Manual: Object Settings). The Manual also warns that a modifier setup that changes mesh topology over time cannot render deformation blur correctly, so disable deformation blur on such objects.
With few steps, Cycles blends straight between the stored positions, so a fast swing, such as a hand or a rotor, blurs along a chord instead of an arc. Raise Steps only on those objects; the table below sums up each setting and its cost.
Motion blur settings and their cost
Scene-level and object-level settings that change blur, render time and memory.
| Setting | Where | Effect |
|---|---|---|
| Position | Render › Motion Blur | When the shutter opens relative to the frame: Start, Center or End on Frame |
| Shutter | Render › Motion Blur | Time in frames the shutter is open; 1.0 blurs over one frame |
| Rolling Shutter | Render › Motion Blur | Top-Bottom scanline effect, like CMOS cameras; Duration blends it with normal blur |
| Shutter Curve | Render › Motion Blur | How the shutter opens and closes over time |
| Deformation | Object › Motion Blur | Blur for deforming meshes such as characters and hair |
| Steps | Object › Motion Blur | Accuracy of deformation blur; actual time steps are 2^(steps-1), more steps use more memory |
3. Render time and memory
Motion blur stores positions at several times within the shutter, so long shutters and high step counts add memory on every GPU and usually lengthen render time. Volumes need a velocity grid for blur, covered in our guide to Cycles volumes and OpenVDB. Test the frame with the fastest motion, not an average one.
4. Consistent blur across GPUs and machines
When a sequence is split across GPUs, each Blender instance evaluates motion for its own frames. Bake particles and physics before rendering; an older Manual page recommends this to get correct and consistent motion (Blender 2.79 Manual: Motion Blur). Keep the same Blender version and file on every instance, and check the frames at the boundaries between instances. See multi-GPU rendering in Cycles for splitting frames.
Once the simulation is on disk, the frame a GPU renders depends only on the cache, not on which instance rendered the frames before it, so blur and motion match across the boundary.
A motion blur checklist before a long render
- Shutter: Position and Shutter set and the same for every shot that should match
- Simulations: particles, cloth and physics baked
- Deformation: enabled only where needed; disabled on topology-changing objects
- Steps: raised only on objects with fast curved motion
- Test: the fastest-motion frame rendered and memory checked
- Boundaries: frames where instances meet compared in playback
For paths, caches and other scene checks, see our 10-point Blender Cycles pre-flight checklist.
Both farm models render Cycles motion blur. On an IaaS server you bake simulations and test the fastest frame on the same GPUs that render the sequence, so what you check is what renders.
Rendering motion blur on an iRender server
- Upload the project with baked caches to iRender Drive before you start the server; uploading is free and does not use rental time.
- Start a server with RTX 5090 (32 GB) or RTX 4090 (24 GB) GPUs and connect by remote desktop.
- Render the fastest-motion frame and check blur and memory.
- Render the sequence one Blender per GPU, then shut down; multi-GPU servers are billed per minute.
Frequently asked questions
1. What shutter value should I use in Blender?
Shutter is in frames: 1.0 blurs over a full frame and smaller values give shorter blur. Match it to the look of any live-action plates in the shot.
2. What do Start, Center and End on Frame mean?
They set when the shutter opens relative to the current frame: starting at it, centred on it, or closing at it.
3. Why does deformation blur use so much memory?
Steps store extra positions; the actual number of time steps is 2^(steps-1), and more steps use more memory.
4. Why is motion blur wrong on an object with modifiers?
The Manual warns that modifiers that change mesh topology over time cannot render deformation blur correctly. Disable deformation blur on that object.
5. Why does blur jump between frames from different GPUs?
Usually unbaked simulations or different settings per instance. Bake physics and keep one file and Blender version.
Render your Blender projects on iRender
iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 (24 GB) or RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. You install Blender once; your server image is saved between sessions, so Blender and your add-ons stay installed.
Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU and 8-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.
This quick start shows how to start a server and render Blender on it:
Two Blender runs we recorded on our servers: 120 frames at 1080p on 4x RTX 5090 at 72 seconds per frame, and the same 4K scene on 4x RTX 5090 and 4x RTX 4090 at 87 and 108 seconds per frame per GPU:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Blender render farm page or download the iRender GPU app.




