Auto zoom in screen recordings: how to check and fix it

Auto zoom in screen recorders such as Screen Studio, Cap and FocuSee reads a recording’s input log (usually the mouse clicks, sometimes the cursor path or typing) and places a zoom that eases in just before each click, holds, and eases back out. It follows the log, not what changed on screen, so it goes wrong in three predictable ways: a click where nothing happens gets a zoom, an action with no click gets none, and a zoom fixed on a click frames a drag where it started instead of where it lands.

So don’t judge auto zoom by watching the video through once. Check each zoom against a list of the moments that matter, which takes a few minutes and works in any recorder. The method is first; after it, one real recording of Ellie, the planner I build, cut with auto zoom on, off and corrected, shows each failure. Those cuts were made with Moonjar, our product (a Mac app in early access), on Ellie’s demo data.

1. Write down the moments that matter before you look at any zoom: each change the viewer has to see, with its time.

2. Delete zooms on nothing. For each zoom, name what changes on screen while it’s in. No answer, no zoom.

3. Add zooms the log missed. Any moment from step 1 without a zoom gets a manual one.

4. Aim at the result. Put the zoom’s center on where the change ends up (the drop target, the new row, the field being filled in), not where the pointer was.

5. Time it to the change. Start about half a second before it, stay until the result can be read, then leave. One zoom per idea.

6. Keep enough context. Around 1.5 to 2 times reads well for a window. If the viewer loses the column a card came from, the zoom is too deep.

7. Leave it wide when the layout is the point. A change that spans the whole window reads better without a zoom. Delete that zoom, or turn auto zoom off for the recording if your recorder allows it.

A zoom log makes steps 1 to 4 quick. Copy this and fill in one row per moment:

The rows above are the log for the recording below. Then go through the recorder’s zooms: any zoom that isn’t on a row gets deleted.

The take is 21.9 seconds of Ellie for Mac’s Kanban view on demo data, recorded as a window by Claude Code on September 16, 2026. Cards move three times. The agent sent its input to the app without moving the Mac’s pointer, so the recorder logged five clicks and all five sit where the pointer was parked, in the empty space at the bottom of the Wed column, for the first 15 seconds. Auto zoom turned those five clicks into two zooms:

Auto zoom followed its rules exactly. One zoom lands on nothing, two moves get no zoom, and the one that covers a move is centered below it. A take driven with a visible pointer (by hand, or by an agent whose computer use moves the real pointer) would put the clicks on the cards, which makes the first two problems less likely. The third would stay, because a drag’s click is where the drag starts. Those are the three ways a zoom misleads, and each has a fix.

The two clips on this page play the whole take twice: first with the automatic zooms, then corrected. In the corrected cut the first zoom is gone, two zooms were added on the moves, and the last one was re-aimed at a fixed point on the card’s path; it holds that point rather than tracking the card.

It zooms in on nothing

Auto zoom on, 1 second into the take: the first zoom frames the empty space below the Wed tasks, where the first logged click sits, and nothing on screen has changed. Made with Moonjar from an Ellie for Mac recording on demo data, September 18, 2026. Background photo: Bernd Dittrich on Unsplash.

A zoom tells the viewer “look here, something is about to happen.” The click at 0.1 seconds did nothing visible, so the first zoom promises an action and then pulls back out two seconds before the first card moves. A click that only focuses a window or lands between two controls does the same.

The fix is to delete the zoom (step 2).

It misses the action

Before (top): the auto-zoomed cut at 4.3 seconds is zoomed out while Research a standing desk moves into Wed, because no click was logged there. After (bottom): the same moment with a zoom added on the move. Made with Moonjar from Ellie for Mac demo data, September 18, 2026. Background photo: Bernd Dittrich on Unsplash.

The first two moves happened without a logged click, so the viewer sees them at full-window size, where the card that moves is one small card among about twenty. Anything that isn’t a click can slip through the same way:

