Final Cut Pro to Pro Tools

Turn a Final Cut Pro timeline into an AAF that Pro Tools opens as a finished session — every clip in its place, with its level, its fades and its markers. Free, and everything runs in your browser: nothing you point it at is uploaded anywhere.

Open the converter · Read the manual

What arrives at the other end

Not a list of converted fields: what the mixer actually finds when the session opens.

  • Your project as it leaves Final Cut Reads the .fcpxml or .fcpxmld you export, with no intermediate step and no second application in the way.
  • Audio cut from your originals Takes from your own files exactly the regions the edit uses, with whatever handles you ask for, so there is something to work with at every cut.
  • The sound work, intact Clip gain, volume automation, pan, fades, crossfades and markers arrive in place, not as notes for somebody to rebuild.
  • Roles turned into tracks Every Final Cut role becomes a DAW track, and you set the order, the names and which ones stay behind before converting.
  • Containers resolved Compound clips, sync clips, multicam and multitrack recordings are opened up and deliver all of their voices, not just the active angle.
  • Standard AAF, not a dialect The default output opens just as well in Nuendo, Fairlight, Reaper and DaVinci Resolve. The non-standard option is opt-in and off by default.

How it works

Three steps, and the whole conversion happens in your browser.

  1. Export the XML In Final Cut Pro, select the project and choose File ▸ Export XML.
  2. Point at your media Drop that file here and point at the folder your original files live in.
  3. Set it up and deliver Choose fades, handles, timecode and tracks. You get a folder: the AAF, its audio, and a report of what travelled and what did not.

Questions people ask

Can Final Cut Pro export AAF?
No. Final Cut Pro exports FCPXML, a document describing the edit, and no AAF at all. fcp2aaf reads that FCPXML and writes the AAF from it, cutting the audio it needs out of your original media.
Is my footage uploaded anywhere?
No. The converter runs inside your browser: the same Python engine that exists as a command-line program is loaded into the page and reads the files you point it at. The network is used only when the page opens, to fetch that engine; from then on you can disconnect from the internet and the conversion still finishes.
What does it cost?
Nothing. There is no account and no sign-up. If you use it commercially, a donation is welcome; the paid programs that do this cost between 80 and 150 dollars.
What does the mixer receive?
A folder, not a file: the AAF, whose name starts with 00_ so it sorts to the top, the conformed audio it points at, and a plain-text report of what travelled and what did not. Hand over the whole folder — on its own the AAF opens a session with every region offline.
Does it work with DAWs other than Pro Tools?
Yes. The default output is standard AAF, which Nuendo, Fairlight, Reaper and DaVinci Resolve open as well. The one non-standard option, grouping a clip's channels into a stereo track, is off by default.
Can it handle very large media files?
Yes. An 8 GB camera rush or a day-long polywav is fine, in WAV, BWF, RF64, MP4 or MOV. The exception is MXF, which no browser can open: extract the audio as WAV first.

Ready to hand the cut over to the mix?

Nothing to install and no account to make. Open the converter, drop your XML in and point at your media: the rest happens in your browser.

Open the converter · Read the documentation