YouTube Video File Size Calculator: Bitrate Math Without Fake Export Guarantees
“How big is a 1-hour 1080p video?” is a bitrate question. The dishonest answer invents exact GB for every export. The honest answer multiplies: how many megabits per second of video and audio, for how many seconds, converted to megabytes and gigabytes — then humility about CRF, VBR, motion complexity, and the fact that YouTube will re-encode whatever you upload.
This page’s tool estimates size from duration, resolution, frame rate, and codec using teaching bitrate mids. It also sketches ideal upload times at 10 / 50 / 200 Mbps as if the full link were available. It does not open your Premiere/DaVinci project, does not measure your real export, and does not predict YouTube’s final CDN encodes.
Below: the formula in plain language, when 60 fps and 4K actually cost storage, H.264 vs H.265 as teaching efficiency (not magic half-size every time), and how this sits next to length and word-count tools. Related: video length calculator, word count calculator, video to GIF, audio converter.
If you only care about upload deadlines, the size and ideal-time sketches help you schedule. If you only care about quality, remember that past a point YouTube’s re-encode dominates — giant mezzanine files can be pure disk waste. This article keeps the product as transparent arithmetic plus practical notes — no fabricated “Real File Size Examples” with invented perfection scores.
AdSense-quality pages do not claim official forever bitrates as destiny. Teaching mids go stale; encoder settings dominate. Use your NLE’s estimated size or a test export when accuracy matters.
In this guide
BasicsWhat is a video file size calculator here?
A teaching estimator for compressed video file size and idealized upload duration. Inputs: length in minutes, resolution, FPS, and codec. Outputs: estimated GB/MB, teaching video/audio Mbps, ideal upload times at three speeds, tips, and a short YouTube-oriented checklist pointing you to current official help docs.
- Creators planning disk space before long 4K exports fill a drive.
- Editors scheduling uploads who need a rough transfer window, not a stopwatch promise.
- Anyone burned by “exact GB” blogs that ignore CRF, VBR, and re-encode reality.
Estimate ≠ export
Your editor may produce a different file at the same resolution label. Motion, grain, audio channels, subtitles, and rate-control mode all move the needle. The calculator multiplies teaching mids; the file on disk is the truth.
Size vs quality vs YouTube’s copy
Three different things: (1) your export file size, (2) perceived quality of that export, (3) what viewers get after YouTube re-encodes. This tool only sketches (1) from bitrate assumptions. It does not score quality or predict ladder bitrates on YouTube’s side.
Who this tool is not for
Broadcast delivery specs with strict mezzanine requirements. Archival masters (often huge). People who need forensic bit-accurate size from a project file. Use professional delivery tools for those jobs.
A realistic first use
Enter your target duration and export settings. Read the GB sketch and ideal upload time. Leave headroom on disk and on the clock. After one real export, compare actual size to the sketch and adjust expectations — not the other way around.
Raw footage vs delivery file
Camera cards and proxies are a different universe of storage. A 10-minute YouTube export can be 1–2 GB while the same shoot’s raw is tens of GB. This calculator is for the delivery/export sketch, not entire project archives.
Why creators still want a GB sketch
Disk fills quietly. Upload windows slip. Collaborators ask “how big is the master?” before a shared drive sync. A transparent estimate answers logistics questions without pretending to be a media-info probe of your timeline. Pair it with one real test export and you have a calibrated planning loop.
What “teaching mid” means for bitrates
A teaching mid is a fixed Mbps we attach to a resolution label so the formula can run. It is not your NLE preset name, not YouTube’s internal ladder, and not a promise that two different 1080p exports will match. When your export panel shows a target bitrate or CRF, prefer that number for serious planning.
StepsHow to use this tool
Enter duration in minutes
Use the finished video length you plan to upload (or a segment). 90 seconds = 1.5 minutes.
Pick resolution
480p through 4K. Higher resolution mids use higher teaching video Mbps.
Pick frame rate
24, 30, or 60. Teaching math multiplies bitrate for high FPS so 60 fps sketches are larger — roughly reflecting more bits for motion detail, not a universal law.
Pick codec
H.264 baseline mid, or H.265 with a smaller teaching mid. Real savings depend on encoder and settings.
Read size, bitrates, and upload sketches
Use the unit note to see the Mbps assumptions. Treat upload times as ideal-link lower bounds.
Tip
Compare 1080p30 H.264 vs 1080p60 and vs 4K with the same duration. The deltas teach storage cost faster than any slogan.
LimitsWhat this calculator is not
- Not a guaranteed export size from Premiere, Final Cut, Resolve, CapCut, etc.
- Not YouTube’s final re-encoded viewer stream size
- Not a live official bitrate table (verify current help docs)
- Not measured upload ETA on your Wi‑Fi
- Not a compressor (use HandBrake/NLE export — or our browser tools where relevant)
- Not storage advice for raw camera archives
| Weak habit | Stronger habit |
|---|---|
| Trusting GB to the decimal forever | Test-export once and recalibrate |
| Max bitrate “for quality” always | Stay near sensible delivery ranges for web |
| Upload sketch = calendar promise | Add buffer for real networks |
| Confusing raw card size with export | Separate archive vs delivery planning |
| Ignoring audio and container overhead | Teaching mid includes simple audio; still approximate |
FormulaFile size in plain language
| Step | Math |
|---|---|
| Duration (s) | Minutes × 60 |
| Total Mbps | Video teaching Mbps + audio Mbps |
| Size (GB) | (total Mbps × seconds) ÷ 8 ÷ 1024 |
| Upload (s, ideal) | (size MB × 8) ÷ upload Mbps |
Worked example: 10 minutes, 1080p, 30 fps, H.264 teaching mid ~8 Mbps video + 0.192 Mbps audio ≈ 8.2 Mbps. Seconds = 600. Size ≈ 8.2 × 600 / 8 / 1024 ≈ 0.60 GB (~600 MB order of magnitude). Change mid to 12 Mbps and size scales almost linearly.
Second example (1 hour 1080p)
60 minutes, same ~8.2 Mbps total teaching. Seconds = 3600. Size ≈ 8.2 × 3600 / 8 / 1024 ≈ 3.6 GB. Real exports cluster in a range around this — not a single magic number for every talking-head vs action video.
Third example (10 min 4K teaching mid)
4K mid ~35 Mbps × 1.0 (30 fps H.264 teaching) + audio. Roughly several GB for 10 minutes. That is why “4K everything” is a storage and upload decision, not only a quality slogan.
Worked table (teaching, H.264-ish mids)
| Duration | Settings (teaching) | Order-of-magnitude size |
|---|---|---|
| 10 min | 1080p30 H.264 | ~0.5–1 GB class |
| 60 min | 1080p30 H.264 | ~3–6 GB class |
| 10 min | 1080p60 H.264 | noticeably larger than 30 fps mid |
| 10 min | 4K30 H.264 | multiple GB |
| 10 min | 4K H.265 mid | smaller than H.264 4K mid, still large |
Ranges exist because content complexity and rate control matter. The tool’s single number is a mid sketch so you can plan — not a lab measurement.
Why divide by 8 and 1024?
Bitrate is in megabits per second. Eight bits make a byte (approx path to megabytes). Another 1024 steps toward gigabytes in this teaching convention. SI vs binary gigabyte debates exist; for creator planning, order of magnitude beats pedantry.
Container overhead and multiple tracks
MP4/MOV containers add a little overhead. Extra audio languages, commentary tracks, and embedded captions can add more. Teaching math uses a simple video+audio mid — good enough for “is this ~1 GB or ~10 GB?” and weak for bit-exact delivery specs.
Two-pass and constrained quality modes
Two-pass VBR aims at a target average bitrate; CRF aims at a quality level and lets size float. Both produce better efficiency than naive CBR for many timelines. The calculator’s fixed mid is closer to “if average Mbps were X” thinking — map your CRF exports back to observed average Mbps after a test.
InputsDuration, resolution, and frame rate
Duration
Longer videos scale size almost linearly at fixed bitrate. Cutting five minutes of fluff saves storage and upload time — and often helps retention too. Related planning: video length calculator.
Resolution
More pixels usually mean higher recommended bitrates for a clean picture. 4K mids dwarf 1080p mids. Many viewers on phones never see full 4K detail. Choose resolution for the story and devices that matter, not for bragging rights alone.
Frame rate
60 fps can look smoother for games and sports. For talking heads, 30 fps (or 24) is often enough. This tool multiplies teaching bitrate at high FPS so storage cost is visible — your encoder may use different scaling.
| Weak habit | Stronger habit |
|---|---|
| Always 60 fps “for quality” | Match FPS to motion needs |
| 4K for every vlog | 1080p when detail and devices do not need 4K |
| Duration = rough guess | Use timeline length you will actually export |
Interlaced and variable frame rate
Most YouTube delivery is progressive. VFR sources can confuse some exports. This calculator assumes a simple constant FPS label. Fix VFR in the NLE when possible before caring about GB to two decimals.
BitrateTeaching bitrate mids
Bitrate is how many bits per second the stream uses. Higher bitrate can preserve more detail at a given resolution — until diminishing returns and platform re-encodes. Teaching mids on this page are planning anchors, not your encoder’s only correct setting.
| Resolution | Teaching video mid (approx) |
|---|---|
| 480p | ~2.5 Mbps |
| 720p | ~5 Mbps |
| 1080p | ~8 Mbps |
| 1440p | ~16 Mbps |
| 4K | ~35 Mbps |
CBR vs VBR vs CRF
Constant bitrate aims at a fixed Mbps. Variable bitrate and CRF/constant-quality modes spend bits where the picture needs them. File size becomes less predictable — often better efficiency. The calculator’s fixed mid is closer to a CBR-style planning thought.
Audio bitrate
We add a simple ~192 kbps teaching audio mid. Music-heavy or multi-channel audio can differ. Audio is usually a small slice next to HD/4K video, but it is not zero.
When higher bitrate helps little
If YouTube will re-encode to its ladder, exporting at extreme mezzanine rates mainly costs disk and upload minutes. For archival masters you keep offline, high quality still matters — label those files as archive, not “YouTube upload.”
CodecsH.264 vs H.265 (teaching)
H.264/AVC is widely compatible and fast to encode on many machines. H.265/HEVC can achieve similar visual quality at lower bitrates for many encodes — at the cost of encode time, licensing/tooling quirks, and uneven playback support outside modern pipelines. This tool’s H.265 option multiplies the video mid by ~0.55 as a teaching stand-in, not a guarantee of 45% savings on every timeline.
What YouTube accepts vs what is smart
Always check current YouTube upload specifications for recommended containers and codecs. Compatibility for your edit machine and collaborators can matter as much as theoretical compression.
AV1 and others
Newer codecs appear in ecosystems over time. This calculator focuses on H.264/H.265 teaching mids. If you export AV1, use your encoder’s estimate — do not force H.264 math onto it blindly.
Encode time is a cost
A codec that halves size but triples overnight render time may lose if you publish daily. Factor machine time into “ROI” the same way you factor disk.
UploadUpload time sketches
Ideal seconds ≈ (file size in megabytes × 8) ÷ upload speed in Mbps. That assumes the entire pipe is yours, with no Wi‑Fi contention, ISP overhead, TCP slow start, or CPU-bound hashing. Real uploads usually take longer. Processing after upload is separate wall-clock time.
| Ideal link | Use |
|---|---|
| ~10 Mbps | Conservative home upload sketch |
| ~50 Mbps | Common mid sketch |
| ~200 Mbps | Fast fiber-class sketch |
How to use the three speeds
If your speed test shows ~40 Mbps upload, plan near the 50 Mbps row and still add buffer. Overnight uploads exist for a reason. Keep the machine awake; verify the file finished.
Upload ≠ ready for viewers
After 100% upload, YouTube still processes. HD/4K ladders can take additional time. Do not schedule a premiere one minute after “upload complete” on a huge 4K file without processing buffer.
YouTubeRe-encode reality and limits
YouTube re-encodes uploads into multiple renditions. Your perfect export is a source for their pipeline, not what every phone plays bit-for-bit. Extremely high bitrates often fail a cost/benefit test for delivery files.
File size and duration caps
Platform limits (maximum file size, maximum duration, verification tiers) change. This tool does not hard-block uploads against a live policy API. Read current YouTube Help before assuming a number from a blog or from our teaching checklist.
Recommended settings docs
Official encoding recommendations exist for a reason: they target quality that survives re-encode without absurd files. Use them as defaults; use this calculator to see GB impact when you deviate.
Shorts and vertical
Vertical 1080×1920 still uses a resolution-class bitrate mid in spirit; this UI uses labels like 1080p rather than full pixel matrices. For Shorts-length videos, duration is short so files stay modest unless bitrate is extreme.
Thumbnails, end screens, and non-video assets
Custom thumbnails, end-screen design assets, and project graphics are tiny next to HD video — until your design library becomes thousands of PSDs. Keep that archive separate from “per video export GB” mental math.
Live streams and premieres
Live streaming has its own encoder bitrate settings and is not the same as uploading a VOD file. Premieres still require a finished file upload (or a stream, depending on setup). Use this tool for VOD file logistics; use encoder docs for live.
Team handoffs
If an editor delivers a “YouTube master,” agree on resolution, FPS, codec, and target average bitrate in writing. Then both sides can run the same teaching sketch and avoid surprise 40 GB drops into a 20 GB free drive.
PitfallsCommon file size mistakes
| Weak habit | Stronger habit |
|---|---|
| Exporting 100 Mbps “just in case” | Stay near sensible web delivery ranges |
| Forgetting 60 fps storage cost | Justify high FPS with motion needs |
| Planning only final MP4 size | Budget raw + project + export |
| Trusting ideal upload minutes | Add real-world buffer |
| Confusing viewer quality with export Mbps | YouTube re-encodes either way |
| H.265 always half size | Measure your encoder, do not assume |
| Filling disk to 0 bytes free | Leave headroom for export temp files |
| Skipping test exports | One 30-second test teaches more than guesses |
The overnight surprise
Starting a 40 GB upload at 11:55 pm on flaky Wi‑Fi is how premieres slip. Size sketches exist so you start earlier — not so you cut it closer.
FAQ-stylePractical questions
How big is a 1-hour 1080p video?
Often a few GB at common web delivery bitrates — teaching mid on this tool lands around that class for H.264 1080p30. Action-heavy VBR/CRF exports vary. Run the calculator with your settings and confirm with a real export.
How big is a 10-minute 4K video?
Multiple GB at 4K teaching mids — larger with high FPS and H.264. H.265 teaching mid shrinks the sketch; still plan disk carefully.
Does 60 fps double file size?
Not always exactly 2×, but high frame rates often need more bits for similar per-frame quality. This tool multiplies the teaching mid at 60 fps so the cost is visible. Measure your encoder for truth.
H.264 or H.265 for YouTube?
H.264 remains a compatibility workhorse. H.265 can save space with longer encodes. Check current YouTube recommendations and your tool chain. Neither choice replaces good lighting and clean audio.
How long to upload 1 GB?
Ideally ~800 seconds at 10 Mbps, ~160 seconds at 50 Mbps, ~40 seconds at 200 Mbps — before real-world slowdowns. Use the tool’s three sketches as lower-bound style planning.
What is YouTube’s max file size?
Limits are policy-defined and can depend on account state. Verify YouTube Help; do not rely on a third-party page (including this one) as the legal source of limits.
How do I reduce size without “losing quality”?
Sensible bitrate, appropriate resolution/FPS, modern codecs, and CRF/VBR. Cutting resolution or FPS when viewers will not benefit is honest optimization. Fake “zero quality loss” claims ignore psycho-visual reality — pick tradeoffs deliberately.
Is the calculator free?
Yes. Unlimited local sketches, no signup.
Does this compress my video?
No. It only estimates. Compress/export in your NLE or dedicated tools. Browser tools on this site (e.g. video to GIF, audio converter) are separate jobs.
Why does my export not match the estimate?
Different bitrate, CRF, audio, motion, two-pass settings, or container overhead. That mismatch is expected. Use the estimate for planning; use the file properties panel for truth.
Should I export higher than YouTube recommends?
Sometimes a modest headroom is fine; extreme rates often waste resources. For archival masters, keep a high-quality copy offline and upload a delivery encode.
What about HDR?
HDR pipelines have different bitrate and color requirements. This calculator’s simple SDR-oriented mids are not an HDR delivery guide. Follow official HDR upload guidance when applicable.
How much storage for a year of weekly videos?
Multiply weekly export size × 52, then add raw/project overhead if you archive those. The calculator helps per-video; yearly planning is spreadsheet multiplication with honest retention of raw files.
Does bitrate equal quality score?
No. A clean 8 Mbps talking-head can look better than a noisy 20 Mbps mess. Lighting, focus, and encoding mode matter. Bitrate is capacity, not a grade.
Can I enter bitrate manually?
Not as a separate field in this UI — resolution/FPS/codec choose teaching mids. If you know exact Mbps, you can still compute offline: GB ≈ (Mbps × seconds) / 8 / 1024. The article formula is the same engine.
What about ProRes or DNx for YouTube?
Mezzanine codecs make huge files and are great for editing, usually poor choices as final YouTube uploads. Transcode to a delivery encode (often H.264/H.265 in MP4) for upload; keep ProRes as an offline master if needed.
Do subtitles increase file size a lot?
Soft subtitle files (SRT/VTT) are tiny next to video. Hard-burned captions are pixels inside the video encode — they do not add a separate track size, but they can slightly change compressibility. Use the SRT toolkit for timing work; do not expect caption files to dominate GB math.
How accurate are the upload sketches on mobile hotspots?
Hotspots vary wildly and often fall far below a speed-test peak. Treat even the 10 Mbps row as optimistic if signal is weak. Download a speed test’s upload number, then still add buffer.
Should I compress with HandBrake before upload?
If your NLE export is oversized relative to delivery needs, a careful HandBrake (or similar) pass can help. Match resolution/FPS, use a sensible RF/bitrate, and preview quality. This site’s calculator only estimates — it is not HandBrake.
SummaryQuick reference
| Item | Remember |
|---|---|
| Size formula | (Mbps × seconds) ÷ 8 ÷ 1024 GB |
| Inputs | Duration, resolution, FPS, codec |
| Mids | Teaching only — NLE wins |
| Upload sketch | Ideal link; add buffer |
| YouTube | Re-encodes; check current help |
| 60 fps / 4K | Costly when unjustified |
| H.265 mid | ~0.55× teaching — measure real |
| Not claimed | Exact export GB or live ETA |
| Next action | Tool |
|---|---|
| Plan target length | Video length calculator |
| Script length vs minutes | Word count calculator |
| Short clip as GIF | Video to GIF |
| Audio-only export path | Audio converter |
One honest experiment
Export a 30-second sample at your usual settings. Note real MB. Scale linearly for a rough full-length guess and compare to this tool’s mid. Adjust your mental model — then schedule uploads with buffer.
File size is logistics: disk, time, and patience. Quality is craft. YouTube’s pipeline is a third system. This calculator only multiplies teaching bitrates so logistics stop being pure guesswork.
This guide stays free of fabricated perfection cards and year-stuffed hype. The math is simple on purpose. Make the inputs match your real export intent, and the sketch becomes useful planning — not cosplay engineering.