Connect Frame.io: link, watch and review your cuts

Connect your workspace's own Frame.io account and the two stay in step. Every new project gets a Frame.io project of its own. Uploaded cuts link to the right deliverable by their file name. You can watch, download and upload cuts without leaving Contentmaker. And a client's comment or a new version moves the card on your board.

It is a workspace-wide connection, so a manager or admin sets it up in Settings → Integrations, on the Frame.io card.

Connect Frame.io

1. Open Settings → Integrations and click Connect Frame.io on the Frame.io card.
2. Sign in at Adobe and allow access. The card then shows Connected and the account it uses.
3. If the card says Finish setup, click it. That step is what lets Frame.io tell us about new comments and versions — until it is done, nothing moves on your board.

Your login reaches several Frame.io accounts? Pick the one this workspace should use from the list on the card. If you only collaborate on an account rather than own it, the card warns you: anything created from Contentmaker would land in someone else's account.

Adobe says your organisation doesn't allow third-party apps? Click Adobe organisation blocking the connection? on the card. Create an OAuth Web App in your own Adobe Developer Console, paste its Client ID and Client secret, click Save Adobe app, and then Connect Frame.io. Saving the app on its own does not connect anything — the card shows One step left until you sign in.

A Frame.io project for every new project

Once connected, every new project gets its own Frame.io project, created and linked the moment the project is. Two settings on the card decide how:

• Give every new project its own Frame.io project — on by default. Switch it off if you would rather arrange Frame.io yourself; nothing that already exists changes.
• Name new Frame.io projects — Client, then project name (like Atlas Brewing — Spring Launch) or Project name only. A title that already starts with the client's name never gets it twice.

Link a project by hand

For a project that already has a home in Frame.io, click Review in the project header. The Frame.io panel opens:

• Link with Frame.io lets you browse your Frame.io: choose the project, open folders, and click Link on the right one.
• Create a Frame.io project makes a new one, named after the client, and links it straight away.
• Once linked, Manage folder link lets you Change linked folder or Unlink.

Cuts link to their deliverables by file name

Upload cuts to the project's Frame.io folder and each one is linked to the deliverable it belongs to, matched by its file name. Dates, version numbers, aspect ratios and file extensions in the name don't get in the way, and a numbered series like Video 9 is understood.

• When a match isn't certain, we don't guess. The file waits under Unmatched Frame.io files at the bottom of the Frame.io panel, where you can Assign to deliverable… or mark it Not a deliverable.
• Auto-link videos in the panel runs the matching again and tells you how many need a look.
• Uploaded the same file name again, newer? The older copy is marked superseded and is never picked up again.
• A deliverable with several outputs — a 9:16 and a 1:1, or Hook A, Hook B and Body — gets a video per output, read from the ratio or the hook in the file name.

Watch, download and upload in the dashboard

• On the board: cards show the cut's preview frame. Click Play to watch it right there. Prefer a compact board? Turn off Preview frame under Fields.
• In the deliverable's Video tab: the cut plays in the panel. Download fetches the editor's original upload, even files a browser can't play, like a ProRes master. Change video… fixes a wrong link, and Open in Frame.io takes you to comments and approvals.
• Upload a cut straight from the Video tab: drop a video in, and keep the panel open until it's done. A first upload goes into the project's Frame.io folder; uploading onto a deliverable that already has a video adds it as the next version.

Playing cuts inside Contentmaker is for your team. Clients watch on their review link.

Comments and new versions move your board

When Frame.io tells us something happened, the card follows:

• A comment on a cut moves the card to your changes requested column.
• A new version stacked on a cut moves it to your waiting for review column — even if it was approved.

Which columns those are is yours to choose, in Settings → Statuses & boards. If no column is marked, nothing moves. Approvals in Frame.io itself are not passed on, so record those in Contentmaker — or let your client approve on their portal or share link.

Review links for your clients

Every linked video has two links: Team, which needs a Frame.io login, and Client link, which your client opens without one. The client link is made for you when a video is linked. Your clients find it on their portal and on the project's share link, where they can also Approve or Request changes.

Not using Frame.io, or using another review tool?

You don't need to connect anything to share a review link. Open the project header's overflow menu, choose Edit review link and paste a link from any review platform. On a deliverable, use its Review link field. A pasted link opens fine but doesn't sync anything — the Frame.io panel shows it as URL only.

For a Frame.io cut, paste a share or review link made in Frame.io, not the app.frame.io address from your browser's address bar — your client can't open that one without a Frame.io login.

Working with Contentmaker's editing service?

Projects you share with Contentmaker get their Frame.io folder in Contentmaker's own Frame.io, filed under your end client next to their earlier projects, where our editors work. You don't need a Frame.io connection of your own for those.

Something wrong?

• Token invalid: Frame.io stopped accepting the connection. Click Reconnect on the card.
• A video landed on the wrong deliverable: open the deliverable's Video tab and use Change video…, or Unlink it in the Frame.io panel.
• Frame.io is still processing this video: the cut was just uploaded. It plays once Frame.io is done.