How to Share a Rough Cut with Clients Without Giving Away Your Deliverable Files

Sharing a rough cut with clients without giving away your deliverable files is a problem that trips up more editors and post houses than it should. The instinct when a client asks to see the cut is to find the fastest way to get it in front of them. That fastest way is often a Dropbox share or a WeTransfer link, and both of those involve handing over the actual file. If this applies to your setup, rough cut screening workflow for a distributed documentary team is worth reading alongside this.

Once a client has the file, you have lost control of it. They can share it with people who were not supposed to see it. They might distribute it before the final approved version is ready. And if the cut has watermarks or burned-in notes that are not in the final deliverable, those might end up being what the client presents to their own stakeholders. If this applies to your setup, sending secure festival screeners without losing control of your film is worth reading alongside this. If this applies to your setup, how to watermark and track a rough cut screener sent to potential co-producers is worth reading alongside this.

Here is how to give clients the review experience they need without handing over files they should not have.

The Core Principle: Review vs Delivery Are Different

This problem exists because a lot of production workflows do not make a clear distinction between sharing for review and delivering the final file. They treat both as "give the client a file."

Review and delivery serve different purposes and need different tools.

• Review: the client needs to watch the cut, form opinions, leave feedback, and approve or request changes. They do not need a file.
• Delivery: the client receives the final approved version in the format specified in the contract. They get a file at this stage, not before.

If you establish this distinction clearly in how you work, most of the "gave them the wrong file" problems disappear because you stop sending files for review at all.

How Stream-Only Review Works

The practical implementation of review-without-files is a review platform where the video streams in the browser rather than downloading. The client can watch at full quality, scrub to any moment, and leave comments pinned to specific frames. They cannot download the source file.

PlayPause works exactly this way. You upload your rough cut, create a share link, and the client watches it in their browser. If they try to download, there is nothing to download. If they share the link with someone else, that person can also watch and comment, which is fine because you know who has the link. What they cannot do is take your rough cut file and do something with it you did not intend.

This is categorically different from sending a file via Dropbox. A Dropbox share is a file that exists on someone else's system. A review link is a window into your file that you control.

Protecting the Cut Before It Is Final

Beyond file control, there are a few other protection layers worth building in for rough cut review:

Visible watermarks: even on a stream-only review, a visible watermark identifying the version ("Rough Cut v1 - Confidential") discourages screen recording and makes it clear what the client is looking at. If the client takes a screenshot or recording to show someone, the "Rough Cut - Confidential" text is in every frame.

Expiring links: if a rough cut review is open for more than a few weeks, the risk that the link gets shared further or accessed by someone who should not have it increases. Setting an expiry date on the link means the window closes automatically after the review period.

Password protection: for sensitive projects, a password on the review link means only people who have specifically been given the password can access the cut. This is a meaningful additional layer for projects where confidentiality is important, like unreleased music videos, unaired TV content, or brand campaigns before launch.

For productions where screener security is especially critical, sending secure festival screeners without leaks covers a more complete approach to screener security.

Review_Cut_v4.mp4In Review

212160p · ProRes

00:34 / 02:18

SR

Sarah 0:34

Frame-accurate note, everyone sees the exact same thing.

What to Tell Clients About the Review Process

Some clients push back when they realize they are not getting a file. They are used to receiving a Dropbox link and downloading a video. Here is how I explain it:

"We share rough cuts via a review link that lets you watch, comment, and approve without downloading. This is intentional: it makes sure the version you are reviewing is always current, and it means we can update the cut without sending you another file. When we reach final delivery, you will receive the proper file in the specified format."

Most clients accept this quickly once they understand the logic. They also discover that a review link where they can leave a comment at the exact moment is a better review experience than downloading a file and emailing notes about it.

For clients who are skeptical of any change from their usual process, how to pitch a structured revision process to a client who has always used email covers how to frame the conversation.

Managing Version Control on Rough Cuts

When you are in the rough cut phase, versions change frequently. If you have been sending files, version control is a nightmare: the client might be looking at the version they downloaded last week while you have moved three cuts further. They do not know the version they have is outdated.

With stream-only review, you control what version is live. When you upload a new cut to the review session, the old version is superseded. The client always sees the most current version when they open the link. You can also maintain both versions in a stack if you want the client to compare them.

This eliminates the "which version did you send me" conversation entirely.

For the broader version management challenge, how to handle multiple cut versions for the same project without confusion covers the full version control approach.

What About Proxy Files and Low-Res Versions?

One common approach is sending a low-resolution proxy instead of the full-quality cut. The theory is that even if the proxy leaks, it is not the deliverable file.

This works to a degree, but it has downsides. A low-res proxy gives the client a degraded review experience, which affects the quality of feedback. They might not catch focus issues or graphic readability problems that would be obvious at full resolution. And a proxy with burned-in timecode or watermarks might confuse clients who are not used to reviewing with those elements visible.

Stream-only review at a reasonable quality level is a better approach than proxy delivery. The client gets a good enough review experience, you control the file, and you do not have to manage a separate proxy transcode workflow.

For post houses sharing proxies with remote clients for other reasons, the right way to share low-res proxies with clients while keeping original media secure covers when the proxy approach is the right choice.

• Establish internally that review and delivery are different processes
• Use a stream-only review platform, not file transfer, for rough cut sharing
• Add visible watermarks identifying rough cuts as confidential
• Set link expiry for sensitive projects
• Explain the review link approach to clients upfront so there is no confusion at first share

The Approval Record Protects You Both Ways

Beyond protecting your files, the review platform approach gives you something valuable at the approval stage: a documented record that the client watched and approved a specific version.

When a client says "I never agreed to that ending" or "you changed something after I approved," you have the review session showing when they opened the link, which version they reviewed, and what they said in their approval. That record protects you in billing disputes and scope arguments.

For agencies dealing with the billing and scope side of this, how agencies prove a client approved a video when the client claims they never did covers how the approval documentation works in practice. If this applies to your setup, how to stop clients changing feedback after they approve a video is worth reading alongside this.

For further reading, the right way to share a locked cut with a sales agent before a market digs into this from a related angle.

PlayPause's Creator plan starts at $9/mo and includes stream-only sharing, password protection, expiring links, and frame-accurate commenting. If you are currently sending files for rough cut review, this is the change that protects you without changing anything about how your clients experience the review.