Why Time-Lapses Eat More Storage Than You Expect
A time-lapse looks like a short video, but underneath it is thousands of full-resolution still photos. That is why a two-hour sunset shoot — which becomes a 48-second clip at 30 frames per second — can demand about 11 GB of card space as JPEG, or roughly 35 GB if every frame is shot as RAW. Photographers who arrive with a half-full card discover this the hard way, because the finished video gives no hint of the mountain of source files behind it.
The good news is that time-lapse storage is completely predictable. Three inputs decide everything: how long you shoot, how often the camera fires, and how big each file is. Run the numbers before the shoot and there are no surprises.
The Core Math: Interval, Duration and File Size
Every time-lapse calculation reduces to three steps. First, count the photos. Then multiply by the size of one file. Then divide by the frame rate to learn how long the finished clip runs.
The time-lapse formula: Photos = shoot duration (seconds) ÷ interval (seconds) · Storage = photos × file size · Clip length = photos ÷ frame rate (fps)
A practical check: two hours is 7,200 seconds. With a 5-second interval the camera takes 7,200 ÷ 5 = 1,440 photos. If each JPEG is about 8 MB, that is 1,440 × 8 MB = 11,520 MB, or roughly 11.25 GB. At 30 frames per second, those 1,440 photos play as a 48-second clip.
File Sizes by Format: JPEG, HEIF and RAW
The format you shoot in is the single biggest lever on storage. A modern camera writes very different files depending on the setting:
| Format | Typical file size | 2 hours at 5 s interval |
|---|---|---|
| Smartphone JPEG | ~4 MB | ~5.6 GB |
| HEIF | ~5 MB | ~7 GB |
| Camera JPEG | ~8 MB | ~11.25 GB |
| RAW | ~25 MB | ~35 GB |
The same shoot needs three times the card space in RAW. That trade-off buys editing latitude — exposure and white balance can be fixed across the whole sequence — but it should be a deliberate choice, not an accident.
Worked Examples: Sunset, Construction Site and a Full Day
Consider three realistic shoots, all finished at 30 frames per second:
- Sunset, 2 hours, 5-second interval, camera JPEG: 1,440 photos → about 11.25 GB → a 48-second clip. In RAW the same shoot needs roughly 35 GB.
- Construction site, 8 hours, 30-second interval, camera JPEG: 960 photos → about 7.5 GB → a 32-second clip. Slow subjects need long intervals, which is why an all-day shoot can still fit comfortably on one card.
- Plant growing, 24 hours, 60-second interval, HEIF: 1,440 photos → about 7 GB → a 48-second clip.
Notice the pattern: the sunset and the 24-hour plant shoot use the same number of photos. Interval is what converts wall-clock time into frames, so a longer shoot with a longer interval can cost less storage than a short shoot with a rapid one.
Clip Length: How Many Photos Become a Minute of Video
Frame rate is the exchange rate between photos and video. At 30 frames per second, one minute of finished video requires 1,800 photos; a 10-second clip needs 300. The cinematic 24 fps standard lowers the bar to 1,440 photos per minute, while buttery 60 fps demands 3,600.
This is worth checking before pressing the shutter. If the goal is a 15-second clip for social media at 30 fps, 450 photos are enough — there is no reason to burn 3,000 frames and the card space that goes with them.
6 Ways to Keep Time-Lapse Storage Under Control
- Match the interval to the subject. Clouds and sunsets look great at 2–5 seconds; construction and plant growth work at 30–120 seconds. Faster than necessary just multiplies storage.
- Shoot JPEG or HEIF unless you grade heavily. RAW triples the storage for latitude most sequences never use.
- Decide the clip length first. 300 photos at 30 fps is a 10-second clip — plan the shoot backward from the video you want.
- Bring a second card. Cards are cheap; re-shoots of a sunrise are not.
- Turn off features you do not need. Long-exposure noise reduction doubles each frame's capture time and drains the battery faster.
- Offload between sessions. A multi-day construction shoot should be copied to a drive each evening.
When RAW Is Worth the Gigabytes
There are shoots where RAW earns its storage. Sunrise and sunset sequences swing through huge exposure changes, and RAW files hold highlight and shadow detail that JPEG discards — the difference shows when the sequence is deflickered and graded. Astro time-lapses benefit too, because noise reduction in post works far better on RAW data.
For everything else — clouds, traffic, crowds, plants — high-quality JPEG or HEIF is visually identical after grading, at roughly a third of the storage. Make RAW a creative decision, not the default.
Frequently Asked Questions
How many photos do I need for a 1-minute time-lapse?
At 30 frames per second, exactly 1,800 photos. The cinematic 24 fps standard needs 1,440, and smooth 60 fps needs 3,600.
Is a 128 GB card enough for a full-day time-lapse?
Almost always. An 8-hour construction shoot at a 30-second interval in camera JPEG is only 960 photos — about 7.5 GB. Even aggressive shoots rarely pass 30–40 GB unless every frame is RAW.
Does a longer interval always mean less storage?
For a fixed shoot duration, yes: doubling the interval halves the photo count and the storage. But interval also controls the look — too long and smooth motion turns choppy, so choose it for the subject first and treat the storage saving as a bonus.
Try it now: Time-Lapse Storage Calculator — enter your shoot duration, interval and photo format to get the photo count, storage needed and final video length before you press the shutter.