When a video file is large, it is tempting to assume that lowering the resolution will fix it, or that switching to a newer codec will automatically cut the size in half. Those ideas can help, but the most direct driver of file size is how much data the video uses over time.

As a rough rule, video size is driven by average total bitrate multiplied by duration. Resolution, frame rate, codec, motion, and visual detail mainly affect how much quality you can preserve at a given bitrate. Understanding that relationship explains why two 1080p videos can differ greatly in size, and why changing 4K to 720p does not always shrink a file as much as expected.

Four axes that explain video size

Duration

How long the video runs

At the same average bitrate, doubling the duration roughly doubles the data size. Removing unneeded duration is one of the most direct ways to reduce size.

Bitrate

How many bits are used per second

This is the most direct rate-based driver of size. A higher average bitrate produces more data over the same duration and generally gives the encoder more room to preserve quality.

Resolution / FPS

How much visual information must be represented

More pixels and more frames usually require more data to preserve similar visual quality, but they do not directly set the final file size.

Codec / Content

How efficiently the video can be compressed

Codec, encoder settings, motion, noise, and fine detail all change compressibility. Two videos with the same dimensions and duration may need different bitrates for similar quality.

Start with average bitrate multiplied by duration

Bitrate describes how many bits are used per second. If a 60-second video has an average total bitrate of 10 Mbps including video and audio, a simple estimate is 10 × 60 ÷ 8 ≈ 75 MB. A real file also contains container overhead and metadata, so the result is not exact, but it is a useful way to understand the scale.

The word average matters. With variable bitrate (VBR), simple scenes may use fewer bits while motion or fine detail uses more. A target shown by an encoder therefore does not always match the final average or exact file size.

Approximate size of a 60-second video from average total bitrate alone
Average total bitrateApprox. size for 60 seconds
2 Mbpsabout 15 MB
5 Mbpsabout 37.5 MB
10 Mbpsabout 75 MB
20 Mbpsabout 150 MB

Why lowering resolution often reduces size

4K contains far more pixels than 1080p and therefore has more visual detail to represent in each frame. To preserve a similar perceived quality, higher-resolution video generally needs a higher bitrate, which is why 4K files often end up larger in practice.

But lowering resolution does not automatically reduce file size by the same ratio. If both 4K and 720p versions are encoded at 10 Mbps for the same duration, their sizes can remain similar. What changes is how those 10 million bits per second are distributed across the pixels, so the lower-resolution version usually has more bits available per pixel while the higher-resolution version is more vulnerable to compression artifacts.

Frame rate works similarly: high fps does not directly set file size

Moving from 30 fps to 60 fps doubles the number of frames represented each second. That can improve motion smoothness for sports, games, or fast action, but it generally requires more bits to preserve comparable visual quality.

If the output is fixed at the same 5 Mbps, however, 30 fps and 60 fps versions of the same duration can have similar file sizes. The 60 fps version simply has fewer bits available per frame. Resolution and frame rate are therefore best understood together with the bitrate needed to maintain the desired quality.

A codec changes how much quality fits into a given bitrate

H.264, HEVC (H.265), VP9, and AV1 are codecs that define ways to compress video. A more efficient codec or encoder configuration may preserve similar visual quality at a lower bitrate. That is where a codec can translate into a smaller file for the same quality target.

Simply changing H.264 to AV1 while keeping the same bitrate and duration does not make the file dramatically smaller. At an average 5 Mbps, either codec still produces roughly five megabits of media data per second. The difference is how much visual quality each can preserve within that budget.

Codec choice also affects playback compatibility and encoding cost. Compression efficiency alone does not make one codec universally best.

The content itself changes how many bits are needed

A mostly static slide deck is much easier to compress than leaves, water, confetti, camera shake, or fast motion. Video codecs save data by exploiting similarities within a frame and across nearby frames, so scenes that change less can often be represented with fewer bits.

Noise and film grain also make compression harder. With quality-oriented variable-rate encoding, complex footage may receive more bits than simple footage, so files can differ in size even when duration, resolution, and frame rate are the same. That is one reason there is no universal “1080p 60 fps equals X MB” rule.

MP4 is a container, not a codec, and audio also counts

