Compress a Zoom Recording Without Blurring the Slides

There are really two jobs here. One is the file already sitting in your Zoom folder. The other is the setting that made it that size. Most guides handle only the second. This one handles both, in the order you will need them.

Why is a one-hour Zoom recording so large?

Size is bitrate multiplied by time, and nothing else. Zoom's own documentation on recording file formats says recording screen sharing uses about 20 MB of storage per hour, while recording video uses about 200 MB per hour, and it calls both figures an approximation because resolution and content change the result.

Turn those into bitrates and they stop sounding like a lot:

• 200 MB in an hour is 1,600 megabits over 3,600 seconds, about 0.44 megabits per second, or roughly 444 kilobits per second for video and audio together.
• 20 MB in an hour is 160 megabits over 3,600 seconds, about 44 kilobits per second.

Those are tiny numbers. A phone video of a street scene runs at tens of megabits per second. So when a Zoom recording lands at 1 GB, 2 GB or more for an hour, the file is not "big because video is big." Something pushed it to a bitrate fifty times higher than the app's baseline. Divide your file size in megabytes by the length in seconds and multiply by 8 to see what bitrate you actually got. The general formula, and what each part costs you, is laid out in video compression by the numbers.

If your number is near 444 kilobits per second, the file is already lean and you have a little room to move. If it is several megabits per second, you have a lot of room, and the next section explains why.

Which Zoom setting inflates recordings?

Zoom's cloud recording settings include an option to optimise the recording for a third-party video editor. Zoom's support article on cloud recording settings describes it as generating the recording in a standard format that is compatible with third-party editors, and states plainly that it may increase file size. If you turn it on because you might cut the meeting in an editor someday, and then never open an editor, you pay for the bigger file every time.

The practical rules:

1. Leave it off by default. Turn it on only for a meeting you know will go through an editor.
2. Check where you are recording. The documented setting above is for cloud recordings. If you record to your own computer, open the desktop app's recording settings and look for an option with a similar name. Menus move between versions, so read the label and the help text, not a screenshot from a blog.
3. Remember the display. Local recordings capture what is on screen. A very high resolution monitor or a huge shared window gives the encoder more pixels to spend bits on. Lowering the capture resolution before a meeting, or sharing one window instead of a whole display, shrinks the file at the source.
4. Record the share, not the grid, when you can. The same Zoom article puts screen-share recording at a tenth of the video figure per hour. If the audience only needs the slides and the voice, that is the cheapest recording you can make.

None of this helps the recording you already have. For that, you re-encode.

How far can a meeting recording shrink before slides blur?

The honest answer is that it depends on how much the source has already been squeezed, and you can find out in about a minute. The method is to compress at three quality levels, then look at the smallest text on a slide at 100 percent, not in a thumbnail.

The compressor offers three quality targets, and the settings behind them are plain. Each one is H.264 encoding at a fixed constant rate factor, which means "hold this quality and let the file size fall where it falls." FFmpeg's libx264 documentation covers how the CRF and preset options behave if you want the underlying reference.

Preset	CRF	Use it when
High quality	23	The slides carry small text or code and you want the safest result
Balanced	28	Normal meetings, a team archive, anything people will watch once
Smallest	32	Size matters more than looks, such as a long all-hands you only keep as a record

A higher CRF number means more compression. Each step of about six CRF points roughly halves the bitrate for the same footage, which is a rule of thumb rather than a promise, because it depends entirely on the content.

A worked example, measured and labeled

Here is what I measured. I did not have a real meeting I was free to publish, so I built a stand-in: a 120-second, 1280 by 720, 25 fps clip with six slides carrying a headline, body text, a data line and a 16 pixel footnote, plus a slowly drifting gradient in the corner where a webcam tile would sit. I encoded it once as a source file, then ran the exact encoder settings the compressor uses (libx264, veryfast preset, yuv420p, AAC audio at 128 kbps) at each of the three CRF values.

Preset	CRF	Video stream bitrate	Whole file, 120 seconds
High quality	23	about 30 kbps	2.47 MB
Balanced	28	about 25 kbps	2.39 MB
Smallest	32	about 21 kbps	2.33 MB

Two lessons came out of it, and neither is the one I expected.

First, on a clean slide, text survived all three. I enlarged the 16 pixel footnote from each output and could not tell CRF 23 from CRF 32 by eye. That does not mean your recording behaves the same way. This source was crisp before I touched it, and a real Zoom recording has already been through Zoom's own compression, which is why soft text can appear earlier for you. Treat my result as the best case, and run your own three-way test on a slide with the smallest text in the deck.

