AAF in Logic Pro: Import, Export and DAW Handoff

An AAF handoff can move an edited audio timeline into or out of Logic Pro, but it is not a portable copy of the mix. Use AAF for regions, track placement and supported automation; print any sound that depends on instruments, plug-ins or routing; include a reference movie and reference mix; then open the turnover on the receiving system before calling it finished.

Verified August 29, 2026 against Apple's current Logic Pro AAF guide, Adobe's Premiere AAF documentation updated August 18, 2026, and the current Avid Pro Tools reference material. Compatibility depends on both exporter and importer, so a short test turnover is safer than trusting the file extension.

What AAF carries in a Logic Pro workflow

AAF, or Advanced Authoring Format, is an interchange container. Apple's current Logic Pro AAF guide says it can import multiple audio tracks with track references, time positions and volume automation. Logic export includes used regions with track and position references and volume automation.

That's useful structure, not a guarantee of a matching mix. A receiving DAW may interpret fades, stereo organization, clip gain, automation or media references differently. AAF won't turn a Logic-only instrument or Audio Units chain into a Pro Tools or Premiere equivalent.

Agree on the turnover spec before exporting

Ask the receiving editor or mixer for the exact target rather than choosing settings by habit:

• destination application and version;
• project sample rate and required bit depth;
• picture frame rate and sequence start timecode;
• embedded media or a separate audio folder;
• trimmed media or complete source files;
• handle length when trimmed media is requested;
• mono, stereo and multichannel expectations;
• whether clip gain, volume automation and fades are expected;
• reference movie codec and burn-in requirements;
• delivery naming and folder structure.

If the receiver has a turnover sheet, follow it. “AAF for Pro Tools” and “AAF for Logic” aren't complete specifications.

Prepare a Logic project for export

1. Save a project alternative named for the turnover date and picture version.
2. Confirm the project sample rate, frame rate, start time and movie sync.
3. Remove muted experiments that should not appear, but keep a backup.
4. Name tracks by content and role, such as DX Boom 1, Foley Feet or Music Stem A.
5. Separate material when the receiver needs independent control.
6. Print software instruments, tuned vocals, restoration, special delays and other irreplaceable processing to new audio tracks.
7. Leave enough tail for reverbs, delays and sustained effects in the printed files.
8. Make a full-length stereo reference mix from the same picture version.

Do not flatten every creative decision blindly. Send both processed and clean versions only when the receiver asked for them, or when the distinction prevents real ambiguity. More tracks aren't automatically a better handoff.

Export a Logic Pro project as AAF

1. If needed, enable Logic's Complete Features.
2. Choose File > Export > Project as AAF File.
3. Set the agreed sample rate.
4. Choose 16-bit or 24-bit and WAVE or AIFF as required.
5. Choose dither only when the turnover spec and bit-depth conversion require it. Do not add it automatically to every export.
6. Name the file with project, picture version and date.
7. Save it inside a clean turnover folder, not among unrelated project files.

Apple lists 44.1, 48, 88.2 and 96 kHz, 16- or 24-bit audio, WAVE or AIFF, and selectable dither in the current dialog. The right choice is the receiving session's format. For picture work, 48 kHz is common, but confirm rather than assume.

Premiere Pro to Logic Pro: test the path first

Adobe's current AAF export guide makes an important limitation explicit: Premiere AAF exports are compatible with Avid Media Composer and Pro Tools, but Adobe has not tested them with other AAF importers. That means Premiere-to-Logic can work. It also means Adobe isn't promising that path.

Run a one-minute test containing dialogue, a stereo clip, a fade, a volume move, one clip with effects, a sync pop and a known timecode. Import it into Logic and compare it with the Premiere reference before the editor commits the full sequence.

Adobe recommends Breakout to Mono for Pro Tools. It also offers rendered clip effects with optional clean copies, embedded or separate audio, Broadcast Wave, complete or trimmed files and handle frames. These are exporter-specific choices. A Logic receiver should request the combination that passes the test rather than copying a Pro Tools preset by name.

Import or open an AAF in Logic Pro

Apple provides three current routes:

• File > Import > AAF to bring an AAF into the current project;
• select the AAF in the All Files Browser and click Open;
• File > Open to open the AAF as a project source.

For a turnover, create a new empty Logic project with the agreed sample rate and frame rate, save it, then import. This keeps old project settings and tempo information from contaminating the test. Add the reference movie separately and line up the stated start time or sync mark.

Run a complete import QC

1. Count imported tracks against the track sheet.
2. Check the first frame, first sync event and final frame.
3. Compare the AAF playback with the supplied stereo reference at several edit points.
4. Inspect clip starts, ends, fades and handles on dialogue and effects.
5. Confirm stereo files did not become unexpected mono pairs or swapped channels.
6. Check volume automation on tracks that visibly change level.
7. Listen for missing production audio, nested sequence material and rendered effects.
8. Search the Project Audio Browser for offline or duplicated media.
9. Save an import report before editorial work begins.

A clean start and end aren't enough. Spot-check a dense scene, a quiet dialogue edit, a crossfade, a stereo ambience and a music transition. Those reveal different translation failures.

Logic Pro to Pro Tools handoff

Send the AAF as one part of the package. Also send printed audio for Logic-only instruments and defining effects, plus the reference mix and movie. Tell the Pro Tools mixer which tracks are raw, printed, alternate or reference-only.

