Video Length Calculator
Video files are measured in two different units that look almost identical, and confusing them is the most common mistake in video math. File size is measured in megabytes, while bitrate is measured in megabits per second. Since one byte holds eight bits, converting between the two always involves multiplying or dividing by eight. Once that single fact is clear, every video length and file size question becomes simple division or multiplication.
The Video Length Calculator on this page works in both directions. In runtime mode, enter a file size in megabytes and a bitrate in megabits per second to find how long the video plays. In file size mode, enter a runtime in hours, minutes, and seconds plus a bitrate to find how large the file will be. Both modes use the same relationship between size, bitrate, and time, just solved for a different unknown.
The Core Formula: Size, Bitrate, and Time
The relationship is straightforward. File size in megabits equals bitrate in megabits per second multiplied by runtime in seconds, and file size in megabytes is that figure divided by eight. Rearranged, runtime in seconds equals file size in megabytes multiplied by eight and divided by bitrate. The calculator applies these formulas exactly, then converts seconds into hours, minutes, and seconds for readability.
Bitrate is the key quality lever in this formula. A higher bitrate packs more data into each second of video, which improves quality but grows the file. A lower bitrate shrinks the file but can introduce visible compression artifacts, especially in fast-moving scenes. Streaming services and cameras let users pick bitrates precisely because the tradeoff between quality and size matters for storage and bandwidth.
Worked Example: Runtime From File Size
Consider a video file of one thousand megabytes encoded at five megabits per second. Multiplying one thousand by eight gives eight thousand megabits, and dividing by five gives one thousand six hundred seconds. That is twenty-six minutes and forty seconds of video. The same file at ten megabits per second would hold only thirteen minutes and twenty seconds, because each second of video consumes twice as much data.
- One thousand megabytes multiplied by eight gives eight thousand megabits of data.
- Eight thousand megabits divided by five megabits per second gives one thousand six hundred seconds.
- One thousand six hundred seconds equals twenty-six minutes and forty seconds.
- Doubling the bitrate to ten megabits per second halves the runtime to thirteen minutes and twenty seconds.
A second check confirms the method. A five hundred megabyte file at two point five megabits per second holds four thousand megabits, divided by two point five gives one thousand six hundred seconds, again twenty-six minutes and forty seconds. The two examples agree because the ratio of size to bitrate is the same, which is a useful sanity check when estimating by hand.
Worked Example: File Size From Runtime
Now reverse the question. A video lasting one hour and thirty minutes contains five thousand four hundred seconds. At a bitrate of eight megabits per second, the file holds forty-three thousand two hundred megabits, and dividing by eight gives five thousand four hundred megabytes, which is about 5.27 gigabytes. That figure helps a creator decide whether a video fits on a drive, an upload limit, or a disc before exporting.
Creators use this direction constantly when choosing export settings. A one-hour tutorial at twelve megabits per second needs about five thousand four hundred megabytes, while the same tutorial at six megabits per second needs about two thousand seven hundred megabytes. Halving the bitrate halves the file, which is why bitrate choice is the first decision in any export workflow, ahead of resolution or frame rate.
Megabytes, Megabits, and Gibibytes
Unit confusion causes more errors than arithmetic. File sizes on computers are often shown in mebibytes or gibibytes, where one gibibyte is one thousand twenty-four mebibytes, while storage makers and many tools use decimal megabytes and gigabytes, where one gigabyte is one thousand megabytes. The difference is about seven percent at the gigabyte scale, which is enough to make a file miss an upload limit that looked safe.
This calculator uses decimal megabytes, with one megabyte equal to eight megabits, and converts to gigabytes by dividing by one thousand twenty-four for the display figure. If your tool reports size in gibibytes, the runtime estimate will be slightly low, since a gibibyte holds more data than a decimal gigabyte. For planning purposes the difference is small, but for exact limits it is worth checking which unit your tool uses.
Why Real Files Differ From the Estimate
Real encoders use variable bitrate encoding, which spends more data on complex scenes and less on simple ones, so the average bitrate rarely matches the target exactly. Container formats also add overhead for audio tracks, subtitles, and metadata, typically a few percent. The estimate is therefore accurate to within a few percent for most files, which is plenty for planning storage, uploads, and recording time.
- Variable bitrate encoding makes the average bitrate differ from the target bitrate.
- Audio tracks, subtitles, and metadata add container overhead of a few percent.
- Two-pass encoding hits the target bitrate more closely than single-pass encoding.
- For exact limits, export a short test clip and scale the measured size.
Recording devices add their own quirks. Cameras and screen recorders may use variable frame rates or hardware encoders with their own rate control, so a one-hour recording can land above or below the estimate. The practical approach is to use the calculator for planning, then verify with a real recording of a few minutes before committing to a long session or a tight storage budget.
Bitrate Choices for Common Platforms
Each platform has its own bitrate sweet spot, and uploading far above it wastes time without improving what viewers see. YouTube re-encodes every upload, so creators typically upload 1080p at around twelve megabits per second and 4K at forty-five to sixty-eight megabits per second, giving the encoder plenty of quality to work with. Uploading at double those rates rarely improves the streamed result, since the platform compresses it again anyway.
Video calls and screen recordings live at much lower bitrates, often two to five megabits per second, because the content is mostly static slides or talking heads. Recording a meeting at a high bitrate produces enormous files with no visible benefit, which is why conferencing tools cap their recording quality. For training videos, eight to twelve megabits per second at 1080p is a good balance between clarity and file size.
Archival masters are the exception, where quality matters more than size. Professional formats such as ProRes can run hundreds of megabits per second, producing files many times larger than streaming versions. Archivists accept that cost because a master must survive future re-encoding without visible loss, and storage is cheaper than re-shooting the original footage.
Recording Time and Storage Planning
Long events need storage planning before recording starts, not after the card fills up. An eight-hour conference recorded at eight megabits per second needs about twenty-eight thousand eight hundred megabytes, or roughly twenty-eight gigabytes, before audio and overhead. A creator planning a full-day shoot should carry cards or drives totaling at least twice that figure, since a second copy is the only protection against a failed card.
Phones deserve the same planning. One minute of 4K video at sixty frames per second can consume roughly four hundred megabytes, so an hour of phone footage can exceed twenty-four gigabytes. Travelers shooting on phones should check free space before important moments and offload footage nightly, since a full phone at the wrong moment loses shots that cannot be repeated.
The backup rule for important footage is simple: keep the original camera files plus the exported edit, on two different drives or in the cloud. The calculator helps size both, since the original and the export often use very different bitrates. A project with twenty hours of source footage at twenty-five megabits per second needs about two hundred twenty-five gigabytes for the originals alone, which decides the drive purchase before editing begins.
- Carry at least twice the estimated storage for important shoots.
- Offload phone footage nightly during travel.
- Keep camera originals plus the export, on separate drives.
- Test a short clip at the planned bitrate before a long session.
Upload time is the final planning number, and it uses the same math in reverse. A five thousand four hundred megabyte file uploaded at ten megabits per second takes about seventy-two minutes, since the file holds forty-three thousand two hundred megabits. Creators on slow connections should start large uploads overnight, or compress to a lower bitrate when the platform will re-encode anyway.
Live streaming adds one more constraint, since the upload bitrate must stay below the connection’s real upload speed with headroom. A streamer with a twenty megabit per second upload connection should stream at no more than about ten to twelve megabits per second, leaving room for network variation and other traffic. Dropping frames from an over-ambitious bitrate looks far worse than streaming at a slightly lower quality.
Audio Bitrate and the Total File Size
Video files also carry audio, and audio bitrate adds to the total size through the same formula. A stereo audio track at three hundred twenty kilobits per second, which is zero point three two megabits per second, adds about one hundred forty-four megabytes over a one-hour video. That is small beside a multi-gigabyte video track, but it matters for audio-heavy content such as podcasts with video, where the audio share of the file is proportionally larger.
Combined audio and video math is simple addition. A ninety-minute video at eight megabits per second plus a stereo track at zero point three two megabits per second uses a combined rate of eight point three two megabits per second. Over five thousand four hundred seconds, that gives about five thousand six hundred sixteen megabytes instead of five thousand four hundred, a difference of roughly four percent. Creators working near a strict upload limit should include the audio rate rather than ignoring it.
Multiple audio tracks multiply the effect. A video with English, Spanish, and French audio tracks at one hundred ninety-two kilobits per second each carries about zero point five eight megabits per second of audio in total, adding roughly two hundred fifty-nine megabytes to a one-hour file. Subtitle tracks add very little by comparison, since text compresses to almost nothing. For most creators, one audio track is a rounding error, but multilingual releases should budget for every track.
Frequently Asked Questions
How do I calculate video length from file size?
Multiply the file size in megabytes by eight to get megabits, then divide by the bitrate in megabits per second. A one thousand megabyte file at five megabits per second plays for one thousand six hundred seconds, or twenty-six minutes and forty seconds.
How do I calculate file size from video length?
Multiply the runtime in seconds by the bitrate in megabits per second, then divide by eight. A ninety-minute video at eight megabits per second needs about five thousand four hundred megabytes, or 5.27 gigabytes.
What is the difference between MB and Mb?
MB means megabytes, a measure of file size, while Mb means megabits, a measure of data rate. One megabyte equals eight megabits, so confusing the two makes estimates wrong by a factor of eight.
What bitrate should I use for 1080p video?
A common range for 1080p video is eight to twelve megabits per second for streaming, and higher for archival quality. The right value depends on frame rate, motion, and how much compression artifact you accept.
What bitrate should I use for 4K video?
4K video typically needs thirty-five to sixty-eight megabits per second for good quality streaming, and more for archival masters. Four times the pixels of 1080p does not mean four times the bitrate, thanks to efficient modern codecs.
Why is my exported file bigger than the estimate?
Variable bitrate encoding, audio tracks, subtitles, and container overhead all add size beyond the simple formula. The estimate is usually within a few percent, but complex scenes push variable bitrate encoders above their target.
Does resolution affect file size directly?
Resolution affects file size indirectly through bitrate, since higher resolutions need higher bitrates for the same quality. The formula itself uses only bitrate and time, so two videos at the same bitrate and length have the same size regardless of resolution.
What is variable bitrate encoding?
Variable bitrate encoding spends more data on complex, fast-moving scenes and less on simple, static scenes. It produces better quality at a given average file size than constant bitrate encoding, but makes exact sizes harder to predict.
How much storage do I need for one hour of video?
At eight megabits per second, one hour needs about three thousand six hundred megabytes. At twenty-five megabits per second, the same hour needs about eleven thousand two hundred fifty megabytes.
Can I use this calculator for audio files?
Yes, the same math applies, since audio bitrates are also measured in kilobits or megabits per second. Convert the audio bitrate to megabits per second first, then use the same formulas.
What is a good bitrate for YouTube uploads?
YouTube re-encodes uploads anyway, so creators usually upload at higher bitrates than the streaming rate, such as twelve megabits per second for 1080p and forty-five to sixty-eight for 4K. Higher upload quality gives the encoder more to work with.
How do I convert seconds to hours, minutes, and seconds?
Divide total seconds by three thousand six hundred for hours, take the remainder and divide by sixty for minutes, and the final remainder is seconds. One thousand six hundred seconds becomes twenty-six minutes and forty seconds.
Does frame rate change file size?
Frame rate affects the bitrate needed for good quality, since more frames per second carry more motion information. At a fixed bitrate, however, the file size formula depends only on bitrate and time, not on frame rate.
What is container overhead?
Container overhead is the extra data a video file carries for audio tracks, subtitles, chapters, and metadata. It usually adds only a few percent to the size, but it explains small differences between estimates and real files.
Is this calculator exact for streaming?
It estimates the video data itself, while streaming adds network overhead, adaptive quality switching, and buffering. For storage and export planning it is accurate within a few percent, which is enough for most decisions.