Motion Blur for Screen Recordings: Fixing Choppy Zooms and Pans
Zoom transitions looking stepped instead of smooth? What motion blur does, where its Strength, Shutter Angle, and Quality controls live, and how to tune them.
You added a zoom to highlight a button, exported the video, and the push toward it does not glide — it arrives in visible steps, like a slideshow of three or four intermediate sizes. Nothing is broken, and the fix is not a faster computer or a higher export resolution.
That stepping is what unblurred fast motion looks like at a fixed frame rate. Real cameras do not have the problem because a shutter stays open for a fraction of each frame and smears whatever moved during that window. Screen recording has no shutter — every frame is a perfectly crisp snapshot — so fast synthetic movement has to be blurred deliberately. That is exactly what Recorded’s motion blur does, and it is already on by default.
Here is what it actually affects, where its controls are, and how to get smooth camera moves without turning your UI into mush.
The Camera Moves, Not the Screen
The important distinction first, because it decides what motion blur can and cannot do for you.
A screen recording contains two completely different kinds of movement:
- Content motion — what the application did while you recorded. A menu sliding open, a page scrolling, a video playing in a browser tab. This was sampled by the capture pipeline and is already baked into the frames.
- Camera motion — what the editor adds afterwards. Zoom pushes and pulls, the pan that follows a zoom target across the frame, and the webcam overlay moving or resizing during a transition. None of this existed while you recorded; it is generated at render time.
Motion blur in Recorded applies to the camera, not to the content. It blurs the zoom and pan move itself, plus webcam overlay transitions. It will not smooth a jerky scroll you recorded, and it will not rescue a 120-millisecond hover animation that the capture only caught three frames of. Those are recording-technique problems, and the guide on recording on a 120Hz or 144Hz display covers why the screen itself samples the way it does.
The upside of camera motion being synthetic is that it has far more frames to work with. MP4 export renders at 60 fps regardless of the capture rate, so a one-second zoom is drawn across roughly sixty positions. That is already smooth. The stepping shows up when the move is fast enough that consecutive positions sit far apart.
Why Fast Zooms Step
Take a zoom from 1x to 2.5x that eases in over 0.3 seconds. At 60 fps that is about eighteen frames to cover the entire magnification change. Each frame jumps the scale noticeably, and every one of those frames is razor sharp. Your eye receives a sequence of distinct, crisp, differently-sized images rather than a continuous move, and reads it as a strobe.
Slow the same zoom to a full second and it covers sixty frames instead of eighteen. The per-frame jump shrinks to a third, and the strobing mostly disappears on its own. This is the first thing worth knowing: blur is a finishing touch on reasonable motion, not a repair for motion that is too fast.
Where the Controls Are
Motion blur lives in the editor’s right-hand panel under the Advanced tab (the wind icon). Open a recording, open the tab, and you get a single card with a toggle and three sliders.
| Control | Range | Default | What it does |
|---|---|---|---|
| Motion Blur | On / Off | On | Master toggle |
| Strength | 1%–100% | 15% | How much the moving frame smears |
| Shutter Angle | 36°–360° | 72° | How long the virtual shutter stays open per frame |
| Quality | 4–16 samples | 6 | How many samples make up the blur trail |
Two things to understand about these numbers.
Strength and Shutter Angle multiply. The blur amount is derived from the camera’s velocity scaled by both values together, so raising each from its default to double does not double the blur — it quadruples it. If a setting looks heavy-handed, pull one of the two back rather than both.
Blur only exists while the camera is moving. The renderer measures how fast the zoom scale and pan offset are changing between frames, and if that velocity is below a small threshold it skips blur entirely. A static shot, a zoom that has finished and is holding on its target, a section with no zoom at all — all of those render exactly as sharp as they would with motion blur turned off. You are not trading overall sharpness for smoother transitions.
The two kinds of camera move are also blurred differently by design. Zoom produces a radial smear outward from the zoom target, the way a real lens does when you rack a zoom ring. Pan produces a directional smear along the travel direction, and it is capped much lower than the zoom blur — panning is usually a supporting move, and smearing it as hard as a zoom push looks wrong.
Settings That Actually Work
The defaults are deliberately conservative. Start there, and only move if you have a reason.
Default (15% / 72° / 6 samples). Close to a real camera’s 1/48-second shutter at 24 fps. Smooths zoom pushes enough that they read as camera work, with no visible smear once the move settles. Right for tutorials, support replies, and documentation where someone may pause mid-zoom and expect to read the screen.
Subtle (8% / 72° / 4 samples). For dense interfaces — IDEs, spreadsheets, dashboards with small type. You still get the softening but the text behind it survives a pause better.
Cinematic (35% / 144° / 10 samples). For marketing clips, launch videos, and anything with fast deliberate pushes between two points of interest. Pairs well with a shorter ease-in, because the blur covers the per-frame jump the speed creates.
Off. Genuinely the right answer sometimes. Turn it off for GIF exports, which run at 10, 15, or 24 fps — at those rates each frame is on screen long enough that a smear stops reading as motion and starts reading as a defect. Also turn it off when you need every frame to be a usable screenshot, or when you are building a thumbnail from a frame inside a zoom.
Raising Quality does not change how much blur you get, only how smoothly the trail is built. Four samples on a long smear can show faint banding; ten or twelve render the same smear cleanly. Each extra sample is more GPU work on every frame of the export, which is one of the reasons exports with heavy effects take longer — why video exports take so long breaks down where that time goes. There is no benefit to 16 samples on a 10% smear.
Fix the Move Before You Touch the Blur
If a zoom still looks wrong at the defaults, the problem is almost always the move. Those controls are in the Zoom tab, on the selected zoom:
- Level runs from 1x to 4x. A 3.5x push covers far more scale change per frame than a 1.8x one. Most product UI only needs 1.5x–2x to be legible, and the restraint buys you smoothness for free.
- Ease In and Ease Out durations run from 0.1 to 2 seconds each. Anything at or below 0.2 seconds is a cut, not a move, and no amount of blur makes it feel otherwise. Around 0.6–1 second is the comfortable range for a push you want viewers to follow.
- Easing type changes how the velocity is distributed.
Ease OutandEase Out Circspend most of their speed early and settle gently, which is the most forgiving shape.Ease Out Expois more aggressive at the start, so it benefits more from blur.Ease In Out Circis symmetric and reads as the most deliberate.
The pairing that produces the stepping complaint is a high zoom level with a short ease duration and an aggressive easing curve. Lengthen the ease first, then reconsider the level, and only then raise the blur. The guide to mastering zoom effects goes deeper on where to place zooms and how long to hold them.
Speed changes interact here too. If you sped a segment up in the Segment tab, any zoom living inside it now covers its scale change in proportionally less time, so a zoom that looked fine at 1x can strobe at 3x. Check your zooms after a speed change, not before.
It Also Covers the Webcam Overlay
The same settings drive webcam overlay motion. When your camera picture-in-picture animates in, animates out, or moves and resizes during a transition, the renderer builds a short trail of fading ghost frames behind it rather than snapping it between positions. The trail length is derived from the Quality and Shutter Angle values, and it fades out on its own once the overlay stops moving.
This matters most for layouts where the webcam travels a long distance — a corner-to-corner move, or a small bubble expanding to a large frame. Those are exactly the moves that look cheap without blur. If you use the overlay in a fixed corner for the whole video, this part never activates and costs you nothing.
When Blur Disappears on Its Own
Motion blur is rendered on the GPU through WebGL. If those calls fail repeatedly — some remote desktop sessions, software renderers, and GPU driver edge cases do this — the renderer stops trying and falls back to drawing frames directly, unblurred. The export still completes and still contains your zooms; they just render sharp.
So if you have blur switched on and the export clearly has none, do not keep raising Strength. Export a short test from the same project on a different machine, or check whether the editor’s preview is also unblurred. A whole project with no blur anywhere points at the hardware path, not at your settings.
A Quick Checklist
[ ] Leave motion blur on — the 15% / 72° / 6 default suits most videos
[ ] Zoom level 1.5x–2x unless the UI genuinely needs more
[ ] Ease In / Ease Out at 0.6s or longer for zooms viewers should follow
[ ] Re-check zooms inside segments you sped up
[ ] Lower Strength (not Quality) for dense text interfaces
[ ] Turn blur off for GIF exports and for frames you plan to screenshot
[ ] Export 10 seconds containing your fastest move and watch it before committing
Motion blur is the kind of setting you tune once and forget. The defaults are already tuned for the most common case, and the real lever on smoothness is how fast you ask the camera to move. Get the ease durations right and the blur quietly does the rest.
New to the editor? Download Recorded and the Advanced tab is there on your first recording, blur already on.