Frame.io
Adobe's review platform finished its V4 rebuild and immediately started shipping AI into it
◆Recent moves
- 14d ago
Drive adds native Intel Mac builds and upload reliability fixes
Drive picks up native Intel Mac builds alongside Apple silicon and a round of reliability work — bounded auth token retries, unstuck sync status after invalid sessions, better Nuke compatibility on mounted drives. Post houses running older hardware and finishing tools were the ones this blocked.
View source ↗ - 19d ago
Multi-Page InDesign Previews
InDesign files now preview as full multi-page documents rendered by Adobe's own engine, replacing a low-res first-page thumbnail. It is a small feature that only Adobe's own review product could ship this way, and it extends Frame.io's reach from video into print review.
View source ↗ - 26d ago
New in iOS: Project Navigation
iOS gets a navigation bar linking assets, share links, and collections directly, with the full folder path visible in deep hierarchies and a prominent upload button. Mobile catching up to the V4 information architecture rather than adding capability.
View source ↗ - 28d ago
Drive handles offline launch and unreliable project loading
Drive handles the failure cases: a real sign-in screen when launched offline, reliable project loading from search or account switching, paginated shared projects, and Open in Drive jumping straight to the contents folder. Sync clients live or die on this kind of work.
View source ↗ - 1mo ago
New in Labs: Frame AI Assistant
⚡ SPARKThe first substantial Lab is a project-aware AI assistant that creates folders, renames assets, applies metadata, summarizes comments and transcripts, and generates images and video inside Frame.io. It pushes the product past review into asset operations and creation, and shipping it through Labs signals Frame.io wants it in customers' hands before it is finished.
View source ↗ - 1mo ago
V2 API Deprecation Notice
The legacy V2 API gets a hard removal date of December 1, 2026, with Camera to Cloud endpoints exempted and V4 confirmed as not deprecated. Consequential for anyone with a V2 integration, but it is the scheduled close of a migration already well underway.
View source ↗