• Keyboard shortcuts and typing. Screen Studio’s guide says that where “no mouse click occurs, it will not zoom to any area”, and in Moonjar’s rules typing with no click before it gets no zoom. FocuSee says its zooms follow typing too.

• Phone recordings. Screen Studio says it can’t record finger taps the way it records mouse clicks, so its iPhone and iPad recordings get no automatic zooms. Recording the iOS Simulator with a tool that logs taps gets around this; see how to record the Simulator with taps showing.

• Imported videos. Cap’s docs note that imported MP4s don’t gain click data, so there is nothing to generate zooms from.

• Menus in a window recording. A window capture doesn’t include the menu a click opens, so a zoom on a menu pick shows no menu, and the change the pick made needs a zoom of its own.

The fix is step 3: add a zoom by hand wherever a moment from your list has none. The corrected cut adds one at 3.2 to 6.0 seconds for the first move and one at 9.5 to 12.0 seconds for the second.

It aims at the click, not at what changed

The same moment, 16.3 seconds in, three ways. Top: auto zoom off. Middle: auto zoom on, centered near the logged clicks, so the lower part of the frame is empty list and the window’s edge. Bottom: corrected, centered on the card’s path from Wed to Thu. Made with Moonjar from Ellie for Mac demo data, September 18, 2026. Background photo: Bernd Dittrich on Unsplash.

The second zoom does cover the drag, and it is far easier to read than the unzoomed frame. But it is centered near the logged clicks, below the list, so the lower part of the frame shows empty list, the window’s edge and the backdrop, and the card ends up toward the right of the frame. A zoom fixed on the click has this problem with any drag, even when the pointer is exactly where it should be: the click is where the drag starts, and the viewer cares about where it ends.

The fix is step 4: re-aim the zoom at where the change ends up. In the corrected cut, the second zoom’s center moved from 29% across and 92% down the window to 43% across and 72% down, the middle of the card’s path, and its span was cut from 6.3 seconds to 3.2 so it leaves once the card has landed.

Two more cases aim a zoom wrong:

• Clicks near an edge. When the window sits on a background, a click near the window’s edge pulls the zoom toward it, so part of the zoomed frame is window border and backdrop, as in the middle frame above.

• A blurred edge band. If the video fades the app into the background at the top or bottom, a zoom toward that edge pulls the content you want into the blur. Check the zoomed frames, not just the timeline.

The pointer can mislead in the same way, since it too comes from the log. If yours sits on the wrong thing or wanders, the cursor guide covers hiding, smoothing and moving it.

None of the recorders’ pages gives its exact rules, such as how close two clicks must be to share a zoom or how long a zoom holds. Moonjar’s are in its source, so here they are as one worked example:

1. Group nearby clicks. Clicks up to 1.5 seconds apart and within about 30% of the screen of each other share one zoom.

2. Arrive early. The zoom starts 0.75 seconds before the first click (a 0.6-second ease plus a 0.15-second lead), so it is fully in just before the click lands.

3. Hold, then leave. It holds for 1.4 seconds after the last click, then eases out over 0.6 seconds.

4. Follow typing. Typing within 2.5 seconds of a click keeps the zoom on that field. Typing with no click nearby gets no zoom.

5. Let go for scrolling. A scroll or swipe soon after a click ends that zoom early, and a scroll never starts one, because scrolling while zoomed in is hard to follow.

6. Tidy the neighbors. Two overlapping zooms on nearly the same spot merge into one. Two on different spots meet end to start, so the camera pans. Anything shorter than a second is dropped.

7. Zoom 1.8 times by default. Moonjar’s tool description calls 1.5 to 2 natural.

Every one of those rules works on the log. None of them can tell whether the click did anything, which is why the check above is needed whichever recorder you use.

These four Mac recorders document an automatic zoom, read from each vendor’s own pages on September 18 and rechecked September 19, 2026. None was installed or tested for this article, so this is what their docs say, not what they did.

Screen Studio

• What it zooms on: clicks. A zoom can be set to Auto (toward your clicks) or Manual (you move a purple dot to the area).

