To estimate a video’s file size, multiply its average combined audio-and-video bitrate by its runtime in seconds, then divide by eight to convert bits to bytes. The result is an estimate, not an exact prediction: it depends on the bitrate you start with and does not account separately for container overhead or metadata.
If you know only the video bitrate, add the audio bitrate before calculating the size of the complete file. Keep decimal MB and binary MiB distinct, and use the estimate to plan storage or transfers rather than to promise an exact upload size.
The file-size formula
The basic formula is:
Estimated size in bytes = average bitrate in bits per second × runtime in seconds ÷ 8
Bitrate describes how much encoded data is produced per unit of time. If an audio-and-video file averages 4,000,000 bits per second for 600 seconds, the calculation is 4,000,000 × 600 ÷ 8 = 300,000,000 bytes. The division by eight converts bits into bytes, since one byte contains eight bits.
The units need to match the formula. Use bits per second (bps) for bitrate and seconds for runtime. A bitrate written in megabits per second (Mbps) must be converted to bits per second before calculating bytes, unless you deliberately carry the units through and make the conversions explicit. For example, 8 Mbps is 8,000,000 bits per second under decimal SI prefixes.
For a duration in minutes, multiply by 60 to get seconds; for hours, multiply by 3,600. A 12-minute duration is 720 seconds. If you skip this conversion, the answer will be out by a factor of 60. YouTube’s API documentation represents video duration in milliseconds and documents uploaded-file size in bytes, so convert duration into seconds before applying the formula. The video resource documentation is useful when you are comparing an estimate with metadata for an uploaded file.
This calculation estimates the media data implied by the bitrate and duration you supply. It cannot be more precise than those inputs. If the bitrate is a rounded setting, or an average based on a short sample, the resulting size will carry that uncertainty forward.
Bits, bytes, MB and MiB
Bitrate is usually expressed in bits per second, while file size is commonly shown in bytes. First divide by eight to get bytes. Then choose whether to express the result in decimal megabytes (MB) or binary mebibytes (MiB).
| Unit | Conversion from bytes | Example: 628,800,000 bytes |
|---|---|---|
| MB (decimal) | Divide by 1,000,000 | 628.8 MB |
| MiB (binary) | Divide by 1,048,576 | About 599.8 MiB |
These are different units, not alternative spellings for the same quantity. The decimal MB is larger than the binary MiB, so the same byte count has a smaller numerical value in MiB. Some file managers and video tools label units differently or show rounded values. When checking an estimate against a displayed size, look for the byte count or confirm which convention the display uses before deciding that the calculation is wrong.
The prefixes in a bitrate also matter. Mbps means megabits per second; MB means megabytes. The lowercase “b” in Mbps denotes bits, while uppercase “B” in MB denotes bytes. Confusing the two can make an estimate eight times too large or too small. A reliable written calculation labels every stage: Mbps, bits per second, bytes, then MB or MiB.
For example, if a result is 300,000,000 bytes, it is 300 MB in decimal units, or about 286.1 MiB in binary units. Those figures describe the same byte count. If you need to know whether a file will fit on a storage device, compare bytes with the device’s reported available capacity rather than relying on a rounded MB/MiB display.
Include both video and audio bitrate
A complete video file normally contains video and audio data, and the estimate should account for both. If you have separate rates, add them first:
Combined bitrate = video bitrate + audio bitrate
Then use the combined value in the size formula. A video stream at 4 Mbps plus audio at 128 kbps has a combined rate of 4.128 Mbps, assuming those figures use the same decimal convention. Convert 128 kbps to 0.128 Mbps, or convert both rates to bits per second, before adding them.
If the tool or file information already gives you a combined audio-and-video bitrate, use that figure rather than adding audio a second time. The YouTube Data API documents separate audio and video stream bitrates as well as a combined bitrate for the uploaded file. It also lists uploaded size as its own property. That distinction is a reminder to check what a displayed bitrate actually covers before using it. Google’s video resource reference describes these fields.
A common mistake is to take a video-only bitrate and apply it as though it described the whole file. That underestimates the encoded audio-and-video data. Audio can be a smaller part of the total in some high-bitrate videos, but it is still part of the file; for music, bhajans or a spoken programme, it is especially important not to leave it out of the calculation.
When the only number available is a video bitrate, find the audio bitrate from the export settings or the file’s media information. If you cannot establish it, state that the estimate excludes audio rather than presenting it as the complete file size. The answer can still help with rough planning, but it is not a total-file estimate.
A worked YouTube-stream example
YouTube’s upload guidance recommends 8 Mbps for 1080p SDR video at standard frame rates of 24, 25 or 30 fps, and 384 kbps for stereo audio. These are upload recommendations, not a promise that every video at those settings will have a particular file size. You can check the current guidance in YouTube Help’s recommended upload encoding settings.
Suppose you are preparing a 10-minute file and use those recommended values as inputs. First convert the audio rate to the same unit as the video rate: 384 kbps is 0.384 Mbps. Add the two rates to get a combined bitrate of 8.384 Mbps, or 8,384,000 bits per second. Convert 10 minutes to 600 seconds.
Now apply the formula:
8,384,000 bits/second × 600 seconds ÷ 8 = 628,800,000 bytes
That is 628.8 MB in decimal units, or about 599.8 MiB in binary units. The arithmetic is exact for the stated inputs, but the input rates are recommendations used for an illustration, not a measurement of a particular finished file. Your encoded file may differ because the actual average bitrate, duration and file structure can differ from the simplified assumptions.
The same YouTube table gives other upload-setting references, including 5 Mbps for 720p SDR at standard frame rates and 12 Mbps for 1080p SDR at high frame rates. Those figures describe recommended video rates; stereo audio remains a separate rate to include when estimating the complete file. Do not read a recommended video bitrate as an all-in file bitrate or as a guaranteed size for a live playback rendition.
For a long pre-recorded loop, the example is useful as a planning scale: if you have a representative combined average bitrate, the formula scales with runtime. A longer file at the same average rate contains proportionally more encoded data. If you are deciding whether an existing file can support a continuous loop, first confirm its playback and stream settings; this guide to YouTube 24/7 settings for anime clips covers a related set of preparation choices.
Estimate from runtime and bitrate
A practical estimate starts with four things: the duration, the video rate, the audio rate and the size unit you want to report. Write them down before calculating. Convert the duration to seconds and the two rates to a shared unit; add the rates if they are separate; multiply; divide by eight; and convert bytes to MB or MiB.
For instance, with a two-hour duration, use 7,200 seconds. If a media tool reports an average combined bitrate in bits per second, multiply that rate by 7,200 and divide by eight. If it reports Mbps, convert Mbps to bits per second by multiplying by 1,000,000 first. Preserve unrounded values through the calculation and round only when you present the final estimate.
Average bitrate is the useful input for variable-bitrate encoding. Variable bitrate means the data rate can rise or fall as the content changes: a visually busy scene may need more data than a still frame, and audio complexity can vary too. A peak bitrate is a momentary high point, not a reliable stand-in for the average across the full runtime. If you estimate the whole file from the peak, the result may be misleadingly large.
When you have no actual average bitrate, a target or recommended rate can still provide a planning estimate. Label the result accordingly: “estimated from the target bitrate” is more honest than “the file will be”. YouTube describes its figures as recommendations and notes that a bitrate limit is not required for uploads; check the current upload guidance rather than treating the listed rates as mandatory settings.
For storage planning, consider whether you are estimating one source file or many files in a playlist. Add the estimates for the individual assets, and leave room for other files and operational needs. A file-size estimate does not tell you how much internet data a 24/7 broadcast will consume, because that depends on what is transmitted and how the streaming setup handles the source. For a separate discussion of running a prepared video continuously, see how to keep a pre-recorded YouTube live stream running on JioFiber.
Why an estimate and the actual file differ
The formula is a useful model, not an exact container-level accounting method. It estimates encoded data from the supplied average bitrate and duration. The finished file may also include container structures, metadata and other overhead that the simple multiplication does not count separately. The difference cannot be predicted from the basic formula alone.
There are also input differences. An export setting may be a target, a maximum, or a rounded display rather than the final average. Variable-bitrate encoding changes its rate over time. The actual encoded duration may differ slightly from the intended timeline, especially if the export includes a short lead-in, tail or extra audio. If you do not know which bitrate a tool is reporting, treat the output as approximate until you verify the measurement.
The cleanest comparison uses the finished file’s actual byte size and a clearly identified combined average bitrate over the same duration. YouTube’s API lists uploaded-file size, duration and combined bitrate separately; they are related properties, but the calculation does not turn one into an exact substitute for the others. This is why a rounded estimate should not be used to diagnose a small size discrepancy by itself.
Also keep the upload separate from playback. YouTube’s recommended upload encoding settings describe what creators can prepare for upload; they do not say that a playback rendition will have the same file size or bitrate. YouTube processes uploaded video for playback, and a viewer’s stream is not simply the original file being served unchanged. If you are preparing a source file for a looping channel, estimate the source file from its own properties, not from assumptions about a viewer’s playback quality.
If the number is for a practical decision, use a margin rather than relying on the last decimal place. For example, storage planning should accommodate the actual file and related working copies, while upload planning should account for the file as reported by the tool you use. An estimate helps you catch an order-of-magnitude mistake, such as forgetting the minutes-to-seconds or bits-to-bytes conversion; it is not a substitute for checking the exported file.
Use the estimate in a 24/7 channel workflow
File size matters at different points in a channel workflow. Before export, it helps compare candidate settings and anticipate storage needs. After export, the file’s reported size is the value to record for upload planning. During continuous broadcasting, the source file’s size and the outgoing live-stream bitrate are separate considerations: the former describes stored encoded data, while the latter describes data sent over time.
If you are comparing ways to run a channel, keep the questions separate. Is the file finished and tested? Does it play through cleanly? How much source storage and transfer capacity does your method need? Will the broadcast continue if your own computer is switched off? The size formula answers only the first part of the storage question; it does not settle the rest. Readers weighing a self-managed setup can also review the practical trade-offs in streaming a playlist to YouTube with FFmpeg on an Azure VM.
For a fixed prerecorded programme, StreamNeo removes the need to keep your own computer running just to rebroadcast the uploaded file; the file-size estimate still helps you prepare and understand the source asset, but does not determine what viewers receive. Check your actual export before committing to a workflow, particularly if the file is part of a long playlist or needs to be transferred over a limited connection.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
How do I calculate video file size from bitrate and duration?
Multiply the average combined bitrate in bits per second by the runtime in seconds, then divide by eight to get bytes. Convert bytes to decimal MB or binary MiB, and state which unit you used. If your bitrate is in Mbps, convert it to bits per second first.
What if I only know the video bitrate?
Add the audio bitrate before estimating the complete file. If you cannot find the audio rate, make clear that your estimate excludes audio; do not label it as the size of the full audio-and-video file.
Why is the actual file not exactly the estimate?
The inputs may be rounded or may describe a target rather than the file’s average bitrate. Variable-bitrate encoding also changes the rate over time, and the simple formula does not count container or metadata overhead separately. Compare with the exported file’s byte size for the actual result.
Is YouTube’s recommended bitrate the same as a guaranteed file size?
No. YouTube’s upload bitrate figures are recommendations for preparing an upload, not a guarantee of the finished file size or a playback rendition’s rate. Use them as possible inputs for an estimate, include audio separately, and check the current official guidance.