You record with a modern webcam, open the file, and the video is a square. Not 1920x1080, not 16:9, but exactly 1552x1552, with your framing cropped in ways you never chose. If this has happened to you, you have hit what we call the 1552x1552 trap.

We ran into it while building KeepTake, and it is one of those bugs that is not really a bug. Every component is behaving as documented. The result is still a ruined recording.

Where the square comes from

The trap comes from Center Stage, Apple’s auto-framing feature. Center Stage keeps you centered by cropping and panning within a larger sensor image. To pan both horizontally and vertically without running out of pixels, the camera exposes a native square capture mode, and on a popular class of devices that mode is 1552x1552.

You will see it on iPhones used as webcams via Continuity Camera, on Studio Display’s built-in camera, and on other Center Stage-capable hardware. The square is not a glitch; it is the canvas Center Stage pans around in.

Here is the trap: when an application opens the camera without explicitly requesting a format, the system hands it the camera’s default, and on these devices the default is the square mode. The app dutifully records exactly what it was given. Nothing errors, nothing warns. You find out when you watch the file.

Why so many apps fall into it

Opening a camera “the easy way” is genuinely easy: ask for the device, start reading frames. Requesting a specific format is more work: you have to enumerate the device’s supported modes, present them somewhere, handle the mode not being available, and remember the choice.

So a lot of software, including simple recorder apps and plenty of code built on capture libraries, skips it. ffmpeg’s avfoundation input, for example, records the square mode on these cameras unless you explicitly pass a video size the device supports. Browser-based recorders add their own layer: they request a resolution as a “constraint”, and the browser is allowed to satisfy it approximately, which can mean cropping or scaling the square feed rather than switching the camera’s real mode.

Video conferencing apps mostly hide the problem, because they crop to 16:9 for their own layouts. That is also why the trap surprises people: the same camera looks normal in every meeting, then records a square in a recorder.

Why you cannot fully fix it in post

You can crop a 1552x1552 recording to 1552x873 and get a 16:9 frame. But you did not compose your shot for that crop, so headroom and framing are off. You have thrown away almost half the pixels you recorded. And if Center Stage was actively panning during the take, the framing moves around inside the square in ways a static crop cannot follow.

The only real fix is recording the right mode in the first place.

The fix: an explicit resolution picker

The camera knows exactly which modes it supports. The fix is software that asks, then tells you.

KeepTake enumerates every format the selected camera actually offers, native 16:9 modes included, and shows them in a plain resolution picker. You see what the camera will really record before you hit record, and your choice is remembered per camera. No silent defaults, no square surprises.

While we were at it, we added optional CAS sharpening (contrast-adaptive sharpening) at record time, because many webcam feeds are slightly soft at their native modes and a gentle, detail-aware sharpen makes talking-head footage noticeably crisper without the halo artifacts of naive sharpening. It is off by default; honest defaults matter more than flashy ones.

Checking your own setup

Before your next important recording:

  1. Record 10 seconds with your normal tool and camera.
  2. Open the file and check its actual dimensions (in QuickTime: Window, then Show Movie Inspector).
  3. If you see 1552x1552 or any unexpected square or crop, your tool is taking the camera’s default mode.
  4. Look for a resolution setting in the tool, and set it explicitly to the mode you want.
  5. If the tool has no resolution setting, it will keep making this decision for you.

Note that turning Center Stage off in Control Center changes the framing behavior, but does not reliably change which pixel format an app receives if the app never asks for one. The setting you need lives in the recording software, or it does not exist.

The pattern behind the trap

The square-video trap is one instance of a broader pattern we keep running into: recording defaults chosen for convenience quietly override what the user meant. The iPhone Continuity microphone hijacking the default input is the same story with audio. Silent format decisions are the video-quality version of the format tradeoffs most tools never surface at all.

A recorder’s job is to capture what you meant, and you cannot mean 1552x1552 if nothing ever told you it was happening. That is the standard we hold KeepTake to: every consequential capture decision, resolution, format, and microphone, is visible and yours.