Resolution does not tell you a video's file size. Bitrate and duration give you a much better starting point—and the final exported file gives you the best one.
Estimate before the export
A video's average bitrate describes how much encoded data it uses each second. Multiply total average bitrate by duration to estimate the amount of data, then divide bits by eight to get bytes. For decimal units, a convenient formula is file size in GB = total Mbps × duration in seconds ÷ 8,000. Include audio bitrate when your video bitrate setting excludes it.
Consider a 20-minute export with 20 Mbps video and 0.32 Mbps audio. Its estimated size is 20.32 × 1,200 ÷ 8,000 = 3.048 GB, before any unmodeled container overhead. At an effective upload rate of 15 Mbps, transferring that amount takes about 27 minutes, 6 seconds. This example is arithmetic, not a recommended export preset.
Use the video file-size calculator to compare scenarios before committing to an export. Once the file exists, replace the estimate with its actual size. That removes uncertainty about the encoder's final average rate.
Why two “4K videos” can be wildly different
Resolution counts image pixels; it is not a storage budget. Codec, frame rate, scene complexity, quality settings, duration, and audio all affect the final output. A still interview and a fast-moving concert need not produce equal file sizes under a quality-based encoder. Variable bitrate can also make the average differ from a target or maximum entered in the export panel.
Check the receiving platform's current requirements instead of using the biggest preset by reflex. YouTube's official encoding guidance, for example, distinguishes resolution, frame rate, SDR/HDR, video bitrate, and audio settings. Its recommendations are destination-specific, not a universal specification for every client, archive, or streaming service.
Optimize the whole schedule
A smaller file can save transfer time, but making it smaller can cost additional export time or compromise the deliverable. Compare total time, not just the upload estimate. If another encode takes 30 minutes and saves 12 minutes of uploading, it does not improve today's deadline unless it solves a separate requirement.
Build a simple chain: final edits → export → local playback check → transfer → platform processing → recipient verification. Some steps may overlap in your workflow, but do not assume that they do. For a fixed publication time, work backward from when the correct quality must be available, not from when the upload needs to start.
YouTube explains that higher-quality versions can remain unavailable while processing continues. Upload Compass does not estimate that service-side processing time. Leave a separate allowance based on your own previous uploads of similar duration and settings, and recheck the platform before a critical release.
Make the network assumption explicit
Your export's bitrate and your internet upload rate may both be written in Mbps, but they answer different questions. The export bitrate determines how much data is produced per second of video. Upload throughput determines how quickly the finished file moves over the network. A 20-minute video does not necessarily take 20 minutes to upload.
Use a recent sustained upload measurement if you have one. Otherwise, model the plan's upstream rate with a realistic efficiency assumption and reserved traffic for calls or backups. Compare a typical case and a slower case. A result with only two minutes to spare is not a robust delivery plan if the inputs are uncertain by tens of minutes.
A practical delivery checklist
- Confirm format, resolution, frame rate, audio, and any size limit with the recipient.
- Export a short difficult section first if quality settings are uncertain.
- Check the completed file's size and play through representative sections.
- Enter that actual size in the upload deadline planner.
- Keep the device powered and connected for the transfer; avoid scheduling disruptive updates.
- Verify completion in the destination and test access with the intended permissions.
Do not delete the local master merely because an upload bar reaches 100%. The file can be transferred but still processing, unavailable to the recipient, or the wrong revision. A good estimate makes room for checking the outcome. That last check is often worth more than shaving a few seconds from the arithmetic.