Premiere Pro Export Settings for Client Review That Upload Fast and Look Right

"MV3 is exporting now, it's 4.9 GB and the upload says 47 minutes, is that okay or should I compress it?" One of my editors dropped that into our agency team chat at twenty to midnight, a couple of weeks after a client had answered a different cut with "why does the text look fuzzy, is this the final quality?"

So inside one month we got the same thing wrong in two opposite directions, right, and both times the cause was that nobody had agreed on Premiere Pro export settings for client review. The first was basically a ProRes 422 HQ mastering preset used for a rough cut of a three minute brand film the client would watch on a laptop. The second was a review copy squeezed to around 3 Mbps, so the client spent a whole round writing notes about compression that isn't even in the timeline.

So this is the review setup I actually run in Premiere, built around one named preset with a bitrate I can defend, and then the part most guides skip, which is when I don't export at all and send the cut straight from the timeline so it stacks as MV2, MV3 and so on.

What a client review export needs and what it does not

The way I explain a review copy to new editors on my team is that it's a message you send so the client can react, much closer to a screenshot than to the project file you keep, right, and its one job is to show the edit at a quality that never generates notes about itself.

So it needs the sequence's frame rate and frame size, full resolution media rather than proxies, audio clean enough to judge dialogue and text sharp enough to read a lower third. It doesn't need 10-bit color, a 4K frame for a talking head or a two pass encode, because those add minutes or gigabytes to every round without changing a single note. For a tour of the whole export window, Premiere Pro export settings explained covers every section.

In PlayPause the client plays a streaming copy in the browser and your original is never touched, which is how our proxy transcoding works, so your upload becomes the source for that copy and it needs to be clean first and small second.

Premiere Pro export settings for client review: codec, bitrate and resolution

Everything below lives in the Export tab, which opens with File, Export, Media, or with Cmd+M on a Mac and Ctrl+M on Windows.

Format: H.264 in an MP4

Set Format to H.264 and leave MP4 in the Multiplexer section. HEVC makes smaller files, but it encodes slower on a lot of machines and saves maybe a minute of upload on a short film, so for review I don't bother. ProRes 422 HQ runs at roughly 220 Mbps for 1080p at 29.97, so a three minute film lands near 4.95 GB, while the same three minutes of H.264 at 10 Mbps comes out around 232 MB, and that gap is the whole difference between a 47 minute upload and a two minute one.

Bitrate: VBR 1 pass, 10 target, 16 maximum

Under Bitrate Settings, choose VBR, 1 pass, with a Target Bitrate of 10 Mbps and a Maximum of 16 Mbps for 1080p at 23.976, 25 or 29.97, and 14 with 20 for 50 or 60 fps or heavy grain. YouTube's recommended upload encoding settings put 1080p at 8 Mbps for standard frame rates and 12 for high ones, and I sit a little above that on purpose, right, because the file becomes the source for a streaming copy and I want some headroom.

I skip 2 pass because it analyses the whole sequence first, which takes noticeably longer for a gain nobody sees on a laptop, and I skip CBR because it spends the same bits on a static interview as on a fast montage. That's the H.264 bitrate for client review I'd defend in any room, and the video compression fundamentals guide explains why a starved bitrate hits fine text first.

Set Performance to Hardware Encoding when your machine offers it, because it's dramatically faster, right, though the catch here is that some older hardware encoders look softer at low bitrates, which is one more reason I never go under 8 Mbps.

Resolution and frame rate: match the sequence

Leave Frame Size and Frame Rate matched to the sequence. A 4K timeline still goes out at 1920 by 1080 with Use Maximum Render Quality ticked, unless the client has to judge sharpness, for instance on a product shot, where I keep 3840 by 2160 at a 40 Mbps target. A 9:16 short goes out at 1080 by 1920 with the same 10 and 16.

Frame rate is where I'm really really strict, because a 23.976 sequence has about 1,439 frames a minute and a 25 fps file has 1,500, so a conformed copy picks up repeated or dropped frames that clients call stutter, and their comments stop pointing at the same moment in your timeline.

A worked example you can check yourself

The math is simple enough to do in your head, right. File size in megabytes is roughly the video plus audio bitrate in Mbps, times the seconds, divided by eight, so three minutes at 10 Mbps with 320 kbps audio is 10.32 times 180 divided by 8, which is about 232 MB. On the 14 Mbps upload that gave my editor his 47 minute estimate, that file goes up in a little over two minutes. VBR lands a bit either side of the target, but it's close enough that a three minute review file coming out at 900 MB tells me the preset is wrong before I even open it.

Audio settings that keep dialogue notes accurate

Audio is where review copies lie most quietly, right, because almost nobody checks it before sending. I set AAC at 48000 Hz to match the sequence, Stereo and 320 kbps, which is the top of Premiere's AAC menu, and over three minutes it costs about 7 MB.

Drop to 128 kbps and sibilance and a music bed under a voiceover turn swirly, so a client in good headphones writes "the voice sounds strange at 00:42" and an editor loses an hour hunting a problem that only exists in the review file. A lav stuck in one channel works the same way, which is why I play every export in headphones before it goes out.

Loudness Normalization in the Effects section stays off unless the master gets the same target, and Timecode Overlay and Name Overlay stay off too, because on a review link every comment already sticks to the exact frame.

