Single 1080p YouTube Video
A 10-minute Full HD (1920x1080) video recorded at 10 Mbps (H.264) will use: Size = (10 Mbps × 600 sec) / 8 / 1024 ≈ 0.73 GB
FREE VIDEO STORAGE CALCULATOR
Quickly find out how much storage space your video files will require before you hit record. Enter your video’s resolution, bitrate, codec, and duration to see exactly how many gigabytes you’ll need for your project.
Enter duration and bitrate, then calculate
The video storage calculator helps you determine exactly how much disk space your video recording will consume. It’s designed for anyone working with video cameras, surveillance systems, content creation, or archiving footage. By entering details like resolution, codec type, bitrate, and total recording time, you get a precise estimate in gigabytes (GB) or terabytes (TB).
This tool is for professionals and enthusiasts who need to plan storage for 4K video projects, multi-day security footage, or even batches of game capture. It works for all common codecs (H.264, H.265, ProRes) and resolutions from SD to 8K. The calculator gives you a straight answer, so you can avoid running out of space or overbuying expensive drives.
Input your video’s details in the fields provided. Select the resolution (for example, 1920x1080 for Full HD), then choose the video codec (H.264, H.265, ProRes, etc.). Enter the average bitrate in megabits per second (Mbps). For a quick reference, common bitrates: 1080p H.264 is typically 8-12 Mbps, 4K H.265 for streaming is 15-35 Mbps, and high-quality ProRes can be over 100 Mbps.
Next, enter your recording duration. You can specify hours, minutes, or even seconds. The calculator instantly shows you the estimated file size. You can also reverse the process: if you have a storage limit, input that and see how long you can record at your chosen settings.
If you’re planning for multiple streams or cameras, multiply the result by the number of feeds. For time-lapse or variable bitrate recording, estimate using the average or maximum bitrate.
The calculation is based on a straightforward formula used in broadcast, CCTV, and editing suites:
Size (GB) = (bitrate in Mbps × duration in seconds) / 8 / 1024
Here’s how it works:
This method assumes a constant bitrate. For variable bitrate (VBR) codecs, use the average bitrate value. Actual file sizes can vary slightly due to codec overhead, audio tracks, and metadata, but this formula gives you a reliable estimate for planning storage space.
When you enter your video details, the calculator outputs the estimated storage requirement in gigabytes (GB) or terabytes (TB) for the specified recording duration and quality. This is the raw space needed just for the video stream, assuming a single file with no audio or minimal audio tracks.
If you’re recording multiple audio tracks, subtitles, or using a container format with a lot of metadata, real-world file sizes may be slightly larger. Some professional codecs (like ProRes or DNxHR) produce larger files than compressed formats like H.264 or H.265. Always round up your storage estimates, especially for long-term archiving or 24/7 surveillance applications.
For multi-camera setups, multiply the storage estimate by the number of simultaneous streams. If you’re planning RAID arrays or NAS storage (like a Synology or QNAP with WD Red Plus drives), factor in redundancy and overhead.
A 10-minute Full HD (1920x1080) video recorded at 10 Mbps (H.264) will use: Size = (10 Mbps × 600 sec) / 8 / 1024 ≈ 0.73 GB
Size = (16 × 86400) / 8 / 1024 ≈ 169 GB per day
Size = (500 × 3600) / 8 / 1024 ≈ 219.7 GB
Size = (20 × 10800) / 8 / 1024 ≈ 26.4 GB
Size = (4 × 7200) / 8 / 1024 ≈ 3.5 GB

Four 4K cameras at 25 Mbps each, recording 8 hours:
IT managers use the video storage calculator to estimate how many days or weeks of surveillance footage their hard drives can hold. For example, 10 IP cameras streaming at 12 Mbps each can quickly fill even large NAS arrays. Use the calculator to plan RAID arrays (WD Red Plus, Seagate IronWolf) for redundancy.
YouTubers, Twitch streamers, and filmmakers use the calculator to see how much SSD or HDD space they need for raw footage, especially when shooting in 4K or recording long gameplay sessions. High-bitrate codecs like ProRes or DNxHR can fill a 2TB drive with just a few hours of footage.
Archivists and post-production houses need precise predictions to budget for LTO tape, cloud storage, or large local drives. The calculator helps estimate how much storage is needed for entire seasons of TV or batches of dailies.
Wedding videographers and live event crews need to know how many SD cards or external SSDs to bring. Estimating ahead prevents running out of space during critical moments.

