Recording on a 120Hz or 144Hz Display: Why Smooth Screens Record Differently
Your 120Hz or 144Hz screen looks smoother than your recordings do. Here is how display refresh, capture rate, cursor sampling, and export frame rate interact.
You bought the 144Hz monitor, or you have a MacBook Pro with a ProMotion panel, and everything on screen glides. Then you record a walkthrough, watch it back, and the glide is gone. Windows snap instead of sliding. A quick cursor flick across the screen lands somewhere in the middle of the frame with no visible travel.
Nothing is broken. A high-refresh display and a screen recording are two different clocks running at two different speeds, and almost every “my recording isn’t as smooth as my screen” question comes down to that. Here is what each clock does, which ones you can influence, and how to record motion that survives the handoff.
Refresh Rate and Capture Rate Are Not the Same Thing
Refresh rate is how often your panel redraws what the GPU hands it: 60, 120, or 144 times per second. It is a property of your hardware and your display settings, and it only affects what you see while you work.
Capture rate is how often the recorder samples the screen. Recorded captures screen frames at 30 fps, and that number does not change when your panel runs at 144Hz. Your display refreshing more often does not give the recorder more frames to save — it just means more of the frames your GPU drew were never sampled.
So a 144Hz panel and a 60Hz panel produce exactly the same recording of exactly the same actions. What differs is your expectation. You spent the session watching 144 updates per second and your recording keeps 30 of them. The footage is not worse than it should be; your reference point was unusually good.
This is also why chasing display settings is the wrong fix. If your recordings are genuinely stuttering — uneven motion, frames that visibly repeat or skip, audio drifting away from the picture — that is a performance problem, not a refresh problem, and the causes are elsewhere: thermal throttling, a saturated disk, or an app competing for the GPU. The performance optimization guide walks through those.
Variable Refresh Rate Doesn’t Confuse the Recorder
ProMotion on Apple displays, and G-Sync or FreeSync on PC monitors, let the refresh rate float — dropping to a fraction of the maximum when the screen is static and ramping up during motion. People reasonably worry that a fluctuating panel means a fluctuating recording.
It doesn’t. Capture is scheduled on a clock of its own rather than locked to your panel’s vsync, so a panel that drifts between 10Hz and 120Hz while you read a page has no bearing on the cadence of the file being written. You do not need to pin your display to a fixed refresh rate before recording, and doing so will not make your footage smoother.
What variable refresh does change is your perception while recording. When the panel ramps up for an animation, you see every intermediate step. The recording samples a handful. That gap is worth remembering when you decide how fast to drive the UI.
The Cursor Is Sampled Separately — and More Often
Here is the part that surprises people. The cursor in your finished video is not the cursor that was burned into the screen frames. Recorded tracks cursor position on its own schedule, roughly 60 samples per second, stores that path alongside the video, and redraws the pointer during editing and export.
Two useful consequences:
Cursor motion is smoother than the screen underneath it. The pointer’s path is reconstructed from twice as many samples as there are screen frames, so even on footage where the UI snaps, the cursor itself travels cleanly.
You can change the cursor after the fact. In the editor’s Cursor tab you can swap the pointer style, scale its size up so it reads on a small player, and add a click animation. There is also a Cursor Smoothing control with Off, Low, Medium, and High settings, which smooths the recorded path — useful when a mouse flick or a shaky trackpad gesture produced a jagged line. The cursor highlight feature page covers what those options look like.
The flip side: because the pointer is redrawn rather than captured, a flick so fast that it crossed the screen in 80 milliseconds still only has about five samples behind it. Smoothing can round the corners of that path. It cannot invent the travel your viewer needed to see.
Export Renders at 60 FPS, Which Is Why Zooms Look Right
Recorded exports MP4 at 60 fps even though the underlying screen frames were captured at 30. That is not padding for its own sake — everything the editor adds on top is synthesized, and synthesized motion benefits from the extra frames:
- Zoom pushes and pulls, which are a virtual camera move over the footage
- Background, padding, and rounded-corner framing around the captured region
- The redrawn cursor and its click animations
- Text overlays and their transitions
All of that is generated at render time, so it gets the full 60 fps treatment regardless of how the screen itself was sampled. A zoom that eases in over a second is genuinely smooth in the export, sitting on top of UI frames that are not.
The Style tab’s Motion Blur toggle leans into this. With Strength and Shutter Angle controls, it blurs synthesized movement the way a camera shutter would, which makes zoom moves read as deliberate camera work instead of a sequence of discrete positions. See the motion blur feature page for how it is applied.
GIF export is the opposite situation: you pick 10, 15, or 24 fps, and at those rates motion is coarse by design. Treat GIFs as illustrations of a single action, not as a way to show fluid interaction.
Record Motion That Survives 30 FPS Sampling
Once you accept the clock mismatch, the practical fixes are all about how you drive the UI — and they make footage better on any display, high refresh or not.
Move the cursor deliberately and stop at the destination. A pointer that travels for 400 milliseconds and then rests for a beat gives the capture something like a dozen frames of travel plus a clear arrival. A flick gives it four frames and no arrival at all.
Let animations finish before you act again. Modal transitions, drawer slides, and tab switches are tuned to look good at your panel’s refresh rate. Give each one a full beat before the next click so the recording at least captures its start, middle, and end.
Don’t build a point around a hover micro-interaction. A tooltip that fades in over 120 milliseconds survives as three or four frames. If the hover state matters, hold it, and add a zoom or a text overlay so the viewer cannot miss it.
Scroll slowly, and prefer keyboard or scrollbar input over flicks. Momentum scrolling on a trackpad produces exactly the high-velocity motion that 30 fps sampling handles worst.
Use zoom instead of mouse travel to direct attention. A zoom push toward the relevant corner of the UI is rendered at 60 fps and reads beautifully. Dragging the cursor there to point at it does not.
Shoot a ten-second test. Record a short take with the fastest motion your video needs, export it, and watch it at the size your audience will. It takes two minutes and it tells you more than any setting page.
Multi-Monitor Setups with Mixed Refresh Rates
A 144Hz main monitor next to a 60Hz secondary is a very common desk setup, and it changes nothing about capture: monitor mode records one display, and that display’s panel refresh does not alter the result. Pick the screen your content lives on and record that one rather than capturing a wide dual-screen canvas that shrinks everything to illegibility. The multi-monitor guide goes through choosing and arranging displays before a take.
If your content genuinely spans two displays, window or area capture is usually the better answer — it keeps the recorded region at a size where text stays readable.
What to Check When Motion Still Looks Wrong
Work through these in order:
- Is it the whole clip or just the fast parts? Uneven motion everywhere points to performance. Motion that only breaks down during flicks and quick scrolls is the capture rate doing exactly what it does.
- Are you watching it at full size? A 1080p export played in a small window is being scaled by the player, which adds its own softness on top of everything else.
- Does the player match the file? Browser players and messaging apps resample video to their own cadence; judder that appears in a chat preview and vanishes in a desktop player is the preview’s doing.
- Did you re-drive the UI more slowly? This is the fix with the highest hit rate, and it costs one more take.
For a deeper look at what frame rate controls in a recording — and what it does not — see choosing the right frame rate. If you want to run the test takes above on your own machine, download Recorded for macOS or Windows and try a ten-second clip of the motion you care about most.