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.
Converted in memory — your file is never stored.
No file yet
Drop a Frame.io comment CSV on the left to preview the markers it will create.
How it works
- Step 1
Export your comments from Frame.io
Open the file's comment list in Frame.io and choose Export comments → CSV.
- Step 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.
- Step 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 step entirely
We built this converter because we kept doing the shuffle ourselves. In Cuevue, clients comment on a review link and those comments export straight to Pro Tools markers — no Frame.io, no CSV, no conversion.
Frequently asked questions
How do I export comments from Frame.io?
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.
Which frame rates are supported?
23.976, 24, 25, 29.97 (including drop-frame), 30, 48, 50, 59.94, and 60 fps. The frame rate is auto-detected from the export and can be overridden from the picker if your sequence differs.
How do the markers get into Pro Tools?
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.
What happens to my CSV? Is it stored anywhere?
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.
Why are long comments cut off?
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.
My markers land in the wrong place — what should I check?
Two things. First the frame rate: 23.976 vs 24 and drop-frame vs non-drop are the 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.
How do I get the markers into Logic Pro (or Cubase, Reaper, Studio One)?
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.
Do you support Premiere or DaVinci Resolve markers?
Not yet — those are next. Pro Tools and MIDI came first because they had no good free alternative. After a conversion you can leave your email to hear when new formats ship.
Why is this free?
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.