Final Cut Pro Export Settings for Review Copies Clients Can Open Anywhere
Final Cut's default ProRes export is built for masters, so here are the H.264 and Compressor settings I use in my agency to keep every client review copy small, quick to upload and easy to open.
Final Cut Pro's default ProRes export is the wrong file to send a client for review, right, and I say that bluntly because I have watched it eat whole evenings in my own agency. An editor finishes a rough cut, hits Share with the defaults, and then watches a huge file crawl into a cloud folder for a version that will be dead by tomorrow lunch. Getting your Final Cut Pro export settings for review sorted is a boring decision, but it quietly sets the pace of every round you run with a client.
I run a video editing agency alongside building PlayPause, so I have been the editor staring at the upload bar and also the person chasing a client who is trying to open a 30 GB file on hotel wifi. What I keep noticing is that the slow rounds are almost always the ones where the file we sent was far heavier than the decision it was carrying.
So this is basically how I set it up now, the Share settings I actually use, the Compressor setting worth saving once, some napkin math on file sizes against upload ceilings, and the part where each export stacks as the next version instead of becoming a folder of files called final_v3_REAL.
A review copy gets watched, commented on and then replaced two days later, so build it for the watching and nothing else.
What a Final Cut Pro review copy needs to do
Before touching a single dropdown, it helps to be clear about what this file is for, right, because a review copy has a much narrower job than the master you deliver at the end. The person opening it is usually not an editor, they are in a browser on whatever laptop or phone they had open, and they only need the picture and sound to be good enough that their notes are about the edit rather than about blocky skies. Whether it is a rough cut or a near final pass, that bar barely moves.
Speed is the part everybody underweights, mostly because nobody times the whole loop. A round goes export, upload, watch, comment, revise, right, and the slowest step sets the pace for all the others, so at the end of the day a gorgeous file that takes ninety minutes to upload has lost before the client presses play. As I explain in the editor's guide to video compression fundamentals, a well made H.264 at a sane data rate looks the same as your timeline for a note on pacing, structure or copy.
A review copy is also disposable, since you will make another one in two days, so any manual step you repeat every round is a small tax you keep paying across the project.
The export you send for review and the export you send for delivery are two different files with two different jobs.
Final Cut Pro export settings for review: Master File versus Apple Devices
Select your project, open the Share menu, and you have two realistic options plus a lot of noise. The default destination is Export File, which many of us still call Master File because that is what the Final Cut Pro share master file route was named in older versions, and out of the box it hands you Apple ProRes 422 at full resolution. That is exactly right for a master and wildly oversized for review, and I'm pretty sure this one default causes more late night uploads than any other button in the app.
You keep Export File and change what is inside it. In the Settings tab, set Format to Computer and Video Codec to H.264, and if your version splits that into Faster Encode and Better Quality, pick Better Quality. Keep the frame rate matched to your project. Keep resolution matched too, unless you are on a 4K timeline and the note is about pacing, where a 1080p copy is fine, and check the Roles tab so you export one stereo mix rather than a multitrack file.
The Apple Devices 1080p and 4K destinations in the same menu are the other honest option for a final cut pro h.264 export, and for a talking head or a simple social cut they are genuinely fine. The catch here is that they target a fixed resolution, so a vertical or odd sized timeline can come out scaled in ways you did not plan. I open the result in QuickTime and check its size and frame rate before it goes anywhere, and Apple's Final Cut Pro user guide covers every Share destination if you want the full list.
HEVC also sits in that codec list and makes a smaller file at the same quality, but it encodes slower on older Macs and some client machines struggle with it after a download, so for review I stay on H.264.
Building reusable Compressor settings for review
If you export for clients every week, saving your own Compressor settings for review is a really really boring twenty minutes, and trust me on any level, it pays for itself by the second project. You build it once, right, add it to the Share menu, and the bitrate stops being a decision anyone makes at the end of a long day.
In Compressor, click the add button at the bottom of the Settings pane, choose New Setting, and pick QuickTime Movie or MPEG-4. Set the codec to H.264 and switch the data rate from automatic to a custom number, because automatic is what makes file sizes unpredictable between projects. I use around 8 to 10 Mbps for 1080p and 20 to 30 Mbps for 4K, key frames on automatic, multi pass off if it is offered, and AAC stereo audio at 256 kbps, which is plenty to judge a mix on laptop speakers.
For a sanity check, YouTube's recommended upload encoding settings ask for about 8 Mbps at standard frame rate 1080p, which is right where my review setting sits. For 4K they ask for around 35 to 45 Mbps, because YouTube treats your upload as a master it will re-encode for every screen, and a copy watched on one client's laptop does not need that headroom.
Save it as something obvious like Client Review 1080, then in Final Cut choose File, Share, Add Destination, drag Compressor Settings into the list and pick your setting. For instance, my agency keeps three of these, for vertical social cuts, 1080p horizontal and 4K, and nobody on the team has thought about a bitrate in a very very long time. Does that make sense, right, the numbers matter far less than the habit of deciding once. On Agency we also put the export spec in each client's Playbook as a checklist item, so whoever exports next ticks off the right setting.
File size, upload limits and when to send ProRes anyway
Here is the napkin math I wish someone had shown me early. File size is basically data rate times duration, so a ten minute cut at 10 Mbps is 6,000 megabits, which is roughly 750 MB. The same ten minutes as ProRes 422 at 1080p, where Apple's target rate sits around 120 to 150 Mbps depending on frame rate, lands between about 9 and 11 GB, and the 4K version has four times the pixels and goes well past 30 GB. So the review copy is about a twelfth of the default export, for a picture the client will not tell apart on a laptop.
That math is where the export choice collides with the platform you send to, right, because every review tool has a ceiling. On PlayPause the max upload is 10 GB on Creator and unlimited on Agency and Enterprise, so an H.264 review copy sails through on any plan, while a ten minute 1080p ProRes file already scrapes the Creator ceiling.
There are still times to send ProRes, mostly when the person receiving it will do more than watch, like a colourist checking a grade on a calibrated monitor or a VFX artist pulling a plate. In a grade check, H.264 banding in a sky gets flagged as a note when it is really a compression artefact, and that wastes a round. Outside those cases, to be very honest, I cannot remember the last time a client needed a master to give me a creative note.
PlayPause makes a streaming copy for browser playback and leaves your original untouched. Everyone on the thread watches the streaming copy, the original sits there for the one person who needs it, and on Agency a viewer can save it straight to Google Drive. The proxy and transcoding page explains that path, and it is why a heavy upload stops being a heavy download for everyone downstream.
Uploading from your Mac without babysitting the transfer
Once Final Cut writes the file, I drop it into the PlayPause Mac desktop app and let it handle the upload while I get on with the next thing. For a batch of social cutdowns, bulk upload takes a hundred plus files in one go. Nothing from PlayPause runs inside Final Cut itself, so the honest workflow is export, upload, review, then work the notes back in your editor, which I walked through in the piece on sending a cut for review without handing over your library.
The client gets one link, right, and opens it in a browser without an account or an install, and their comments land on the exact frame instead of in an email that says "around the middle bit". The link can be password protected or revoked instantly if the wrong version went out, and you can see who opened it and when, which has ended more than one "I never got it" conversation in my agency. If you work solo, the page for freelance video editors covers setting this up without it feeling corporate.
Export a full quality master every round, wait on the upload, then chase a client who cannot open the file
Export a light review copy, drop it into the Mac app, and the client opens one browser link while your original stays untouched
Keeping each export stacked as the next client version
Every new export should stack on the same card as MV1, MV2, MV3 and so on, right, because the moment you have three separate uploads in a folder the client will comment on the wrong one, and you will lose a morning reconciling notes that were never about the same cut. With a stack, the version label tells everybody which cut they are looking at.
Stacked versions also open up side by side compare on Agency and up, where MV2 sits next to MV3, which is really useful in a picky colour round or when a client swears a shot used to be longer. I weighed that against staying inside the app in the piece on Final Cut markers versus review links.
- Keep one card per deliverable for the whole life of the project
- Name exports by version, never by date or by "final"
- Let the platform hold version history instead of your Finder window
The same discipline works in any editor, which is why the Premiere export settings for client review guide reaches almost identical conclusions, and the Final Cut for iPad export route is worth knowing if you cut away from your desk. You see what I mean here, the menus move around but the review copy stays the same, and it fits the wider client approval stages of any project.
- Audio mixed loud enough to judge on laptop speakers
- Frame rate matching your timeline exactly
- A readable version name on the file itself
- Link permissions set before you send it
Frequently asked questions
What export settings should I use for a Final Cut Pro review copy?
Choose Share, then Export File, set Format to Computer and Video Codec to H.264, and leave resolution and frame rate matched to your timeline, which gives the client a file that plays anywhere at a fraction of the ProRes size. If you export every week, build the same thing as a custom Compressor setting at around 8 to 10 Mbps for 1080p, add it as a Share destination, and you never pick those options by hand again.
Do I need Compressor for a final cut pro h.264 export?
No, the built in Share options handle H.264 well on their own, and for most rounds that is all you need. Compressor earns its place when you want a fixed data rate instead of an automatic one, so file sizes stay predictable across projects, and when you want one saved setting the whole team exports with. For me it is about consistency far more than picture quality.
Should I ever send ProRes when I export for client approval on a Mac?
Only when the person receiving it will do more than watch, so a colourist checking a grade, a VFX artist pulling plates or a sound house conforming to picture. For a creative note on pacing, structure or copy, a good H.264 gets you the same answer far faster. Check your upload ceiling first, right, since a long 4K ProRes file sits comfortably on Agency and Enterprise and can blow past the 10 GB limit on Creator.
Does PlayPause plug into Final Cut the way it does into Premiere?
No, and I would rather be straight with you about that. The Premiere Pro panel shows comments inside Premiere and jumps the playhead when you click one, and nothing like that exists for Final Cut, so the flow there is export, upload, review, then work the notes back in your editor. The PlayPause for Final Cut Pro page walks through what that looks like day to day.
Every one of these is a small decision you make once, right, so that every round after it is one export and one link instead of an evening of file management. If you want to test it on your next client cut, every plan on PlayPause pricing comes with a 7-day free trial and is priced flat per workspace rather than per member, so you can put a real review copy in front of a client this week and see whether the round closes faster.
So yeah. That's my way of saying it.
Saumyajit co-founded PlayPause after years watching review and approval quietly eat creative teams' deadlines. He writes about the workflow side of video, feedback, versioning, and getting to a clean sign-off.
Related resources
Keep reading
Bring your team into one review space
Centralize feedback, lock approvals, and deliver faster, start free today.
Sign Up for Free