Frame.io finished moving every legacy V3 account to V4 - automatic upgrades started October 27, 2025, and V4 has been the only version since. Nothing was optional about it, so the useful question is not "should we migrate" but "what did the upgrade change under us, and what should we verify?" This checklist covers the six areas the upgrade touched: your review links, your comments, your roles, your integrations, your storage model, and your settings - with the removals called out honestly, because several are permanent.
What V4 actually changed
V4 (announced by Adobe in October 2024, fully rolled out through 2025-2026) rebuilt the platform's structure. The renames are cosmetic; the behavior changes behind them are not:
| V3 concept | V4 equivalent | What actually changed |
|---|---|---|
| Teams | Workspaces | New structure; workspaces default to "Restricted" status after upgrade |
| Review & presentation links | Share links | Old links still open and comments carried over - but migrated shares are not editable in V4 |
| Team-only comments | Internal comments | Hidden by default after upgrade; support can restore them as internal comments |
| Team Manager / Collaborator roles | Workspace Admin / Member with permission levels | Five member permission levels (Full Access → View Only) replace the old role set |
| Archival storage + allocations | Single storage pool | Archival storage discontinued; per-user storage allocations no longer supported; projects are active/inactive |
The verification checklist
1. Open your old review links. Legacy links migrated and comments carried over - but confirm the ones that matter still play, because migrated shares are read-only in V4. If you need to edit one, "Duplicate as V4 Share" creates an editable copy - with a new URL, so anything already sent to clients points at the old one.
2. Find your hidden team-only comments. Internal notes were hidden by default in the upgrade. If your team's private review threads vanished from view, they were not deleted - restoring them as V4 internal comments goes through support.
3. Audit roles and access. Everyone was remapped automatically: Account Owner → Owner, Account Admin → Content Admin, Team Manager → Workspace Admin, members → five permission levels. Check that nobody landed on Full Access who should sit at Edit or Comment Only - and that workspace "Restricted" status matches who should see what.
4. Test every integration before you need it. This is the biggest silent change: the DaVinci Resolve integration is gone (comments can still be imported via EDL), as are the Vimeo, Dropbox, and CaptureOne integrations. V4 projects can no longer be created from the Final Cut Pro share destination (Mac app uploads still work). Existing Slack project notifications keep working but new ones cannot be created. The Premiere Pro comment panel works; After Effects support arrived by July 2026.
5. Re-apply your secure-sharing default. The Secure Sharing default setting does not survive the upgrade - re-enable it, or new shares are created without it.
6. Check storage and notifications. Archival storage and per-user allocations are gone - review what "inactive" projects mean for your archive budget. Project notifications were replaced by account-level notification settings, so re-set who hears about what. Camera-to-cloud users: Friendly File playback was removed (Lightroom connections are supported).
If you run integrations or automations
The API story matters more than any UI change. The V4 API reached early access on June 3, 2025 with webhooks and custom actions, but self-service API access was still "coming soon" as of mid-2026, and server-to-server credentials through Adobe's Developer Console are the long-term auth model. Anything you built on the legacy V3 API - or on Zapier - needed rebuilding, and shops running server-side workflows were moved onto Frame-managed developer tokens during migration. If your pipeline depends on API automation, budget for it before you depend on it; the migration gaps were real enough that customers queued for ALM migration prioritization.
The cost check while you are in there
An upgrade that changes structure and integrations is the natural moment to re-read the plan you are on. As of November 2026, Frame.io runs Free (2 members, 2 projects, 2 GB), Pro at $15/member/month (up to 5 members), Team at $25/member/month (up to 15), and Enterprise tiers - with reviewers free via share links on every tier. The full seat math against flat-priced alternatives is in Frame.io pricing explained, and the line-by-line plan breakdown is in video review tool pricing compared.
If the checklist found gaps, you have options
None of this means V4 is wrong for your team - Adobe rebuilt the platform around workspaces, collections, and custom metadata, and enterprises on the Adobe ecosystem get real value from that. But teams whose loop runs through DaVinci Resolve, whose clients submit via public project links, or whose archive depended on archival storage just lost workflow pieces permanently, and "rebuild the habit" and "switch tools" are both legitimate answers. Frooty's angle on the same problem set: a Premiere and After Effects panel plus a DaVinci Resolve bridge (the macOS Resolve panel needs the Studio plan), reviewers never billed on any plan, and Studio at $39/mo flat with unlimited members as of November 2026. The honest, no-importer-exists migration path is in migrating from Frame.io to Frooty, and the durability habits that survive any vendor's platform rewrite are in the Dropbox Replay status checklist.
FAQ
Was the Frame.io V4 upgrade mandatory?
Yes - automatic upgrades of legacy V3 accounts began October 27, 2025, and V4 is now the only version. Enterprise accounts could schedule their own update window, but the destination was the same. That is why the checklist matters: the upgrade happened to your workspace whether or not anyone was watching.
Do my old Frame.io review links still work in V4?
Yes - legacy review and presentation links migrated, comments carried over, and the links still open. The catch is that migrated shares are not editable in V4: "Duplicate as V4 Share" gives you an editable copy under a new URL, while everything already shared with clients still points at the original.
Does Frame.io V4 work with DaVinci Resolve?
No - the Resolve integration was removed in V4; the documented workaround is importing comments via EDL. The Vimeo, Dropbox, and CaptureOne integrations were removed in the same sweep, and new Slack project notifications cannot be created. If your loop runs through Resolve, either adopt the EDL import habit or evaluate a tool that still ships Resolve support.
Is the Frame.io V4 API available yet?
The V4 API entered early access on June 3, 2025 with webhooks and custom actions, but self-service access was still listed as "coming soon" as of mid-2026, and authentication moves to server-to-server credentials via Adobe's Developer Console. Legacy V3 API integrations and Zapier flows needed rebuilding.
How much does Frame.io V4 cost?
As of November 2026: Free (2 members, 2 projects, 2 GB), Pro $15/member/month for up to 5 members, Team $25/member/month for up to 15, and custom Enterprise tiers. Reviewers on share links are free on every tier - the seat math and its alternatives are in Frame.io pricing explained.