Timelapse Recording Storage Calculator

Timelapse Recording Storage Calculator

Estimate daily frame count, still-image storage, encoded video storage, playback length, and retention days for security, project, garden, and smart home timelapse recordings.

📍Recording presets 8 common timelapse scenarios
🎛Timelapse inputs Frames/day = hours x 3600 / interval
Use active capture hours, such as daylight-only or full-day recording.
A lower interval creates more frames and more still-image storage.
Resolution sets pixels per frame and a compression detail multiplier.
This estimates image size from raw RGB bytes after JPEG compression.
Each camera creates its own frame set and encoded playback file.
Playback seconds = captured frames per camera divided by output fps.
Video GB uses bitrate x playback seconds; enter 0 if you keep stills only.
Retention uses 90% usable capacity to leave filesystem and app overhead.

Storage summary

Porch daylight profile: 720 frames per camera per day and about 1.5 GB/day combined archive.

Balanced
Frames per day 720 per camera, 720 total frames
Still image storage 1.37 GB/day 1.95 MB per captured image
Encoded video storage 0.01 GB/day 24.0 sec/day playback at 4.0 Mbps
Retention estimate 83.6 days based on 115.2 usable GB
Frames per day formula12.0 hours x 3600 / 60 sec = 720 frames per camera
Image size formula1920 x 1080 x 3 / 1048576 x 0.18 x 1.00 = 1.07 MB
Still archive formula720 total frames x 1.07 MB / 1024 = 0.75 GB/day
Video archive formula4.0 Mbps x 24.0 sec x 1 camera / 8 / 1024 = 0.01 GB/day
Combined storage formula0.75 GB stills + 0.01 GB video = 0.76 GB/day
Retention formula128 GB x 90% usable / 0.76 GB/day = 151.3 days
📊Core storage factors Five-column planning grid
3600Seconds per hour
90%Usable capacity
3RGB bytes per pixel
8Bits per byte
1024MB per GB
🗂Reference tables Resolution, interval, video, and scenarios
ResolutionPixelsMegapixelsRaw RGB MBDetail factor
720p HD1280 x 7200.92 MP2.64 MB0.82x
1080p Full HD1920 x 10802.07 MP5.93 MB1.00x
2K QHD2560 x 14403.69 MP10.55 MB1.08x
4K UHD3840 x 21608.29 MP23.73 MB1.18x
12 MP still4000 x 300012.00 MP34.33 MB1.35x
Interval8 hours12 hours24 hoursUse case
5 sec5760 frames8640 frames17280 framesFast workspace change
10 sec2880 frames4320 frames8640 framesConstruction detail
30 sec960 frames1440 frames2880 framesRoom or porch review
60 sec480 frames720 frames1440 framesGarden or daylight view
300 sec96 frames144 frames288 framesSlow seasonal change
Video bitrate24 sec clip2 min clip10 min clipTypical match
1 Mbps0.003 GB0.015 GB0.073 GB720p review file
3 Mbps0.009 GB0.044 GB0.220 GB1080p light motion
5 Mbps0.015 GB0.073 GB0.366 GB2K balanced file
12 Mbps0.035 GB0.176 GB0.879 GB4K compact file
20 Mbps0.059 GB0.293 GB1.465 GB4K archive file
ScenarioHoursIntervalResolutionPlanning note
Porch daylight12 hr60 sec1080pLow daily frames
Garden growth14 hr120 sec2KStill archive first
Garage workbench6 hr15 sec1080pShort high-detail session
Build site 4K10 hr10 sec4KHigh still storage
Whole-house check24 hr300 sec720pMany cameras, low rate
💡Storage planning tips
Still-image archive: If you keep every JPEG frame, resolution and interval usually matter more than encoded video bitrate. Verify the calculated MB per image against a real sample frame when the camera is available.
Retention buffer: This calculator uses 90% usable capacity so the estimate does not assume every advertised gigabyte is available for recordings, thumbnails, indexes, and filesystem overhead.

It’s not uncommon for someone to purchase a camera, aim it at their front porch and run out of storage space on their hard drive … only after they’re already there. When this happens, they’ll often frantically try to locate any captured footage that hasn’t yet been replaced with more recent shots of an empty walkway.

This isn’t as simple as purchasing the largest microSD card possible. You must carefully consider how resolution, capture interval, and encoding settings affects your storage. This applies to each setting alone and how they work together over days or weeks of continuous recording.

How to Save Space on Your Camera

How much data will you use each day? Can you sustains higher-res stills vs. Can you create smooth video playback?

First, it’s important to understand that capturing frames cost money in bytes, if done without care about compression. Each time the shutter clicks, a new frame is captured and written as a file to the card. And depending on how fast-paced your workspace might be, setting your interval too low, like every five seconds… Will result in thousands of photos generated in a single day. Regardless of who will watch them or not, they’ll start adding up pretty quickly.

To run the numbers yourself, plug into the calculator found on this page the number of hours you’d like to record and the number of photos you want to take per minute. It breaks out what it would cost to store both the raw images and the encoded video file that stitches all those photos back together.

Why does this matter? Each photo, even a 4K one, is much larger then a video clip of the same length at a lower resolution, even if the video looks smooth. Storage size is also dependent on resolution more than most people know. Going from 1080p to 4K doesn’t simply double the number of pixels, it almost quadruples them. On top of that, each pixel needs three bytes of color information before it is compressed. You can see why there is so much going on here.

If you’re shooting at a high quality jpeg setting then you’re instructing the camera to keep more details, meaning bigger file sizes. But again, it’s a minor consideration, unless you want to get three months of footage on a single 128GB card. The tool comes with a reference table that explains how much disk space certain resolutions take up in terms of raw pixels. This shows you the real difference: Your porch camera will last for months while your garden timelapse fills up a drive in two weeks.

When it comes time to export the video, that’s when bitrate matters most. You don’t care about bitrate if you’re leaving the footage in separate photos. Only once you convert everything into a single file do you want your bitrate set so you have a smooth 30 frames per second playback at the end of the day.

Higher-bitrate videos look more crisp, and they gobble up gigabytes quickly. Most users who aren’t shooting cinema-grade timelapse will be just fine with moderate bitrates. After all, timelapse doesn’t require cinema-quality video to track progress on a project or see how a house has changed over time.

The other consideration in your estimate of time-to-storage is that there’s some overhead on any system that’s going to use it. No drive is 100 percent available for storing data due to filesystems needing to store thumbnails, indexes, etc. If you have a ninety percent utilization buffer (i.e., plan to utilize only 90 percent), then your card won’t fill up unexpectedly before you thought it would.

For multi-camera rigs, this only increases the demand by the number of lenses you’re using. Two cameras don’t simply double your amount of footage. They double everything related to your storage calculations.

It’s really about finding the right balance. You need to capture enough to remember it later, but minimize how much you have to store without worrying about being “optimal” just for the sake of it. Does checking whether someone dropped off a package require 60 frames per second of 4k video? No, but 720p once every minute will do just fine and free up TONS of storage space. Want to document how your plants grow over the summer? Accepting more frequent high resolution (4k) captures despite their increased storage costs could of been a fair tradeoff.

When you know what matters, you can set up your system with a clear idea of what gets captured and when. This stops you from having to guess when the next thing will be overwritten. It transforms something that could be a hassle into a log of moments in time.

Timelapse Recording Storage Calculator

Leave a Comment