Turn Frame.io comments into DaVinci Resolve markers
Drop a comment CSV, download a marker .edl Resolve imports natively — one timeline marker per comment. Free, no account needed.
Match your session's tempo so markers land in time.
The Frame.io video's rate — not your session or timeline's.
How it works
- 1
Export your comments from Frame.io
Open the file's comment list in Frame.io and choose Export comments → CSV.
- 2
Drop the CSV here
Preview every marker live. Frame rate is auto-detected, with manual override, drop-frame support, and a start-of-sequence timecode offset.
- 3
Import into Resolve
Download the .edl, then in Resolve: Timeline → Import → Timeline Markers From EDL. One timeline marker per comment, note text included — no plugin needed.
Tryfree — skip the CSV entirely
Stop the export-convert-import shuffle. In Cuevue, clients leave comments right on the review link — then you push them to Resolve markers in one click. No Frame.io, no CSV, no conversion.
Frequently asked questions
In Frame.io, open the file's comment panel and choose Export comments → CSV. The converter reads the standard export columns — Commenter, Comment, Frame, Timecode — and turns each top-level comment into one marker. Replies are skipped so threads don't become duplicate markers.
Natively — no plugin needed. Open your timeline in Resolve and choose Timeline → Import → Timeline Markers From EDL, then pick the downloaded .edl. Each comment lands as a timeline marker at its timecode, with the comment text attached as the marker note.
Legacy Frame.io (V3) did — the comments menu had a Resolve (EDL) option, and Resolve 16/17 Studio even had a native integration. Frame.io V4's comment export offers CSV and plain text (as of July 2026), so on V4 you export the CSV and convert it here. If your account still shows the EDL option, use it — you only need this tool for the CSV. Converting here also adds what the built-in export didn't: skip-completed filtering, marker name and comment control, a frame-rate override, and a start offset for timelines that don't begin at zero.
A CMX 3600 EDL with one event per comment — the marker name rides the FROM CLIP NAME line and the full comment text rides a COMMENT line, which is what Resolve's marker import reads. Frame.io comments are point comments, so each marker is one frame long at the comment's timecode.
23.976, 24, 25, 29.97 (including drop-frame), 30, 48, 50, 59.94, and 60 fps. Use the frame rate of the video you reviewed in Frame.io — it's auto-detected from the export, and the picker is only there for the rare case the CSV can't be read.
Two things. First the frame rate: set it to the frame rate of the video you reviewed in Frame.io — 23.976 vs 24 and drop-frame vs non-drop are the usual culprits. Second the timeline start: Resolve timelines often start at 01:00:00:00, and markers whose timecode falls before the timeline start are silently dropped on import. Set the start offset to your timeline's start timecode (e.g. 01:00:00:00) so every marker lands inside the timeline.
No. The file is converted in memory and discarded as soon as your marker file is returned. Nothing is written to storage, logged, or retained — client notes on unreleased work never stick around on our servers.
Yes. Pick Pro Tools session (.ptx) or Premiere Pro markers (.csv) in the export format menu above, or use the dedicated converters at cuevue.io/tools/frameio-to-protools-markers and cuevue.io/tools/frameio-to-premiere-markers — same tool, preset to those formats.
We make Cuevue, a review platform for audio and video teams where marker export to Resolve, Premiere, and Pro Tools is built into the review player. The standalone converter is free because the CSV shuffle is a pain we know well. No signup, no watermark, no catch.