Skip to content
Latentshoot
Menu

How long a shoot takes

How long does a photoshoot take?

There is no single answer, but there is a method: realistic per-shot ranges, where the hidden hours go, and how to turn your own past shoots into something better than a guess.

There is no single answer, but there is a method

Any answer to "how long does a photoshoot take" that is a single number is wrong for somebody else’s shoot. A duration depends on what kind of shot it is, whether a lighting setup has to change, whether hair and makeup are involved, whether the crew is moving between locations, and how many times any of that repeats across the day. So rather than memorising a number, build a method: realistic ranges by type of work, an honest account of the hours that never make it onto a shot list, and a way of turning your own past shoots into next time’s estimate instead of guessing again from zero.

Realistic timings by type of work

Treat the ranges below as a starting point to adjust to your own pace, not a number to defend on the day.

Type of shotRealistic rangeWhat drives the variance
Flat lay or product detail, existing setup10–20 minHow many angles, and whether the layout needs restyling between them.
Product hero shot, dedicated lighting25–45 minTime to light, not to shoot — most of it is setup, not the exposure.
Simple portrait, one look, existing light10–15 minHow settled the subject is; a stranger takes longer than a returning client.
Portrait with a full lighting change25–45 minRebuilding the setup, not the portrait itself.
Full wardrobe change (a lookbook look)20–40 minGarment complexity and whether hair or makeup need a touch-up too.
Company move to a second location20–40 min each wayReal travel time plus re-setting up on arrival — rarely as short as the drive itself.
Group or multi-person composition20–35 minCoordinating more people takes longer than the exposure ever does.
A shot pinned to golden or blue hourFixed window, not flexibleThe light sets the time available; see planning around golden hour.

Where the hidden hours actually go

The gap between "the shots took four hours" and "the day took nine" is almost never the shots. It is the time around them, and photographers who have run the day say so plainly:

"Hair and make up can take an hour or two (longer if you start chatting, which I’ve been known to do)."

PetaPixel, "8 Steps to Arranging a Fashion Editorial Shoot"

Beyond hair and makeup, the hours that do not make it onto a shot list but reliably eat into the day include: setting up and striking a lighting rig between setups, moving between locations, not just driving but arriving, unloading and resetting, reviewing frames with a client on set, and the ordinary friction of a shoot — a battery that needs swapping, a card that needs clearing, a break nobody scheduled but everybody needs. None of it is waste; all of it is real time a day needs to budget, and a schedule that only totals the shots and ignores it will be wrong by exactly the size of the gap.

Two more categories are worth naming because they are so easy to leave off a first estimate entirely: the setup at the very start of the day — unloading, building the first lighting rig, briefing anyone new to the crew — which rarely takes less than twenty to thirty minutes even on a familiar set, and the strike at the end, which takes longer than it looks because it happens when everyone is already tired and thinking about getting home. Neither belongs to any one shot, so neither shows up unless the schedule has a line for it.

Building your own estimate instead of guessing

Those ranges are a starting point for your first shoot. From the second one on, the better number is your own: what a shot like this really took last time, on your set, with your team. Latentshoot records how long every captured shot really took and uses it to suggest a duration for the next similar one — the middle of what really happened, not the average, so one three-hour disaster with a difficult subject does not drag every later estimate upward. And it will not settle on a learned number from a couple of shoots either.

3

shots on record before Latentshoot will offer a learned estimate

Fewer than that, and a plain round number is more honest than a pattern built from two examples.

A pattern built from two examples is an anecdote, and an obviously round number is a more honest guess than a confident-looking one built from almost nothing.

Latentshoot’s on-set mode on two phone screens. The left screen shows a red '25m late against the plan, right now' banner above the shot currently being taken, its full spec, and three buttons — Captured, Retake, Skip. The right screen is the running order, labelled as re-timed, with completed shots struck through and a marker against the current time, followed by the shot in progress and the shots still to come.
Every row below the marker on the right-hand screen has just moved, because the shots above it ran to the time they really took rather than the time they were given. Tapping Captured is also what feeds the number the next estimate is built from.

A day that does not need the last two shots dropped

A realistic estimate is not about accuracy for its own sake. It is that a day built on honest numbers shows you the overrun while you can still do something about it, rather than at 5pm when your only options are cutting a must-have shot or paying for another half-day. At the end of the day, comparing what was planned against what actually happened, per group rather than as one overall number, is also the fastest way to see which part of the estimate was wrong: a whole group running long usually means the setup itself was under-timed, not that any one shot was slow.

The same method scales to a multi-day production: build the estimate for one day properly, using your own recorded pace rather than a guess, and a three-day shoot is simply three of those days end to end, each one able to absorb its own overrun rather than borrowing time from the day after it.

Does not this only help once I have already shot a lot of jobs?

On your very first shoot, yes. There is nothing to learn from yet, so the ranges above and your own judgement are what you have. The value builds from the second shoot on, which is exactly why it is worth estimating honestly rather than optimistically on shoot one: an optimistic guess that gets blown through teaches you nothing next time, because no accurate number was ever recorded to learn from.

The Captured, Retake and Skip taps above are how Latentshoot records what a shot actually took — the same on-set screen the numbers in this guide come from.

Build a day that actually fits

Frequently asked

How many looks can I shoot in a day for a lookbook?

A commonly cited range is ten to thirty looks in a day, depending on the pace of the shoot — see the lookbook planning guide for how to turn that range into a number for your own day.

Does travel between locations count as part of the shoot time?

Yes, and it is one of the most commonly under-budgeted parts of a day — a company move costs real time on both ends, not only the driving, so it belongs in the schedule as its own block rather than being absorbed silently into whichever shot comes after it.

How do I get better at estimating over time?

Record what each shot actually took, not only what was planned, and go by the middle of your own past shoots rather than a general rule of thumb — a handful of real examples from your own set beats any generic guideline.

No card. Every actual duration recorded on set makes the next estimate better — on the free plan too.