Calculator
Formula used
First, convert bitrate to bits per second and duration to seconds. Then compute:
Divide by 8 because one byte contains eight bits.
How to use
- Pick the calculator mode that matches your goal.
- Enter bitrate and duration, or file size and duration.
- Add overhead if you expect container or protocol extras.
- Choose decimal or binary units for readable results.
- Press Calculate to see results above this form.
Example data
| Bitrate | Duration | Overhead | Estimated size (decimal) |
|---|---|---|---|
| 128 Kbps | 00:03:30 | 0% | 3.36 MB |
| 2.5 Mbps | 00:10:00 | 3% | 193.13 MB |
| 5 Mbps | 01:00:00 | 2% | 2.30 GB |
| 25 Mbps | 00:30:00 | 5% | 5.91 GB |
These rows are illustrative and may vary by encoding settings.
Bitrate, time, and size in practice
Bitrate expresses how many bits are produced each second. When you multiply bitrate by duration, you get total bits. Dividing by eight converts bits into bytes, which storage devices report. For example, 5 Mbps for 60 minutes is roughly 2.25 GB before overhead, assuming decimal units. This calculator standardizes units first, so mixed inputs like “2.5 Mbps” and “00:10:00” still produce consistent totals.
Choosing the right unit system
File sizes are shown in decimal (KB/MB/GB) or binary (KiB/MiB/GiB) terms. Decimal uses powers of 1000 and matches most network and encoder bitrate labels. Binary uses powers of 1024 and often matches operating system file explorers. The difference grows with larger files: a “1 GB” decimal file is about 0.93 GiB. Switching the display system helps you align estimates with your reporting tools.
Understanding overhead and container growth
Real files are rarely pure payload. Containers, headers, indexing, encryption, and transport framing can add overhead. A small percent is common for formats with metadata or for streaming protocols. Use the overhead field as a buffer when you need safer planning numbers. If you know your workflow, set overhead based on measured samples. If you do not, start with 2–5% for conservative estimates.
Using results for bandwidth and storage planning
Storage planning is simplest when you estimate per-item size and then scale. Multiply one-hour size by episode count, course modules, or archive days. For delivery planning, compare the file size against your upload window and throughput. If your upstream is 20 Mbps, a 5 GB upload typically takes about 35 minutes in ideal conditions, but longer with congestion. Exporting CSV or PDF keeps the assumptions documented.
Reverse calculations for target quality
Sometimes you have a fixed file size limit, such as an email attachment or platform cap. In reverse mode, the calculator estimates the bitrate required to fit that limit for a given duration, after overhead. This is useful for picking encoder settings, setting ABR ladder targets, or sizing camera proxies. Treat the result as an average bitrate goal, then validate by encoding a short segment first.
FAQs
What inputs can I use for duration?
Enter HH:MM:SS, MM:SS, or a numeric value with a unit. When you use a time format, the unit selector is ignored and the calculator converts the time directly into seconds.
Should I choose decimal or binary units?
Use decimal when comparing to bitrates and network speeds. Use binary when matching operating system file sizes. The calculator can show both so you can reconcile encoder labels with disk reporting.
What does overhead represent?
Overhead is an added percentage for containers, headers, metadata, encryption, and transport framing. If you are unsure, start with 2–5% as a safety margin and refine it from real exported files.
How accurate is this for variable bitrate media?
For VBR content, accuracy depends on the average bitrate. Use the average from your encoder stats or a media inspector. The formula still applies; the bitrate value simply represents the mean rate over the whole duration.
Can I estimate streaming data usage?
Yes. Use the bitrate and total watch time as duration, then include protocol overhead if needed. Compare the resulting size to your data cap to estimate expected consumption for a session or a month.
How does reverse mode help encoding?
Reverse mode finds an average bitrate that fits a size limit for your duration and overhead. Use it as a target setting, then test-encode a sample to confirm quality and container behavior before processing everything.