Frame.io V4 dropped DaVinci Resolve. Here's the workflow I use now.

Frame.io's own V4 documentation says DaVinci Resolve will not be supported, and recommends uploading assets manually and importing comments back as an EDL. The native integration only ever covered Resolve 16 and 17 Studio, and it has not been updated in years. If you cut in Resolve, you need a different plan.

Frame.io is still good software

I want to say that before anything else, because posts like this usually turn into an excuse to kick a competitor and you can smell it from the first paragraph. If you cut in Premiere and you live in Creative Cloud, V4 is fine. Camera to Cloud is still the real thing for high-end production and nothing I make competes with it.

This is narrower than that. It is about one workflow that stopped working.

What actually changed

The integration was never Frame.io's to begin with. Blackmagic built it, against Frame.io's older public API, and Frame.io's help page still lists it as supporting Resolve 16 Studio and 17 Studio only. Previous Studio versions and the free version were never covered. There have been no updates to it in years.

V4 shipped with a public API that is not backward compatible with the old one. At that point the integration had nothing left to talk to. Accounts that stayed on the legacy platform kept it running for a while, in some cases as late as Resolve 20, and that window closed when migration became mandatory.

So this was not a decision anyone announced on a stage. It is an integration that quietly ran out of road, and the people who notice are the ones who were using it every day.

The EDL workaround, honestly

It works. I have done it. You export an EDL of the comments, import it into Resolve, and the notes land as markers.

What the documentation does not tell you is how it feels on the fourth round of notes on a Thursday. You are exporting a file to move three sentences from a browser into a timeline. The round trip has to be rebuilt by hand every time, in both directions, and every manual step is a place where version three of the cut gets notes meant for version two.

The failure is never dramatic. It is just slow, and it is slow at the exact point in a job where you have the least patience left.

What I use now

I built the thing I wanted, which is that the Resolve app pulls comments from the review link straight onto the timeline as native markers, and renders the next version back out to the same link from the same panel. No EDL, no export step, no second window.

That is the whole feature. It is not clever. It is just the part of the old workflow that went missing, put back where it was.

If you are deciding right now

You have three real options. Stay on legacy Frame.io with an old Resolve, which is a shrinking room. Accept the EDL round trip, which is fine if your notes cycles are short. Or use something that talks to Resolve directly.

Any of those can be the right call. What does not work is assuming it still functions the way it did two years ago, which is how most people find out: mid-job, with a client waiting.

The tools that survive a decade are usually the ones built by someone who still has to use them on Thursday.