How to Compress a Zoom Recording (and Why It's So Big)
How to Compress a Zoom Recording (and Why It's So Big)
An hour-long Zoom call recorded locally routinely lands somewhere between 500 MB and 1.5 GB. That is a strange amount of data for what is, visually, a few faces in boxes and some slides.
The size is not arbitrary, and understanding where it comes from makes it obvious which fixes work. It also makes clear why Zoom recordings compress extremely well after the fact — often to a tenth of their original size with no visible difference.
Why the Files Are So Large
Real-time encoding under load. Zoom encodes while simultaneously running the call — decoding everyone else's video, handling audio, sharing your screen. It cannot afford to spend time analysing frames for efficient compression, so it uses fast settings that produce more bits than the content requires. This is the same constraint that makes screen recordings large, discussed in reduce screen recording file size.
Parallel tracks. A local recording can capture gallery view, active speaker view, the shared screen, and per-participant audio as separate streams. The conversion that runs when the meeting ends assembles these; it does not meaningfully compress them.
Editor optimisation. Zoom's "Optimize for third-party video editor" setting produces a file that is easier for editing software to scrub through — at the cost of a substantially larger file. Most people have this on without knowing what it does.
Constant capture of static content. Video calls are largely static. A face barely moving against a fixed background, or a slide sitting unchanged for ninety seconds, generates almost no new visual information — but a real-time encoder still writes a steady stream of bits for it.
That last point is the reason for the good news: a properly configured re-encode has enormous room to work with.
Compressing a Recording You Already Have
Settings that suit Zoom content
Zoom recordings are the easy case. Faces on static backgrounds and shared slides both compress far harder than general video.
| Setting | Value |
|---|---|
| Encoder | H.264 (sharing) / H.265 (archiving) |
| Quality (RF/CRF) | 25–27 |
| Resolution | 1280×720, or 1920×1080 if slides carry fine detail |
| Frame rate | 30fps, or 24fps for slide-heavy calls |
| Audio | AAC 96–128 kbps — speech does not need more |
| Preset | Medium |
RF 25–27 is aggressive by general video standards but appropriate here. A landscape shot at RF 26 would show visible artefacts; a talking head at RF 26 looks essentially identical to the source. See best HandBrake settings for how RF values map across content types.
Audio deserves a note: Zoom records AAC at a higher bitrate than speech requires. Dropping to 96 kbps mono for a voice-only recording is inaudible and can save 30 MB across an hour.
The ffmpeg one-liner
ffmpeg -i zoom_0.mp4 -vf "scale=1280:-2,fps=30" -c:v libx264 -crf 26 -preset medium -c:a aac -b:a 96k zoom_small.mp4
A 1.2 GB one-hour recording typically comes out somewhere around 80–150 MB with that, depending on how much video was on.
Trim first
The largest reduction available is usually not an encoder setting. Most recorded calls contain several minutes of arrival chatter at the start and goodbyes at the end. File size scales linearly with duration — cutting a 60-minute recording to the 35 relevant minutes is a 42% reduction before any compression happens.
Recording Smaller in the First Place
In Zoom → Settings → Recording:
- Turn off "Optimize for third-party video editor." Unless you are genuinely editing the recording, this only inflates the file.
- Turn off "Record a separate audio file for each participant." Useful for podcast editing, wasteful otherwise.
- Turn off "Record video during screen sharing" if the participant thumbnails do not matter. Screen-share-only recordings are dramatically smaller.
- Consider cloud recording. Zoom re-encodes cloud recordings server-side after the meeting, producing files roughly a third to a half the size of local ones. The trade is storage limits on your plan and less control over the original.
In the main Video settings, disabling HD for your own camera also reduces the recorded size when your video is part of the capture.
Hitting Specific Sharing Targets
| Destination | Practical limit | Approach |
|---|---|---|
| Email attachment | 20–25 MB | Only viable for short clips — trim hard, 720p, RF 27. See email attachment size limits |
| Slack | 1 GB (paid) | Compression optional but courteous — large uploads are slow and consume workspace storage |
| Google Drive / Dropbox | Effectively unbounded | Compress anyway to cut upload time. See compress video for Google Drive |
| Telegram | 2 GB free / 4 GB Premium | Send as a file to avoid Telegram's own re-encode — details here |
| LMS / course platform | Often 100–500 MB | 720p at RF 26 usually clears it comfortably |
For emailing specifically: a one-hour recording will not fit under 25 MB at any watchable quality. Send a link. Compressing video for email covers where the practical boundary sits.
To work backwards from a hard limit, the video file size calculator converts target size and duration into a bitrate.
What to Expect
Approximate results from re-encoding a local Zoom recording at 720p, RF 26:
| Original | Typical compressed size |
|---|---|
| 30 min, gallery view, 4 participants | 600 MB → ~50–70 MB |
| 60 min, screen share + speaker | 1.2 GB → ~80–120 MB |
| 60 min, audio-heavy with static slides | 900 MB → ~40–60 MB |
Reductions of 85–95% are normal, which reflects how much headroom real-time encoding leaves on the table rather than anything clever in the re-encode.
Doing It in One Step
The settings above are not hard, but nobody wants to open HandBrake and reason about RF values after every recorded call — which is why most Zoom recordings sit at full size in a folder until the disk fills up.
Compresto handles it on macOS. Drop the recording in, pick a target size or quality level, and it selects the codec, resolution and quality for you. It uses Apple's media engine, so an hour-long recording compresses in well under a minute rather than grinding the CPU, and it processes folders in batch — useful if you have a term's worth of recorded meetings to deal with at once.
Everything runs locally, which matters: recorded calls frequently contain things that should not be uploaded to a web compression service.
Frequently Asked Questions
How big is a one-hour Zoom recording?
Local recordings usually fall between 500 MB and 1.5 GB per hour. Cloud recordings are smaller, roughly 150–500 MB, because Zoom re-encodes them server-side after the meeting.
Can I compress a Zoom recording without losing slide readability?
Yes. Keep the resolution at 720p or higher and shared screen content stays sharp — flat colour and text are the cheapest content to encode, so a quality setting that would soften camera footage leaves slides untouched.
Where are Zoom recordings saved on a Mac?
By default in ~/Documents/Zoom/, in a folder named for the meeting date and title. The MP4 appears after the conversion step that runs when the meeting ends.
Why is my Zoom recording not converting?
The conversion step can fail if Zoom quits or the machine sleeps during processing. Double-clicking the .zoom file in the recording folder restarts it. If that fails, Zoom's zTscoder recovery tool can process the raw capture files.
Should I record locally or to the cloud?
Cloud recordings are smaller and get re-encoded properly, but consume plan storage and give you less control. Local recordings are larger but yours outright. If size is the concern and you have cloud storage available, cloud is the easier answer.
Does compressing a Zoom recording affect the audio?
Only if you choose to reduce the audio bitrate. Speech is transparent at 96–128 kbps AAC, well below what Zoom records at, so dropping it is usually free. Music or anything with production value deserves 160 kbps or more.
How do I compress a Zoom recording on Windows?
The same settings apply — HandBrake and ffmpeg are both cross-platform. Use H.264 at CRF 25–27, 720p, 30fps. The Zoom-side settings for smaller recordings are identical across platforms.