DislifyDislify

Command Palette

Search for a command to run...

All articles
GuidesVideo CompressionBitrateFile CompressionMedia Optimization

What Is Video Bitrate? How It Affects File Size and Quality

Learn what video bitrate means, how it affects file size and visual quality, and why lowering bitrate is often one of the best ways to make videos smaller.

By jack chynaAug 20, 20267 min read8 views
Dislify blog cover illustrating video bitrate with a video player, bitrate slider, estimated file size, and quality impact chart.

What Is Video Bitrate? How It Affects File Size and Quality

If two videos have the same resolution and duration, why can one be 40 MB while the other is 300 MB?
A big part of the answer is bitrate.
Bitrate controls how much data a video uses over time. It has a major effect on file size, visual quality, upload speed, and how aggressively a video can be compressed.
Understanding bitrate makes it much easier to figure out why a video is large and how to shrink it without destroying the quality.

What is video bitrate?

Video bitrate is the amount of data used to represent one second of video.
It is commonly measured in:
Kbps — kilobits per second
Mbps — megabits per second
For example, a video encoded at:
8 Mbps
uses roughly 8 megabits of video data every second.
A higher bitrate gives the encoder more data to preserve detail.
A lower bitrate uses less data, which usually produces a smaller file.
That means bitrate directly affects the tradeoff between:
file size and visual quality.

Higher bitrate usually means a larger file

Imagine two 1080p videos that are both five minutes long.
One is encoded at 4 Mbps.
The other is encoded at 20 Mbps.
Even though both videos have the same resolution and duration, the 20 Mbps version can be several times larger because it stores much more data every second.
This is why simply looking at resolution is not enough when trying to understand file size.
A 1080p video can sometimes be larger than a 4K video if its bitrate is unusually high.

Why do videos use high bitrates?

High bitrates are not automatically bad.
More bitrate can help preserve details in scenes containing:
Fast movement
Gameplay
Particle effects
Foliage
Water
Detailed textures
Screen recordings with small text
Frequent scene changes
When a scene changes quickly, the encoder has more information to represent.
Giving the encoder more bitrate can help avoid visible compression artifacts.
The problem is that many videos are exported with more bitrate than they actually need.

Why screen recordings can become huge

Screen recording software often prioritizes quality while capturing your screen.
That makes sense while recording, but the resulting file can be much larger than necessary for sharing.
For example, a screen recording may capture:
1440p resolution
60 FPS
High video bitrate
High-quality audio
Very little compression
The recording may look excellent, but sending it through Discord, email, or another platform can become difficult because of the file size.
Re-encoding the video with a more reasonable bitrate can dramatically reduce the file size while keeping the recording clear.

Bitrate is different from resolution

Resolution describes the dimensions of the video.
Common examples include:
720p
1080p
1440p
4K
Bitrate describes how much data is used to represent those pixels over time.
The two are related, but they are not the same thing.
You can have:
High resolution with a low bitrate
High resolution with a high bitrate
Low resolution with a high bitrate
Low resolution with a low bitrate
That is why reducing resolution is not always the first thing you should do when trying to make a video smaller.
Sometimes lowering the bitrate is enough.

Bitrate and frame rate

Frame rate also affects how much information the encoder needs to process.
A 60 FPS video contains twice as many frames per second as a 30 FPS video.
For fast-moving gameplay, 60 FPS may be worth keeping.
For slower content such as:
Tutorials
Talking-head videos
Screen demonstrations
Memes
Casual clips
30 FPS may be perfectly acceptable.
Lowering both frame rate and bitrate can produce a much smaller file when high frame rates are unnecessary.

Constant bitrate vs variable bitrate

You may also encounter two common bitrate strategies:

Constant bitrate

Constant bitrate, or CBR, tries to use roughly the same bitrate throughout the entire video.
It can be useful when predictable bandwidth is important.
However, simple scenes may receive more data than they actually need.

Variable bitrate

Variable bitrate, or VBR, allows the encoder to use different amounts of data depending on the complexity of each scene.
A simple scene might use less data.
A fast or detailed scene might use more.
This can often provide a better balance between quality and file size.

Can you calculate video file size from bitrate?

You can estimate it.
A simplified calculation is:
File size ≈ bitrate × duration
You also need to account for audio and some container overhead, but bitrate gives you a useful approximation.
For example, reducing a video from:
12 Mbps
to:
6 Mbps
can roughly cut the video portion of the file size in half.
The exact result depends on the encoder, codec, audio settings, and video content.

How low should you set the bitrate?

There is no single perfect bitrate for every video.
The right value depends on:
Resolution
Frame rate
Video complexity
Codec
Desired quality
Target file size
Where the video will be uploaded
Lowering bitrate too aggressively can introduce artifacts such as:
Blockiness
Blurred textures
Smearing during movement
Loss of fine detail
Hard-to-read text
The goal is not simply to use the lowest bitrate possible.
The goal is to use only as much data as the video actually needs.

Why modern codecs matter

Bitrate does not tell the entire story.
Different codecs can produce very different quality at the same bitrate.
Common codecs include:
H.264
H.265 / HEVC
VP9
AV1
Newer codecs can often achieve similar visual quality using less data.
However, compatibility also matters.
H.264 remains widely supported across browsers, devices, messaging applications, and media players, making it a practical option for many sharing workflows.

How Dislify handles video compression

You do not necessarily need to calculate bitrate manually.
Dislify is designed to process media using compression presets and target-based workflows.
You can upload your video and choose how aggressively you want it optimized.
Depending on the workflow, compression can adjust factors such as:
Video bitrate
Resolution
Audio bitrate
Encoding quality
Output format
Target file size
Dislify then processes the file through its media worker and returns the optimized result.
For situations where a platform has a strict upload limit, you can also target a specific output size rather than experimenting with export settings repeatedly.

When should you lower bitrate?

Lowering bitrate is especially useful when:
Your video looks fine but the file is unusually large
You need to meet an upload limit
You are sharing gameplay clips
You are sending videos through Discord
You want faster uploads
You are reducing storage usage
You are preparing media for a website or application
It is often one of the most effective ways to reduce video size without immediately lowering the resolution.

Final thoughts

Video bitrate determines how much data is used every second of your video.
More bitrate can preserve additional detail, but it also increases file size.
Less bitrate creates smaller files, but reducing it too far can noticeably damage quality.
Good compression is about finding the point where the video still looks right while removing data that does not need to be there.
Instead of guessing export settings repeatedly, you can use Dislify to compress the video, choose a preset or target size, and let the processing pipeline handle the optimization.
Compress your next video with Dislify and keep the quality where it matters.

Comments

Share your thoughts or questions about this article.

Ready when you are

Put the guide into practice.

Compress a file in the workspace or connect Dislify to your product through the API.