Time-Lapse Planning Calculator
Plan a still-image time-lapse from final clip length, recording duration, playback frame rate, and average image size.
Shoot assumptions
The calculator opens with a realistic example. Replace any value to update the plan instantly.
Final video duration in seconds. Use a positive decimal with a dot.
Elapsed capture duration in hours, not the final playback duration.
Playback frame rate; common project rates include 24, 25, 30, and 60 fps.
Average size of one saved photo, using decimal megabytes.
Live results
Capture interval
15.00 s
Take one photo every 15.00 seconds to fill the planned clip.
Number of photos
480
Memory usage
12.00 GB
Plan details
| Parameter | Value | Role |
|---|
Storage is an estimate based on average per-image size. Camera compression, scene detail, RAW/JPEG choice, and sidecar files can change real card usage.
How to use this time-lapse calculator
What this calculator does
This calculator plans the arithmetic of a still-image time-lapse. It uses four shoot assumptions to estimate the Capture interval, the Number of photos, and total Memory usage. The model assumes one captured photo becomes one playback frame, photos are taken at a uniform interval, and there are no dropped or duplicated frames. It is a planning tool, not a recommendation for exposure, shutter speed, battery life, camera write speed, weather, subject motion, or safe equipment operation.
When to use it
Use it when you want to plan a sunrise or sunset sequence, compress a few hours of clouds or city movement into a short edit, estimate card capacity before a long shoot, or check whether a target clip length and frame rate imply an interval your camera can practically maintain. Adobe's time-lapse shooting guidance also emphasizes that useful intervals depend on how quickly the scene changes, so treat the calculated interval as the mathematical target and then test it against the subject.
How to calculate
The calculator opens with a complete demonstration plan and an immediately available example XLSX export. To make it yours:
- Replace Clip length with the desired final video duration in seconds.
- Enter Total recording time in hours, then set Frames per second to the playback rate of your editing sequence.
- Enter the average Image size in decimal megabytes per photo. The results and Plan details table update live as each valid value changes.
- Read Capture interval first, then confirm Number of photos and Memory usage against your camera, card capacity, and workflow. Choose Download Excel to export the current validated plan.
- Choose Reset to clear the demonstration and all input data. Reset intentionally leaves the calculator empty, so Download Excel is disabled until you enter a complete valid set again.
Input guide
Clip length is required and accepts a positive decimal number of seconds, such as 20. A longer clip requires more frames at the same playback rate, which shortens the capture interval for a fixed recording duration. Do not paste timecodes such as 00:00:20; enter seconds only. Total recording time is required and accepts positive decimal hours, such as 2. Increasing it while other inputs stay fixed lengthens the interval between photos. Do not enter minutes without converting them to hours first.
Frames per second is required and accepts a positive numeric playback rate up to 240 fps; 24 is the demonstration value. A higher rate increases the required photo count and therefore shortens the interval for the same clip and recording time. SMPTE's overview of standard video time-code rates shows why rates such as 24, 25, 30, 50, and 60 fps are common in media workflows. Image size is required and accepts a positive decimal number of MB, such as 25. It changes storage only; it does not change the interval or photo count. Use an average from representative files rather than the camera's megapixel count.
Output guide
Capture interval is the required time in seconds between consecutive photos. A smaller value means more frequent captures. Number of photos is the frame count implied by Clip length × Frames per second; it is an exact arithmetic identity for the entered values, although a real camera ultimately records whole files. Memory usage estimates aggregate still-image storage from Number of photos × Image size. The display switches to GB at 1,000 MB and uses decimal storage prefixes; NIST's explanation of decimal and binary data-size prefixes explains the distinction between GB and GiB.
The live summary pills repeat the current photo count, interval, storage estimate, and playback rate for fast scanning. In the Plan details table, Parameter names each input or calculated quantity, Value shows the current formatted value, and Role distinguishes user inputs from calculated results. Zero or negative values are rejected because they cannot form a usable time-lapse plan; malformed grouped numbers, decimal-comma input, and scientific notation are also rejected rather than silently reinterpreted.
Worked example
The opening example uses a 20-second Clip length, 2 hours of Total recording time, 24 Frames per second, and 25 MB Image size. The photo count is 20 × 24 = 480 photos. Two hours equals 7,200 seconds, so the interval is 7,200 ÷ 480 = 15.00 seconds per photo. Storage is 480 × 25 MB = 12,000 MB, displayed as 12.00 GB. Those same typed values are used in the first rendered results and the startup Excel workbook.
How the time-lapse math works
interval seconds = recording seconds ÷ photos
storage MB = photos × image MB
These equations separate three planning questions. Playback determines how many still frames the finished clip consumes. The real-world recording window determines how far apart those frames must be captured. File size then converts the frame count into a storage estimate. Because the storage equation is independent of recording duration, changing a two-hour shoot to four hours does not change storage if clip length, frame rate, and image size stay fixed; it only doubles the interval.
Before the shoot, round operational settings only when your camera requires it. For example, a calculated 7.73-second interval may need to be set to 8 seconds on hardware that accepts whole seconds. That practical rounding changes the real frame count slightly, so allow extra recording time and card capacity. In post-production, keep the intended playback frame rate consistent with the sequence settings used to assemble the stills. Adobe's documentation on importing image sequences and specifying frame rate illustrates the connection between a still sequence and playback timing.
For storage, leave headroom rather than planning to fill a card exactly. File sizes vary with format and content, especially compressed JPEGs, and cameras may also create metadata or companion files. For long sessions, power, write speed, thermal behavior, weather, and intervalometer limits can become more important than the arithmetic itself.