A client once told us they were "confused" because the video we sent for approval looked slightly worse than the one that showed up on their website two days later. Same edit, same cuts, same music — but the final version was visibly sharper, and the little "REVIEW COPY" text in the corner was gone. They assumed we'd done something extra at the last minute. We hadn't. That's just what a review copy is supposed to look like.
This mix-up comes up more than people expect, so it's worth explaining plainly: the file we send for feedback and the file we deliver as final are not the same file with a watermark peeled off. They're built differently, for different jobs, and understanding the difference actually makes the review process faster.
Why Review Copies and Final Files Are Different Files, Not Different Versions of the Same File
The instinct is to assume "final" just means "review copy, but done." In practice, a review copy and a final export usually come from different technical pipelines entirely.
During editing, most professional workflows run on proxies — lightweight stand-in files generated from the original footage so the edit stays responsive. A typical Premiere Pro ProRes Low Resolution proxy comes in around 66.5 MB at roughly 1024×540 pixels, a fraction of the size and resolution of the source media. That's what gets cut together, and often what gets sent for early review, because it's fast to upload, fast to stream, and fast for a client to open on a laptop over hotel Wi-Fi. The final export, by contrast, is conformed back to full resolution — the proxies get swapped out for the original high-resolution files before the last render goes out. Skip that conform step and the "final" file is quietly still running on proxy-quality footage, which is a real mistake editors sometimes catch only after export.
Resolution isn't the only thing that changes. Review copies are almost always watermarked, and there's an actual craft to doing it right. The convention among professional editors is a center-placed, semi-transparent mark — something like "DRAFT" or "REVIEW COPY – NOT FOR DISTRIBUTION" — set around 40% opacity. Bottom-corner watermarks get cropped out in five seconds. Center placement, burned into the pixel data rather than laid on as a removable overlay, means the mark survives re-encoding, screen recording, or someone trying to strip it out. It's not about distrust — it's a basic protection for unfinished, unpaid-for work, and it's standard practice across the industry, not a VizEdits-specific overlay.
Then there's the export spec itself. A file destined for a client's review link and a file destined for YouTube or Instagram are encoded to completely different technical targets. A finished YouTube upload typically runs H.264 or H.265 at 1920×1080 or higher, with a bitrate in the 15–50 Mbps range and 48kHz AAC audio. An Instagram Reel or TikTok cut is a vertical 1080×1920 frame at a much higher bitrate relative to its size, because the platform's own compression is aggressive and the file needs to survive it without falling apart. None of that platform-specific tuning happens on a rough cut. It happens once, at the very end, once the edit itself is locked.
What a Review Cut Is Actually For
The rough cut isn't meant to look finished — and if we send you one that looks finished, we've usually done something wrong. The point of an early cut is structure: is the story in the right order, does the pacing work, is the message landing where it should. Color correction, final sound mixing, licensed music, and polished titles typically come later, closer to the fine cut and finish cut stages, on purpose. A review copy that already has full color grading and final audio can actually slow a project down, because it invites detailed polish notes on a version that's still going to change structurally.
This is also why we don't hand a client a maze of feedback formats and hope for the best. A clean round needs a couple of things attached to it every time: what kind of cut this is (are you judging structure, or are you judging polish), and what's actually in scope for that round. Skip that framing and reviewers invent their own process — which is how a rough cut ends up with detailed color notes from one person and structural notes from another, on the same round, pulling in opposite directions.
The data backs this up. Teams using frame-accurate, timestamped comments consistently report fewer revision rounds than teams collecting notes over email or Slack. On the flip side, one estimate puts the cause of 67% of unplanned agency revision rounds on vague, unstructured, or late client feedback — not on the editor missing the brief. "Make it punchier" at 11pm isn't direction, it's homework, and it usually produces a version that still misses the mark, followed by another round to fix the miss.
Rough Cut, Fine Cut, Final Cut: What Changes at Each Stage
| Stage | What it shows | What's still missing | What kind of feedback belongs here |
|---|---|---|---|
| Rough cut | Full structure, scene order, pacing, scratch narration | Color grading, final audio mix, licensed music, polished graphics | Story, order, timing — "cut this scene," "this section drags" |
| Fine cut | Refined cut points, draft motion graphics, temp titles | Final color pass, finished sound design, professional voiceover | Specific cut points, pacing detail, music timing |
| Finish cut / final | Full color correction, final mixed audio, licensed music, platform export, no watermark | Nothing — this is picture lock | Final sign-off only; further changes are a new round |
This structure isn't arbitrary. It maps to when different work actually gets done, and it's why a note like "can we brighten this shot" means something different depending on which stage it lands in. On a rough cut, that note might not even matter yet, since color hasn't happened. On a finish cut, it's a real, actionable request.
Why the Difference Actually Saves Everyone Time
It's tempting to think "just send me the good version so I only have to look at it once." In practice, that backfires. Industry estimates put a reasonable revision target at two to three structured rounds for most projects with a clear brief. Teams that consistently need five or more rounds usually have a feedback-collection problem, not a creative one — and one of the most common causes is external stakeholders joining the review late, after Round 1 is already locked in. That alone can multiply revision rounds three to four times over, because decisions that felt settled get reopened by someone who wasn't in the room the first time.
Sending a rough, watermarked, structurally-focused cut first — and asking for structural feedback only — front-loads the big decisions before time gets spent on color, sound, and final polish that might get cut anyway. It's a lot cheaper to trim a scene at the rough cut stage than to re-grade and re-mix a scene that gets cut after finishing work was already done on it.
If your team is still passing notes over email screenshots or a group text, that's usually the first thing we help fix before we even touch the timeline — a structured review flow does more for turnaround time than almost anything else in the process, and it's part of what our Video Editing work is built around from the first cut onward.
What "Final" Actually Means When We Deliver It
Picture lock is the term for the moment no further editorial changes get made to the cut itself — after that point, work shifts to finishing touches like sound and grading, not structural edits. When we say a file is final, we mean: full resolution conformed from source footage, complete color pass, finished audio mix, any licensed music cleared and in place, exported to the platform-specific spec it's actually going to live on, and no watermark. That last part matters more than it sounds like it should — a clean, unwatermarked file only goes out once a project is genuinely signed off, which protects both sides from the file getting used, reposted, or aired before it's actually approved.
We'll also typically hand over more than one final file, not because the edit changed, but because a YouTube upload and an Instagram Reels cutdown of the same project need different aspect ratios, bitrates, and audio specs to look right on each platform. That's routine, not extra work — it's part of what a proper final delivery looks like when a project is going to more than one destination, which is worth flagging early if your video is heading to multiple platforms.
A Quick Checklist for Clients Reviewing a Cut
- Confirm which stage you're looking at (rough, fine, or final) before giving detailed polish notes.
- Leave feedback tied to a specific timestamp rather than a general impression.
- Consolidate every stakeholder's notes into one document per round, not a drip of separate messages.
- Get every decision-maker into the review by Round 1, not partway through.
- Give an explicit approval when a cut is right — "looks good" in a side chat isn't a locked sign-off.
If any of that structure feels like it's missing from how your current reviews go, it's worth getting a second opinion on your process before the next project starts, rather than mid-round when a launch date is already close.
The Bottom Line
A review cut and a final cut are built to do different jobs, not to look different for its own sake. The rough version exists so structural problems get caught while they're still cheap to fix. The final version exists as the one clean, complete, platform-ready file that's actually meant to go live. Confusing the two — either by polishing a rough cut too early or by giving structural notes on a locked final — is one of the more common ways projects lose time that had nothing to do with the creative work itself.
Understanding what each stage is actually for is the fastest way to get a faster turnaround, fewer rounds, and a final file that looks the way it's supposed to the first time it's watched.
Ready to work with a team that treats review and final delivery as two distinct, intentional stages instead of one blurry back-and-forth? Get in touch and we'll walk you through how our video editing and production workflow handles review rounds, revisions, and final delivery from the first cut to picture lock.