Recording a 3D modelling session without tanking your viewport framerate — interval settings for modelling, sculpting and rendering, and what to skip.
3D work is close to the ideal timelapse subject. Sessions are long, the change is dramatic and visual, and a blank viewport turning into a finished model is genuinely satisfying to watch in 40 seconds.
The complication is that 3D work is also the one case where recording can actively hurt you. Blender wants your GPU, and so does a screen recorder. Get that wrong and you're modelling at 12fps to produce a video of yourself struggling.
Why normal screen recorders hurt here
A standard recorder captures 30 or 60 frames every second and encodes each one. That's continuous GPU and CPU work running alongside an application that already wants all of it. In a viewport-heavy sculpt you'll feel it immediately.
Interval capture doesn't have this problem in the same way. Grabbing one frame every 3 seconds is roughly 1% of the work of grabbing 30 every second, and between frames the recorder is idle. Your GPU goes back to Blender.
This is the practical argument for recording 3D work as a timelapse rather than recording normally and speeding it up afterwards — the speed-up approach makes you pay the full cost during the session, when you can least afford it.
Interval by activity
3D sessions aren't uniform. What you're doing changes what interval makes sense:
| Activity | Interval | Why |
|---|---|---|
| Blocking / base mesh | 2 s | Shape changes fast, worth catching |
| Detailed sculpting | 3–5 s | Slower, incremental change |
| Retopology | 5 s | Methodical, very repetitive |
| UV unwrapping | 5–8 s | Long stretches of little visible change |
| Texturing / shading | 3 s | Look develops in visible steps |
| Rigging | 8 s | Mostly panel work, low visual change |
| Rendering | 15 s+ | Nothing to see but a progress bar |
If you're doing all of it in one sitting, 3–5 seconds is a reasonable compromise across the whole session. You'll over-sample the slow parts and under-sample the blocking, which is the right way round — nobody minds a slightly long retopology section, and everybody notices when the model jumps from cube to finished head.
For a target video length rather than a rule of thumb, the frame interval calculator works backwards from what you want.
Recording just the viewport
You almost certainly don't want your whole screen.
Blender's UI is dense — outliner, properties, timeline, shader nodes. At the size a timelapse gets watched, all of that is illegible noise around the part people care about. Recording a region containing the viewport gives you a cleaner video and a smaller file.
The exception is node-based work. If the point of the video is showing a shader coming together, the node editor is the content, and you should frame that instead.
Two practical notes: put Blender in fullscreen before you set the region, so nothing shifts mid-session, and turn off any overlays you don't want permanently baked into the footage — the 3D cursor, stats, gizmos. You can't remove them afterwards.
Skip the render
The most common mistake is leaving the recording running through a final render.
A 40 minute render produces 40 minutes of a progress bar. At a 3 second interval that's 800 frames of almost nothing, which at 30fps is 27 seconds of your finished video spent watching a number climb. It'll be the most boring part of the timelapse by a wide margin.
Either stop the recording before you render and start a new one, or set a much longer interval for that stretch. What people actually want at the end is the final render itself, held for a couple of seconds — not the process of producing it.
Add a timer
3D work benefits from this more than most, because the effort is the story. A model that took 14 hours and one that took 40 minutes look similar in a 40 second video; the timer is what separates them.
Elapsed time in a corner, monospace font so the digits don't jitter. More on the options in how to add a timer overlay.
Settings summary
For a typical modelling session:
- Interval: 3 seconds
- Frame rate: 30fps
- Region: viewport only, Blender fullscreen
- Overlay: elapsed time, bottom right
- Render: stop recording, or switch to a 15s+ interval
- Export: MP4 for YouTube, WebM if it's going on your own site
A 4 hour session at those settings gives you about 4,800 frames and a 2 minute 40 video. If that's too long — and for most platforms it is — either raise the interval to 6 seconds or trim in the editor afterwards.
One thing that isn't about settings
Watching your own sessions back is a surprisingly good way to notice how much time goes into things you didn't think were taking time. In my case it was fiddling with the same set of options repeatedly before committing to anything. You don't see that while you're doing it; you see it immediately at 180x.
That's a separate benefit from making something worth posting, and honestly the one I'd defend more strongly.