Cinematography Shotlist Time Calculator

Build a shoot-day estimate that respects how set time really works

A shot list can look deceptively small when you only think in terms of finished screen time. A page of inserts, overs, wides, and moving shots may add up to just a few minutes of recorded footage, yet still consume most of a crew day. The reason is simple: a shoot day is usually shaped far more by preparation than by rolling time. Blocking, relighting, lens swaps, camera movement, eyeline adjustments, continuity checks, talent notes, and resets all live in the space between shots. This calculator is designed to make that hidden time visible. It combines the number of planned shots, average camera run time, average setup time per shot, and a contingency buffer so you can see whether your list fits a realistic working window.

That makes the tool useful for more than one kind of person. A cinematographer can use it to sense whether a proposed list is ambitious but reachable or quietly impossible. A producer or 1st AD can use it for fast scenario testing before building a fuller stripboard or day-out-of-days. Film students can use it to learn why a five-minute scene does not automatically mean a five-minute shoot. Even freelance creators working with a tiny crew can use it to decide whether to cut coverage, simplify setups, or move an insert sequence to another block of the day.

The most important lesson behind the math is that a shot list is a count of setup cycles, not just a count of seconds on the card. Twenty shots with eight-second takes do not create a three-minute day. They create twenty transitions from one shot to the next, and those transitions are often where the schedule is won or lost. A planning estimate that ignores them can make a short list look comfortable when it is actually headed for overtime. A planning estimate that includes them gives you a defensible first-pass answer you can discuss with the rest of the team.

How to choose the inputs without fooling yourself

Number of Shots should mean distinct planned camera setups in the way your team actually intends to work. If you are capturing a scene as a wide, two singles, an insert, and a slider push-in, that is not one scene for this calculator; it is five shots. Likewise, if one setup will later split into a second angle with a meaningful reposition, count that extra angle separately. The more honestly your shot count reflects real setup changes, the more useful the estimate becomes.

Average Shot Length is measured in seconds and refers to camera rolling time per shot, not the scene's final edited duration and not the total time you spend living on that setup. For many narrative days, this number is surprisingly small. A setup might roll two or three takes of a short line reading and still only average a handful of seconds of usable camera time. If your day mixes very short inserts with longer steadicam or walk-and-talk pieces, do not guess from memory. Sample a few representative shots, total the expected rolling time, and divide by the number of setups. A rough weighted average is better than a number that merely sounds cinematic.

Setup Time per Shot is usually the most influential input. It should represent the average number of minutes between finishing one planned shot and being genuinely ready to roll the next one at the granularity of your shot list. On some days that average may be five or six minutes. On others it may be fifteen, twenty, or more. If you underestimate setup time, the total will look artificially safe because the formula multiplies that average across every shot.

For many crews, setup time includes things such as:

• minor blocking changes and actor marks
• lens, filter, support, or camera-height adjustments
• small relights, flags, negative fill, bounce, or practical tweaks
• brief sound, playback, battery, card, or monitor resets

What setup time does not automatically include is every possible disruption in the day. A major company move, a complicated meal break turnaround, heavy hair and makeup changes, stunts, weather holds, or client review delays may deserve their own planning line or a much larger safety margin. That is where the Buffer for Delays comes in. The calculator applies the buffer after it combines footage time and setup time, which makes it a practical way to represent the schedule friction you expect but cannot pin to one exact shot.

A lean studio day with a prepared crew and repeatable lighting may justify a modest buffer such as 5% to 10%. A location day with multiple departments waiting on the same narrow sequence may need 15% to 25% or more. The point is not to pick the biggest number and hide uncertainty inside it. The point is to match the buffer to the amount of unpredictability that is still left after you have been honest about average setup time.

What the calculator is actually doing

The calculation is intentionally straightforward. First, it converts total rolling time from seconds into minutes. Then it adds the repeated setup time created by the shot count. Finally, it applies the contingency buffer as a percentage on top of that subtotal. In plain language, the estimate asks: how long will all planned camera run time take, how long will all the transitions between shots take, and how much extra protection do we want for real-world delays?

In that formula, N is the number of shots, t is average shot length in seconds, s is setup time per shot in minutes, and c is the buffer percentage. The page then formats the answer into hours and minutes for quick reading. Because the on-page output rounds to whole minutes, it is best treated as a planning estimate rather than a second-by-second schedule.

If you like abstract formulas, the same idea can still be described in a general calculator form. The two MathML expressions below are preserved from the original page, and they remain true as broad ways to think about how many calculators work and how repeated contributions add up.

For this specific calculator, each shot contributes two repeated pieces of time: a little footage and a much larger setup block. That is why changing the shot count usually has a stronger effect than changing shot length by a few seconds. Most shoot days are dominated by repetition of process, not by the time the sensor is actively recording.

Worked example: why setup dominates the day

