How Much Storage Does Video Use? File Size by Resolution and Duration

Video storage requirements can range from a few hundred megabytes to hundreds of gigabytes. A short compressed clip recorded for social media may be relatively small, while an hour of high-quality 4K production footage can consume a significant portion of a storage drive.

Resolution is important, but it does not determine file size by itself. The most influential factors are bitrate and duration. Frame rate, codec, audio settings, color depth, compression method, and the complexity of the footage also affect the finished file.

As a result, there is no single file size that applies to every 1080p or 4K video.

A practical estimate requires at least two values:

• The total bitrate of the video
• The duration of the recording

Use the Video File Size Calculator when you know the bitrate and duration. If you have a storage limit but do not know which bitrate to use, start with the Video Bitrate Calculator.

---

Quick Video Storage Estimates

The following table uses common H.264 upload bitrates for standard dynamic range video at 24, 25, or 30 frames per second.

The estimates use decimal storage units and represent the video track only. Audio, metadata, subtitles, multiple tracks, and container overhead can make the finished file slightly larger.

These are planning estimates rather than guaranteed output sizes. A variable bitrate export may finish above or below the target depending on the content and encoder.

Uncompressed video, intermediate editing codecs, RAW formats, and professional camera originals can be many times larger than the compressed delivery files shown here.

---

What Determines Video File Size?

The approximate size of a video file is determined by the amount of data used per second and the number of seconds in the recording.

The basic relationship is:

File size = total bitrate × duration ÷ 8

Bitrate is normally expressed in bits per second, while storage is expressed in bytes. Because one byte contains eight bits, the calculation divides the total number of bits by eight.

Total bitrate can include:

• Video bitrate
• Audio bitrate
• Additional audio tracks
• Metadata and container overhead
• Other embedded data streams

For quick calculations, video and audio bitrate provide a sufficiently useful estimate. Container overhead is usually small compared with the video stream, although it should be considered when a strict upload or storage limit applies.

---

Resolution Does Not Directly Determine File Size

It is common to assume that every 4K video is larger than every 1080p video. That is not necessarily true.

A heavily compressed 4K video can have a lower bitrate and smaller file size than a high-bitrate 1080p recording. The 4K file still contains more pixels in each frame, but the encoder may allocate much less data to each pixel.

That does not mean the smaller 4K file will look better. If its bitrate is too low, compression can remove fine detail and create visible artifacts.

Resolution describes the dimensions of the image:

• 720p commonly uses 1280 × 720 pixels
• 1080p commonly uses 1920 × 1080 pixels
• 1440p commonly uses 2560 × 1440 pixels
• 4K UHD commonly uses 3840 × 2160 pixels

Bitrate describes how much data is used per second.

Both values affect quality, but only bitrate and duration allow a direct estimate of compressed file size.

---

How Much Storage Does 720p Video Use?

For a compressed H.264 upload at 24–30 fps, 5 Mbps is a practical reference bitrate for 720p video.

At 5 Mbps, the video track uses approximately:

• 37.5 MB per minute
• 375 MB per 10 minutes
• 1.13 GB per 30 minutes
• 2.25 GB per hour
• 5.4 GB per 2 hours
• 54 GB per 20 hours

A stereo audio track will add to these totals. For example, 384 Kbps audio adds approximately 2.88 MB per minute or 172.8 MB per hour.

At 60 fps, a higher bitrate is generally necessary to maintain similar visual quality. Using 7.5 Mbps for the video track produces approximately:

• 56.25 MB per minute
• 562.5 MB per 10 minutes
• 1.69 GB per 30 minutes
• 3.38 GB per hour

720p remains useful for bandwidth-limited workflows, previews, webinars, remote recordings, and smaller displays. However, small text and detailed interface elements may be harder to preserve than in a 1080p or 1440p source.

---

How Much Storage Does 1080p Video Use?

For standard H.264 uploads at 24–30 fps, 8 Mbps is a useful starting point for 1080p video.

At 8 Mbps, the video portion uses approximately:

• 60 MB per minute
• 600 MB per 10 minutes
• 1.8 GB per 30 minutes
• 3.6 GB per hour
• 7.2 GB per 2 hours
• 86.4 GB per 24 hours

With a 384 Kbps stereo audio track, the combined target bitrate becomes 8.384 Mbps.

A one-hour file would then be approximately:

8.384 × 3,600 ÷ 8 = 3,772.8 MB

The estimated total is approximately 3.77 GB before allowing for minor overhead.

For 1080p at 48–60 fps, a 12 Mbps video bitrate produces approximately:

