A video file is not sized by resolution alone. A short 4K clip can be smaller than a long 1080p recording, and a highly compressed 1080p file can be smaller than a lightly compressed 720p file. The useful quantity is the amount of encoded data used over time: the bitrate.
This article uses a simple estimate so you can plan storage and compare options. Every number below is an illustration, not a platform benchmark or a promise about a specific download.
The basic formula
If you know the average bitrate and the duration, you can estimate the encoded size:
File size in bytes ≈ bitrate in bits per second × duration in seconds ÷ 8.
Divide by 8 because there are eight bits in a byte. The result is an estimate of the media payload. A real file also contains container metadata, possibly multiple tracks and variable-bitrate deviations, so the final size can be somewhat larger or smaller.
When a tool quotes a bitrate in Mbps (megabits per second), convert it to bits per second by multiplying by 1,000,000. When it quotes kbps (kilobits per second), multiply by 1,000. Be careful not to confuse megabits per second (Mbps) with megabytes per second (MB/s): the latter is a data-transfer rate in bytes, eight times larger for the same number.
Illustrative calculations
The following examples use hypothetical average bitrates. They are not claims about what a particular platform or resolution always uses.
| Scenario | Average bitrate | Duration | Estimated size |
|---|---|---|---|
| Short video, moderate bitrate | 5 Mbps | 60 s | 5,000,000 × 60 ÷ 8 = 37,500,000 bytes ≈ 37.5 MB |
| Two-minute video, higher bitrate | 8 Mbps | 120 s | 8,000,000 × 120 ÷ 8 = 120,000,000 bytes = 120 MB |
| Audio-only MP3 | 128 kbps | 180 s | 128,000 × 180 ÷ 8 = 2,880,000 bytes ≈ 2.88 MB |
| Long high-bitrate video | 20 Mbps | 300 s | 20,000,000 × 300 ÷ 8 = 750,000,000 bytes = 750 MB |
The last example exceeds FAST-VID's default 500 MB output limit even though the duration is only five minutes. That is why a high-bitrate quality option can be unavailable or can fail after the final size is measured. A lower quality or audio-only output may fit.
If you know the video and audio bitrates separately, estimate each track and add them. For example, a video track at 6 Mbps plus an audio track at 128 kbps for 60 seconds gives approximately 45 MB plus 0.96 MB before overhead. The combined file is close to 46 MB, but the exact count depends on the encoder and container.
What changes the real file size
Duration
Duration has a direct, linear effect. Double the duration at the same average bitrate and the estimated payload doubles. A long recording can become large even at a modest bitrate.
Bitrate
Bitrate is the main driver in the formula. A higher average bitrate generally means more data and a larger file. A variable-bitrate encode may use more data in complex scenes and less in simple ones, so the average is more useful than a single peak value.
Resolution
Higher resolution gives the encoder more pixels to describe. It often requires a higher bitrate to preserve detail, but the relationship is not fixed. A 4K file encoded at a low bitrate can be smaller than a 1080p file encoded at a high bitrate, though it may show more compression artifacts. The resolution guide and 1080p vs 4K comparison explain the visual trade-off.
Codec
Different codecs compress differently. H.264, H.265, VP9 and AV1 can produce different file sizes at similar perceived quality. A newer codec may be more efficient, but it may also be less compatible with older devices. The compression guide covers codecs and containers.
Frame rate
A higher frame rate provides more frames per second. It can improve motion smoothness, but it also gives the encoder more frames to store. The effect on size depends on how well the codec predicts motion and how much the source changes between frames.
Audio
Audio adds data, especially for long recordings. A stereo track at a higher bitrate is larger than a mono track at a lower bitrate. For a short clip the audio may be a small fraction of the total; for a long audio-only file it is the main component.
Container and metadata
MP4, WebM and other containers add headers, indexes and metadata. The overhead is usually small compared with the media payload, but it means the formula is an estimate rather than an exact file-size prediction.
MB, GB and the binary confusion
Storage is commonly described in decimal units. One kilobyte (kB) is 1,000 bytes, one megabyte (MB) is 1,000,000 bytes, and one gigabyte (GB) is 1,000,000,000 bytes. Those are the SI-style definitions used by many storage manufacturers and by FAST-VID's own megabyte calculation.
Some operating systems and file managers use binary units but still display “MB” or “GB.” In strict binary notation, one mebibyte (MiB) is 1,048,576 bytes and one gibibyte (GiB) is 1,073,741,824 bytes. That difference is why a file described as 500 MB by one tool can appear slightly smaller or larger in another.
For planning, the decimal estimate is close enough: 1 GB is roughly 1,000 MB. But do not expect a 500 MB limit to equal exactly 500 MiB of displayed file size. The unit convention matters at the boundary.
How FAST-VID estimates and limits size
FAST-VID's result card can show an estimated file size when the source exposes enough bitrate and duration information. The estimate is used to mark choices that appear too large. The default output limit is 500 MB; the app treats that as 500,000,000 bytes, following the decimal convention above rather than an unlimited download budget.
An estimate is not a guarantee. A variable-bitrate file may finish above or below the estimate, and a source may not provide a reliable size at all. If the final file exceeds the limit, the job can fail after measurement. Choosing a lower quality or audio-only output is the practical response.
FAST-VID does not manage your local disk after the browser saves the file. It can request the download, but the final copy occupies your device's storage until you delete it. The no-install workflow guide explains the server-to-browser boundary.
Planning storage without false precision
- Use the formula for a rough estimate, then leave a margin for overhead and variable bitrate.
- Estimate video and audio separately when you know both bitrates.
- Check the actual duration before multiplying; a “short” clip can still be several minutes.
- Do not assume 4K is always four times the size of 1080p at the same duration.
- Leave free space for the browser's temporary download and for the final file.
- Move large archives to another drive if internal storage is tight.
A simple rule is better than a false exact number: a high-bitrate video can consume hundreds of megabytes in minutes, while a modest audio file usually consumes only a few megabytes. The formula tells you which case you are in.
Frequently asked questions
How many MB is one minute of video?
There is no single answer. At a hypothetical average bitrate of 8 Mbps, one minute is about 60 MB before overhead. At 2 Mbps it is about 15 MB. Real files vary with codec, resolution, frame rate and encoder settings.
Does 4K always use four times the storage of 1080p?
No. The pixel count is four times larger at 16:9, but storage follows bitrate and duration. A 4K file can be larger, smaller or similar depending on how it was encoded.
Why does my file not match the estimate?
The estimate uses an average bitrate and ignores some overhead. Variable bitrate, multiple tracks, metadata and encoder decisions can make the actual file differ.
Is 500 MB enough for a long video?
It depends on the bitrate. A five-minute file at a hypothetical 20 Mbps would be about 750 MB, which exceeds the limit. A lower bitrate or shorter duration may fit. FAST-VID cannot exceed its configured limit.
Should I use MB or MiB?
Use MB for the decimal estimate in this article: 1,000,000 bytes. If a file manager shows MiB or a binary-based “MB,” the same file may display a different number. The difference is a unit convention, not missing data.
Sources and references
- MDN: Media container formats — containers, tracks and metadata.
- FFmpeg codec documentation — codec and bitrate reference.
- NIST: Metric SI prefixes — decimal unit definitions.
Try FAST-VID
Open the FAST-VID downloader, paste a supported public link and compare the estimated sizes and available formats. Treat every estimate as a planning aid, not a guarantee.