4K Bitrate And Hourly Size
4K video file size per hour mainly depends on the video bitrate, then gets adjusted by frame rate, codec efficiency, audio bitrate, and container overhead. Bitrate is usually expressed in megabits per second (Mbps), while file size is measured in megabytes (MB) or gigabytes (GB). A practical planning rule converts Mbps into GB per hour by accounting for the 8-bit-per-byte relationship and the number of seconds in an hour.
For planning, start with the target video bitrate shown in your editor or encoder settings. If you export 4K at a constant bitrate (CBR), the file size stays close to the estimate. If you export variable bitrate (VBR), the average bitrate still predicts size, but the encoder may spend more bits on complex scenes and fewer bits on simple ones, which can shift the final result by a few percent.
Example: a 100 Mbps 4K export typically lands near 45 GB per hour for the video stream alone. Add audio (often 128–320 kbps) and you might see a small bump, usually under a few percent. If your export is 200 Mbps, the video stream alone often lands near 90 GB per hour. These are planning numbers, not guarantees, because codec behavior and scene complexity affect the actual average.
Why Estimates Go Wrong
People often treat bitrate as if it directly equals file size without checking units, codec mode, or whether the bitrate refers to video only. A common mistake is mixing megabits (Mb) with megabytes (MB). Another mistake is forgetting that some settings show total bitrate for both video and audio, while others show video-only bitrate.
Codec choice changes how many bits are needed for the same visual quality. H.264, H.265/HEVC, and AV1 differ in compression efficiency, so the same “quality” can correspond to different bitrates. Even within one codec, encoder settings like profile, level, GOP structure, and lookahead can change the average bitrate. That’s why two exports with the same resolution and frame rate can still produce different sizes.
Frame rate also matters because it changes how many frames must be encoded per second. Doubling from 30 fps to 60 fps often increases the required bitrate for similar motion detail, though the exact factor depends on encoder and content. If you record at 60 fps but export at 30 fps, the size can drop, but the motion characteristics change too.
Container overhead is usually small compared with video bitrate, yet it can still matter when you’re close to a storage limit. MP4 and MKV both carry metadata, indexes, and sometimes timecode tracks. Audio tracks add their own bitrate, and some exports include multiple audio tracks or subtitles, which can add a few hundred megabytes over long durations.
How To Estimate Your Size
Start With Video Bitrate
Use the video bitrate your encoder reports for the output. If the tool shows Mbps, convert to GB per hour using the relationship between bits and bytes and the number of seconds in an hour. A practical planning shortcut: 1 Mbps of video bitrate corresponds to about 0.45 GB per hour for the video stream. So 50 Mbps ≈ 22.5 GB/hour, 100 Mbps ≈ 45 GB/hour, and 150 Mbps ≈ 67.5 GB/hour.
If your tool shows a bitrate range for VBR, use the average value for planning. When the UI shows “target quality” instead of bitrate, you can run a short test export on a representative segment and measure the resulting size per minute, then scale up. This method works well because it captures your specific codec settings and content complexity.
One practical aside: if you export a 2-minute clip and the file is 1.2 GB, that implies 36 GB per hour. That scaling ignores audio and metadata differences, but those are usually small compared with video bitrate for 4K exports.
Account For Audio And Tracks
Audio bitrate is usually far smaller than video bitrate in 4K exports. Common audio settings include AAC at 128 kbps, 192 kbps, or 320 kbps, or Opus in some workflows. For planning, audio adds roughly 0.06 GB per hour at 128 kbps and about 0.14 GB per hour at 320 kbps. If you include multiple audio tracks, the audio contribution can double or triple, though it still rarely dominates the total size.
Subtitles and chapter markers add little space unless you embed large subtitle formats or multiple language tracks. If you export with “burn in subtitles,” the text becomes part of the video frames, which can slightly increase bitrate needs for complex scenes.
Use Codec-Specific Reality Checks
HEVC (H.265) often achieves similar quality at lower bitrate than H.264, while AV1 can be even more efficient in many cases. The exact savings depend on encoder quality and the content’s motion and texture. If you switch codecs, you can’t reuse the old bitrate-to-size mapping without testing, because the bitrate target changes.
When you need predictable sizes, choose CBR or a constrained VBR mode if your encoder offers it. Many encoders still vary bitrate within a range, but the spread can be narrower. If your workflow requires strict storage planning for a fixed upload limit, run a test export and measure the average bitrate over the full duration, not just the first few minutes.
Some tools show “average bitrate” after encoding. That number is the one you should use for planning future exports of similar content, because it reflects the encoder’s actual behavior.
Plan Storage With Headroom
Even with careful estimates, leave headroom for variations in scene complexity and encoder behavior. A conservative approach is to plan using the estimate plus 5–10% for VBR exports. If you’re near a hard cap—like a cloud upload limit or a filesystem quota—use a test export of a representative segment and scale from that measured size.
Also check whether your export includes thumbnails, waveform data, or additional tracks. Some editing workflows generate extra streams or embed color metadata. Those additions are usually small, yet they can matter when you’re trying to fit a long recording into a specific storage tier.
If you’re exporting for playback devices, verify that the chosen bitrate and codec level are supported. A file that plays on a desktop may fail on a set-top box if the level or profile is outside what the device expects, which leads to re-exports and wasted storage.
Educational Case Examples
Example 1: VBR HEVC For A Lecture
A creator exports a 4K lecture at 30 fps using HEVC with a quality-based VBR setting. The editor shows an estimated average video bitrate around 60 Mbps, and the audio is AAC at 192 kbps. A 10-minute test export produces a 6.8 GB file, which scales to about 40.8 GB per hour. The final export lands close to that number because the lecture has mostly static scenes with limited motion.
When the same settings are used on a sports clip with fast motion, the average bitrate rises and the file size per hour increases. The difference comes from the encoder spending more bits on motion detail, not from a change in resolution or frame rate.
Example 2: CBR H.264 For A Short Event
An editor exports a 4K event at 60 fps using H.264 in CBR mode at 120 Mbps, with AAC audio at 256 kbps. The planning estimate for video alone is about 54 GB per hour. The actual file size is slightly higher after encoding because the container and audio add overhead, but the result stays close to the estimate since CBR reduces bitrate swings.
If the editor accidentally selects a setting that targets total bitrate for both video and audio, the video stream bitrate becomes lower than expected. That misconfiguration can produce a smaller file but also changes quality, which is why checking the encoder’s “video bitrate” field matters.
Bitrate To Size Checklist
Use this table to sanity-check your expected file size for the video stream. Treat it as a planning guide, then confirm with a short test export when you need accuracy.
| Video Bitrate (Mbps) | Approx GB/Hour (Video) | Typical Use Case | What To Verify |
|---|---|---|---|
| 50 | ~22.5 GB | Lower-motion content | Video-only vs total bitrate |
| 100 | ~45 GB | General 4K exports | VBR average bitrate |
| 150 | ~67.5 GB | High-motion or higher quality | Codec and frame rate |
| 200 | ~90 GB | Very high bitrate targets | Device playback limits |
Step-by-step checklist for a reliable estimate:
- Confirm the unit: Mbps for video bitrate, not MB/s or total bitrate.
- Check whether the bitrate shown is video-only or includes audio.
- Use the average bitrate for VBR, not the peak or target range.
- Estimate video size using ~0.45 GB per hour per 1 Mbps.
- Add audio contribution if you include multiple tracks, then add 5–10% headroom for VBR.
- Run a 2–10 minute test export on representative content and scale from measured size.
Common Mistakes To Avoid
One frequent error is exporting at a “quality” preset that maps to a bitrate range, then assuming the output will match a single number. VBR encoders adjust bitrate based on scene complexity, so the same settings can produce different sizes across clips. Another mistake is ignoring frame rate changes between source and export, which can double the number of frames that must be encoded per second.
People also misread bitrate fields in software UIs. Some tools show “bitrate” for the whole file, while others show “video bitrate” only. If you plan storage using the wrong field, your estimate can miss by tens of percent. I’ve seen workflows where the audio track was added after the fact, and the final size exceeded the plan even though the video bitrate matched the expectation.
Another practical issue is mixing remux and transcode assumptions. Remuxing (changing container without re-encoding) keeps the video stream bitrate close to the source, while transcoding changes it. If you treat a remux like a transcode, your planning numbers won’t match.
FAQ
How Do I Convert Mbps To GB Per Hour?
Use the planning relationship that 1 Mbps of video bitrate corresponds to about 0.45 GB per hour for the video stream. Multiply your Mbps by 0.45, then add a small amount for audio and container overhead.
Does VBR Change The File Size Prediction?
VBR changes the predictability of exact size, but the average bitrate still predicts size reasonably well. A short test export on representative content gives the most reliable scaling for your specific encoder and scenes.
Do Audio Tracks Matter For 4K Size?
Audio usually adds a small fraction compared with 4K video bitrate. At common AAC bitrates (128–320 kbps), audio adds roughly hundredths of a GB per hour, unless you include multiple audio tracks.
Why Does The Same 4K Export Produce Different Sizes?
Codec mode, encoder settings, and scene complexity change the average bitrate. Even with the same resolution and frame rate, motion detail and texture complexity affect how many bits the encoder spends.
What Should I Check In My Export Settings?
Confirm whether bitrate is video-only or total, verify the frame rate, note whether the mode is CBR or VBR, and check how many audio/subtitle tracks are included. Then run a short test export if you need tight storage planning.
Author's Insight
Bitrate-to-size planning works best when you treat bitrate as an average over time and confirm which stream the number refers to. Many export dialogs show “target” values that map to encoder behavior rather than a strict guarantee, so test exports reduce uncertainty. For storage planning, the ~0.45 GB per hour per 1 Mbps rule is a useful starting point for the video stream, then audio and overhead add a smaller adjustment. When you need repeatable results, prefer CBR or constrained VBR and keep frame rate consistent between source and export.
Key Takeaways
- 4K file size per hour scales mainly with video bitrate; 1 Mbps ≈ 0.45 GB per hour for video.
- VBR exports vary with scene complexity, so average bitrate and test exports matter.
- Check whether the bitrate shown is video-only or total, and verify frame rate.
- Add audio and track overhead, then keep 5–10% headroom for VBR when storage is tight.