Dev teams use the calculator for storing hours of playtest footage or bug reproduction videos, often across multiple workstations.
Always use the average or maximum bitrate for your codec. Manufacturers often list the maximum supported bitrate, but most recordings use less. If your camera or software uses variable bitrate, round up - variable scenes (like action or explosions) spike usage.
Don’t forget audio. While video streams are the main storage driver, multi-channel audio (like 5.1 surround or uncompressed WAV) can add extra space, especially in professional workflows.
Storage math rarely matches exactly. Filesystem overhead, metadata, and container formats (MP4, MOV, MKV) can add a few percent to the final file size. For critical applications, add a 10-15% buffer.
RAID and NAS configurations add redundancy and sometimes overhead. RAID 5, 6, or 10 setups reserve some usable space for parity. Calculate with your effective storage, not raw drive size.
For long-term archiving, plan for future growth. 4K and 8K workflows are growing. Drives fill up fast at higher resolutions and bitrates. Buy storage with headroom for tomorrow’s demands.
The video storage calculator is a fast, reliable way to estimate how much space your video project will require, whether you’re recording a single video, planning for 24/7 surveillance, or archiving massive production footage. By entering your resolution, codec, bitrate, and duration, you get a clear answer in gigabytes or terabytes - no guesswork, no surprises.
For best results, double-check your camera or software’s real-world bitrate, leave extra storage for audio and system overhead, and always buy a little more than you think you’ll need. Knowing your storage requirements up front saves time, money, and headaches - so you can focus on the footage that matters.
To estimate storage for 4K surveillance, first find the bitrate your camera uses (often 12-25 Mbps for H.265 at 4K). Multiply this by the number of cameras and the total hours per day you record. Use the calculator: enter 3840x2160 resolution, your bitrate, and 24 hours for a daily estimate. Scale up for the number of days you want to keep footage. For example, 16 Mbps × 24 hours × 10 cameras = 1.7 TB per day. Always add 10-15% buffer for real-world overhead.
It depends on the bitrate and codec. With H.264 at 8 Mbps, a 1-hour 1080p video uses about 3.5 GB. The formula: (8 Mbps × 3600 sec) / 8 / 1024 ≈ 3.5 GB. If you use a higher bitrate for better quality, the file will be larger. ProRes or uncompressed formats will use much more space. Always check your camera or software settings for the actual bitrate.
YouTube recommends 8-12 Mbps for 1080p H.264 uploads and 35-45 Mbps for 4K H.264. If your footage is high motion or has lots of detail, use the higher end of the range. H.265 can halve the storage needed at similar quality but check if your editing and playback tools support it. For best upload quality, export at the recommended bitrate, then use the calculator to estimate your file size.
First, determine your bitrate (for example, 8 Mbps for 1080p H.265). Multiply by 604,800 seconds (7 days). So, (8 × 604800) / 8 / 1024 ≈ 592 GB per camera for a week. Multiply by the number of cameras in your system. Always leave extra space for filesystem overhead and unexpected spikes in bitrate.
The calculator estimates storage based on video bitrate and duration, assuming a constant bitrate. In practice, file size can be slightly higher due to audio streams, container overhead (MP4, MOV, MKV), metadata, or variable bitrate fluctuations. Some codecs also add a small overhead. For critical workflows, always add a 10-15% buffer above the calculated value.
Codec choice has a major impact. H.265 (HEVC) offers about twice the compression of H.264 at similar quality, so your files will be half the size at the same bitrate. ProRes and DNxHR are much less compressed and use far more space, but preserve more detail for editing. Always select the codec and bitrate that match your use case - distribution, archiving, or post-production.
Yes. For time-lapse, enter the average bitrate your camera outputs after processing, or estimate based on the final rendered file settings. For slow-motion, use the actual output bitrate, which may be much higher due to increased frame rates. Always check your workflow and use the calculator with those numbers for an accurate estimate.
Audio adds extra data, but usually much less than video. For stereo AAC at 128 kbps, 1 hour uses about 57 MB. For multi-channel or uncompressed WAV, it can be higher. Add the audio bitrate to your total bitrate before calculating, or add 5-10% to the final estimate for typical audio tracks.
For archiving or 24/7 recording, use NAS-rated hard drives like WD Red Plus or Seagate IronWolf. They’re built for reliability and continuous use. SSDs are fast but cost more per TB. For finished projects, consider LTO tape or cloud storage for long-term safety. Always keep backups in separate locations.
Calculate the storage per camera using your chosen resolution, bitrate, and duration. Multiply by the number of cameras to get the total space needed. For example, four 4K cameras at 20 Mbps each recording 8 hours: (20 × 28800) / 8 / 1024 ≈ 70 GB per camera, so 280 GB total. Always add extra for metadata and RAID overhead if using NAS.
Yes, VBR means the bitrate - and file size - fluctuates depending on scene complexity. Use the average bitrate reported by your camera or encoder for estimates. If you expect a lot of high-motion or complex scenes, use the maximum bitrate to avoid underestimating. Actual file size will be between the min and max values.
Absolutely. Find the official bitrate for your chosen codec, resolution, and frame rate (for example, ProRes 422 HQ at 4K30 is about 707 Mbps). Plug that value into the calculator with your duration. ProRes and DNxHR files are large - bring plenty of storage for longer projects.
Assume 1440p capture at 20 Mbps for 2 hours per day over 7 days. Total seconds: 14 hours = 50,400. Size: (20 × 50400) / 8 / 1024 ≈ 123 GB for the week. If you stream and record at once, use the higher of the two bitrates or add both if saving separate files.
MB stands for megabyte (about 1 million bytes), GB is gigabyte (about 1 billion bytes), and TB is terabyte (about 1 trillion bytes). In storage math, 1 GB = 1024 MB, and 1 TB = 1024 GB. When planning video storage, always remember that drive manufacturers often use decimal values (1 TB = 1000 GB), so your actual usable space may be slightly less.
You can, but the calculator is designed for video bitrates, which are much higher than audio. For audio-only, simply enter your audio bitrate (e.g., 320 kbps for MP3) and duration. The result will be accurate, but usually measured in megabytes, not gigabytes, for most music or podcast projects.
8K video uses enormous bitrates, especially in ProRes or RAW. For 8K H.265 at 60 Mbps, 1 hour needs about 27 GB. For ProRes 422 HQ at 8K, the bitrate can exceed 2200 Mbps, so 1 hour is about 990 GB. Always check your camera or encoder’s bitrate chart and use the calculator for a precise estimate.
Free tools to analyze, compare, and optimize your PC gaming performance
Estimate video export and render duration
Use Tool →Estimate 3D and video render duration
Use Tool →Calculate storage needed for games and files
Use Tool →Estimate backup storage requirements
Use Tool →Check if your PC meets the requirements for these popular games
Benchmark data from PassMark and publisher specs. Calculators run locally in your browser — we never upload your hardware info.