• 90 MB per minute
• 900 MB per 10 minutes
• 2.7 GB per 30 minutes
• 5.4 GB per hour
• 10.8 GB per 2 hours

The actual bitrate needed depends on motion and visual detail. A static presentation can be compressed more efficiently than gameplay, sports, handheld footage, or a scene containing moving water and detailed foliage.

---

How Much Storage Does 1440p Video Use?

A common 1440p resolution is 2560 × 1440 pixels. It is also called QHD and may be grouped under 2K by some video platforms.

Using a 16 Mbps H.264 reference bitrate for 24–30 fps video produces approximately:

• 120 MB per minute
• 1.2 GB per 10 minutes
• 3.6 GB per 30 minutes
• 7.2 GB per hour
• 14.4 GB per 2 hours

At 60 fps, a 24 Mbps video bitrate produces approximately:

• 180 MB per minute
• 1.8 GB per 10 minutes
• 5.4 GB per 30 minutes
• 10.8 GB per hour
• 21.6 GB per 2 hours

The difference between 30 fps and 60 fps becomes significant when planning storage for long recordings.

For example, 20 hours of 1440p video would require approximately:

• 144 GB at 16 Mbps
• 216 GB at 24 Mbps

These totals exclude audio and overhead.

1440p is often useful for gameplay, interface demonstrations, and desktop recordings because it preserves more detail than 1080p without requiring as much storage as 4K.

---

How Much Storage Does 4K Video Use?

4K UHD contains 3840 × 2160 pixels, which is four times the pixel count of 1920 × 1080 video.

For H.264 uploads at 24–30 fps, a reference range of 35–45 Mbps produces the following approximate sizes.

At 35 Mbps

• 262.5 MB per minute
• 2.63 GB per 10 minutes
• 7.88 GB per 30 minutes
• 15.75 GB per hour
• 31.5 GB per 2 hours

At 45 Mbps

• 337.5 MB per minute
• 3.38 GB per 10 minutes
• 10.13 GB per 30 minutes
• 20.25 GB per hour
• 40.5 GB per 2 hours

For 4K at 48–60 fps, YouTube’s published H.264 upload reference range is 53–68 Mbps.

At 53 Mbps

• 397.5 MB per minute
• 3.98 GB per 10 minutes
• 11.93 GB per 30 minutes
• 23.85 GB per hour

At 68 Mbps

• 510 MB per minute
• 5.1 GB per 10 minutes
• 15.3 GB per 30 minutes
• 30.6 GB per hour

A 60-minute 4K60 export can therefore occupy approximately 24–31 GB at these reference video bitrates before audio and overhead are added.

Camera originals and professional editing formats can be substantially larger. Do not use compressed upload estimates to plan storage for RAW video, ProRes masters, multicamera productions, or other acquisition formats.

---

Video File Size at 60 fps

Higher frame rates usually increase storage requirements because the encoder must process more frames every second.

A 60 fps recording contains twice as many frames as a 30 fps recording of the same duration. The bitrate does not always need to double because consecutive frames may contain similar information, but more data is generally required to preserve comparable quality.

The following estimates compare standard and high-frame-rate upload references.

Use 60 fps when smoother motion provides a meaningful benefit, such as sports, gameplay, action footage, and rapid camera movement.

For interviews, lectures, podcasts, presentations, and other relatively static content, 24–30 fps can reduce storage requirements while remaining appropriate for the material.

---

How Audio Affects Video File Size

A video file can contain one or more audio streams. Each stream has its own bitrate and contributes to the final file size.

YouTube’s upload recommendations include:

• Mono audio: 128 Kbps
• Stereo audio: 384 Kbps
• 5.1 surround audio: 512 Kbps

The approximate storage used by a single audio track is:

Audio is a relatively small part of a high-bitrate 4K file, but it can be more noticeable in long recordings or low-bitrate video.

Multiple language tracks, commentary tracks, isolated microphone recordings, and surround audio should each be included in a detailed storage estimate.

---

How the Video Codec Changes Storage Requirements

A codec compresses the video data. Different codecs can produce different file sizes and visual quality at the same resolution.

H.264

H.264, also called AVC, is widely supported by video platforms, browsers, editing applications, and playback devices.

It remains a practical choice for:

• Online video uploads
• General-purpose MP4 files
• Client delivery
• Broad device compatibility
• Workflows that require predictable playback

H.264 is the basis of the example storage tables in this article.

H.265

H.265, also called HEVC, is designed to provide more efficient compression than H.264. Depending on the encoder and source material, it may preserve similar perceived quality at a lower bitrate.

