What Proxy Settings Actually Get Dailies Uploaded Fast on Set

Every production office has had the night where dailies don't land until 2 a.m. because someone exported proxies at the wrong settings and the upload choked on a hotel wifi connection. We built PlayPause because we kept watching this exact failure happen on set after set, and it's basically never a bandwidth problem in the way people assume. It's a settings problem. Get the codec, resolution, and bitrate right for the actual upload pipe you have that night, and a full day of coverage moves from camera card to client inbox before the crew even wraps craft services. Get it wrong, and you're re-encoding at midnight while a director waits on notes that were due at breakfast.

This piece is a practical rundown of the proxy transcode settings that actually get dailies uploaded fast, not a theoretical explainer on compression. We're going to walk through codec choice, resolution ceilings, bitrate targets, and the on-set workflow that ties it together, because at the end of the day the settings only matter if the whole chain from camera to client review link is built around them.

The Codec Question: ProRes Proxy, DNxHR LB, or H.264

For years the default answer was ProRes Proxy, and for editorial handoff inside a single facility that's still a fine choice. ProRes Proxy decodes fast, it's forgiving on older machines, and most NLEs treat it as a first-class citizen. The problem is that ProRes Proxy is still an intraframe codec, which means every single frame is fully encoded on its own, and that keeps file sizes considerably larger than what you actually need for a same-day upload over a cellular hotspot or a hotel connection that's shared with forty other guests.

DNxHR LB solves some of the same problems and is worth considering if your post pipeline is already Avid-centric, but for pure upload speed neither ProRes Proxy nor DNxHR LB is the right tool. H.264, and increasingly H.265 where hardware encoding is available on set, is the codec that actually gets you a small enough file to move over a real-world upload connection. H.264 uses interframe compression, meaning it only stores the differences between frames instead of re-encoding every frame from scratch, and that's the entire reason the file sizes come down so dramatically.

For instance, a twelve-minute take shot in ProRes 422 HQ at 4K comes in around fourteen gigabytes. Transcode that same twelve minutes to H.264 at 1280x720 and a 6 megabit-per-second target bitrate, and you're looking at roughly five hundred forty megabytes. That's not a small difference, that's the difference between a ten-minute upload and a two-hour upload on a mediocre connection, and it's the entire reason productions that ignore this keep missing their dailies window.

Resolution and Bitrate Numbers That Actually Work

Resolution is where most on-set proxy workflows go wrong, because someone assumes client review needs to match the acquisition format and generates full 4K proxies out of habit. It basically never does. A client reviewing dailies on a laptop screen or an iPad cannot tell the difference between a 1280x720 proxy and a full 4K file when both are being viewed at less than full screen size, which is how review footage gets watched about ninety percent of the time anyway.

Our recommendation, and what we see working crews use successfully across documentary, commercial, and scripted sets, is a 1280x720 resolution ceiling for same-day dailies uploads, dropping to 960x540 if you're working off a satellite uplink or a genuinely bad cellular connection in a remote location. Bitrate should land between 5 and 8 megabits per second for H.264 at that resolution, which keeps visible compression artifacts low enough that a director or DP can still make a real judgment call on performance, framing, and exposure, without inflating the file past what your connection can move in a reasonable window.

Audio deserves a mention here too because it gets ignored constantly. AAC at 128kbps stereo is more than sufficient for review purposes, and trying to carry uncompressed or high-bitrate audio through a proxy built for upload speed defeats the entire point of the exercise. Keep the audio codec light and let the picture settings do the actual work of shrinking the file.

Building a Same-Day Upload Workflow On Set

Getting the settings right is only half the job. The other half is building a repeatable process so the DIT or assistant editor isn't reinventing the transcode chain every single shoot day under time pressure. This is where a lot of productions lose the time they thought they saved with good proxy settings, because the human workflow around the export is slow or inconsistent.

That third step matters more than people give it credit for. If your transcode and your upload are sequential and blocking, meaning nothing uploads until every file in the batch is done encoding, you've basically doubled your total time for no reason. A workflow that starts uploading finished files while later files are still transcoding, right alongside them, is a meaningfully faster path to a client's inbox, and it's one of the specific reasons we built Batch Uploads into PlayPause the way we did, so a DIT can queue an entire card's worth of dailies and let the platform handle staggered delivery instead of babysitting a progress bar.

Common Mistakes That Blow Up Upload Windows

