The iPhone Headshot

First, kill the thing that isn’t true

You have been told phones have poor dynamic range — that they blow out highlights and crush shadows and that is why they cannot do professional work. This is no longer true and we are not going to repeat it.

A typical smartphone sensor encodes about 10 bits per pixel — 1,024 tonal values. A large-sensor camera encodes 12 to 14 bits — 4,096 to 16,384. On that comparison the phone loses badly, and that is the comparison the photography internet froze in 2014. But phones do not take one exposure. They merge between two and eight frames and reconstruct the tonal range computationally, and the result is that in many high-contrast situations a phone now outperforms a 14-bit full-frame sensor. (DXOMARK have published on exactly this; so has the computational-photography literature.)

The resolution argument is even weaker. Your headshot is going to be viewed as a small tile in a browser. Every phone on the market has been massively over-delivering pixels for that job for a decade.

So the honest position — which is more interesting than either extreme — is this. The phone’s sensor is fine. Its dynamic range is fine. Its resolution is absurdly more than any casting platform needs. And its default lens is wrong, its fake bokeh eats your hair, and its default processing quietly airbrushes you. All three of those are free to fix. None of them are reasons to spend $600.

Problem one: the lens. And the reason is not the one you have been given.

Here is the sentence everyone repeats: “long lenses compress and flatter your face, short lenses distort it.” That is a shorthand, and stated that way it is wrong. Getting it right is the single most useful thing on this page.

Perspective distortion is caused by camera-to-subject distance. Not by focal length. Focal length has one job in this story: it dictates how far away you have to stand to fill the frame with a head.

Think about what happens when you get close. Your nose is perhaps ten centimetres nearer the lens than your ears are. From three metres away, that ten centimetres is a trivial fraction of the total distance and your features render in roughly the proportions a person sees when they are talking to you. From thirty centimetres away — arm’s length, selfie distance — that same ten centimetres is a third of the entire camera-to-subject distance. So the nose balloons, the forehead swells, the chin comes forward, and the ears and the back of the head shrink away into nothing. Nothing about the lens did that. Your proximity did.

A wide lens does not distort your face. It forces you close enough that the distance does.

The numbers, from Apple’s own spec sheet

This is where it gets actionable, because the phone already contains the solution and does not tell you.

On the iPhone 17 Pro, per Apple’s published specifications: the main camera is a 24mm equivalent. That is a wide-angle lens. It is an outstanding wide-angle lens. It is the wrong lens for a face. The Ultra Wide is 13mm — catastrophically wrong for a face. The 2x setting is a 48mm equivalent, a 12MP crop from the 48MP main sensor, which Apple itself describes as “optical-quality.” The 4x telephoto is a true 100mm equivalent, 48MP, with a tetraprism folded optical path. That is a genuine portrait lens on a phone. 8x gets you to 200mm.

And here is the detail that settles the argument: Apple’s own Portrait mode defaults to the 2x, 48mm-equivalent setting. The manufacturer does not use the main wide lens for portraits either. The manufacturer agrees with us.

If your phone has no telephoto, the 2x is a digital crop. You lose pixels. You keep the geometry — because geometry is a function of where you stand, and standing further back is free. A cropped 12MP frame at the right distance beats a full 48MP frame at the wrong distance, every single time. The pixels are not the point. The distance is the point.

One thing we will not do: cite you a study. There is a widely-circulated plastic-surgery paper on “selfie distortion” that gets quoted everywhere. We could not verify it, so we are not going to lean on it. The geometry above is uncontroversial and needs no citation — you can prove it to yourself in your hallway in ninety seconds, which is better than a footnote anyway.

Problem two: Portrait Mode is a cut-out, and it eats hair

Understand what Portrait Mode actually is, because the marketing never says it.

