Before encoding a YouTube playlist, estimate each MP4’s size by multiplying its duration in seconds by its combined audio and video bitrate, then dividing by eight. Add the per-video estimates to plan storage; the result is approximate, particularly when you use variable-bitrate encoding.
This method gives you a practical figure before you export, without pretending that duration alone determines file size. Choose bitrate assumptions that fit each video, keep decimal and binary units distinct, and leave room for variation in the actual output.
What the estimate is for
A file-size estimate helps you decide whether your planned exports fit on a drive, how much space to reserve for a playlist, and whether an upload will be manageable on your connection. It is useful before encoding because changing the export settings after you have prepared many videos can mean repeating work.
The estimate is based on encoded data rate over time. A longer video generally needs more data at the same average bitrate; a higher bitrate generally means a larger file for the same duration. But two videos of equal duration can still produce different files if their content or encoding settings differ.
Treat the answer as a planning range, not a promised output size. If you are preparing a continuous channel, storage planning is only one part of the workflow: for a separate view of ongoing local storage needs, see how much storage a 24/7 prerecorded channel may need. That article addresses a different planning question; here, the calculation is for the MP4 files you are about to encode.
The duration-times-bitrate formula
The basic formula is:
Estimated bytes ≈ duration in seconds × combined bitrate in bits per second ÷ 8
The division by eight converts bits to bytes, since one byte contains eight bits. The word “combined” matters: it means the audio bitrate plus the video bitrate, not just the video figure. The result estimates the encoded data for the file; it is not an exact prediction of every byte in the final MP4.
For example, a ten-minute video lasts 600 seconds. If your assumed combined bitrate is 8,384,000 bits per second, the arithmetic is:
8,384,000 × 600 ÷ 8 = 628,800,000 bytes
That is about 629 MB using decimal units, or about 600 MiB using binary units. The calculation is based on the chosen bitrate assumption; it does not show that a particular encoder will produce exactly that file size.
To convert a duration into seconds, multiply hours by 3,600, minutes by 60, then add the remaining seconds. A video lasting 1 hour, 12 minutes and 30 seconds is 4,350 seconds. Use the same units for every clip before adding estimates, so you do not accidentally combine a duration in minutes with a bitrate in bits per second.
YouTube’s Data API video resource documentation lists duration and the combined bitrate of a video as separate properties. That reflects the practical point of the formula: duration tells you how long the file runs, while bitrate provides the rate at which encoded data is produced. Neither one alone is enough to estimate size.
Include audio and video bitrate
Add the audio bitrate to the video bitrate before multiplying by duration. If your video assumption is 8 Mbps and the audio assumption is 384 kbps, first express them in compatible units: 8 Mbps is 8,000 kbps, so the combined assumption is 8,384 kbps, or 8.384 Mbps. In bits per second, that is 8,384,000 bps.
YouTube Help’s recommended upload encoding settings provide reference bitrates for resolution, frame-rate class, and audio configuration. For instance, its SDR guidance lists 8 Mbps video for 1080p at standard frame rates and 12 Mbps for high frame rates; the audio references include 384 kbps for stereo. These are useful assumptions for estimating, not a guarantee of the bitrate your encoder will use or the size it will produce. Check the current table when choosing settings, as recommendations can change.
The distinction between audio and video is easy to overlook if an export dialogue displays them separately. Leaving audio out makes the estimate too small, even where its contribution is modest next to the video stream. For stereo music, spoken audio, or ambience, choose the audio setting you actually intend to export rather than assuming it is zero.
Resolution alone does not identify a single bitrate. Frame rate and whether you are exporting SDR or HDR also affect the appropriate reference point. A 1080p standard-frame-rate assumption should not be applied to a 4K or high-frame-rate video simply because both are destined for YouTube. Match the assumption to the planned export, and keep it consistent with the actual encoder settings as far as you can.
Estimate each video in a playlist
Make a short worksheet before encoding. Record each video’s duration, its intended resolution and frame-rate class, the assumed video bitrate, the audio bitrate, and the resulting combined bitrate. This exposes clips that need a different assumption instead of hiding them inside one playlist-wide average.
For each row, convert duration to seconds, convert both bitrate figures to bits per second, add them, and apply the formula. If a clip’s settings differ materially from the others, calculate it on its own assumptions. A short 4K clip and a long 1080p clip should not automatically inherit the same bitrate merely because they belong to one playlist.
The example below uses YouTube’s reference values for 1080p SDR at 30 fps and stereo audio. The figures are illustrative calculations, not measured exports. The combined rate is 8.384 Mbps in both rows, so the difference in estimated size comes from duration.
| Clip | Duration | Combined bitrate assumption | Estimated bytes | Approx. decimal size |
|---|---|---|---|---|
| A | 10 minutes (600 seconds) | 8.384 Mbps | 628,800,000 | 629 MB |
| B | 20 minutes (1,200 seconds) | 8.384 Mbps | 1,257,600,000 | 1,258 MB |
If clip B were exported at a different resolution, frame rate, HDR setting, or quality target, give it a separate assumption rather than copying clip A’s row. You can use YouTube’s guidance as a reference point, but the settings in your encoder and the kind of output you want should guide your own estimate.
It is also useful to calculate a lower and upper scenario when the bitrate is uncertain. Hold the duration fixed and change only the bitrate assumption. That shows the effect of the encoding choice directly and makes it easier to discuss storage needs without presenting a single uncertain number as certain. For example, you might compare a reference-rate assumption with a higher-rate choice you are considering; label each scenario and avoid calling either one the guaranteed result.
If your playlist is for a continuous channel, check that the clips’ export assumptions reflect their actual role. A static devotional image with a bhajan track, a detailed local-news loop, and a study-music video with a moving background may not be encoded at the same data rate under a quality-targeted mode. For practical questions around handling a continuous playlist, see how to schedule recurring YouTube playlist rotations and software choices for a continuous study-music playlist. Those workflow choices do not change the formula, but they can affect how you prepare and manage the source files.
Add estimates and convert storage units
Once you have a byte estimate for every video, add the byte values to find the playlist estimate. If every clip uses the same combined bitrate, adding all durations first and calculating once gives the same arithmetic result. In practice, per-video rows make it easier to spot a clip with a different export setting and correct its assumption before you total the list.
Be precise about storage units when you report the result. Decimal units use powers of 1,000: 1 MB is 1,000,000 bytes and 1 GB is 1,000,000,000 bytes. Binary units use powers of 1,024: 1 MiB is 1,048,576 bytes and 1 GiB is 1,073,741,824 bytes. Thus, the same byte count has different numeric values in MB and MiB, or in GB and GiB. State which convention you have used rather than writing an ambiguous “GB” when you mean GiB.
For the worked ten-minute estimate of 628,800,000 bytes, dividing by 1,000,000 gives 628.8 MB, normally rounded to about 629 MB. Dividing by 1,048,576 gives roughly 600 MiB. Both describe the same estimated byte count; they are not competing estimates. The playlist total should be calculated in bytes first, then converted once to your chosen reporting unit to avoid accumulating rounding differences.
For an upload, the relevant content size is the actual file size in bytes. Google’s resumable upload documentation describes the upload content length in terms of the video file’s byte size. That is another reason to keep your worksheet’s original byte totals, even if you also want a rounded figure for comparing with a drive’s displayed capacity.
Why actual MP4 size can differ
A bitrate-based estimate assumes an average data rate over the whole duration. In constant-bitrate encoding, the output is designed to stay closer to a selected rate, though container and metadata details still mean the simple formula is not a byte-for-byte prediction. In variable-bitrate encoding, the encoder can use more data for complex passages and less for simpler ones, so the average across the file is what ultimately matters.
YouTube recommends variable bitrate in its upload settings guidance. Google’s VP9 encoding recommendations also describe how constrained-quality encoding allocates more bits to difficult scenes and fewer to easier scenes. That document is about VP9, not a special MP4 size rule; it illustrates why content and quality-targeted encoding can change the average data rate. A still background and a fast-moving, detailed scene may not spend bits in the same way.
Other differences follow from your chosen export: resolution, frame rate, HDR, quality mode, and audio configuration can all affect the bitrate assumption or resulting output. A file also includes container and metadata details not represented explicitly in the basic formula. The duration-times-bitrate calculation is still useful, but it is a simplified model of the encoded file, not a file inspector.
For that reason, treat YouTube’s published bitrate values as upload references rather than a promise about a third-party encoder’s result. If you need a more dependable estimate for a particular workflow, encode a representative short sample with the intended settings, inspect its actual average bitrate or size, and use that result to refine the assumptions for similar material. A sample can improve your estimate; it still cannot make every different clip identical.
Plan storage around your assumptions
Use a range rather than an unexplained safety margin. For each clip, calculate a lower and upper estimate using two plausible combined bitrates for its intended export. Add the lower values together and add the upper values together. You then have a clear planning interval tied to assumptions you can review, rather than a universal allowance that may not fit your footage.
Keep working space separate from the estimate of finished MP4s. During editing or export, you may keep source footage, temporary files, and final files at once. The formula estimates the final encoded files only; it does not account for those other copies. If you retain source material, include it in a separate storage line instead of quietly treating it as part of the MP4 calculation.
For a channel that uploads or rotates files regularly, record the assumptions and update them when your settings change. A playlist made from 1080p SDR clips may be estimated one way, while an archive that mixes high-frame-rate or 4K material needs more specific rows. If upload data is a concern as well as disk space, the guide to reducing upload size for a 24/7 YouTube playlist in India covers that related planning issue; smaller files can trade off against image quality, so do not reduce a bitrate without considering how the video should look.
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
Does video duration alone tell me the MP4 size?
No. Duration tells you how long the file runs, but you also need an assumed combined audio and video bitrate. Two clips of the same length can have different sizes if their settings or content produce different average bitrates.
Should I include audio bitrate in the calculation?
Yes. Add audio bitrate to video bitrate before multiplying by duration, and make sure both are expressed in the same units. Omitting audio will understate the estimated file size.
Is the estimate exact for variable-bitrate encoding?
No. Variable-bitrate encoding may allocate different amounts of data to different parts of a video, so the actual average bitrate can differ from your assumption. Use the calculation as a planning estimate, or encode a representative sample to refine it.
What is the difference between MB and MiB?
MB is decimal and uses 1,000,000 bytes; MiB is binary and uses 1,048,576 bytes. Label the unit you use, and convert the playlist’s byte total only after adding the individual estimates.