
A save through Frame.io Drive Mounted Storage is not automatically a new client review version. Frame.io V4 distinguishes Version Saves, attached to the current version, from Version Stacks, which organize uploaded revisions. Neither state alone proves that a client reviewed or approved the footage.
Key Takeaways
- Mounted Storage saves sit within the current version's history.
- A Version Stack groups uploaded revisions under one asset location.
- Record the exact reviewed output and intended use before calling it approved.
Identify which history you are looking at
Use the Frame.io Versioning guide, dated September 25, 2026, for this V4 distinction. It says Mounted Storage saves are nested in version history and attached to the latest version being worked on. The save counter includes the save's date, time and author. This function requires Mounted Storage in Frame.io Drive.
An uploaded Version Stack is a different arrangement. The documented manual procedure is to finish uploading a new revision, then drag it onto the original. The stack's version selector provides access to earlier revisions. Do not infer that every save counter increment represents another issued film.
Check the actual object as well. A saved editing project and an exported viewing movie serve different purposes. A project save can preserve editing work without producing a new playable client cut.
Create an explicit review checkpoint
For a proposed portrait-film workflow, an editor saves the project repeatedly while changing the opening. Only the completed viewing export is intended for the client. Calling every project save a client revision would make the feedback record ambiguous.
- Record the project or source asset and the relevant save information.
- Export the movie that the recipient should actually inspect.
- Finish its upload before deliberately organizing it into the appropriate Version Stack.
- Open the intended revision and verify the opening, soundtrack and ending.
- Record the revision issued for review, the decision requested and any later approval.
The approved-version handoff record helps connect source, selection and use. It complements the platform history; it does not rename a save as an approval.
Recover a save without rewriting the review record
The official guide allows downloading a particular save through its three-dot menu. If an earlier save contains the desired edit, recover it as a working state and inspect it before issuing anything. Do not assume that recovery reproduces every external dependency or automatically republishes a previously approved export.
If the recipient says the film has not changed, first compare the exact viewing revision with the issued record. A changed project save and an unchanged export can coexist. If feedback concerns story rather than final quality, identify that scope using the review-copy and master distinction.
Verify the issued revision with the recipient
Have the intended reviewer open the actual review destination and identify the expected cut through an observable change, such as the revised opening. Keep the earlier decision attached to the earlier revision unless the reviewer explicitly approves the new one.
The concept, content and master approval guide explains why approval also needs a defined scope. Accept the handoff when the platform revision, viewed movie and decision record agree. A recent save timestamp is insufficient evidence by itself.
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
- Frame.io: Versioning in Frame.io: The September 25, 2026 V4 guide distinguishes uploaded Version Stacks from Mounted Storage Version Saves attached to the current version. Save history includes date, time and author; a specific save can be downloaded.
Documentation-based guidance from the complete official source captured October 29, 2026. No account operation, upload, approval, storage measurement or recipient test was performed. The portrait-film scenario and acceptance procedure are proposed. The newer dedicated Versioning guide governs the save distinction; older Drive wording must not replace it.
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.