Running out of card space halfway through a sunset time-lapse is a shoot-ending mistake. This estimator tells you exactly how much storage a sequence needs from four inputs — interval, duration, resolution and format — and also shows how long the finished clip will be, so you can plan both the card and the edit before you press start.
How it works
The calculation has two parts: how many frames you capture, and how big each one is.
Frame count is the total shoot time divided by the interval between frames:
frames = floor( (duration in minutes × 60) / interval in seconds )
Per-frame size is estimated from the image resolution and the file format. For compressed formats the tool uses representative megabytes-per-megapixel figures:
JPEG normal ≈ 0.3 MB per MP
JPEG fine ≈ 0.5 MB per MP
RAW compressed ≈ 1.5 MB per MP
For uncompressed RAW it computes directly from the bit depth, since each pixel stores that many bits per channel:
bytes per pixel = bit depth / 8
frame size = megapixels × 1,000,000 × bytes per pixel
Total storage is simply frames × per-frame size, converted to gigabytes.
Worked example
A two-hour shoot at a five-second interval gives 7200 / 5 = 1440 frames. Shooting a 24-megapixel
camera in compressed RAW (~1.5 MB/MP) makes each frame about 36 MB, so the sequence needs roughly
1440 × 36 ≈ 51.8 GB. Played back at 24 fps, those 1440 frames produce a 1440 / 24 = 60-second
clip.
Tips and notes
- Add 15 to 20 percent headroom: detailed, high-contrast scenes compress less and grow larger, especially in JPEG.
- HDR or bracketed time-lapses multiply the frame count by the number of exposures per interval — factor that in by adjusting the interval or duration.
- Card write speed matters as much as capacity for short intervals and large RAW files; a slow card can cause dropped frames before storage even fills.