
Restoring an older Vimeo cut creates a new active version using that older footage. It does not simply rewind the existing version number, and Vimeo says comments on other versions remain in Version History. An empty comment view on the new active version is therefore not, by itself, evidence that the earlier client feedback was deleted.
Key Takeaways
- Restored footage becomes a newly numbered active version.
- Earlier collaborator comments remain associated with their historical context.
- Verify both the selected footage and the relevant historical feedback.
Separate the footage from the history entry
Vimeo's version-management documentation gives a useful distinction: restoring V3 can create V6 that uses V3's footage. V6 is now active, while the previous version records remain part of the history. Available options may vary by plan.
The image content can consequently look familiar while the platform version identity is new. Avoid recording only returned to V3 in the delivery notes. Record the new active version and the historical footage it came from, using the approved-version handoff record for the actual issued movie.
Look for feedback on the version that received it
Open Video Settings, find the version indicator beside the video name and inspect Version History. Select the earlier version that received the missing notes. Vimeo states that collaborator comments remain available on past versions after restoration.
A proposed investigation is:
- Record the current active version and visible footage.
- Identify which historical cut the client originally reviewed.
- Open that history entry and check its associated comments.
- Compare each still-relevant request with the restored footage.
- Record which requests remain outstanding on the newly active cut.
If a note cannot be found, check the exact video, version and comment context before concluding it was lost. Repeated restores or speculative deletions make that investigation harder.
Do not treat restoration as fresh approval
For a hypothetical portrait film, V3 has the preferred facial performance, while V5 contains later sound corrections. Restoring V3's footage does not establish that the new active movie includes those V5 corrections. Check the restored movie rather than assuming all later work survives.
Similarly, finding an old approval does not prove it covers a changed release purpose. The concept, content and master approval guide helps distinguish the decision about a scene from approval of the finished delivery file.
Keep the original feedback in its original context. Summarize unresolved actions for the new review instead of presenting old notes as if they had been posted against the new version.
Verify the restored cut before issuing it
Watch the beginning, affected scene, soundtrack and ending of the active movie. Confirm captions and any required delivery variation independently. Update the handoff instructions so the recipient knows which version to inspect and why its number differs from the footage source.
Use the review-copy versus master guidance when the restored cut is only ready for another review. Accept the recovery when historical notes are accounted for and the new active movie satisfies its stated purpose, not merely when an old image reappears.
Related tasks
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- What Does Approved Mean for an AI Project: Concept, Story or Final Master?
- Should I Send a Review Copy or the Final Master of an AI Video to a Client?
Sources and scope
- Vimeo: How to manage video versions and access history: Restore creates a new active version using an older version's footage. Comments on other versions remain accessible in Version History, and the new version can have a clean comment state.
Documentation-based guidance from the full Vimeo version-management source captured October 29, 2026. No restore, deletion, download or comment test was performed. Version numbers in the example are hypothetical and describe the documented relationship, not an observed account history. Plan-specific options may differ.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.