The phone does not have a sensor large enough or a lens fast enough to produce a genuinely shallow depth of field. So it fakes one. It builds a depth map — from the stereo disparity between two lenses, from the LiDAR sensor, and from machine-learned segmentation — then it cuts you out of the background and applies synthetic blur to everything it decided was not you. It is a computed cut-out. It is not an optical effect. It is Photoshop, running in real time, guessing.

And it fails in precisely the place a headshot cannot afford to lose.

Hair is the number one failure mode. Fine strands at the edge of the head are notoriously difficult to segment, so you get partially blurred hair, a faint halo around the skull, and blur bleeding onto the subject. The algorithm also gets confused by glasses frames, earrings, flyaway strands and hands near the face. And there is a characteristic tell once you know to look for it: one eye, or one side of the face, rendering softer than the other despite being exactly the same distance from the camera. That is the signature of an estimated depth map rather than an optical one, and once you have seen it you cannot unsee it.

Is it still broken in 2026? The honest answer is “better, not solved.” Reviewers report tighter hair-edge rendering on the iPhone 17 Pro than on the 16 Pro, described as a hardware-level improvement rather than a software patch. So: improving generation on generation, still visibly imperfect on fine hair. Anyone telling you it is solved is guessing, and anyone telling you it is still terrible is a decade out of date.

Problem three: your phone is retouching you, and it does not ask

This is the sneakiest one, and it is the one nobody warns actors about.

A modern phone does not take a photograph. It computes one. It merges multiple frames, applies HDR tone-mapping, runs noise reduction, adds sharpening — and, crucially, applies skin smoothing and “beautification” — automatically, by default, before the image ever reaches your eyes.

Now put that next to what casting actually complains about. Frank Moiselle: “touched up in such a way that really it doesn’t represent you.” The agent Carrie Johnson: “you don’t want it to look plastic.”

Your phone is doing to your face exactly what an over-retoucher does — and unlike the retoucher, it never asks your permission and never shows you the original. The single most common complaint casting directors have about headshots is being applied to you, by default, by a device in your pocket, at the moment of capture.

The fix is real and it is one setting. Shoot in a mode that turns the processing off or down.

Use Apple ProRAW / RAW at 48MP, or a third-party camera app that captures RAW — Halide, Lightroom Mobile, Blackmagic Camera. RAW files are unprocessed: no smoothing, no beautification, no baked-in sharpening. They come out of the phone looking flat and dull, and that is correct. That is what an unprocessed photograph of a real face looks like. You then do the small amount of processing yourself, on purpose, in the direction you chose.

And turn off every “beauty,” “smooth skin” or Portrait Lighting effect. Portrait Lighting is a synthetic relight applied on top of a computed depth map. It is a filter with a serious-sounding name. It has never been anything else.

What a phone genuinely cannot do

We are not going to pretend the gap is zero. Three things are real.

Genuinely optical, very shallow depth of field, with the particular way real defocus falls away behind an eye. Synthetic blur is not the same thing and a trained eye sees it instantly. Extreme low light without either noise or heavy computational intervention — though this is irrelevant to you, because you should be shooting in good light anyway and that is free. And rendering fine skin texture at large print sizes — also largely irrelevant, because the image is going to live as a small tile in a browser.

Notice how thin that list is once you remove the parts that do not apply to a headshot.

Will a platform reject a phone photo?

No casting platform prohibits phone-shot photos. Not one. Be precise about this, because the folklore is muddled.

Spotlight prohibits “holiday photos or screen grabbed photos from your phone or tablet.” Read that carefully. That rule is about snapshots and screenshots. It is not about the device. A properly lit, properly framed image shot on an iPhone and uploaded as a full-resolution file is not what that clause is aimed at. But it is a moderation judgement call — so an image that looks like a phone snap can absolutely be rejected. The instruction that follows is simple: don’t make a phone snap. Make a photograph.

And the point that closes this: the reason the headshots that worked in 2010 worked is that somebody put a light in the right place and gave the actor something to think about. Neither of those things is in the camera. Neither of them ever was.