Turn Frame.io comments into Premiere Pro markers
Drop a comment CSV, download a Premiere-ready marker .csv — one named sequence 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 Premiere
Download the marker .csv and load it with a free importer extension — Markerbox or Marker Importer (Window → Extensions). One named sequence marker per comment, description included.
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 Premiere 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.
Premiere Pro can't import a marker CSV natively — you need a free importer extension. Install Markerbox (markerbox.pro) or Marker Importer from Adobe Exchange, open it via Window → Extensions with your sequence active, and load the downloaded .csv. Each comment lands as a named sequence marker with the full comment text in the marker's description.
Yes — if you work inside the Frame.io extension for Premiere, comments appear right in the panel. This converter is for when you have the CSV instead: a client's export, an archived project, or an account you're not a member of — or when you want marker-name control, completed-comment filtering, and a start offset before the notes land in your sequence.
A tab-separated CSV with the same columns Premiere itself uses when exporting markers — Marker Name, Description, In, Out, Duration, Marker Type — so importer extensions read it as if Premiere had written it. 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 start offset: if your Premiere sequence starts at 01:00:00:00 instead of zero, set that as the start offset so marker timecodes line up with the sequence.
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 DaVinci Resolve markers (.edl) 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-resolve-markers — same tool, preset to those formats.
We make Cuevue, a review platform for audio and video teams where marker export to Premiere, Resolve, 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.