• Fixing zooms: click the zoom timeline to add one, drag a zoom’s edges to retime it, set its level, and right-click to disable or remove one (Screen Studio’s guide to adding and editing zooms). Turning off “Create zooms automatically” in its recording settings stops automatic zooms.

• Limits: no automatic zooms on iPhone and iPad recordings.

• Cost: a subscription. You can use it without an active plan, but exporting video files requires a plan, so you can check its zooms on your own take first.

CleanShot X

• What it zooms on: the cursor. Smart zooms “follow your cursor” in Studio Mode, which arrived in version 5.0 on September 1, 2026. Its pages don’t say whether zooms are placed on clicks.

• Fixing zooms: its FAQ says Studio Mode lets you “add animated zooms to specific parts of your screen recording”. No page describes changing where an automatic zoom points.

• Cost: a one-time license with a year of updates, or a Pro subscription; both list the video editor with smart zooms. An existing one-time license gets Studio Mode only if its updates cover version 5.0.

Cap

• What it zooms on: clicks. In Studio Mode, you generate zoom segments from the clicks Cap recorded, and each one’s focal point follows the recorded action.

• Fixing zooms: click or drag on the Zoom track to add a segment, set the amount from 1x to 4.5x, and switch a segment to Manual to pick its exact focal point (Cap’s Studio Mode docs).

• Limits: no automatic zooms for imported videos, which carry no click data.

• Cost: the Studio Mode editor is on every plan, the free one included, but the free plan is for personal use; commercial use needs a paid license.

FocuSee

• What it zooms on: click areas, with zooms generated after recording; its homepage adds typing.

• Fixing zooms: its auto zoom page describes adjusting zoom timing and position in the editor, or turning zooms off for parts of the video or all of it (FocuSee’s auto zoom page).

• Cost: paid plans, all with auto zoom, yearly or once; the free trial exports one video. It runs on Windows and Mac.

Current prices for all four, and what each lets you try before paying, are compared in Screen Studio alternatives, and three of them go head to head in Screen Studio vs Cap and Screen Studio vs CleanShot X.

If what you record is a web page, Chrome extensions do this too. Cursorful’s Chrome Web Store listing describes “automatic zooms and pans based on clicks”, and Zumie zooms automatically on browser-tab recordings only; for a screen or window recording its zooms are manual.

Moonjar is a Mac app that Claude Code, Codex and other agents drive over MCP, in early access with no published price. Its timeline isn’t dragged by hand: you ask your coding agent, and the app shows the result.

The corrected cut on this page is the auto-zoomed one, duplicated and then fixed with four edits, one per row of the zoom log:

• delete {label:'Z1'} removes the zoom on nothing.

• add_zoom {start:3.2, end:6, focus:{x:0.25, y:0.62}} adds one on the first move.

• add_zoom {start:9.5, end:12, scale:1.6, focus:{x:0.31, y:0.58}} adds one on the second, a little wider because that card crosses two columns.

• update {label:'Z2', set:{focus:{x:0.43, y:0.72}, start:15.2, end:18.4}} re-aims and shortens the last one.

Every reply lists each zoom with its time span, level and center, and returns frames from the edited moments, so a zoom aimed at the wrong place shows up before the video is rendered. Claude Code video editing walks through a whole cut made this way, from dead-time cuts to the render. If you’d rather your agent cut your demos, ask for early access.

Zooms are one pass of editing a demo. For the rest (choosing the moments, cutting the waits, captions and export), see how to make an app demo video.

The images were made with Moonjar, our product, from one Ellie for Mac recording on demo data (made September 16, 2026), cut, corrected and rendered on September 18, 2026. Frames were pulled from the renders and labeled with ffmpeg. The background photo behind the window, also on the cover, is by Bernd Dittrich on Unsplash. Moonjar’s rules were read from its source code on September 19, 2026. The other apps are described from their own pages, read on September 18 and rechecked September 19, 2026. This page was drafted with AI assistance.