A lower bitrate produces a smaller file, but there are tradeoffs:

• Encoding may take longer
• Editing can require more processing power
• Hardware support varies
• Some software and devices may have compatibility limitations
• Platform behavior can differ

H.265 is often considered for 4K, HDR, delivery to supported devices, and space-limited archives.

AV1

AV1 is another modern compression format designed for efficient video delivery. It can reduce bandwidth and storage requirements, but encoding performance and compatibility depend on the software, hardware, and destination platform.

Newer graphics processors and devices may provide hardware acceleration, while older systems may encode or decode AV1 more slowly.

ProRes and Other Editing Codecs

Apple ProRes and similar intermediate codecs are designed for production and editing rather than minimal file size.

They preserve more image information and are easier for editing systems to process, but the resulting files can be much larger than H.264, H.265, or AV1 delivery files.

A compressed 1080p upload may use only a few gigabytes per hour, while a high-quality intermediate recording at the same resolution can use tens or hundreds of gigabytes.

Always distinguish between:

• Camera recording format
• Editing format
• Master archive
• Upload file
• Streaming output
• Viewer playback file

They serve different purposes and should not be expected to have the same size.

---

CBR and VBR File Sizes

Bitrate control affects how closely the finished file matches a simple calculation.

Constant Bitrate

Constant bitrate, or CBR, attempts to maintain a consistent data rate.

With a true 8 Mbps total bitrate, a one-hour file should be close to:

8 × 3,600 ÷ 8 = 3,600 MB

CBR is commonly used for live streaming and systems that require a predictable data rate.

However, actual files can still differ because of:

• Audio
• Container overhead
• Encoder behavior
• Bitrate limits
• Metadata
• Temporary rate variation

Variable Bitrate

Variable bitrate, or VBR, allocates different amounts of data to different scenes.

A static scene may use less data, while a fast or detailed scene may use more. The target bitrate represents an average goal rather than an exact rate for every second.

Because of this variation, a VBR export can finish smaller or larger than a basic estimate.

Two-pass VBR can analyze the content before completing the final encode. This may distribute the available data more efficiently, especially when there is a target file size.

When the upload limit is strict, leave a safety margin rather than setting the calculated bitrate to the exact maximum.

---

Why Two Videos with the Same Settings Can Have Different Sizes

Two exports can use the same resolution, frame rate, codec, duration, and nominal quality preset yet still have different sizes.

The difference may result from content complexity.

Video that is relatively easy to compress includes:

• A speaker in front of a plain wall
• Static slides
• Simple animation
• A locked camera shot
• Large areas of consistent color
• Limited movement

Video that is difficult to compress includes:

• Fast action
• Detailed gameplay
• Moving water
• Smoke or fog
• Confetti
• Snowfall
• Dense foliage
• Film grain
• Low-light sensor noise
• Camera shake
• Rapid scene changes

A quality-based encoder may assign substantially more data to the second group. The result is a larger file, even when the duration and resolution are unchanged.

This is one reason resolution-based storage charts should be treated as planning references rather than guarantees.

---

How Color Depth and HDR Affect File Size

Standard video commonly uses 8-bit color, while HDR and professional workflows may use 10-bit or 12-bit color.

Higher color depth can represent more tonal information and may reduce visible banding in gradients. However, it can also increase processing and storage requirements, especially when combined with:

• Higher resolutions
• Higher frame rates
• Less aggressive compression
• Chroma sampling such as 4:2:2 or 4:4:4
• Professional acquisition codecs

YouTube accepts specified 10-bit and 12-bit formats for HDR uploads and recommends higher H.264 bitrates for HDR than for comparable SDR uploads.

A 4K HDR file should therefore not automatically be expected to match the size of a basic 4K SDR file.

For storage planning, use the actual export bitrate whenever possible instead of estimating from the HDR label alone.

---

Decimal Gigabytes vs. Binary Gibibytes

Storage calculations can appear inconsistent because decimal and binary units are both used.

In decimal units:

• 1 KB = 1,000 bytes
• 1 MB = 1,000,000 bytes
• 1 GB = 1,000,000,000 bytes

In binary units:

• 1 KiB = 1,024 bytes
• 1 MiB = 1,048,576 bytes
• 1 GiB = 1,073,741,824 bytes

Drive manufacturers commonly advertise capacity using decimal units. Operating systems and applications may display storage differently.

A calculated 10 GB decimal file is approximately 9.31 GiB.

This difference does not mean data is missing. It is a difference in the units used to represent the same number of bytes.

When working with strict upload limits, verify whether the platform defines MB and GB using decimal or binary units.

---

