
A Frame.io V4 Share containing a folder changes when that folder's contents change. Adding a working take to the shared folder can therefore add it to the client's existing link without sending another URL. Check the Share's actual contents and container membership before treating the link as a fixed review package.
Key Takeaways
- Shared folders update dynamically as their files are added or removed.
- A working folder and a curated client selection need different handling.
- The recipient's real view is the acceptance check for the review package.
Find out what the link contains
The official Shares in Frame.io guide says a shared folder retains its structure and dynamically updates the Share link. It also describes adding individually selected assets from multiple locations. These are different ways to define the package's membership.
Open the existing Share configuration and identify whether it contains a folder, selected assets, or both. Check nested material where applicable. Do not infer membership from the handful of thumbnails visible in an old email or screenshot.
Review version visibility separately. The Share's Show all versions setting determines whether reviewers can see all versions in stacked media or only the latest. Removing an unrelated working file does not answer whether earlier stacked revisions remain available.
Contain an unintended addition without losing evidence
If private material appears unexpectedly, an authorized owner should first decide whether to disable the affected Share's visibility while correcting its scope. Frame.io documents a visibility control for allowing or blocking link access. Preserve useful comments and the actual asset identity before reorganizing files.
A proposed correction sequence is:
- Identify the unexpected asset and the folder route exposing it.
- Compare the Share's live contents with the intended review list.
- Adjust the package through an authorized configuration change.
- Recheck versions, captions, comments and download permissions.
- Verify the corrected link from the intended recipient's context.
This is a containment procedure, not a guarantee that nobody opened or copied the material. Access changes do not establish what happened before the correction.
Keep working candidates outside the issued package
For a hypothetical portrait commission, an editor shares a folder containing two chosen takes. Later, a face-correction experiment is saved into the same folder. That organizational change also changes the client's package. A separate working location would avoid using the issued folder as a scratch area.
The approved-version handoff guide explains how to record the selected file. Pair that record with a deliberate Share membership check. A filename marked approved does not prevent another file in the container from being shared.
Accept access and editorial scope together
Have the reviewer confirm the intended cuts, not simply that the link opens. Check every included asset and any accessible prior versions. Keep the review-copy and final-master distinction clear in the accompanying instructions.
For wedding films, private-cut and public-teaser approval remains a separate decision. A convenient existing link is not permission to expose a newly added scene. Close the check when actual package membership and the approved audience match.
Related tasks
- Should I Send a Review Copy or the Final Master of an AI Video to a Client?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- How to Make a Public Wedding Teaser From a Private AI Film
Sources and scope
- Frame.io: Shares in Frame.io: Files added or removed within a shared folder dynamically update its Share link. Shares can also contain individually selected assets, and visibility, comment, download and version controls are separate settings.
Documentation-based guidance from the full Frame.io V4 Shares source captured October 29, 2026. No share was created, disabled or audited in an account. The client-film scenario and proposed containment process are not incident reports. Share activity cannot establish complete downstream copying or viewing.
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.