Timelapse Calculator
How many photos, how long to shoot and how much storage for your timelapse — from interval, clip length and frame rate.
1,104 views
How It Works
Timelapse math starts from what the finished clip should look like: frames needed = target clip length (seconds) × playback frame rate (fps). Once you know how many frames the edit requires, divide the real duration of the event by that number to get your shooting interval: interval (seconds) = real event duration (seconds) ÷ frames needed.
Worked example: a 10-second, 30 fps clip of a 3-hour sunset needs 10 × 30 = 300 frames. The event lasts 3 × 3600 = 10,800 seconds, so interval = 10,800 ÷ 300 = 36 seconds — fire the shutter roughly every 36 seconds and the footage compresses cleanly into the target length.
The number this gives you is only half the job — the interval also has to match how fast the subject actually moves. Slow-changing scenes (drifting clouds, a sunset's color shift, plant growth) tolerate long intervals because little changes between frames. Fast subjects (pedestrians, traffic, a construction crew) need short intervals; stretch the interval too far and motion turns into a stroboscopic, "jerky" jump-cut instead of smooth flow. Go the other way — too short an interval on a slow subject — and you waste storage and shooting time on near-identical frames, producing an oddly "over-smooth" or static-feeling clip. The arithmetic is exact; matching the result to the subject's motion speed is still a judgment call.
What to Know
Storage is the other constraint worth planning before you start: 300 RAW files at roughly 30 MB each is about 9 GB for a single 10-second clip — multiply that across several setups in a shoot day and cards fill fast. JPEG keeps files far smaller and is the common default for timelapse unless heavy exposure or color grading is planned in post, in which case RAW's extra latitude is worth the space.
One more check worth doing before a long shoot: multiply your interval by the frames needed to confirm total shooting time actually fits your battery life and card capacity. A 6-hour star-trail sequence at a 40-second interval needs roughly 540 frames spread across those 6 hours — easily enough to outlast a single battery charge, so a spare battery, external power or a dedicated intervalometer with its own power supply is worth planning for alongside the interval itself.
- Match the interval to subject speed, not just the arithmetic result.
- Shoot in full manual mode so the camera can't re-meter between frames.
- Decide RAW vs JPEG based on how much grading you plan afterward.
Frequently Asked Questions
What interval should I use for a sunset timelapse?
5-10 seconds works well for a typical sunset: a 45-minute sunset at a 6 s interval yields 450 frames — an 18-second clip at 25 fps that captures the color change smoothly. Slower, more gradual skies can stretch toward 10 s without looking choppy.
24, 25 or 30 fps for the final video?
Match your delivery: 24/25 fps looks cinematic and stretches your frames further; 30 fps suits web and mixed-footage projects. The same 300 frames give 12.5 s at 24 fps but 10 s at 30.
How do I choose an interval for fast subjects like crowds or traffic?
Fast subjects need much shorter intervals than skies — commonly 1-3 seconds for a busy street, sometimes under a second for a dense crowd. The test: two consecutive frames should show clear but believable movement, not subjects that vanish and reappear across the frame. Because fast subjects need more frames per minute of real time, the shoot uses up far more storage than a sunset would for the same clip length.
How much storage should I plan for?
Multiply frames needed by your per-photo file size: 300 RAW files around 30 MB each is roughly 9 GB, while the same shoot in JPEG might stay under 2 GB. Many timelapse shooters default to JPEG for exactly this reason, reserving RAW for shots where heavy color grading is planned.
How do I avoid flicker?
Shoot fully manual — fixed aperture, shutter, ISO and white balance. Aperture flicker from the lens re-stopping each frame is the top culprit; manual lenses or "aperture priority lock" tricks solve it.
Similar Tools
Report a Problem
Timelapse Calculator
Comments
No comments yet — be the first to write one!