Suppose your current plan includes 20 shots, the average shot runs for 8 seconds, the crew needs about 15 minutes to set up each shot, and you want a 10% delay buffer. The footage portion is easy to calculate: 20 × 8 = 160 seconds of total rolling time, which is about 2.67 minutes. The setup portion is much larger: 20 × 15 = 300 minutes. Before the buffer, your base estimate is therefore about 302.67 minutes. After applying a 10% contingency, the total becomes about 332.93 minutes, which this page will present as roughly 5 hours and 33 minutes.

That example is valuable because it corrects a common intuition error. Someone looking only at the 160 seconds of recorded footage might assume the day is tiny. The calculator shows the opposite: the rolling time is almost irrelevant compared with the accumulated setup work. Once you see that relationship, schedule discussions become more practical. Cutting four shots may save nearly an hour. Cutting four seconds from each shot barely changes the day at all.

Scenario comparison

The table below keeps the same assumptions for average shot length, setup time, and buffer while changing only the shot count. It illustrates how strongly repeated setup work drives the total. Times are shown as planning-friendly approximations.

This kind of comparison is often more useful than hunting for one perfect number. Run a conservative version, a baseline version, and an aggressive version. If all three fit, you probably have room. If only the optimistic case fits, your shot list may be balanced on assumptions you do not actually control.

Reading the result like an AD, producer, or DP

The result is best understood as an estimate of on-set shooting time for the planned shot list, not automatically the entire call-to-wrap day. If your average setup time already includes brief internal resets, that is fine. If it does not include lunch, travel, major company moves, rehearsal blocks, heavy makeup changes, or data-wrangling overhead, add those separately when building the full schedule. Many users get the most value from the calculator by treating it as the shooting core of the day and then layering larger logistical blocks around that core.

A good sanity check is to change one input at a time and ask whether the output moves in the expected direction. Add one more shot and the total should increase by roughly one more setup cycle plus a few seconds of footage. Raise setup time from 10 minutes to 15 minutes and the day should jump dramatically. Raise shot length from 8 seconds to 10 seconds and the result should move only slightly. If your test changes do not behave that way, the problem is usually an input interpretation issue rather than a bad formula.

Once the estimate looks reasonable, the copy button can help you share or save the scenario. That is useful when you are comparing alternate shot counts, discussing whether to combine setups, or documenting why a proposed page count no longer fits the day. A copied summary turns the calculator from a private scratchpad into a small communication tool for the team.

Common planning mistakes this calculator helps expose

The first mistake is confusing scene length with shot workload. Two pages of dialogue covered in a master and two inserts may schedule very differently from half a page that demands a macro insert package, multiple singles, a dolly move, and practical-light continuity. The calculator pushes attention back to setup count, which is often the more truthful workload metric.

The second mistake is choosing a setup-time average that reflects only the easiest shots. If your day contains a mix of quick tripod pickups and slower motion-control or lighting-heavy frames, one optimistic average can flatter the whole plan. In those cases, it is better to run separate passes by cluster: for example, one calculation for straightforward coverage and another for specialty inserts or movement shots. Add the results together and you will usually get a better schedule than by pretending every setup behaves the same way.

The third mistake is treating the buffer as wasted pessimism. A delay buffer is not an admission of failure; it is a planning acknowledgement that creative work unfolds in a real environment. Wardrobe notes, performance refinements, drifting weather, playback issues, traffic around a location, and a dozen tiny coordination moments can all be reasonable and still take time. Without a buffer, the schedule implies that nothing human will happen all day. Most crews know better.

Assumptions, limits, and when to split the day into separate estimates

This calculator is intentionally lightweight, so it does not model every production variable. It assumes your chosen averages are representative, the units are entered correctly, and the day can be described as repeated shots with roughly similar setup effort. Real production rarely stays that tidy for long. When the day contains a morning interior dialogue scene, a midday company move, and an evening exterior insert package, one average may hide more than it reveals.

In those mixed cases, split the work into smaller planning blocks. Run one estimate for the interior dialogue sequence with its own shot count and average setup time. Run another for the insert package, which may have short rolling time but unusual art, focus, and lighting demands. Then add a separate allowance for the company move or meal break. This approach keeps the math simple while still respecting the fact that different sections of the day behave differently.

Also remember that the calculator does not directly price the creative cost of rushing. A day can look numerically possible and still feel artistically cramped if the schedule leaves no room for performance discovery, meaningful rehearsal, or a spare take after a technical correction. That is not a flaw in the calculator; it is a reminder that scheduling is partly arithmetic and partly judgment. The number gives you a grounded starting point. The team still decides what quality level is acceptable.

Used well, this tool is not just about predicting an end time. It helps you ask better production questions: Do we need fewer setups? Should inserts move to a different day? Is the buffer honest enough for this location? Are we pretending a complex move is a standard setup? Those are exactly the conversations that prevent an impressive-looking shot list from turning into a stressful, overpromised day on set.