Compress Video for Client Review and Delivery on a Mac

Most limits are generous and a few are brutal. The generous ones belong to tools built for video. The brutal ones belong to anything that began as an email or a phone app. These were read on each service’s own page on 9 October 2026 unless the row says otherwise.

The Instagram and TikTok rows come from developer documentation for scheduling tools and APIs, and the in-app uploader can differ, so test one post first. Notice what is missing: a review platform with a cap that a short 1080p cut would hit. Instagram’s 300 MB is the closest, and a cut at YouTube’s 8 Mbps (about 60 MB a minute) passes it after about five minutes. The small numbers are in email and free transfer tiers.

Duration bites before size. At Vimeo’s 20 Mbps ceiling for 1080p, LinkedIn’s 15 minutes is about 2.25 GB, well under its 5 GB. For the audio side of a production, see compressing audio and video for podcasters.

Sources: YouTube’s recommended upload encoding settings and Vimeo’s compression guidelines. Both are recommendations for what to upload, not targets for what to deliver to a client. Compress a final with Smol only when a slow uplink forces it; otherwise export from the editor at the published bitrate. Some upload endpoints transcode again, so a hard compression before upload can mean paying the quality cost twice. The only generation-loss measurement we have is an ffmpeg four-pass test, in the guide to reducing video file size.

The mismatch for Smol users is that these specs speak bitrate and Smol speaks CRF. CRF is a quality target, and the bitrate is whatever the footage needs. Here is what the quality labels produced on one clip, with the average bitrate worked out as bytes × 8 ÷ 10 seconds.

Measured with H.265 only, on Big Buck Bunny, an animated source with no audio track, so these bitrates are lower than camera footage will need. Handheld, noisy or fast footage lands higher at the same CRF. On this clip only “maximum” (VMAF 96.70) sits inside Vimeo’s 1080p range and above YouTube’s 8 Mbps. H.265 saved 18% to 30% against H.264 at matched quality on that clip, so expect H.264 files to land larger.

We have no Smol H.264 ladder, and CRF values do not carry across codecs. In the same post an H.264 encode at CRF 23 in ffmpeg scored VMAF 93.30 in 7,462,187 bytes, against 6,111,954 bytes at 93.83 for Smol’s H.265 default. For H.264, treat the labels as starting points and check your own result with size in megabytes × 8 ÷ seconds. We also have not documented what Smol does with video frame rate, audio codec or bitrate, or whether it moves the moov atom to the front of the file, so inspect one export in QuickTime Player’s Movie Inspector before relying on it for a platform spec.

For a hard bitrate or file-size target, Smol is the wrong tool: CRF cannot hit a byte count, and Smol’s video settings are codec, quality, speed preset, resolution and audio removal. Profile, GOP length and two-pass bitrate modes are not among them.

Two details deserve a second look. Smol’s resolution choices are bounding boxes: setting 1920 on a 3024×1964 recording produced 1662×1080. We have not tested a vertical clip, so check one before a batch. And there is no 960×540 option, which won a busy-footage test in the email guide. For screen recordings, see compressing a Mac screen recording: a 60-second, 56,384,195-byte recording became 3,691,160 bytes at Smol’s default and 1,399,221 at resolution 1920, in 16.3 seconds.

1. 1

   Start from the master or the best export

   Every compressed copy should come from the highest-quality file you have, never from a previous copy. In ffmpeg, four identical CRF 28 passes took a clip from VMAF 90.03 to 77.37 while the file shrank only 39%. The numbers are here.

2. 2

   Drop the files or the folder onto Smol

   Video, images and PDFs can share one batch. By default each output is a copy next to the original with a _compressed suffix, so originals are not overwritten. Output location and naming can be changed in settings.

3. 3

   Choose MP4 and the codec

   Use the Compress operation, not Convert: quality is a Compress setting. H.264 for anything a client or a platform will open. H.265 is Smol’s default and is the right pick only for your own library or for recipients you know are on recent Apple devices.

4. 4

   Choose quality and resolution

   “high” for review cuts, “maximum” for finals, an exact CRF if you have a number in mind. With H.264, check the result on your own clip. Leave resolution on original unless the destination is smaller. Switch audio removal on for silent b-roll and loops.

5. 5

   Run it and read the per-file results

   Smol shows progress and savings for each file. On its direct compress path, if compressing would make a file larger, Smol keeps the original instead of writing a bigger copy.

6. 6

   Watch it before it leaves

   Scrub to the busiest 30 seconds, read the smallest on-screen text, listen for audio sync, then divide the size by the duration. If it looks blocky, lower the CRF by 2 to 4 and re-encode from the source.

For a single file, the Finder Quick Action adds a “Compress with smol” item to Finder’s right-click menu. For a whole shoot, the batch guide compares the four routes on twelve clips.

Small enough to open from a link on a laptop or a phone, sharp enough that the client can judge the edit. Resolution is your call, and Smol offers original, 3840, 1920, 1280 and 854 wide. Smol does not add a watermark or burned-in timecode, so do that in the editor before you export. Then open the compressed copy and the source in the same player and compare the darkest scene and the skin tones before anything leaves.

The Smol rows come from one animated clip, so camera footage will land higher. The point of the table is the order of magnitude: a ten-minute review cut at the high label is hundreds of megabytes on clean footage, not gigabytes. Check your own.

