The review link and your editing timeline are two different pipelines, and pixels change between them for five honest reasons: the streaming transcode, the resolution cap, color management, the proxy you edited with, and the client's screen. "It looks different on the link" is therefore usually not a bug — it is the review pipeline doing its job — and the fix is knowing which of the five you are looking at. Here is each source, then the diagnosis table.
The five sources of drift
- 1. The streaming transcode. Review platforms re-encode uploads into playback-friendly streams (H.264/H.265 ladders) so playback starts fast and survives weak connections. Streaming bitrates are lower than your master's, so fine grain, fast motion, and heavy compression sources (long-GOP camera files) soften first. This is physics, not negligence: the review export vs delivery master split exists because playback and archival want different files.
- 2. The resolution cap. Many tools cap playback resolution on free or entry tiers — on Frooty, for example, the free tier reviews at 1080p while Studio serves original resolution — and most tools cap somewhere for streaming sanity. A 4K cut reviewed on a capped tier is genuinely softer than your 4K timeline. Check the tier before blaming the transcode.
- 3. Color management. Your NLE monitors through a color-managed pipeline; a browser assumes sRGB and drops most HDR metadata. Graded Log footage that looks contrasty on the suite display can read flat or shifted in the browser — the classic "why does it look washed out" ticket. The color approval workflow post covers the display-side honesty (reviewers on uncalibrated laptop panels are grading with their thumbs).
- 4. Your proxy, not your master. What you see in the timeline may be proxy media; the file you uploaded is the full-res render. When the review link looks worse than your timeline, sometimes it is actually looking better than your proxies — sharpness differences are a proxy artifact, and the proxy workflow glossary explains the split.
- 5. The client's screen. Brightness at 100%, night-shift warm, True Tone on, a 60%-scaling laptop window playing a 1080p stream at half size. The client is reviewing your pixels through their device's mood filter — which is why frame-pinned comments ("this shot") beat adjectives ("this whole thing feels soft") for getting usable notes.
The diagnosis table
| Symptom on the review link | Likely cause | What to do |
|---|---|---|
| Globally softer than the timeline | Streaming transcode and/or a capped tier | Check the plan's playback cap; export the review file with a healthier bitrate; for detail-critical rounds ask reviewers to look at full-screen playback |
| Colors flat, lifted blacks, or shifted | Color management: Log grade meeting an sRGB browser | Do one browser test yourself on a graded export; pin a reference frame in the thread ("how it should look"); keep color sign-off on calibrated displays, not the link |
| Judder or stutter on motion | Frame-rate mismatch or heavy long-GOP source transcoded hard | Confirm the export's frame rate matches the sequence; test on a second network; remember streaming playback stutters on weak connections — it is not the cut |
| Edges cropped or titles tight | Safe zones and scaling on the client's device | Review vertical cuts on a phone-shaped window (the vertical review post covers safe zones); ask for a screenshot pinned in the comment |
| Audio quieter or harsher than the suite | Device speakers and player normalization, not your mix | Do the phone-speaker test before delivery (the audio review pass runs this earlier); keep broadcast loudness compliance at finishing, not in review |
What actually helps
- Set expectations in round one. One line in the kickoff email — "the review stream is optimized for playback; final masters are delivered at full quality" — prevents the quality conversation entirely (the onboarding checklist has the slot for it).
- Pin frames, not adjectives. When the client says "soft around here," ask for a comment pinned to that exact moment with a screenshot — frame-accurate comments turn a vibe into a fixable note (the frame-accurate review standard, and how drawing annotations point at pixels words cannot).
- Burn-ins for the ambiguous cases. A timecode burn-in on the review export makes "that shot at 1:24" unambiguous — the per-NLE recipes live in Premiere and Final Cut.
- Watch your own link first. The one-minute habit: open the review link on your phone before sending it. You will catch 90% of "it looks different" tickets before the client invents their own explanation.
The deeper point: the review link is a communication surface, not a reference monitor. It is allowed to be a little softer and a little flatter than your timeline — as long as the notes that come back are pinned to exact frames, the difference between pipelines stops mattering, and the version that ships gets judged on the displays that will actually show it.
FAQ
Does the review link show the same quality as the final export?
No — review streams are re-encoded for fast, resilient playback, and entry tiers often cap resolution (Frooty's free tier reviews at 1080p; Studio serves original resolution, as of November 2026). The delivered master is a separate, archival-grade export. Treat the link as a feedback surface, and the master as the deliverable.
Why do colors look washed out on the review link?
Almost always color management: your editor's graded pipeline versus a browser that assumes sRGB (and drops HDR metadata), further muddied by the client's uncalibrated laptop panel. Verify with one graded frame in the thread as a reference, and keep final color sign-off on a calibrated display rather than on any streaming link.
Can clients review in original resolution?
Depends on the tool and the tier. Check the plan: on Frooty, Studio plans stream original resolution while the free tier caps review playback at 1080p; most competitors cap playback somewhere for streaming performance. For graphics-heavy or VFX rounds where pixels are the subject, review on a tier that shows the real thing.
How do I get precise feedback when playback looks soft?
Shift feedback from adjectives to anchors: frame-pinned comments, drawn annotations, timecode burn-ins on the export, and screenshots attached to the note. Precision of reference beats fidelity of stream — a soft stream with frame-exact notes produces a better cut than a pristine stream with "it feels off."