The `.mp4` extension identifies a container that can hold video, audio, and other tracks. MP4 can carry video encoded with H.264, HEVC, AV1, and other codecs, so “MP4” alone does not determine quality or size. Two MP4 files can differ greatly because their codecs and bitrates differ.

Audio also contributes to the total. A file with 5 Mbps video and 128 kbps audio has a simplified total average bitrate of about 5.128 Mbps. The audio contribution becomes more noticeable as duration grows. Subtitles, chapters, metadata, and container structures add some overhead too, although video and audio bitrate usually dominate normal video file size.

When reducing size, identify which tradeoff is actually changing

There is more than one way to make a video smaller. Trimming removes duration. Lowering average bitrate reduces the amount of data used each second. Lowering resolution or frame rate can make acceptable quality easier to achieve at a lower bitrate. A more efficient codec can sometimes preserve comparable quality with fewer bits.

Each choice has a tradeoff. Lower bitrate can introduce more artifacts, lower resolution removes detail, and lower frame rate reduces motion smoothness. Newer codecs can have narrower playback support or longer encoding times. The practical goal is not the smallest possible file, but a balance between size, acceptable quality, compatibility, and processing time for the intended use.

Four checks for understanding a video file's size

When you want to understand why a video is large, these four checks are more useful than looking at resolution alone.

  1. Check durationAt the same settings, a longer video produces more data. Start with the duration to establish the scale of the file.
  2. Check average bitrateAverage bitrate across video and audio is the most direct rate-based driver of size. Total bitrate × duration ÷ 8 gives a useful estimate.
  3. Check resolution and frame rate4K / 1080p / 720p and 30 / 60 fps affect the bitrate needed for comparable quality. At the same bitrate, size can remain similar while quality headroom changes.
  4. Check codec and contentCompression efficiency differs among H.264, HEVC, VP9, and AV1, and content such as motion, noise, and fine texture changes how hard the footage is to compress. Quality-oriented VBR can therefore produce different final sizes.
Try it in Browser Kitty

Video Compressor

Compress video in your browser with resolution and bitrate controls.

Open toolView tool details

Tips and limitations

  • A useful way to think about 4K is that preserving good 4K quality often requires a higher bitrate, which tends to make the resulting file larger.
  • With the same duration and average bitrate, files can be roughly similar in size even when resolution or codec differs. The main difference is usually quality and compression efficiency.
  • With VBR or quality-targeted encoding, the same settings can produce different average bitrates and final sizes depending on the footage.
  • MP4 and WebM are container names. When judging size and compatibility, also inspect the video and audio codecs inside them.
  • Trimming unwanted duration can reduce size without lowering the quality of the kept frames, so it is a different option from recompressing the video.

Frequently asked questions

Is a 4K video always larger than a 1080p video?

Not necessarily. With the same duration and average total bitrate, sizes can be similar. In practice, 4K usually needs a higher bitrate to preserve comparable visual quality because it contains more pixels, so 4K files often end up larger.

If I halve the resolution, will the file size also halve?

Not automatically. If the encoder keeps the same output bitrate, file size may change very little. Lowering resolution can make it easier to maintain acceptable quality at a lower bitrate, and that lower bitrate is what reduces size.

Will AV1 always make a smaller file than H.264?

Not automatically. At the same bitrate, file sizes remain roughly similar. AV1 can be advantageous when it reaches acceptable quality at a lower bitrate than H.264, but results depend on the content, encoder, settings, and playback compatibility requirements.

Why can two 1080p videos of the same duration have very different sizes?

They can differ in average bitrate, frame rate, codec, audio bitrate, VBR behavior, motion, and noise. 1080p describes the frame dimensions; it does not specify how many bits are used each second.

Why does the actual file size differ from the bitrate estimate?

With VBR, the final average may differ from the target. Audio, container structures, and metadata also contribute. The estimate also changes depending on whether the bitrate you are looking at is video-only or the combined total for video and audio. Differences between units such as MB and MiB can also make the displayed number look slightly different.

References

The discussion of compression, bitrate, resolution, content complexity, and the difference between containers and codecs is based on the following official documentation. This article intentionally avoids fixed codec-to-codec savings percentages because results vary with content, encoder, and configuration.