Avoid promising that buses, sidechains, plug-in automation or channel-strip state will rebuild. Even when volume automation is supported, compare its shape and level after import. If the mixer's session must begin at a specific timecode, state the start in the turnover note and place a sync reference where both sides can verify it.

For music production rather than picture post, full-length consolidated stems from a common start point can be more robust than a complicated AAF. Use AAF when editable region placement adds value. Use stems when sonic certainty matters more than edit reconstruction.

Embedded vs separate audio, complete files vs handles

Embedded media makes one self-contained file, which is convenient until size, recovery or re-export becomes a problem. Separate audio creates a visible media folder that's easier to inspect and replace. Adobe notes that its Separate Audio option preserves more metadata and allows unchanged files to be reused in later exports.

Complete source files preserve every available handle but can create a large package. Trimmed media is smaller. It also limits later edits. Handles add usable audio before and after each cut. The right duration depends on the editorial stage and receiver, so document it in frames or seconds and verify a real clip after import.

Fix common AAF failures

Media is offline or missing

Confirm whether the AAF is embedded or references a separate folder. Keep the AAF and media together, remove cloud placeholders, copy locally and retry. If relinking remains unreliable, request a new turnover with copied audio or complete files.

Audio arrives at the wrong time

Compare frame rate, project start, source timecode and picture version. Use the reference movie burn-in and sync event to determine whether the offset is constant or drifts. A constant offset suggests start-time interpretation. Growing drift points toward a rate mismatch.

Fades or automation differ

Compare against the reference mix, not memory. Ask for rendered critical transitions or printed tracks where the translation is unacceptable. Keep clean source audio when the receiving editor needs to rebuild the move.

Stereo becomes unexpected mono tracks

Check the exporter's channelization or Breakout to Mono option and the destination's import behavior. Identify left and right pairs by name before combining them, and verify polarity and alignment.

A human-readable turnover folder

Build a reference movie the audio editor can trust

The reference movie should be light enough to play smoothly and clear enough to judge sync. Burn in the picture version, source timecode and frame rate where they remain visible without covering faces or subtitles. Include a two-pop or another agreed sync event when the production uses one. The movie's scratch track is useful for locating errors, but the separate stereo reference mix should be the sonic authority.

Open the movie outside the editing system before delivery. Confirm the first frame, final frame, burn-in, audio playback and duration. A movie with the correct filename but an older cut can waste more time than a broken AAF. The technical files look healthy while every creative decision is compared against the wrong picture.

Print critical sounds without destroying editability

For each irreplaceable Logic sound, decide whether the receiver needs a processed print, a clean source or both. A tuned vocal may need the approved tuned print plus the original production audio. A software instrument may need a full-length stereo print and, when later rebalancing is expected, sensible stems. A tempo-synced delay may need a wet print with its full tail. Label every version so the receiver doesn't have to audition mystery duplicates.

Start printed files at a shared project position when practical. That makes manual recovery possible if the AAF structure fails. Preserve handles or full-length files when the editor will change cuts. Do not normalize, limit or sample-rate-convert the prints unless the turnover specification calls for it.

Write the receiver report while the export is fresh

A short plain-text note should state the source application and version, picture version, sample rate, bit depth, frame rate, sequence start, media method, handle length, printed tracks and known exceptions. Record whether volume automation and fades passed the test. Name the person who approved the test import and the date it was checked.

This isn't paperwork for its own sake. It prevents the next engineer from guessing which information was expected to travel in AAF, and which choices were deliberately rendered to audio.

• 01_AAF: the interchange file;
• 02_Audio: separate media or printed tracks;
• 03_Picture: reference movie with timecode burn-in;
• 04_Reference: stereo guide mix and optional split references;
• 05_Docs: track sheet, settings, known exceptions and contact information.

Use the same version string on the AAF, movie, mix and note. A beautiful folder structure can't repair a picture mismatch, but it can stop one from being mistaken for the current turnover.

Frequently asked questions

What transfers from Logic Pro in an AAF?

Apple says used regions, track and position references, and volume automation are included. Verify the result in the destination and print Logic-specific instruments, plug-ins and routing separately.

Can Logic Pro import an AAF from Premiere Pro?

Logic can import AAF, but Adobe says Premiere AAF is tested with Avid Media Composer and Pro Tools, not other importers. Run a representative test before the full Premiere-to-Logic turnover.

Can Pro Tools open an AAF exported from Logic Pro?

AAF is a standard Pro Tools interchange route, but the receiving mixer should test region placement, channelization, fades, automation and media before work begins.

Do Logic Pro plug-ins transfer through AAF?

Do not expect plug-in chains, software instruments or complex routing to rebuild in another DAW. Print defining sounds and document what was rendered.

Should AAF audio be embedded or separate?

Use the receiver's specification. Embedded is compact to deliver; separate media is easier to inspect, relink and replace. Test large or complex turnovers either way.

Why send a reference mix with the AAF?

It proves the intended sync, edits, levels and creative processing. The receiver can compare the reconstructed timeline against a known playback result.

AAF handoff checklist

• The destination app, sample rate, bit depth, frame rate and start time are written down.
• Track names are readable and obsolete material is excluded.
• Logic-only or creatively essential processing is printed.
• The AAF media choice and handle length match the receiver's request.
• The reference movie and mix use the same picture version.
• A representative test AAF has been imported by the receiver.
• The final package has been opened from a separate local folder.
• Known translation limits are recorded instead of hidden.

Continue through the Logic Pro Recording & Editing hub for project organization, editing and delivery workflows.