Motion blur that follows the speed
The shutter scales with the local speed, so blur shrinks as time slows, like footage from a high-speed camera.
Render the frames between your frames.
Slow any stretch of your timeline to 0.001× and render true sub-frames. Your keyframes and caches never move.
Buy on SuperHive$14.99 until 21 October, then $19.99$19.99
TimeShift off and on.
The same scene rendered normally (left) and with a slowed chunk (right), the Timeline underneath.
Same scene, same Timeline. On the right, a chunk slows to 0.07× and eases back out to normal speed.
On the right, the slowed chunk renders the frames in between, so the wobble stays smooth instead of stepping.
Easier than retiming your keyframes.
Other ways to slow a shot edit the scene so Blender plays it back slower. TimeShift leaves the scene alone and renders the moments in between.
| Retiming keyframes | Scene-speed drivers | TimeShift | |
|---|---|---|---|
| Your animation | Keys moved, or copied into a new action | Driven by drivers the add-on adds | Never edited. Only the render times change. |
| What slows down | The selected object's keyframes | The animations and simulations you pick | The whole scene at once, camera included |
| Setup | Bake each object and section | Scan the scene, pick elements, set base speeds | Mark the moment and set a speed |
| Physics | Not slowed | Speed set per simulation | Bake once, then change speeds freely |
Try a speed ramp.
This is TimeShift's own retime math. Each tick is one rendered frame; they bunch where the chunk slows time.
Scene frames60
Rendered frames215
Length at 24 fps9.0 s
Slowest speed0.096×
How it works in Blender
Everything that moves slows down with it.
Keyframes, drivers, procedural Geometry Nodes and shaders are exact. Physics plays from the bake.
Rigid bodyFrom bake ClothFrom bake Hair dynamicsFrom bake Geometry NodesExact ShadersExact Characters and camerasExact
Built for the render, not just the viewport
Exact for shaders and node trees
Sub-frame time reaches drivers, procedural Geometry Nodes and materials.
Your file stays as it was
Nothing is moved or rescaled, and render settings are restored after every run.
Outputs
PNGJPEGOpenEXRTIFFEXR passesFrame map
Beauty images include your compositor and view transform.
Works where you work
- Blender 4.2 and newer
- Cycles and EEVEE
- Extension or legacy add-on
Questions
Does TimeShift change my keyframes or animation?
No. It only changes the times it renders at. Keyframes, NLA strips, drivers, camera markers and caches are never edited, and the render settings it changes are restored afterwards.
How is this different from Blender's Time Stretching?
Time Stretching (Output > Frame Range) applies one ratio to the whole scene. TimeShift slows or speeds only the chunks you mark, ramps in and out of them, and leaves the scene settings alone. If both are active, their speeds multiply.
Does it work with Cycles and EEVEE?
Yes, both. With Cycles, Persistent Data is enabled for the render to speed it up, then restored.
Do I have to bake anything?
Only physics. Keyframes, drivers, procedural Geometry Nodes and shaders are sub-frame exact with no bake. Rigid body, cloth, soft body, particles, hair and dynamic paint need one click of Bake All Dynamics.
Why does my fluid or smoke stutter in slow motion?
Mantaflow caches hold whole frames and Blender does not interpolate them, so there is nothing to sample between frames.
How much longer will my render take?
Render time grows with the number of output frames: a 20-frame chunk at 0.1 becomes about 200 frames. Check the estimate under the panel, and use Preview TimeShift to judge the timing first.
What's new
Preview fixes
- Play in Blender plays every preview frame
- Save MP4 also plays in Blender’s player
- Preview Output in the sidebar panels
TimeShift
GPL-3.0-or-later$14.99$19.99Launch price until 21 October$19.99
- The add-on for Blender 4.2 and newer
- Updates through SuperHive