Half the size, none of the difference

Most recordings carry two or three times more data than the picture needs. Knowing which setting to lower is the difference between an invisible saving and a visibly worse clip.

01

Which setting saves the most, safely?

Bitrate. It is the amount of data spent per second, and camera and screen recorders set it generously by default. Lowering it is usually invisible until it becomes severe. Resolution is the setting to leave alone, because losing pixels cannot be undone and cropping already discards a large share of them.

02

What each setting saves and costs

Most recordings carry two or three times the data the picture needs, which is why bitrate is where the slack is.

Setting loweredSpace savedWhat it costs
BitrateLarge, often halfUsually nothing visible
Frame rateLargeVisible on movement
ResolutionVery largePermanent, and worse after cropping
Audio bitrateAlmost nothingAccuracy of the words
Trimming lengthDirectly proportionalNothing, if the ends were dead

03

Why platforms compress again anyway

Every major video app compresses what you upload again to suit its own players and network conditions. That means your carefully tuned file is never shown as is. What you control is the quality of the starting point: a clean, moderately sized file survives the platform's compression better than a tiny, heavily squeezed one.

Uploading an extremely large file does not help either. Beyond a certain point, extra data is simply discarded by the platform's own encoder. The goal is a file comfortably above what the platform will produce, not one that tries to preserve every bit of the camera original.

04

Things that compress badly

Fine textures such as grass, water, confetti, noise from low light and fast camera movement all need a lot of data to look good. Clips that contain them fall apart first when the bitrate is lowered, showing blocks and smearing. If your footage is full of these, be more generous with the settings.

Flat, well-lit talking heads compress beautifully. A speaker in front of a plain wall can survive aggressive compression with almost no visible change. Knowing which kind of footage you have tells you how far you can push the file size down.

05

Keeping the original untouched

Always compress a copy, never the only file. Once detail is thrown away it cannot be recovered, and you may want the full-quality recording later for a longer edit, a different platform or a future clip. Storage is cheap compared with the cost of re-recording.

Name compressed versions clearly, for example by adding the word upload to the file name, so you never mistake a reduced copy for the master when you come back to the project months later.

06

A quick visual check

After compressing, play the original and the smaller version side by side on the screen your viewers use, pausing on the busiest moments. If you cannot tell them apart at normal viewing distance, the saving is real. If you can, step back one level and check again.

Pay particular attention to faces and on-screen text. Viewers forgive a softer background, but blotchy skin or blurred letters make a clip look cheap immediately.

07

Smaller file, same clip

  • Lower bitrate before anything else. It is the setting with the most slack in it.
  • Leave resolution alone. Cropping to vertical already uses a fraction of the width, so pixels are the thing to keep.
  • Compare a few seconds side by side. Judge the saving on your own footage rather than on a rule.

Compress a copy and run both to compare.

Questions people ask

How much can I cut without seeing it?
It depends on the footage. Static talking heads tolerate a lot; fast movement and detailed scenes tolerate less. A short test tells you more than a number.
What about lowering the frame rate?
It saves real space and it changes how motion looks, so it is a visible change rather than an invisible one.
Is audio worth compressing?
There is little to gain, and audio quality directly affects how accurate the words on screen are. Leave it.
Which format should I export?
An mp4 is the safe answer, and it is what most tools produce by default.
Can I avoid this entirely?
A supported link avoids the upload altogether, which sidesteps the whole question.

Read next

01Checking before postingGuide02Consent to recordGuide03When it pays offGuide