Saving a client review preset in Premiere Pro and Media Encoder

With those settings in, open the Preset menu at the top of the Export tab, choose Save Preset and give it a name that carries the numbers, like Client Review 1080p H264 10M, which is the Premiere Pro review export preset every editor on my team uses. A second one, Client Review 4K Detail 40M, handles sharpness checks, and those two cover almost every review copy my agency sends.

For long exports I click Send to Media Encoder and keep cutting. On my builds the saved preset appears in Media Encoder under User Presets and Groups, its Preset Browser can export it as a file, and the Preset Manager in Premiere, under More Presets, imports that file, so one copy in a shared folder keeps the whole team consistent. Trust me on any level, a client noticing that MV2 looked different from MV3 costs more trust than any setting.

For a Premiere Pro quick export for review, the Quick Export button at the top right takes a preset and a location and goes, so once your preset sits in that list the review copy is a two click job.

When to upload straight from the timeline instead of exporting

This is the PlayPause part, and I'll keep it to what the panel actually does. The PlayPause Premiere Pro panel pairs with your workspace by code, shows the client's comments inside Premiere, jumps the playhead to the frame when you click a comment, and uploads a cut straight from the timeline, which replaces the export, find, drag and rename loop. For a mid-round fix like trimming a pause, that's what I reach for, right, because the ceremony shouldn't be bigger than the change.

I still export manually for the master, the 4K detail check and the approval round, because when I export a sequence for client approval I want the exact file they signed off on sitting on a drive. The post on feedback without re-exporting every round goes further, and the Premiere Pro workflow page shows how the panel fits an Adobe setup.

Naming and stacking review exports so versions never mix

Version stacks come with Creator and up, and they're why naming stopped being a fight in my agency, right, because each new export lands on the same card as MV2, MV3, MV4 instead of on a separate card. Before each round I duplicate the sequence as BrandFilm MV3 and export it as BrandFilm MV3 1080p, so the sequence, the file and the card carry one number, which is basically version control for editors. When a client writes "in MV3 at 01:14", only one thing can be meant, and knowing which sequence version was approved goes deeper on that.

On Agency and up I compare MV3 against MV4 side by side to check a fix round, and who-watched analytics on Creator and up tell me whether the client even opened MV3 before I export MV4, and I'm pretty sure that habit has saved us more pointless exports than any codec choice.

Max upload is 10 GB on Creator and Unlimited on Agency, and a review copy never gets close, since a 60 minute podcast at 10 Mbps is about 4.6 GB, but a ProRes master hits 10 GB at roughly six minutes, so if you deliver masters through the link, that limit decides the plan. The basics of getting a shareable review link have their own post.

Common export mistakes that trigger extra review rounds

To be very honest, most of the rounds we wasted in my agency started as export accidents the client politely wrote up as notes, and the classic is Use Proxies left ticked in the General section, which builds the review copy from low resolution proxies, so the client asks whether the blur is intentional. Use Previews does something similar when your preview files are a lightweight format.

Then there's the vertical short pushed through a 16:9 preset, which comes back with black bars down both sides, and the In and Out range left on from a trim, so the client asks where the ending went. A grade that looks washed out on the client's Mac is its own category, unpacked in why Premiere Pro export colors look different, and on the Apple side there's our guide to Final Cut Pro review exports.

My last check takes about a minute and runs on the exported file rather than the timeline, so I scrub to the last frame, play the busiest dialogue in headphones and put the smallest text on screen at full size.

Some illustrative math, right, say you run 12 videos a month at three rounds each, that's 36 rounds, and if one in six goes on something the export did rather than the edit, that's six rounds a month spent on nothing. Does that make sense, right, at the end of the day a saved preset just means every note the client writes is a note about the edit.

Frequently asked questions

What bitrate should I use for a 1080p client review export?

I use H.264 with VBR 1 pass, a 10 Mbps target and a 16 Mbps maximum for 1080p at standard frame rates, and 14 with 20 for 50 or 60 fps. That sits slightly above YouTube's own 1080p recommendation, right, and keeps a three minute film around 232 MB, which uploads in a couple of minutes on an ordinary office connection.

Should I send ProRes or H.264 for client review?

I send H.264 for every review round and keep ProRes for the master, because ProRes 422 HQ at 1080p runs at roughly 220 Mbps, so three minutes comes to nearly 5 GB. The client can't see that extra quality in a browser but definitely feels the wait, so ProRes waits for delivery day, when the file goes to an archive or a colorist.

Can I use Quick Export for client review copies?

You can, once you've saved a proper review preset, because the default adaptive presets choose their own bitrate and you never quite know what you sent. In the recent builds I've used, marking your Client Review preset as a favorite in the Preset Manager puts it in the Quick Export list, so every review copy goes out with settings you actually chose.

Does PlayPause change my original export file?

No, your original is never touched. PlayPause makes a streaming copy that the client plays in the browser, and the file you uploaded stays exactly as you exported it. That's why I send a clean 10 Mbps file instead of crushing it, you see what I mean here, the upload is the source for playback, so it should be good enough that nobody notices it.

If you want to test this on a live project, every plan on PlayPause pricing comes with a 7-day free trial, so save the preset tonight, send MV2 through a review link, stack MV3 on the same card next round, and see whether the notes coming back are finally about the edit.

So yeah. That's my way of saying it.