Frame.io V2 API shutdown · December 1, 2026

Migrating off V4 anyway? Here's the move that doesn't re-lock you into per-seat.

Adobe's deadline means anything wired to the old API gets rebuilt this year either way. The only question is what you rebuild on.

Two paths, side by side

The deadline is Adobe's, not ours: their developer notice sets December 1, 2026 for the legacy V2 API shutdown (checked July 2026 — confirm against their current announcements).

Rebuild on V4Move to Millimeters
Migration work before Dec 1Re-wire every V2 integration to the V4 API
Pricing after the movePer member (seat) on paid plans — frame.io/pricing, July 2026
Client experienceShare links; account prompts vary by feature
At the storage limitSee their current terms
What else is in the planReview platform (+ Creative Cloud ecosystem)
What you'd give upNothing from your current stack
CostSee frame.io/pricing

Frame.io is still shipping. This isn't a eulogy — it's a fork in the road that their deadline put in front of you.

The move, in five steps

  1. 01

    Collect

    Download your originals and project files from wherever they live today.

  2. 02

    Upload

    Drag them into Backup — your folder structure is kept exactly as-is.

  3. 03

    Re-link

    Create a review link per active cut. Passwords and expiry are optional.

  4. 04

    Notify

    Send clients the new link. No account for them to make — it just opens.

  5. 05

    Close out

    Approvals land timestamped, and the finished work is already archived.

Straight answers: no one-click importer, and old comments don't come across — export what you need for the record first.

Re-tool once.
On your own terms.

No credit card · Free plan forever · Move one project first