The quiet fix: swap the file, keep the link
One drag replaces the file behind every link you have sent. No new URL, no email, and nothing shows up in any version list.
You sent the link Monday. Tuesday you spot a typo in a lower third. The fix should not cost you a new link, an email thread, or a client who wonders what else changed.
The move
Export the fix, then drag the file onto the asset's tile in the project view. The tile lights up, the upload runs, and a toast confirms the swap by filename. Done. Every review link, reel, and embed that carries this asset now serves the new file at the same URL.
What the client experiences
Nothing. The link they have plays the fix the next time they open it. No version list appears, because visibility is off by default for every version, and a quiet fix never touches it. Their earlier comments stay pinned to the cut they were made on, so nothing they wrote goes missing or drifts onto the wrong frame.
When to use it, and when not to
Use the quiet fix for typo fixes, re-renders, missing-asset patches, and any change the client should see rather than discuss. When the new cut is a decision you want the client to weigh in on against the old one, use Publish a cut instead, so both cuts appear in the link's version rail by name.
The link-side story, including what happens to approvals already collected, is covered in Send a new cut without breaking the link.
Questions
Will the client get notified that the file changed?
No. A quiet fix sends nothing and shows nothing. The next time they open the link, the new file plays. If you want them to know, tell them, or publish the version so they can see it listed.
What happens to comments they already left?
They stay pinned to the version they were made on, with a badge naming that version. Feedback on the earlier cut never silently reattaches to the new file.
Ready to try it?
Host video, collect frame-accurate review, and see who's watching. Free to start.
Start free