For where to put it, a review platform beats an attachment. YouTube says unlisted videos can be seen and shared by anyone with the link, so an unlisted link is not a private one. For unreleased work, that is a question for your client’s NDA, not for the encoder.

H.264 for anything a client or a platform will open. H.265 for your own library and for recipients you know are on recent Apple hardware. Smol defaults to H.265, so switching to H.264 is the first change to make for deliveries.

Our calm test clip sat near the 3% end and our busy one near the 30% end; your footage will land somewhere between or beyond. On calm footage like ours, codec does little for size, and the compatibility cost may not be worth paying. On a Mac, Safari plays HEVC everywhere, but our test found an MP4 tagged hev1 unplayable in AVFoundation while the same file tagged hvc1 played. The size and tag tests are in H.265 vs H.264: what actually changes.

Slower than your editor’s export by a wide margin, and that is the main reason not to use Smol on a deadline. Smol encodes in software and processes files one after another. Times below are from the sibling posts, on an Apple M2 Pro, with each post’s own conditions.

On our busy test Mac, Smol’s four-clip runs took anywhere from 24.06 to 85.99 seconds, so treat any single timing as a range. As arithmetic, not a measurement: 24.1 seconds per 10 seconds of 1080p, if it scales, is about 24 minutes for a ten-minute video.

What you get for the wait is quality per byte. Smol’s default scored VMAF 93.83 at under half QuickTime’s bytes. The 4K guide measured the same trade in ffmpeg: its hardware encoder needed 42.5 MB to match the quality its software encoder reached at 5.5 MB. Our view: for the 6 pm review cut, export with your editor’s hardware encoder and send it. Use Smol for the overnight folder, for finals going over a slow uplink, and for files other people sent you. The full trade is in the 4K guide.

No. Masters and intermediates are large on purpose, because they have to survive grading, effects and a second export. Apple’s own ProRes figures put a 1080p, 29.97 fps ProRes 422 HQ stream at about 220 Mbps.

The other side, from the 4K guide: an ffmpeg software encode took a four-second ProRes 422 LT master of 218,034,032 bytes to a 5,479,361 byte delivery file. That file is right for watching and wrong for editing. Smol also writes only H.265 or H.264, so it cannot make a ProRes intermediate, and every pass through a delivery codec loses quality.

If only the container is wrong, do not re-encode at all. Rewrapping an H.264 MOV as MP4 with ffmpeg took 0.06 seconds and came out bit-identical in our MOV to MP4 test. Smol’s convert path always re-encodes, and on that clip the file grew by 37.3%.

HandBrake’s own documentation gives RF 20 to 24 as the range for 1080p, which is a useful starting point whatever tool you use. Adobe’s Media Encoder page lists ingest, proxies, presets and Watch Folders, and HandBrake’s repository shows commits through 9 October 2026. If you already own Media Encoder or Compressor, check them first for video work. See our HandBrake comparison for the long version. Smol earns its place when the folder is mixed, the editor is closed, and you would rather not learn an encoder’s settings.

Frame.io is a different case: it says you do not need to compress before upload and that it prepares your largest files for smooth playback. Take it at its word and send the export.

Smol compresses on the Mac that holds the file. Nothing is uploaded, there is no account and no server, and it works offline. That describes what the software does. It is not a statement about any NDA or contract, which your client and your lawyer decide. Smol’s metadata stripping is documented for images and PDFs; we have not tested it on video files, so do not rely on it there. For stills from the same shoot, see removing EXIF data on a Mac. The wider question of handling client files is in Smol for confidential documents.

Pricing for a team is Solo $29 once for one Mac, Team $49 once for three Macs, and Enterprise $20 per seat, once, from 5 to 500 seats. A preset lives on one Mac, so write the settings down and recreate the same “review cut” preset on each Mac to get consistent output. The photos from the same shoot go through the same app; see Smol for photographers and Smol for marketing teams. Prices are on the pricing page.

A watched folder can compress whatever lands in a “Review exports” folder, with one caveat that matters here: watched folders can make files that are already optimized larger. Point one only at fresh, unoptimized exports, never at files you have already compressed. The behavior is described in the watched folder guide.

If an AI coding agent is part of your pipeline, Smol’s MCP server lets Claude Code, Codex or Google Antigravity run jobs locally. In the batch guide that meant telling the agent to compress a folder at a pinned CRF and reading the per-file byte counts back.

Masters and intermediates. Smol writes H.265 or H.264 only. It cannot make ProRes, and it should never replace a master. If a colorist or another app needs an intermediate, use your editor, Compressor or Media Encoder.

A deadline. A hardware export finished a 10-second clip in 2.2 seconds where Smol took 24.1. If the review cut is due in an hour, export from the editor and send it. Larger files are the price, not a defect.

An exact bitrate or size. CRF targets quality, so Smol cannot land on 8 Mbps or 15.0 MB, and it does not expose profile, GOP or two-pass settings. Where a spec names those, use HandBrake’s average bitrate mode, ffmpeg or Compressor.

Subtitles, chapters, filters, deinterlacing or HDR work. HandBrake and Compressor do these; Smol does none.

A review platform that handles size for you. Frame.io takes files up to 5 TB without compression. Send the export.

A container swap. If an H.264 MOV only needs to be an MP4, ffmpeg -c copy is instant and lossless, and Smol would re-encode.

Not on a Mac. Smol is macOS only, and it needs macOS 13 or later on Apple Silicon, or macOS 14 or later on Intel.