On April 15, Frame.io announced Frame.io Drive, a desktop app with mounted-storage capability. In plain English: your Frame.io project shows up in Finder like an external drive, and you can edit from it without downloading files first. It replaces the old Frame.io Transfer app, with both supported during a transition period.
The pitch is familiar if you've been paying attention to this corner of the market. LucidLink, Shade, and Suite Studios have been selling versions of "edit directly from the cloud" for a few years now. Frame.io's entry matters because the company already owns the review-and-approval layer for most post-production shops. If they can bolt edit-from-cloud onto that existing footprint, they don't have to win editors from scratch — they just have to keep them from leaving.
What Frame.io Drive Actually Does
Think of Frame.io Drive like the difference between a rental house that ships gear to your door and a rental house with a pickup window. Transfer was the shipping model — you'd request files, wait, and work on them locally. Drive is the pickup window — media appears in your file browser, and the app fetches the bytes you actually need when you open a clip.
The implementation is caching, not true streaming. When you import a clip into Premiere, DaVinci Resolve, After Effects, Avid Media Composer, or Media Encoder, Frame.io Drive pulls the file into a local cache and hands it to the NLE. Subsequent scrubs and plays read from cache. Renders go directly back to the mounted project and upload to Frame.io automatically, up to 250 versions per project before older ones move to trash.
Two notes from the mounted storage optimization guide worth knowing:
- Your local SSD needs to be the first cache path in your NLE settings, not the mounted project. Otherwise you're asking a remote disk to serve as your scratch disk, which will be painful.
- Direct I/O needs to be on for each storage path. This is the same setting that trips up editors working off NAS mounts.
For single editors on decent internet, this works. For teams sharing a project where four people need the same R3D files at the same time, cache warming becomes the bottleneck.
The Pricing, Which Is the Same as Frame.io Pricing
Frame.io Drive isn't a separate SKU. It's a feature of existing plans, which means you're paying the same per-seat rate whether you use it or not. Here's how the included storage stacks up.
Free. Two members, 2 GB of storage. Enough to try it on a single short project.
Pro. $15 per seat per month, up to 5 members. 2 TB base plus 2 TB per additional member. A fully populated five-person Pro team gets 10 TB for $75/month — effectively $7.50/TB.
Team. $25 per seat per month, up to 15 members. 3 TB base plus 2 TB per additional member. Fifteen people on Team get 31 TB for $375/month, or about $12/TB.
Enterprise. Custom pricing. Typically where you'd land if you need Storage Connect (pointing Frame.io at your own cloud bucket) or more than 15 seats.
Annual billing drops these by roughly 13%.
The per-TB math only works out when your headcount matches your storage needs. A solo editor on Pro is paying $15/month for 2 TB — that's $7.50/TB, fine. A solo editor who needs 20 TB on Pro pays for 10 seats and gets 18 TB of extra storage they can't use. Same problem as Dropbox Business — seat-based models punish storage-heavy, people-light teams.
How It Stacks Up Against Shade and Suite Studios
Three companies, three very different bets on what editors actually want.
| Provider | Model | Cost | Effective $/TB |
|---|---|---|---|
| Frame.io Drive | Per-seat + bundled TB | $15–25/seat/mo | $7.50–$12 |
| Shade | Per-seat + bundled TB | $20/seat/mo (annual) | ~$40 |
| Suite Studios | Per-TB + per-seat | $75/TB + $10/extra seat | $75 |
| LucidLink | Per-TB only | $16–85/TB | $16–$85 |
Frame.io Drive
What you're buying. A review platform with streaming-edit capability bolted on. The killer feature isn't the mounted drive — it's that your editors, your clients, and your storage all live in the same tool.
Who it fits. Teams already using Frame.io for review. If you're paying for it anyway, the mounted drive is a free upgrade to your workflow. If you need 15+ TB but only have three people, you'll hate the scaling.
Shade
What you're buying. A unified media management and storage platform with AI-indexed search. Growth plan is $20/seat/month (annual), capped at 15 seats. Each seat includes 500 GB of active storage, Enterprise bumps it to 1 TB per seat.
Who it fits. Small creative studios who want MAM-style search and metadata on top of storage. The AI-indexing angle is real — Shade lets you search by "beach b-roll" or "interview cutaways" across your archive, which Frame.io does not.
Suite Studios
What you're buying. Straight cloud storage with a desktop client that mounts your Suite Drive for NLE access. $75/TB/month for managed storage, 5 users included, $10/month for each additional user. BYOS (bring your own storage) available if you want to point Suite at your own S3 bucket.
Who it fits. Studios with predictable storage needs who want a single line item they can forecast. The per-TB model is clean, but $75/TB is five-to-ten times what you'd pay on Backblaze B2. You're paying for the editor-friendly mount and caching.
LucidLink (for reference)
Still the incumbent in this category. $16/TB on the Standard tier (Wasabi backend), $85/TB on Performance (AWS backend). No per-seat costs. The mount is a true file system, not an app. If you're running a large facility that needs deterministic bandwidth, LucidLink is still where most people land.
The Frame.io Drive Bet
Frame.io is betting that the average editor doesn't want to manage two subscriptions: one for review, one for storage. By making the mounted drive a feature rather than a product, they turn "should I also buy LucidLink" into "I already have this."
The downside is the pricing model. Frame.io's per-seat-plus-bundled-TB math made sense when people were paying for review and using Dropbox or B2 for archives. Once the drive becomes the main event, the inefficiency of paying for unused seats becomes more visible. A post house with three editors and 30 TB of projects is going to do the math and probably conclude that Suite's $75/TB at five included seats ($375/month for 5 TB, with Frame.io already covered elsewhere) is cleaner, or that Backblaze B2 at $6.95/TB ($208.50/month for 30 TB) plus a separate review tool is cheaper overall.
The storage calculator is the fastest way to run these numbers against your own team size and storage needs. Plug in your TB, your headcount, and it'll tell you where each provider actually lands for your specific configuration.
One Question Worth Asking Before You Switch
Whichever of these tools you end up on, the real question is not "which cloud storage should I buy" but "how much do I actually need."
Most editors are carrying 30–60% unused footage across their active projects. On a 30 TB archive, that's 9 to 18 TB of media sitting in project bins that never made it onto a sequence. You're about to start paying Frame.io, Shade, Suite, or LucidLink to host all of it.
Before committing to a plan, it's worth scanning what you have. Clip Sweeper reads your Premiere Pro projects, follows the reference chain down to the actual timeline usage, and tells you which files are safe to delete. You might find you need a 10 TB plan instead of a 20 TB one, which changes the math on every comparison above.
The tools are converging. Everyone is going to offer mounted storage eventually. The real leverage is not storing files you never needed to keep.