How to Calculate Video File Size Manually

Use the following process when the bitrate is measured in Mbps and the duration is measured in seconds.

Step 1: Add Video and Audio Bitrates

Suppose the video bitrate is 12 Mbps and the audio bitrate is 384 Kbps.

Convert audio to Mbps:

384 Kbps = 0.384 Mbps

Add the two:

12 + 0.384 = 12.384 Mbps

Step 2: Convert the Duration to Seconds

For a 30-minute video:

30 × 60 = 1,800 seconds

Step 3: Multiply Bitrate by Duration

12.384 × 1,800 = 22,291.2 megabits

Step 4: Convert Bits to Bytes

22,291.2 ÷ 8 = 2,786.4 MB

The estimated file size is approximately 2.79 GB in decimal units.

Use the Video File Size Calculator to perform this conversion without manually changing the units.

---

How to Calculate a Bitrate from Available Storage

The calculation can also be reversed when the storage capacity and duration are known.

The formula is:

Total bitrate = available file size in bits ÷ duration in seconds

Suppose a file must remain below 2 GB and has a duration of 30 minutes.

Convert the storage limit:

2 GB = 16,000 megabits

Convert the duration:

30 minutes = 1,800 seconds

Calculate the total bitrate:

16,000 ÷ 1,800 = approximately 8.89 Mbps

If the audio bitrate is 0.384 Mbps:

8.89 − 0.384 = approximately 8.51 Mbps

The theoretical video bitrate is about 8.51 Mbps. However, setting the export to exactly that value could exceed the limit because of overhead or encoder variation.

A slightly lower target provides a safer result.

Use the Video Bitrate Calculator to calculate the available video bitrate from a duration and file-size limit.

---

How Many Hours of Video Fit on a Storage Drive?

The following table estimates how many hours fit on a drive using video bitrate only. Real capacity will be slightly lower after formatting, audio, overhead, other files, and operating-system differences are considered.

Do not fill a production drive to its absolute limit. Editing software, cache files, proxy media, project backups, exports, and temporary renders require additional space.

A reliable workflow also needs backup capacity rather than a single copy of each recording.

---

Planning Storage for a Video Project

A production usually requires more storage than the size of the final video.

For example, a 20-minute finished video may involve:

• Several hours of camera footage
• Multiple cameras
• Separate audio recordings
• Screen captures
• Graphics and animations
• Proxy files
• Render cache
• Project files
• Draft exports
• The final master
• The compressed upload file
• One or more backups

A useful planning formula is:

Total project storage = source media + working files + exports + backups

If a project records three cameras for two hours, calculate all six camera-hours rather than only the duration of the final edit.

If each camera records approximately 30 GB per hour:

3 cameras × 2 hours × 30 GB = 180 GB

That is only the original camera media. It does not include proxies, cache, audio, graphics, exports, or backups.

---

Local Recording and Live Streaming Need Separate Estimates

A live-streaming bitrate is not necessarily the bitrate used for the local recording.

A creator might transmit a 1080p stream at a platform-compatible bitrate while recording a higher-quality copy locally. The local recording may use:

• A higher bitrate
• A quality-based recording mode
• A different codec
• Multiple audio tracks
• A higher resolution
• A less compressed editing format

If a two-hour stream is transmitted at 10 Mbps but recorded locally at an average of 40 Mbps, the local file will be approximately four times larger before audio and overhead are considered.

Always calculate storage from the local recording settings, not only the streaming settings.

---

How to Reduce Video File Size

Reducing file size usually involves a tradeoff between quality, compatibility, processing time, and storage.

Lower the Bitrate

Lowering bitrate directly reduces file size. This is usually the most predictable method.

Reduce it gradually and inspect:

• Fast movement
• Fine textures
• Small text
• Gradients
• Dark scenes
• Film grain
• Particle effects

Use a More Efficient Codec

H.265 or AV1 may produce a smaller file than H.264 at a similar perceived quality. Confirm compatibility with the destination device, editor, client, and platform before changing codecs.

Reduce the Resolution

Changing from 4K to 1080p can substantially reduce the bitrate needed for acceptable quality. This may be appropriate when the audience does not require 4K delivery.

Reduce the Frame Rate

Changing from 60 fps to 30 fps can reduce storage requirements, but only do this when the lower frame rate is suitable for the content.

Remove Unnecessary Tracks

Delete unused audio tracks, duplicate streams, embedded previews, or other data that does not need to remain in the delivery file.

Trim Unused Footage

Duration directly affects file size. Removing unnecessary footage reduces storage without lowering the quality of the remaining video.

Export from the Original Project

