Why Is My Video File So Large? (And How to Fix It)

A video file is large for exactly one reason: its bitrate multiplied by its length. Everything else people blame — 4K, 60 fps, the codec, the camera — matters only because it pushes the bitrate up. Once you can see the arithmetic, the fix is obvious, and it is usually one change rather than five. Most oversized files shrink by 50–80% with no visible difference, and you can do it free in your browser at the video compressor without uploading anything.

The one piece of arithmetic

File size ≈ (video bitrate + audio bitrate) × duration ÷ 8

Bitrate is measured in megabits per second, file size in megabytes, and there are 8 bits in a byte — that division is the only fiddly part. A worked example:

• A 1080p clip recorded at 12 Mbps, running 10 minutes (600 seconds).
• 12 × 600 = 7,200 megabits.
• 7,200 ÷ 8 = 900 MB.

You can run this backwards on any file you have. Take its size in megabytes, multiply by 8, divide by the length in seconds, and you have its bitrate in Mbps. A 900 MB file that runs 10 minutes is 12 Mbps. Now you know whether the number is reasonable — and for most 1080p content that is watched rather than edited, 12 Mbps is roughly three times more than it needs.

The five things that inflate the bitrate

1. The recorder's default settings

This is the most common cause by a wide margin. Cameras, phones and screen recorders ship with defaults tuned for people who will edit the footage afterwards, which means deliberately generous bitrates. A screen recorder capturing a static slide deck at 40 Mbps is not broken — it is doing what it was told.

2. Resolution

4K has four times the pixels of 1080p, and needs roughly three to four times the bitrate to look equally good. If the video will be watched on a phone, a laptop, or embedded in a page, those extra pixels are being stored and never seen. Dropping 4K to 1080p is the single biggest saving available — commonly 60–75% on its own.

3. Frame rate

60 fps is twice as many frames as 30 fps, and costs roughly 30–50% more bitrate depending on the content. It is worth it for sport and gameplay. It is pure waste for a talking head or a screen recording. Note that this one has to be fixed when you record — re-encoding an existing 60 fps file cannot recover what a 30 fps capture would have saved.

4. The codec

Some formats barely compress at all, on purpose:

• ProRes, DNxHD, MJPEG, uncompressed — editing formats that store each frame separately. ProRes 4K runs to several gigabytes per minute. If your file is absurdly large, check this first.
• Older codecs in AVI files — DivX, Xvid and friends are generations behind H.264 and need far more bits for the same picture.
• H.264 — the universal standard, and a reasonable target for almost everything.
• HEVC / H.265 — roughly half the size of H.264 at similar quality, which is why iPhones use it, at the cost of much worse compatibility.

5. What is actually in the frame

Compression works by storing the differences between frames. A locked-off interview or a slide deck changes very little from frame to frame and compresses beautifully. Confetti, rain, water, foliage, fast pans and video game footage change almost every pixel every frame, and resist compression no matter what you do. This is why two 10-minute 1080p files can differ in size by a factor of five and both be encoded correctly.

Diagnose your file in a minute

What you see	Likely cause	Fix
Gigabytes per minute	ProRes or another intra-only editing codec	Re-encode to H.264. The reduction is enormous — often 95%+.
~170–400 MB per minute	4K recording, probably from a phone	Drop to 1080p and re-encode.
~60–100 MB per minute	Normal 1080p camera footage at a high bitrate	Re-encode at quality 24–26, keep the resolution.
Huge but visually simple (slides, UI)	Screen recorder default bitrate	Re-encode at original resolution — see the screen recording guide.
Large old file, .AVI extension	An outdated codec	Convert to H.264 MP4 with the AVI to MP4 converter.
Reasonable bitrate, still too big	It is simply long	Trim it. Half the length is half the file at zero quality cost.

To read the numbers directly: on Windows, right-click the file and check Properties → Details; on macOS, open it in QuickTime and press Cmd+I; or use MediaInfo on either. All of them show bitrate, resolution and frame rate.

Why some files barely shrink

Occasionally you compress something and get back a file only slightly smaller — or the tool tells you it could not do better. That is not a failure, it is information: your file was already efficiently encoded, and there simply were not many wasted bits to remove.

SqueezeVid checks for this before it starts. It measures how many bits your source spends per pixel and picks a starting quality accordingly — an already-lean file gets a gentler setting than a bloated one, because hammering an efficient source only destroys detail without saving much. Two safeguards follow from the same idea:

• The output cannot come out bigger than the input. The encoder is capped below the source's own bitrate, so re-compressing an already-small file never backfires — a genuine hazard with naive tools.
• Anything under a 5% reduction is reported as a failure, not a success. If your file cannot meaningfully shrink, you get told, with the option to squeeze harder at a lower quality — rather than being handed a "compressed" file that saved you nothing.

Fix it, in order of impact

1. Drop the resolution if it exceeds how the video will be watched. 4K to 1080p is the biggest single win available.
2. Re-encode at a sensible quality. A value of 24–26 removes most of the waste while staying visually indistinguishable in normal viewing.
3. Trim the dead time. The cheapest compression in existence: it costs nothing in quality.
4. Leave the editing format behind. If it is ProRes or uncompressed, converting to H.264 dwarfs every other change you could make.
5. Record smarter next time. 1080p at 30 fps, at a moderate bitrate, and you will never need this article again.

Frequently asked questions

Why is my 10-minute video 2 GB?

That is about 27 Mbps, which points to 4K footage, a high-bitrate camera profile, or an editing codec like ProRes. Work out the bitrate — size in MB times 8, divided by length in seconds — and compare it against the content. A talking-head clip at 27 Mbps is spending three or four times what it needs.

Does a longer video always mean a bigger file?

Yes, linearly, at a fixed bitrate. Doubling the length doubles the size. This is why trimming is such an effective fix and why long recordings cannot hit small size targets — the audio track alone consumes about 1 MB per minute before any picture is stored.

Will compressing make my video look bad?

Not at sensible settings. At a quality value of 24–26 with the resolution unchanged, most people cannot tell the compressed file from the original on a phone or laptop screen, while the file is 50–70% smaller. Visible damage comes from forcing a very small target onto a long or high-motion video, not from compression as such.

Why did my file get bigger after I compressed it?

With some tools that genuinely happens: re-encoding an already-efficient file at a higher bitrate than the original inflates it. SqueezeVid caps the encoder below the source bitrate specifically so the output cannot exceed the input, and it flags any result that failed to shrink by at least 5%.