Turn Frame.io comments into Pro Tools markers
Drop a comment CSV, download Pro Tools .ptx or MIDI markers for Logic, Cubase, and Reaper. Free, no account needed.
Match your session's tempo so markers land in time.
Auto-detects frame rate (23.976–60, drop-frame aware), with a start-of-sequence offset. Fine-tune everything once a CSV loads.
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
Download your markers
Pro Tools .ptx (open it or pull markers in via Import Session Data), or a MIDI .mid that imports into Logic Pro, Cubase, Reaper, and Studio One. One named marker per comment.
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 Pro Tools 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.
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 — not your DAW session rate. It's auto-detected from the export, and the picker is only there for the rare case the CSV can't be read.
You download a .ptx session file with one marker per comment, carrying the comment text. Open it directly in Pro Tools, or bring the markers into an existing session with File → Import → Session Data.
No. The file is converted in memory and discarded as soon as your .ptx is returned. Nothing is written to storage, logged, or retained — client notes on unreleased work never stick around on our servers.
Pro Tools caps marker names at 246 characters and marker comments at 255. Longer notes are truncated to fit; the full text is always visible in the preview before you download.
Two things. First the frame rate: set it to the frame rate of the video you reviewed in Frame.io, NOT your Pro Tools session rate. The two are independent — Pro Tools markers are placed by absolute time, so a 24fps session and a 25fps source still need 25 here. 23.976 vs 24 and drop-frame vs non-drop are the other usual culprits. Second the start offset: if your sequence starts at 01:00:00:00 instead of zero, set that as the start offset so marker positions line up.
Choose the MIDI markers (.mid) export format, set Project tempo to your session's BPM, and import the downloaded .mid into your DAW. MIDI marker positions are tempo-relative, so matching the tempo (or importing the file's tempo track) is what makes them land at the right time.
Yes. Pick Premiere Pro markers (.csv) or DaVinci Resolve markers (.edl) in the export format menu above, or use the dedicated converters at cuevue.io/tools/frameio-to-premiere-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 Pro Tools marker export 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.