If possible, re-export from the original editing timeline. Repeatedly compressing an already compressed file can reduce quality even when the new file uses a relatively high bitrate.

---

Common Video Storage Mistakes

Estimating from Resolution Alone

Resolution does not reveal the actual bitrate. Check the recording or export settings before planning storage.

Confusing Mbps and MB/s

Mbps means megabits per second. MB/s means megabytes per second.

Because eight bits equal one byte:

8 Mbps = approximately 1 MB/s

A 40 Mbps video therefore uses approximately 5 MB per second before audio and overhead.

Forgetting Audio

Audio may be small compared with 4K video, but it still contributes to the total. Multiple tracks can make the difference more noticeable.

Ignoring Source Footage

The final upload may be 3 GB, while the camera originals occupy 300 GB. Production storage should be based on the acquisition workflow.

Assuming Drive Capacity Is Fully Available

A drive advertised as 1 TB may display a lower numerical capacity in an operating system because of decimal and binary unit differences. Formatting and existing files also reduce available space.

Leaving No Space for Editing

Video editors generate previews, cache, proxies, autosaves, and temporary files. A nearly full drive can reduce performance and interrupt exports.

Keeping Only One Copy

A single storage device is not a backup. Hardware failure, accidental deletion, file corruption, theft, or physical damage can destroy the only copy.

---

Frequently Asked Questions

How large is one hour of 1080p video?

At an 8 Mbps video bitrate, one hour uses approximately 3.6 GB before audio and overhead. At 12 Mbps, it uses approximately 5.4 GB.

Camera originals or editing formats may be much larger.

How large is one hour of 4K video?

At 35 Mbps, one hour uses approximately 15.75 GB. At 45 Mbps, it uses approximately 20.25 GB. A 4K60 video at 68 Mbps uses approximately 30.6 GB per hour.

How much storage does a 10-minute 1080p video use?

At 8 Mbps, the video track uses approximately 600 MB. Adding a 384 Kbps audio track increases the estimate to about 629 MB before minor overhead.

How much storage does a 10-minute 4K video use?

At 35 Mbps, approximately 2.63 GB is required. At 45 Mbps, the estimate is approximately 3.38 GB. Higher-frame-rate or professional formats may be considerably larger.

Does 4K use four times more storage than 1080p?

Not automatically. 4K contains four times as many pixels as 1080p, but compressed file size depends on bitrate and duration. The bitrate does not have to increase in direct proportion to pixel count.

Does 60 fps double the file size?

Only if the bitrate also doubles. A 60 fps video typically needs a higher bitrate than a 30 fps video, but the exact increase depends on the codec, encoder, content, and quality target.

Why is my exported video larger than the estimate?

The file may include audio, multiple tracks, metadata, overhead, or a higher actual average bitrate. Variable bitrate encoding can also produce an output that differs from the target.

Why is my exported video smaller than the estimate?

A variable or quality-based encoder may use less data for simple content. Some applications also interpret target and maximum bitrate settings differently.

Can I calculate file size without knowing the bitrate?

You can use a rough resolution-based estimate, but it will not be reliable. The bitrate or a known recording profile is needed for a meaningful calculation.

Is video file size based on upload speed?

No. Upload speed affects how long the transfer takes, not the size of the file. A 10 GB video remains 10 GB whether the connection is fast or slow.

How long will a video take to upload?

The approximate relationship is:

Upload time = file size in bits ÷ upload speed

Real uploads usually take longer because of network overhead, speed variation, congestion, and platform processing.

---

Final Storage Recommendations

Use bitrate and duration as the foundation of every video storage estimate.

For compressed H.264 uploads at 24–30 fps, these values provide useful starting points:

• 720p at 5 Mbps: approximately 2.25 GB per hour
• 1080p at 8 Mbps: approximately 3.6 GB per hour
• 1440p at 16 Mbps: approximately 7.2 GB per hour
• 4K at 35–45 Mbps: approximately 15.75–20.25 GB per hour

Higher frame rates, HDR, multiple audio tracks, less compressed codecs, and professional acquisition formats can increase storage requirements.

Before starting a project:

1. Identify the recording codec and bitrate.
2. Add the duration of every camera and recording source.
3. Include all audio tracks.
4. Allow space for proxies, cache, projects, and exports.
5. Reserve additional capacity for backups.
6. Test the real recording profile before a long production.

Use the Video File Size Calculator for an immediate estimate based on bitrate and duration.

For help choosing the bitrate, read What Video Bitrate Should You Use for 1080p, 1440p, and 4K? or calculate a value with the Video Bitrate Calculator.