Blog · 28 August 2026

4K video file size: what one minute really weighs

From 260 MB to over 13 GB per minute, depending on the codec. The bitrates manufacturers publish, the formula for sizing your own file, and how to send it.

What one minute of 4K actually weighs

The figures below come from manufacturers' own technical pages, checked on 28 August 2026. The "1 minute" and "10 minutes" columns follow by simple multiplication.

Sources: YouTube's recommended upload bitrates; Blackmagic Design's technical specifications for the 3840 × 2160 row; Apple's ProRes support page, which requires an external drive able to write 220 MB per second to record 4K at 60 fps, and 440 MB per second at 120 fps.

Note the spread: roughly 1 to 50. Two files labelled "4K" can weigh 340 MB or 13 GB for the same minute of footage. That is why a number picked up from a forum is useless to you — you need your own.

The formula, in one line

A video file is a bitrate flowing for a length of time. Nothing more.

• Bitrate in MB per second × 60 = one minute. 51 MB/s → 3,060 MB, or 3 GB.
• Bitrate in megabits per second × 7.5 = one minute. 45 Mbps → 337 MB.

The 7.5 comes from dividing by 8: a byte is eight bits, and a minute is sixty seconds. This is the classic trap in spec sheets, which quote codecs in megabits and drives in megabytes. A factor of 8 sits between them, and it slips into estimates and client quotes alike.

Where do you read your own bitrate? A file's info panel shows it ("total bitrate"), and any editing suite prints it in the export window, right next to the codec.

Why two "4K" videos weigh completely different amounts

Four settings account for the difference, and resolution is not one of them.

1. The codec. By far the dominant factor. H.264 and HEVC store a full frame now and then, and after that only what changed between frames. ProRes writes every frame in full — which is what makes it comfortable to edit, and what makes it enormous. Apple puts it plainly: ProRes files take up as much as 30 times the storage of HEVC files.
2. The frame rate. Going from 30 to 60 fps means twice as many frames to write. The file does not quite double — expect about half as much again.
3. Colour depth. HDR, 10-bit and Log encoding pack more information into every pixel. That is what makes grading possible, and it is paid for in gigabytes.
4. What moves in frame. A locked-off shot of a wall compresses beautifully; a handheld shot in a crowd does not. On a variable-bitrate codec, two shots of equal length easily differ by 30 %.

"552 5.3.4 Your message exceeded Google's message size limits"

This is the wall almost everyone hits after the shoot: trying to email the file. Sometimes the answer only arrives later, as a bounce message:

552 5.3.4 Your message exceeded Google's message size limits

There is nothing to fix. No consumer mail service accepts a 4K video, however short it is.

And those few seconds are generous. Email carries text only, so the video is rewritten into printable characters before it leaves, which makes it about a third heavier in transit. Under a 25 MB limit you need a file of roughly 18 MB on disk — two or three seconds of 4K.

The hard part is not storing it, it is moving it

Storing 40 GB costs nothing now. Pushing it across the internet is another matter, and three things get in the way.

Time. Your upload speed — the one that matters when sending — is far below your download speed. On a line that uploads at 10 Mbps, 8 GB takes 1 hour 47 minutes. On a 200 Mbps upload, five minutes. Do that sum before promising a client a delivery time.

Interruptions. A ninety-minute upload has plenty of time to meet a dropped connection, a sleeping laptop, a lift. On many tools, the whole thing then starts again from zero.

Quotas. Dropping 60 GB of rushes into a free storage plan fills it in one go — and with Google the same quota serves Gmail, so once it is full you stop receiving mail altogether.

Sending the 40 GB as they are — no account, no subscription

Compressing harder is not the answer when the file has to stay editable: nobody re-encodes ProRes rushes to H.264 to email them to an editor, or there was no point shooting ProRes.

toobigtoshare moves the file exactly as it is, up to 2 TB per transfer — a full camera card goes in one piece. You drop the file, you get a link, you paste it wherever you like. Whoever receives it clicks and downloads: no account to create, on either side, and no email address is asked of you. If the upload is cut off, it resumes where it stopped instead of starting over. The file is deleted after 3 days, at a date and time shown to you up front.

There is nothing to cancel either: $5.49 for one transfer, whatever its size. No monthly plan, no volume tiers.

Send your 4K rushes — up to 2 TB, no account, one link to paste anywhere.

Frequently asked questions

How big is an hour of 4K video?

About 20 GB for 4K compressed at 45 Mbps, the bitrate of a careful web export. The same hour shot in ProRes 422 HQ approaches 400 GB, and passes 700 GB in ProRes 4K at 60 fps. Always multiply your own bitrate by 3,600 seconds rather than trusting an average.

Is 4K four times bigger than 1080p?

No — about five times bigger at comparable settings: 8 Mbps for 1080p against 35–45 Mbps for 4K in YouTube's recommendations. 4K has four times the pixels, but compression removes some of that, while HDR and frame rate add it back.

Should I compress a 4K video before sending it?

For final delivery, yes: an export at 45 Mbps still looks excellent on screen. For rushes headed to an edit or a grade, no — re-encoding destroys exactly the information the editor needs. In that case, send the original file as a link.

What is the difference between Mbps and MB/s?

A byte is eight bits, so 8 Mbps equals 1 MB/s. Codecs and broadband plans are quoted in megabits, drives and files in megabytes. Confusing the two puts a factor of 8 into both your size estimate and your upload time.