We've watched enough dailies workflows fail in the field to know the mistakes repeat across genres and budgets. A few show up constantly enough to call out directly.

• Exporting proxies at the acquisition resolution instead of a review-appropriate 720p ceiling
• Using an intraframe codec like ProRes Proxy for upload when H.264 would cut the file by eighty percent or more
• Uploading through a general file-sharing tool that wasn't built for time-coded video review, forcing the client to download the whole file before they can watch any of it
• Skipping a consistent naming and metadata convention, which turns a fast upload into a slow client-side hunt for the right take
• Not testing the actual upload connection on location before day one, so the crew discovers the bottleneck live during the first day's dailies push

That second point is worth sitting with for a second. Plenty of crews still default to ProRes Proxy purely out of habit, carried over from years of editorial-only proxy workflows, without questioning whether it's the right tool for the specific job of getting a file into a client's hands over an upload connection that same night. It's a perfectly good codec for the edit bay. It's the wrong codec for a hotel's shared wifi at 11 p.m.

What We Recommend for Different Camera Formats

The exact numbers shift a little depending on what's actually coming off the camera, so here's a rough breakdown by common acquisition format, all still aimed at that same 5 to 8 Mbps, 1280x720 H.264 target for the final upload file.

For RED and ARRI raw formats, generate the proxy directly from raw during ingest rather than round-tripping through an intermediate ProRes file first, since that extra step adds real time to a process that's already time-constrained on a shoot day. For standard 4K XAVC or H.264 camera-native footage from Sony or Panasonic bodies, a straight transcode down to the target resolution and bitrate is usually a single-pass operation that most ingest software handles without drama. For anamorphic or unusual aspect ratios, make sure the proxy preset preserves the correct desqueeze so the client isn't reviewing a distorted frame and second-guessing framing decisions that were actually fine on the day.

That shift from "dailies eventually arrive" to "dailies arrive while the crew is still on location" is basically the whole point of getting proxy transcode settings right. It's not a nice-to-have for productions with a big enough budget for dedicated IT support. It's a workflow decision that any DIT or assistant editor can implement with the right export presets and the right delivery tool.

Getting Proxies From Camera Card to Client Review Without the Bottleneck

Once the transcode settings are dialed in, the remaining bottleneck is almost always the tool doing the actual delivery and review. This is the part of the chain we spend the most time thinking about, because a fast proxy that lands in a client's inbox as a raw download link with no way to comment on a specific frame or timecode isn't actually solving the dailies problem, it's just moving where the friction shows up.

We built PlayPause specifically around that second half of the equation. It's a flat-price, per-workspace video review platform, so a production doesn't need to think about per-seat costs when the whole point of dailies is that everyone from the director to the client needs to be in the review link, not locked out of it. Compare that to the seat-based pricing model most competitors run, and it's a meaningfully different economics conversation for a production that's adding and removing reviewers constantly across a shoot. We cover that difference in detail on PlayPause vs Frame Io if you want the specific breakdown.

For editors cutting selects the same night the dailies land, the PlayPause Premiere Pro plugin pulls comments and timecoded notes straight into the timeline, so the notes from that fast upload don't sit in a separate browser tab disconnected from the actual edit. And when a client is reviewing on set or from a hotel room with the same shaky connection that made proxy settings matter in the first place, Offline Review means the review experience doesn't fall apart just because the upload did its job and the client's wifi didn't.

Making the Whole Chain Actually Fast

Right, so to bring this together: pick H.264 over ProRes Proxy or DNxHR LB for anything that has to move over an upload connection the same day. Cap resolution at 1280x720 for review purposes, drop to 960x540 only if the connection genuinely can't handle more. Target 5 to 8 Mbps for video and 128kbps AAC for audio. Build a workflow where upload starts the moment the first file is ready instead of waiting on the whole batch, and choose a review portal that treats the arrival of the file as the start of the feedback process, not the end of your job.

None of this is complicated once it's written down, which is honestly the frustrating part. Most dailies delays aren't caused by hard technical problems, they're caused by nobody sitting down and setting the export preset correctly once. If your production is still fighting this fight every shoot day, take a look at PlayPause pricing and see what a flat, predictable cost looks like next to what you're currently losing in crew overtime waiting on an upload bar. As the American Society of Cinematographers has long emphasized in its own technical resources, the technical choices made on set ripple through every stage that follows, and proxy settings are exactly the kind of small decision that either saves your production hours every single day or costs them.