Final Cut Pro for iPad Export: Getting a Cut Into Client Review Fast
I cut a lot on an iPad now, so here is the whole loop: export a review copy out of Final Cut Pro for iPad, upload it straight from the camera roll, and let the client comment on the exact frame.
Final Cut Pro for iPad export takes me about five minutes on a nine minute travel cut, and then the file sits in the camera roll until somebody gets back to a desk, which on a location job can easily be two days, right. Five minutes of render against forty eight hours of waiting means the export is well under one percent of the time between finishing the cut and hearing a single note back, and once you count the week that way the whole problem changes shape.
I run a video editing agency alongside PlayPause, and on location jobs a fair share of our first cuts now start on an iPad, basically because the laptop is in a bag back at the hotel while the client wants to see something before the day closes out. When you edit on iPad, client review is the part that still falls over, because the default habit is to wait until you are home, plug in, upload and send, and by then the two days are gone.
So this is the mobile editing workflow I want to lay out, and it is a small one once you have done it twice: export a review copy to the camera roll, upload it with the PlayPause mobile app, send one link, and let the client leave frame-accurate notes in their browser while you are still on the road. There is no laptop anywhere in that chain, right, and to be very honest that is the only claim I am making here.
What Final Cut Pro for iPad export actually gives you
The share options on the iPad version are simpler than the Mac ones, and for a review copy that is genuinely fine. From inside the project you tap the share button at the top of the screen, choose to export, and check the resolution and codec before you confirm. Once the render finishes, the Final Cut Pro iPad share sheet gives you the destinations. Save Video drops the file into Photos, and Save to Files puts it in iCloud Drive or on an external drive plugged into the port, while the codec list stays short, ProRes 422 HQ at the top end and HEVC or H.264 for everything normal.
The catch here is that none of those destinations is a review destination, right, they are storage destinations. A file in your camera roll is invisible to everyone but you, and an iCloud Drive link drops your client into a generic preview player with nowhere to put a note, so the export finishes and you are still zero steps closer to a note on frame 412, does that make sense, right.
One thing to say plainly is that the one native PlayPause panel we build lives inside Premiere Pro. Everywhere else, including both versions of Final Cut, the flow is export, upload, review, and then you work the notes back in the editor yourself. I go into how that shakes out on the PlayPause page for Final Cut Pro, and the wider options are in my roundup of review apps for Final Cut users. It sounds like a downgrade and it really really is not, because a review export is small and quick anyway, and every note comes back with a timecode you can jump straight to.
The export is five minutes of your day and the waiting is two days of it, so fix the waiting first.
Choosing export settings on iPad for a review copy
A review copy is a different animal from a master, and almost every mistake I see here comes from treating the two as the same file. A client watching on a phone in a taxi gets nothing out of ProRes 422 HQ, and what they actually need is a file that uploads over hotel wifi in a few minutes and still shows the cut honestly, so H.264 at 1080p is what I export nine times out of ten.
Keep the frame rate exactly where the project is, right, for two separate reasons. A 25 fps shoot conformed to 30 for review will stutter on every pan, the client will comment on it, and you lose a round explaining that the master is fine. The frame rate explainer on Wikipedia covers why that conversion is never free. The reason people miss is that every PlayPause comment is pinned to a frame, so when the review copy matches the timeline the timecode on a note maps straight back, and when it does not you end up doing arithmetic on every single note.
A worked example on size and upload time
This is the math I run before I hit share, using that same nine minute cut. Google's recommended upload encoding settings put 1080p at around 8 Mbps for standard frame rates and 12 Mbps for 50 or 60, which is a fair sanity check even when the destination is not YouTube. Call it 10 megabits a second, and 540 seconds times 10 is 5,400 megabits, roughly 675 MB, which on hotel wifi uploading at 20 megabits a second is about four and a half minutes. Apple's encoder tends to run a little richer, so the real file may land nearer 1 GB, which is still fine.
Now take the same nine minutes in ProRes 422 HQ at 1080p and 30 fps, which runs at roughly 220 megabits a second, and you are looking at something like 15 GB, or well over an hour and a half of upload on the same wifi. That size decides more than speed, right, because Creator caps a single upload at 10 GB while Agency and Enterprise have no cap, so the ProRes file will not go up on Creator at all, and on the bigger plans you sit on a hotel bed watching a progress bar.
I have a longer breakdown in Final Cut Pro review export settings, and the other side of the fence in Premiere Pro client review settings, and the logic is the same in both, small and matched to the timeline. Once a longer corporate piece moves to the Mac, I also burn a timecode window into the review copy and never into the master, and the reasoning lives in burning in timecode for review.
How to upload video from camera roll into a review link
This is the step everybody assumes needs a computer, and it really does not. PlayPause has a mobile app, and this exact moment is basically why it exists, because you open it, pick the export out of your camera roll, and it uploads into the project you already set up for that client, right. The same app carries statuses and share links, so everything you need on the road lives in one place, and if the app is on your phone rather than the iPad, AirDrop the file across first.
Two things happen quietly on upload. Your original file is never touched, and browser playback runs off a streaming copy, which is why a client on a weak connection can still scrub the cut without downloading a gigabyte first. And if this is not the first pass, the new upload stacks onto the same card as MV2, then MV3, so the client never gets a second link to lose, right. Version stacks are on every plan from Creator up, and for a freelancer running three or four jobs at once that detail quietly does a lot of the admin, which is roughly the argument on the page for freelance editors.
Frame-accurate note, everyone sees the exact same thing.
Sharing the cut with a client from your phone or iPad
The share itself is one link, sent in whatever app the client already lives in, and they open it in a browser with no account and no install. They tap the link and the player is there, and then they can leave a comment pinned to the exact frame, drag a range comment across a section, or draw on the frame when the note is about where something sits rather than when it happens.
You wait until you are back at a desk to upload, so the client sees the cut two days late
You upload from the camera roll on the train and the notes are waiting for you when you land
For anything sensitive, which for me is most brand work before launch, put a password on the link, and remember you can revoke a link instantly the moment a project ends. Link lifespan is a plan thing and worth knowing before you promise a client anything, right, because Creator links run 30 days and then the files expire, Agency links run 90 days, and Enterprise links never expire. For instance, a month long event series fits inside the Agency window, but a client who keeps coming back to cuts from last year needs the never expiring links on Enterprise, and I get into why short-form breaks differently in why short-form review is broken.
Reading client comments and changing status on the go
This is where the mobile loop actually pays you back. The comments come in pinned to the frame, timestamped and threaded, with @mentions when more than one person is looking, and you can read them at an airport gate without opening an editor at all. If you have Slack connected, every comment drops into a channel, which sounds small and is the feature my team notices most, because nobody has to remember to go and check, right.
Set the card to In Review when you send it and to Approved when the client signs off, so nobody has to send a status message at all.
You also get who-watched analytics on Creator and up, so you can see who opened the link, when, and from which city, and I'm pretty sure that is the most quietly useful thing in the product for anyone who has been told "I never got the link". A client who has watched twice and said nothing is a very very different conversation from a client who has not opened it yet, and the analytics tell you which one you are in before you follow up. Custom statuses plus versions is basically the whole revision loop, because everything sits on one card instead of scattering across email and WhatsApp, which I walk through in a revision loop that closes.
Moving the project to a Mac for the final round
At some point you land, and the final round wants a real machine where you can trust the colour and the sound. The move is boring in a good way, because Final Cut Pro for iPad can export the project for the Mac, you open it in Final Cut Pro on the Mac, and the Final Cut Pro user guide covers the import side the first time. As far as I know it is a one way trip, so only make the move once the iPad part of the job is genuinely done.
Then work through the comment list as your checklist, because every note is tied to a timecode you can jump to, and there is no hunting through a WhatsApp thread for what the client said about the second cutaway, which in my agency used to double every round, right.
On Agency and up you also get AI transcription with a clickable transcript, side-by-side version compare for showing what changed between MV2 and MV3, and guest version upload, where a second editor can push a file in with just a name and an email. Playbooks sit on the same plans, and that is where I keep each client's style rules, the lower third font and so on. And if you are still sending Final Cut library folders around to get feedback, read sending a cut without your library before your next job.
Frequently asked questions
Can I run a whole client review from an iPad with no laptop at all?
I do it regularly on travel jobs, so for review rounds the answer is a comfortable yes. Export the review copy from Final Cut Pro for iPad to your camera roll, upload it in the PlayPause mobile app, send the share link, and read the frame-accurate comments as they arrive. The only thing I still take back to a Mac is the final master, because that round deserves a proper screen and proper speakers.
Which export preset should I use for a review copy?
H.264 at 1080p, at the same frame rate as your project, basically every time, because it uploads in minutes rather than hours and plays in any browser while still showing the cut honestly. Save ProRes for the master. The one exception is a note specifically about grade or fine detail, and even then I would rather send a short 4K section than a 15 GB export nobody can load on hotel wifi.
Does the client need an account or the app to comment?
No, and that is the whole design, right. They open the link in a normal browser on whatever device they have, and they can leave timestamped comments, range comments and drawings on the frame without signing up for anything. Trust me on any level, the number of rounds you lose to somebody refusing to create an account is really not a small number.
What happens when I upload the next version?
It stacks on the same card as MV2, MV3 and so on, so the client keeps using the same link and the older versions stay there with their comments intact. On Agency and up you can put two versions side by side and show exactly what moved. At the end of the day that is what stops the "which file is current" argument before it starts, you see what I mean here.
If your first cuts are starting on an iPad now, the render is the cheap five minutes and the gap after it is the expensive part, and that gap is the easiest thing in the whole workflow to fix, right. Every plan on the PlayPause pricing page comes with a 7-day free trial, so take one travel job, run it end to end from the camera roll, and see whether the notes come back the same day instead of the same week.
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