How Many Hours of 4K Video Fit on 1TB

How many hours of 4k video fit on 1tb? At 100 Mbps (typical 4K H.264): about 22 hours. Switch to HEVC at 45 Mbps and it is ~49 hours; 4K streaming at 15 Mbps stretches to ~148 hours. The formula: hours = 8,000,000 ÷ (bitrate in Mbps × 3,600). Check storage math with our free gigabytes to megabytes converter.

The Short Answer: 4K Hours Per Terabyte

How many hours of 4k video can 1tb hold? It depends entirely on bitrate — the number of megabits the encoder writes per second — so there is no single answer, only a formula with famous landmarks. On a true 1 TB (one trillion bytes): 15 Mbps (4K streaming, YouTube/Netflix) ≈ 148 hours · 25 Mbps (efficient HEVC camera footage) ≈ 89 hours · 45 Mbps (YouTube's 4K upload recommendation) ≈ 49 hours · 100 Mbps (typical 4K H.264 from cameras) ≈ 22 hours · 200 Mbps (high-end mirrorless, 4K60) ≈ 11 hours · 734 Mbps (Apple ProRes 422, 4K30) ≈ 3 hours. Two things jump out. First, the range is enormous — 3 hours to 148 hours on the same terabyte — because bitrate spans a 50× range. Second, '1 TB' on the box is not 1 TB on the drive (more on that below): usable space is about 931 GB, which shaves roughly 7% off every number above. The rest of this guide derives the formula, maps real cameras to bitrates, and explains why the codec matters more than the '4K' label.

The Bitrate Formula (4K Video File Size Per Hour)

Every answer on this page comes from one equation. A bitrate of B megabits per second writes B/8 megabytes per second, times 3,600 seconds per hour: GB per hour = B × 0.45. Check: 100 Mbps × 0.45 = 45 GB/hour — matches the standard figure. Then hours on 1 TB = 1,000 GB ÷ GB per hour, or in one step: hours = 2,222.22 ÷ B. Verify against the landmarks: B = 100 gives 22.2 hours; B = 15 gives 148.1 hours. The companion question — 4k video file size per hour — is the same formula read backwards: 15 Mbps = 6.75 GB/hr · 25 Mbps = 11.25 GB/hr · 45 Mbps = 20.25 GB/hr · 100 Mbps = 45 GB/hr · 200 Mbps = 90 GB/hr · 734 Mbps = 330 GB/hr. Two gotchas: this counts video only (audio adds ~0.1–0.5 GB/hr, negligible), and variable-bitrate footage averages out — a static interview at '100 Mbps VBR' may average 60, while fireworks night footage pegs the max. When planning a shoot, always budget with the maximum bitrate your camera's spec sheet lists, then add 10% headroom.

Real Camera Bitrates: iPhone, GoPro, Mirrorless

Spec sheets hide bitrates in footnotes; here are the numbers that matter. iPhone (4K60, HEVC): about 400 MB/min ≈ 53 Mbps → roughly 42 hours per TB — Apple's efficiency is why phones punch above their weight. iPhone (4K60, 'Most Compatible' H.264): about 700 MB/min ≈ 93 Mbps → ~24 hours per TB. GoPro Hero (4K60, H.264): ~100 Mbps → ~22 hours per TB; in HEVC mode ~75 Mbps → ~30 hours. Sony A7S III / A7 IV (4K, XAVC S): 100–140 Mbps → 16–22 hours per TB. DJI drones (4K60): ~120 Mbps → ~18.5 hours per TB. YouTube 4K uploads: the platform recommends 35–45 Mbps for standard 4K, 53–68 Mbps for 4K60 HDR — creators archiving masters at 45 Mbps get ~49 hours per TB. Netflix 4K streams: ~15 Mbps → 148 hours per TB of streamed data (a useful way to size a data cap, not a drive). The pattern: phones and drones sip via HEVC, action cams and mirrorless cameras drink via H.264, and pro codecs (ProRes, DNxHR) gulp hundreds of Mbps. Match your storage plan to your camera's actual codec, not to the '4K' badge — and when the numbers get big, our gigabytes to megabytes converter keeps the units straight.

Codec Matters More Than Resolution

'4K' describes frame size (3,840 × 2,160 pixels), not file size — the codec decides how many bits each frame costs. H.264 (AVC): the universal default, 100 Mbps for good 4K; every device plays it. H.265 (HEVC): roughly half the bitrate for the same quality — 4K that costs 100 Mbps in H.264 costs ~50 Mbps in HEVC, which is why iPhones default to it and why it doubles your hours-per-terabyte. AV1: ~30% more efficient than HEVC still, but encode support is young (YouTube serves AV1; few cameras record it). ProRes / DNxHR: editing codecs that barely compress — gorgeous to cut, brutal to store (hundreds of Mbps; ~3 hours per TB). The practical workflow most creators land on: record in HEVC or H.264, edit in ProRes proxies, archive the camera originals. Archiving in ProRes 'for quality' multiplies storage costs 5–15× for no visible gain over the camera original — the most expensive mistake in this whole guide. And a warning for the quality-obsessed: re-encoding H.264 → HEVC to 'save space' loses a generation of quality each pass; either shoot HEVC natively or accept the H.264 file sizes.

How Many Hours of 1080p Video Fit on 1TB

Drop the resolution and the hours explode — how many hours of 1080p video fit on 1tb is the natural follow-up question. 1080p needs roughly a quarter of 4K's bitrate for equivalent quality (a quarter of the pixels). Landmarks on 1 TB: 8 Mbps (1080p streaming) ≈ 278 hours · 12 Mbps (1080p60, YouTube recommendation) ≈ 185 hours · 25 Mbps (1080p Blu-ray-ish) ≈ 89 hours · 50 Mbps (1080p ProRes proxy) ≈ 44 hours. That 278-hour figure is why 1 TB still feels cavernous for Full HD — eleven and a half days of continuous 1080p streaming fit on one drive. The formula is unchanged (hours = 2,222.22 ÷ bitrate), only the bitrates move. One more useful conversion: 720p at 5 Mbps ≈ 444 hours per TB. If you are choosing between shooting 4K and 1080p for a long event (weddings, conferences, surveillance), this math is the decision: 4K at 100 Mbps gives you 22 hours per terabyte, 1080p at 12 Mbps gives you 185 — and for talking-head footage the visible difference on most screens is far smaller than the 8× storage gap suggests.

Why Your Drive Holds Less Than 1 TB

Every number so far assumed a full trillion bytes — but a '1 TB' drive gives you about 931 GB usable, trimming ~7% off every answer (22.2 hours becomes ~20.7). Why? Drive makers count in decimal (1 TB = 1,000,000,000,000 bytes) while operating systems count in binary (1 TiB = 1,099,511,627,776 bytes) — the same decimal-vs-binary gap our 1TB shows as 931GB explainer covers in full. Formatting (file-system overhead) nibbles a little more. Practical rule: multiply every hours-per-TB figure by 0.93 for real drives. And when buying storage for video, think in shooting days, not terabytes: a wedding videographer shooting 4K100Mbps generates ~45 GB/hour × 10 hours = 450 GB per wedding — one 1 TB drive holds two weddings with headroom, and the 3-2-1 backup rule (three copies, two media, one offsite) triples that. SSD vs HDD changes speed and price, not capacity math: a 1 TB SSD and a 1 TB HDD hold the same ~20.7 real hours of 100-Mbps 4K. Keep the terabyte-to-megabyte formula guide and the ToolNest homepage bookmarked for the rest of the storage math.

Quick Answers

How many hours of 4K video fit on 1TB? ~22 hours at 100 Mbps H.264, ~49 at 45 Mbps HEVC, ~148 at 15 Mbps streaming — on a true trillion-byte TB; ~7% less on a real drive. What is the 4K file size per hour? Bitrate × 0.45 = GB/hour (100 Mbps → 45 GB/hr). Does HEVC really halve file sizes? Roughly — same perceived quality at ~50% of H.264's bitrate, which doubles hours per terabyte. How much 4K can an iPhone hold? A 256 GB iPhone holds ~10.7 hours of 4K60 HEVC (400 MB/min) — and that is before iOS, apps, and photos take their cut. Should I archive in ProRes? Only if you are still editing it — for finished work, the camera original is 5–15× smaller with no visible difference. Run any bitrate through the formula (hours = 2,222.22 ÷ Mbps), or convert the units with our gigabytes to megabytes converter.