Frame.io V3 is legacy now: what a small team should check

The help site says legacy and names no date. Here are the five things worth checking on your own account, and what each one means if you move.

Updated

Frame.io's help site now titles itself the Frame.io V4 Knowledge Center. Its largest collection, 123 articles as of this writing, is filed under "Frame.io Legacy (V3) Article Collection". That is the whole announcement: not a countdown, a filing decision. The migration dates that circulated, October 27, 2025 for the move to version 4 and June 1, 2026 for the last legacy accounts, came from customer emails, and some accounts report other dates. The help center itself no longer states them, and nothing on it names a date when the V3 articles, links or exports stop working, so we are not going to name one either.

What a filing decision means for a small team is different from what it means for a studio with an admin. Nobody is going to migrate you. The checks below take under an hour, and they tell you whether V4 is your tool for the next few years or whether this is the moment you were already looking for.

Take a share link you sent in 2025 and open it in a private window. What does the client see: the cut, a sign-in wall, a redirect, or nothing? Do it for one link with comments on it, because the comments are what your client remembers. If the old link still works, note the date. You will want to know how long that stays true.

Check two: count the versions that survived

Pick an asset that went through four or more cuts under V3 and open it in V4. Count the versions, read their labels, and check which one plays by default. If the labels are numbers you did not choose, that is worth knowing before you lean on them in a dispute about which cut the client signed off.

Check three: find the approval

For the same asset, find the approval and the person who gave it, and check whether it is tied to a specific version or to the asset as a whole. An approval that floats free of a version is a story with a missing page.

Check four: read the seat line on your invoice

Frame.io accounts are being consolidated into the Adobe Admin Console, and V4 plans are priced per member, which is where the price moves for a team of three to eight people. Count the people who sign in against the people who only ever comment. On HoldFast the second group is always free and never needs an account, and the plans are flat. That is the one structural difference that shows up on the invoice.

Check five: list the integrations you touch weekly

Camera to cloud, the Premiere panel, a storage mount: write down the ones you used in the last month, not the ones on the feature page. Then confirm each one exists in V4 on your plan. Whatever you find, that list is also your migration list if you go anywhere else, and it is usually shorter than you expected.

If the checks send you looking

Do not evaluate on the announcement. Run one real project through both tools with a real client and read the notes that come back. The vocabulary translates cleanly, and the guide on the habits that carry over is the place to start.

Ready to try it?

Host video, collect frame-accurate review, and see who's watching. Free to start.

Start free