Second, the audio became the biggest stream in the file. At 128 kbps, audio costs 57.6 MB per hour (128,000 bits per second times 3,600 seconds, divided by 8). In my test the picture was down near 25 kbps while the sound sat at 128 kbps, so audio was about 1.92 MB of a 2.39 MB file. When the video is that cheap, the audio track is where the bytes go. It also means a meeting whose original audio was recorded below 128 kbps can see its audio stream grow slightly after re-encoding, and that is one more reason to compare the output size to the input rather than assuming. If you only need the picture, an audio-free copy is a separate job, and a voice-only archive is a different one.

The takeaway for planning: with slide content, picture quality is nearly free, so spend your attention on checking legibility rather than chasing a smaller CRF.

Should you cut the dead air before compressing?

Yes, and for a second reason beyond tidiness. Waiting-room minutes, the "can everyone hear me" opening and the chatter after the host stops sharing all cost bytes and all cost a viewer's patience. Trim first and the encoder only works on what stays.

Trimming also decides whether the free tier fits. The free compressor takes input files up to 200 MB. Using Zoom's own 200 MB per hour figure for video recordings, a meeting around an hour long sits right at the cap, and anything longer or higher bitrate will not fit. Your options, in order of effort:

1. Trim it. The trim tool lets you cut the start and end. Because a lossless cut can only begin on a keyframe, the first second or two may differ from what you picked. The reasoning is in why lossless trimming snaps to keyframes.
2. Split it. Cut a long meeting into two or three parts and compress each. The method is in splitting a long video into parts.
3. Use Pro. Pro lifts the 200 MB input cap and removes the corner watermark. Without Pro, video exports carry a small semi-transparent VidClip mark in the corner, and on a shared slide that mark sits over part of the picture, so check it does not cover anything you need.

Order matters: trim, then compress. Doing it the other way round means you re-encode footage you were about to throw away.

How do you compress a Zoom recording step by step?

1. Find the MP4. By default Zoom writes local recordings into a Zoom folder under your Documents, but the path is set in the app's recording settings, so look there if it is not where you expect.
2. Note the file size and the meeting length so you can compute the bitrate you started from.
3. Trim the waiting-room and sign-off minutes in the trim tool.
4. Open the video compressor, drop in the file, and pick Balanced to start. The file is read into your browser's memory and processed on your own processor. Nothing is sent to a server, which matters for a recording that includes client discussion.
5. Compare the output size to the input, then scrub to the slide with the smallest text and check it at full size.
6. If it is soft, rerun at High quality. If it is clean, try Smallest and see whether you can tell the difference. Keep the smallest one that reads well.
7. Keep the original until you have played the compressed copy end to end and confirmed the audio stays in sync.

Encoding speed depends on your machine. A browser does the work on your own CPU, so a long recording takes real time, and a laptop on battery takes longer. That is the cost of nothing uploading, and for private meetings it is a fair trade.

Do cloud recordings need compressing at all?

Often not. A cloud recording lives in Zoom's storage and plays from there, so its size matters to your storage quota and to anyone who downloads it, not to someone clicking the share link. Compress only when the file leaves Zoom: you downloaded it to attach to an email, drop into a shared drive that has a size limit, or hand to a client who will download it anyway.

For email specifically, the receiving mail server's limit is the one you cannot see, and the safe target is well under the nominal cap. Compress video for email covers how to size a file with headroom and when a link beats an attachment. The setting from earlier matters here too: if a cloud recording came out huge because it was optimised for an editor, a quick re-encode is usually the easiest fix for a download you need to send.

FAQ

How big is a one-hour Zoom recording?

Zoom's support documentation puts screen-share recording at about 20 MB per hour and video recording at about 200 MB per hour, both described as approximations. Your file can land well above that if a setting such as optimising for a third-party editor is on, or if the capture resolution is high. To see what you actually got, divide the size in megabytes by the seconds, then multiply by 8.

Can I compress a Zoom recording on my phone?

The compressor runs in a browser, so a recent phone browser can load the page, but the work happens on the phone's own processor and memory, and a long recording is heavy for that. A short clip is realistic, and an hour is likely to be slow or to fail on an older device. For a long meeting, a laptop is the safer place to do it, and the 200 MB free input cap applies either way.

Does compressing a Zoom recording affect the audio?

The audio is re-encoded to AAC at 128 kbps, which is comfortable for speech. It is a re-encode, so it is not bit-identical to the original, but speech at that rate does not usually sound different. As the test above showed, the audio stream can become the largest part of a slide-heavy file, so it is worth knowing it is there.

Can I email a Zoom recording?

Sometimes, if you shrink it first and the receiving server allows the size. Both ends impose limits and you only know yours, so aim well under the cap and consider sending a link for anything long. The full reasoning, with a size target per provider, is in compress video for email.