What is an AAF file?

An AAF file (Advanced Authoring Format, .aaf) is a binary interchange container that carries a timeline — clips, tracks, edits, effects metadata, and optionally the media itself — between post-production applications. It's the standard way a picture edit travels from Avid Media Composer to Pro Tools for the audio mix, and one of the three big timeline interchange formats alongside EDL and FCP7 XML. If someone sent you an .aaf, this guide explains what's inside it, what opens it, and what to ask for instead when AAF isn't the right vehicle.

What an AAF file contains

AAF describes a composition: the sequence structure of an edit. Concretely, that's:

• Tracks and clips — video and audio events with in/out points and timeline positions
• Source references — which media files (or tape/reel IDs) each clip comes from, with source timecode
• Edit metadata — transitions, some effects and their parameters, clip names, comments, track names
• Optionally, the media itself — an AAF can either link to external media files or embed the audio/video inside the .aaf

That last distinction is the one that bites people. An embedded AAF is self-contained (and large — it carries the actual media); a linking AAF is small but useless without the media files it points at. When an audio mixer says "send me an AAF," they usually mean embedded audio so the session arrives complete.

Under the hood, AAF is a binary object database (it uses Microsoft's Compound File format as its container) — unlike an EDL or XML, you can't open it in a text editor and read it. The format is maintained by the Advanced Media Workflow Association (AMWA), which grew out of the original AAF Association.

What actually opens an AAF

AAF is a professional-NLE format, and the list of things that open it is short:

• Avid Media Composer — AAF's home turf; import and export are native
• Avid Pro Tools — the classic destination: picture editors export AAF, mixers import it as a session
• DaVinci Resolve — imports AAF timelines (File > Import > Timeline), commonly for conform from Avid
• Adobe Premiere Pro — imports and exports AAF, with a rougher translation than Avid↔Avid
• Audio apps (Nuendo, Logic via extensions, Fairlight) — varying degrees of AAF session import

No media player, browser, or general file converter opens an AAF, because there's no "play" in it — it's an edit description, not a video.

AAF vs EDL vs XML: when each is the right handoff

The short version of the full comparison: AAF wins when audio matters (multichannel track layout, levels, handles, embedded media — the Pro Tools turnover) or when either end is Avid. FCP7 XML wins for Premiere↔Resolve edit handoffs. EDL is the one-video-track, cuts-only fallback that survives anything. If your destination rejects your AAF, the escape ladder is XML first, then EDL.

"Can I convert an AAF to something else?"

Here's the honest answer: converting out of an AAF requires an application that can open it — one of the NLEs above — because the binary format needs real playback of Avid's object model. CutConvert doesn't convert .aaf files. What usually solves the underlying problem instead:

• You need the cut in another NLE → go back to the source and export FCP7 XML (or have Resolve import the AAF and re-export what you need — Resolve's free edition handles this).
• You need a cut list → export an EDL from the source, then convert the EDL to CSV for a readable spreadsheet of every event.
• You need the captions/subtitles from the edit → those don't ride in AAFs anyway; export an SRT or the caption format directly and convert from there.

The pattern: AAF is a destination-specific delivery, not an editable intermediate. When it's the wrong destination, re-export from the source rather than trying to crack the AAF open.

FAQ

What is an AAF file? An Advanced Authoring Format file — a binary container that carries an edited timeline (tracks, clips, edit points, source references, and optionally embedded media) between post-production applications. It's the standard Avid interchange format, especially for picture-to-sound turnovers into Pro Tools.

What opens an AAF file? Avid Media Composer, Pro Tools, DaVinci Resolve, and Premiere Pro, plus some audio applications. Nothing consumer-grade opens one — it's an edit description, not a playable video file.

What's the difference between an embedded and a linking AAF? An embedded AAF contains the actual media inside the file (large, self-contained — what audio mixers usually want). A linking AAF only references external media files and is broken without them. Check which kind you're exporting before sending it.

Is an AAF the same as an OMF? Same job, different generation — OMF is the older Avid interchange format with a 2 GB file-size limit and cruder metadata. AAF replaced it; use AAF unless the receiving system is old enough to demand OMF.

Can I convert an AAF file without Avid or Resolve? Practically, no — reading an AAF requires an application that implements Avid's object model, and DaVinci Resolve's free edition is the cheapest one that does. The usual fix is re-exporting from the source NLE in the format you actually need (XML for edit handoff, EDL for cut lists).

Do subtitles or captions travel inside an AAF? Not usefully — caption data is delivered as sidecar files (SRT, SCC, MCC, STL) alongside the media, not inside the AAF. If you need broadcast captions from an edit, export the subtitle file and convert that.