← All posts

How to move your files off Frame.io (without downloading everything)

Three ways to migrate a Frame.io library to another review tool, what comes across, what doesn't, and how to check nothing went missing.

Seamlift17 Nov 2026 · 4 min read

Most teams that want to leave Frame.io stay for one reason: the footage. Years of projects sit in there, and moving them sounds like a weekend of downloads and re-uploads.

It doesn't have to be. Here are three ways to move a Frame.io library, from the slowest to the fastest, and a checklist so you know nothing was left behind.

Full disclosure: we make Seamlift, and option 3 is our importer. Options 1 and 2 work with any review tool.

Before you start: decide what you're actually moving

You almost never need to move everything.

  • Active projects: move these first, so current reviews carry on in the new tool.

  • Finished projects you might reopen: move the final cut, the project file and the source folder. Skip old review drafts.

  • Archive: if it's only kept "just in case", a cheap cloud drive or a NAS is a better home than a review tool. Review tools charge for storage you watch and comment on, not cold storage.

Write the list down. It's also your checklist at the end.

Option 1: download and re-upload

The method that always works.

  1. In Frame.io, open a project, select the folders you need, and download them. Large selections arrive as several zip files.

  2. Unzip and check the folder structure is intact.

  3. Upload the folders to the new tool, keeping the same structure.

Good for: a few small projects. The catch: every byte goes through your computer twice. 500 GB on a 100 Mbps connection is roughly 11 hours down and, on a typical home upload speed, much longer back up. Your machine has to stay awake the whole time.

Option 2: hop through a cloud drive

If you already pay for Google Drive or Dropbox with enough space:

  1. Download from Frame.io onto a machine with a fast connection (an office line, or a cloud desktop).

  2. Sync the folders to your drive.

  3. Import from the drive into the new tool, if it supports that.

Good for: teams with a fast office connection. The catch: you still download everything once, and you need spare drive space for the whole migration.

Option 3: import straight from a Frame.io share link

Some tools can copy files directly from Frame.io's servers to theirs, so nothing passes through your computer.

In Seamlift it works like this:

  1. Go to Integrations → Frame.io and connect your Frame.io account once, through Adobe sign-in.

  2. In Frame.io, make a share link for the folder or files you want to move.

  3. Paste the link into Seamlift. You get a preview first: "Footage · 19 files · 1.03 GB", the folder tree, and any files that will be skipped and why (for example, downloads turned off).

  4. Pick a destination: a new project named after the share, or an existing project and folder.

  5. Click Import. A progress card shows files and gigabytes copied. You can close the tab; the import keeps going, and you get an email when it's done.

Files arrive with their folder structure, and they behave exactly like files you uploaded: previews, the player, frame-accurate comments, versions, and the Premiere Pro panel.

Good for: anything bigger than a couple of projects. Current limits:

  • The import is in beta. Request access on the Frame.io page in Integrations and we turn it on.

  • It brings files and folders. Frame.io comments don't come across yet. Export the comments you still need (Frame.io can export them as a list) or resolve them before you move.

  • For version stacks, only the current version comes across.

  • It works with Frame.io V4 (Adobe sign-in) accounts.

  • The import has to fit your storage. If it doesn't, the preview tells you before anything starts.

What doesn't move, whichever option you pick

  • Comments and annotations. No tool migrates another tool's drawings reliably today. Resolve open notes or export them first.

  • Share links. Old Frame.io links stop being the place clients go. Send new links from the new tool.

  • Reviewers and permissions. Re-invite your team and decide who needs what role.

  • Integrations. Reconnect your editing app panels (Premiere Pro, DaVinci Resolve) to the new tool.

A checklist so nothing goes missing

  • File count matches per project (Frame.io shows a count per folder).

  • Total size roughly matches. Small differences are fine; a missing gigabyte isn't.

  • Open three random files in each project and play them to the end.

  • The folder structure is the same, so your editor's project file still finds its media.

  • Open comments are either resolved or exported.

  • Your team and clients are invited, and old share links have been replaced.

  • Only then: cancel the old plan or delete the old projects.

How long does it take?

  • Option 1: limited by your own connection, both directions. Plan for days on a large library.

  • Option 3: limited by Frame.io's speed. A 1 GB folder usually finishes in about a minute; large libraries in hours, not days, and without your computer on.

Picking where to move to

If you're still deciding, we compared the main options honestly in Frame.io alternatives and Seamlift vs Frame.io. The short version for Seamlift: 10 GB free, every feature on every plan, no per-seat fees, prices in USD and INR, and you can publish the approved cut to YouTube from the same project.

Try Seamlift free, then request Frame.io import access from Integrations.

  • migration
  • frame-io
  • comparison

Stop emailing timestamps.

Drop your first cutStart free