Side-by-side video version comparison is the review step where two cuts of the same edit play in one view so a reviewer can judge what changed - not just what the new version looks like in isolation. Frame.io shipped a revamped Comparison Viewer with drag-to-reveal modes in July 2026, which tells you the feature is now table stakes; the useful question is when to compare side by side, when to review sequentially, and what reviewers in each discipline are actually checking for. This post is that practice guide, written by a review tool that ships version stacks and side-by-side comparison natively (Frooty - full disclosure, as always on this blog).
Sequential review vs side-by-side: the decision rule
Review sequentially when the question is "is this cut good?" First-pass reviews are about story, pacing, and feel - and feel dies in a split screen. A client watching v2 cold reacts the way a real audience will. Watch it alone first, at full attention, and comment at timestamps as usual.
Compare side by side when the question is "what changed, and is the change right?" This is the second pass on the same version's notes: did the color shift fix the mismatch at 1:24, does the trimmed opening still land, is the new super legible. The reviewer needs both cuts in view because the judgment is relative.
Compare before approving, always. The single most valuable habit: before a version moves to approved, the decision owner plays it against the previous version once. Approvals issued off a single cold watch are the ones that generate "wait, the old ending was better" a week later - the round-two problem the versioning guide exists to prevent.
What each discipline actually compares
| Reviewer | Comparing for | How they watch |
|---|---|---|
| Client / decision owner | Did my notes land; is the story re-paced correctly | Sequential first, then synced side-by-side at the flagged timestamps |
| Editor | Timing deltas: trims, holds, the frame the cut moved | Synced playhead, stepping frame by frame at cut points (frame-accurate review matters here) |
| Colorist | Grade consistency across versions - no scene drift | Split screen paused on matched frames; the color approval workflow pairs this with a calibrated display |
| VFX / motion | Shot replacements at exact frames | A/B toggle on single frames, not playback - does the comp hold up at rest |
| Legal / brand | Supers, disclaimers, logo moments unchanged or correctly updated | Paused side-by-side at each super's frames |
The pixel-diff honesty box
Frame.io's July 2026 viewer added pixel-diff modes - a visualization of the two versions' difference signal, useful for VFX QC. Most review tools, Frooty included, compare visually: synced playback, split or toggle views, frame-stepping. True pixel-diff belongs to dedicated QC tooling in a pipeline that already has one; for client rounds and approval sign-off, synced visual comparison covers the actual judgment being made. If a vendor's marketing leads with pixel-diff, check whether their version stacks and comment threads survive the comparison - those carry the round.
Round rules that keep comparison honest
- One version per round. Upload v2 as a version, never as a replacement file - comparison needs the stack (the review checklist makes this step two).
- Comment on the new version. New notes pin to v2's timestamps, so the thread history shows which version each note belonged to.
- Name what changed in the version note. "v2: tightened open, new grade" tells reviewers where to point the comparison.
- Resolve old threads. A clean stack shows which feedback is closed; unresolved v1 threads drifting under v2 are how double-fixes happen.
FAQ
What does side-by-side video version comparison mean?
Two versions of the same edit playing in one review view with a shared or individually controllable playhead, so reviewers judge what changed between rounds instead of re-watching each cut in isolation.
Should clients review video versions sequentially or side by side?
Sequentially for first impressions and story notes, side by side for verification - checking that previous notes landed and the changes are right. The strongest round habit is sequential first watch, then a comparison pass before approval.
What is pixel-diff video comparison?
A QC technique that visualizes the literal pixel differences between two renders - useful for VFX and color QC sign-off. It is different from side-by-side review, which is a human judgment of change; Frame.io added pixel-diff modes in July 2026, while most review tools compare visually.
How do I keep versions organized for comparison?
Upload every round as a version in one stack - never as separate uploads or replaced files - name each version with what changed, and keep new comments pinned to the version under review so threads map to rounds.