Skip to main content
Calcimator

Time-Lapse Storage Calculator

Memory card capacity from interval, duration, and resolution.

About this calculator

This calculator works out everything you need to plan a time-lapse shoot: how many frames you'll capture, how long the resulting video will run, and how much storage and battery capacity to bring. Total frames come from dividing your total shoot duration (converted to seconds) by the interval between shots, so a 2-hour shoot at a 5-second interval yields 1,440 frames. Video length is simply that frame count divided by your chosen output frame rate — the calculator does not add or drop frames to hit a target runtime, so if you want a longer final video you need a shorter interval or a longer shoot, not a different frame rate. Storage is calculated by multiplying frame count by the file size per frame, with JPEG assumed to run about 30% of the size of RAW at the same resolution; the calculator lets you flag whether you're shooting RAW or JPEG and adjusts accordingly.

From total storage it derives how many memory cards of your specified size you'll need (rounding up, since a partial card still counts as one), plus the inverse calculation — the maximum shoot duration a single card can hold at your current interval and file size. Battery needs are estimated very roughly at 400 shots per battery, a conservative average that doesn't account for cold weather, long exposures, or in-camera processing between shots, all of which drain batteries faster than the shutter count alone suggests. The speed-up factor (interval × fps) tells you how much faster real time will appear to move in the finished video.

Inputs

Results

Total frames

1,440

Video length (sec)

60

Total storage (GB)

35.16

Video length (min)1
Memory cards needed1
Max shoot on 1 card (min)218
Batteries needed (est.)4
Speed-up factor (×)120
How to Use This Calculator
  1. Enter the interval between shots in seconds and the total duration of the time-lapse sequence.
  2. Set your camera RAW file size in MB.
  3. Input the target playback frame rate (typically 24 or 30 fps).
  4. Review the Total Number of Frames, Required Storage in GB, and Final Video Duration.
  5. Use the Playback Speed Multiplier to verify the real-world time compression matches your creative goal.

How the result changes with Interval (seconds)

Interval (seconds)Total framesVideo length (sec)Total storage (GB)
2.52,88012070.31
3.751,9208046.88
7.59604023.44
135532313.5

What each input means

Interval (seconds)
Time between each frame capture in seconds.
Shoot duration (min)
Total shooting duration in minutes.
Output video FPS
Frames per second for the output video (24 cinema, 30 web).
File size per frame (MB)
Average file size per image (RAW ~25MB, JPEG ~8MB).
Shoot RAW? (1=yes, 0=JPEG)
1 for RAW files, 0 for JPEG (JPEG uses ~30% of RAW size).
Memory card size (GB)
Capacity of each memory card in GB.

What each result means

Total frames
Total number of images to be captured.
Video length (sec)
Duration of the final time-lapse video.
Video length (min)
Video duration in minutes.
Total storage (GB)
Total storage space required for all frames.
Memory cards needed
Number of cards of the specified size needed.
Max shoot on 1 card (min)
Maximum shooting duration on a single card.
Batteries needed (est.)
Estimated batteries needed (~400 shots per battery).
Speed-up factor (×)
How much faster the video plays vs. real time.

How this is calculated

Worked example, using the default values

  1. Identify Input Parameters
    4 parameters
    Interval (seconds) = 5, Shoot duration (min) = 120, Output video FPS = 24, File size per frame (MB) = 25 = 6 input(s) provided
  2. Calculate Total frames
    Total frames = floor(shootDurationSec / intervalSec)
    1440 = 1440
  3. Calculate Video length
    Video length = totalFrames / fps
    60 = 60
  4. Calculate Total storage
    Total storage = totalStorageMb / 1024
    35.16 = 35.16
  5. Calculate Video length
    Video length = videoDurationSec / 60
    1 = 1
  6. Calculate Memory cards needed
    Memory cards needed
    1 = 1

Engine last updated . Checked against 2 independently-derived tests — how we verify calculators. Built by Paul Gunder, a software engineer, not a licensed financial, medical, or legal professional.

Frequently Asked Questions

Why doesn't raising the output frame rate shorten my final video length?

Video length is simply total captured frames divided by fps — the calculator never retimes, drops, or interpolates frames to hit a target runtime. To make the video shorter or longer at the same fps, you have to change your interval or total shoot duration; changing fps only changes how many of your existing frames play back per second.

Why does my storage estimate drop when I switch from RAW to JPEG?

The calculator assumes JPEG files run about 30% of the size of RAW at the same resolution, so the effective file size used in the storage calculation is multiplied by 0.3 whenever you flag JPEG instead of RAW. Total storage — frame count times per-frame size — drops proportionally even though the total number of frames captured stays exactly the same.

How is the batteries-needed number calculated, and why might it be optimistic?

It divides total frame count by 400, a rough average shots-per-battery figure, and rounds up. It doesn't account for cold-weather drain, long bulb exposures, image review, or Wi-Fi/GPS left running between shots, all of which push real shots-per-charge below 400 — so pack extra batteries beyond the raw number, especially in cold conditions.

What does the speed-up factor tell me that video duration doesn't?

Speed-up factor (interval × fps) tells you how much faster real elapsed time appears to move in the finished video — a 5-second interval played back at 24 fps means every second of video represents 120 seconds of real time. Video duration alone just tells you total runtime, not that time-compression ratio.

The questions that sit next to this one — chosen by subject, including calculators filed under a different category.

More in Creative, Media & Design.