Recording Proper 4K Video on an iPhone: Settings, Storage, the Front Camera Question, and When 4K Is the Wrong Choice

Every iPhone sold in the last several years can record 4K video, and most creators have it switched on without ever having thought about what it is doing. The result is a lot of footage that is technically 4K and practically no better than 1080p: soft because the phone was focused on the wall, flickering because exposure kept hunting, and taking up four times the space for no visible gain. This post is the setup walkthrough for recording 4K that is actually worth the pixels, written for people who film themselves talking to the camera. It covers the settings, the trade-offs, and the honest cases where you should turn 4K off.

What 4K buys you, and what it does not

4K (3840 by 2160 pixels in landscape, the same count rotated in portrait) has four times the pixels of 1080p. For a talking-head video the benefit is rarely that viewers see more detail in your face; most of them watch on a phone, where the difference is invisible. The real benefits are three. You can crop: a 4K frame lets you punch in to a tighter shot in the edit and still deliver 1080p, which is the cheapest way to add a second camera angle you do not own. It survives compression better: platforms re-encode everything, and a sharper source comes out of that process looking cleaner. And it future-proofs the footage for a larger screen.

What 4K does not do is fix light, focus, stability or sound. A 4K clip of a badly lit face is a very detailed record of bad lighting. If you have not already worked through the basics of position, light and audio, the talking-head setup guide comes first; this post assumes that groundwork and adds the resolution layer on top.

The settings, in order

Open Settings, then Camera. The relevant screens are Record Video and Formats. Here is what to set and why.

• Record Video: 4K at 24, 25 or 30 fps. Choose by region and taste: 24 fps looks filmic, 25 fps matches European broadcast and avoids flicker under 50 Hz lighting, 30 fps matches most social platforms and North American lighting. Pick one and stay on it for every clip in a project; mixing frame rates in one edit causes stutter. Do not use 60 fps for a talking head unless you plan to slow footage down; it doubles the file size and makes the image look like a news broadcast.
• Formats: High Efficiency. This records HEVC (H.265), which is roughly half the size of H.264 for the same quality. The Settings screen prints an estimate next to each resolution and frame rate; on recent iPhones 4K at 30 fps in High Efficiency is listed at roughly 170 MB per minute, and 4K at 60 fps well over double that. Switch to Most Compatible only if an old editing application or a client's workflow genuinely cannot open HEVC, and switch back afterwards. Note that some combinations, such as 4K at 60 fps, are only available in High Efficiency on many models.
• HDR Video: off for talking heads. HDR looks superb on an iPhone screen and causes grief everywhere else: washed-out colours when uploaded, odd skin tones indoors, and mismatches when you mix it with non-HDR clips or graphics. Turn it on deliberately for scenery, not by default for faces.
• Lock Camera and Lock White Balance: on. Lock Camera stops the phone switching between its lenses mid-clip, which is a visible jump. Lock White Balance stops skin tones drifting as a cloud passes the window. Both are under Record Video on models that support them.
• Grid and Level: on. Not quality settings, but they are the difference between a straight horizon and a tilted one you only notice when it is too late to reshoot.

The front camera is fine; the eye line is what matters

Creators are regularly told to use the rear camera because it is better. It is better, on paper: larger sensor, better lens, more light. In practice the trade is the other way round for a talking-head video. Using the rear camera means you cannot see the framing, cannot see the script, and cannot tell when your head has drifted out of shot until you check the clip afterwards. The front camera on any iPhone from the last few years records 4K at 24, 25 and 30 fps, and in the light you should be using anyway, a window or a soft panel, the quality difference between the two cameras is far smaller than the difference between a clip where you are looking at the lens and one where you are not.

That eye line is the whole reason a camera-overlay teleprompter exists. Teleprompter: Camera Overlay floats the script over the front-camera preview, next to the lens, so reading and looking at the camera are the same movement; it records portrait 4K through that same preview, and the script never appears in the saved video. If you have been avoiding the front camera for quality reasons, try one clip each way at 4K in good light and compare them on a laptop screen. Most people stop worrying about it. The earlier post on keeping eye contact with the camera covers the habit side of this.

Focus and exposure: the two things 4K makes more visible

At 1080p, slightly soft focus hides. At 4K it does not. Before every recording, tap on your face in the preview to set focus and exposure there, then press and hold until you see the AE/AF Lock label, so the camera stops reconsidering every time you move. If the app you are recording in does not expose that control, keep still and keep the light steady; autofocus on iPhones is good, but it is also keen, and a hand gesture that passes the lens can pull focus to your fingers for half a second.

Exposure flicker is the other 4K-visible fault. It comes from light that changes, usually a window with moving cloud or a lamp on a slightly flickering dimmer, and from the phone adapting to it. Lock exposure, close the curtain and use a lamp on a stable supply, and the problem disappears. If your face is too dark against a bright window, move so the window is in front of you rather than behind you; no resolution setting fixes backlighting.

Storage: the practical arithmetic

At roughly 170 MB per minute for 4K at 30 fps in HEVC, a one-hour batch-recording session of takes and retakes is around 10 GB. That is manageable on a 256 GB phone and painful on a 64 GB one. Three habits help. Review takes immediately and delete the bad ones while you still remember which they were. Offload finished takes to a computer or external drive at the end of each session rather than letting them pile up for a month. And if you are the kind of creator who records a week of content in one sitting, check free space before you start; a multi-take session like the one described in the voiceover and podcast post depends on not running out halfway through take fourteen.

If space is tight, 4K at 24 fps uses noticeably less than 30 fps, and 1080p at 30 fps uses less than half of either. Dropping to 1080p for throwaway content and keeping 4K for anything you might crop or reuse is a sensible policy.

When 4K is the wrong choice

• Low light. The phone compensates by raising ISO, and at 4K the noise is clearer, not hidden. A well-lit 1080p clip beats a noisy 4K one every time.
• Long recordings on an older phone. Extended 4K sessions warm the phone and can trigger throttling or a recording stop; 1080p is cooler and safer for a forty-minute lecture.
• Content that is only ever a 60-second vertical clip. If you will never crop and the platform will downscale anyway, 1080p saves space and upload time with no visible loss. The 60-second script post is where this kind of content lives.
• Editing on a laptop that struggles. 4K HEVC timelines are heavy. If your editor stutters, either record 1080p or create proxies; do not fight the machine.
• When the goal is the first take, not the best take. Resolution is a quality setting, and quality settings invite perfectionism. If you are still finding your voice on camera, lock in the basics, record at 1080p, and come back to 4K when the words are working.

A pre-flight checklist

• Settings: 4K at 24, 25 or 30 fps; High Efficiency; HDR off; Lock Camera and Lock White Balance on.
• Free space: at least 2 GB per ten minutes you plan to record, plus margin.
• Light in front of you, stable, not flickering.
• Focus and exposure locked on your face.
• Phone on a tripod or a solid prop, in portrait if the content is vertical, lens at eye height.
• Script loaded and positioned next to the lens; one rehearsal read before the first take.

Do all of that once, save it as your default, and the resolution question stops being a question. Next in the series: batch-recording a week of content in one sitting, the workflow that makes all of these settings pay off.