Importing an AAF into Pro Tools takes about 30 seconds once you know what you are doing. The problem is that 30 seconds of clicking can set you up for two hours of cleanup if you did not set things up correctly on either end of the handoff.
The session you get after a raw AAF import is organized around the picture editor's workflow. Their clip names reflect their edit decisions, not your audio types. Their track layout reflects their timeline, not your routing template. Getting from that to a session that is ready for a dialogue editor or re-recording mixer is where the real work lives, and a lot of that work is preventable if you know what to ask for before the file is exported.
This guide covers the full import process: the NLE-specific export settings that affect what arrives, the actual Pro Tools import steps, what to verify immediately after, the most common problems you will run into and why they happen, and what still needs to happen after the import is technically complete.
What You Need Before You Import an AAF
The Pre-Import Checklist
Getting these questions answered before the AAF lands saves time that would otherwise be spent diagnosing problems after import.
Which NLE was used, and which version? The way Avid Media Composer generates an AAF is fundamentally different from how Adobe Premiere does it. Which version of Premiere matters too, because stereo handling behavior has changed across releases. The answer to this question tells you what to expect when the file arrives.
Are handles included? Handles are the extra audio before and after each edited clip. Without them, dialogue editors have nothing to work with at edit points. The professional standard is a minimum of two seconds and ideally ten. If handles are not included by default in the editor's export settings, they need to be requested explicitly. Finding out handles are missing after import, when the edit is already loaded and locked, is avoidable.
What stereo delivery format was used? This is especially important for Premiere-originated AAFs. The question is whether stereo files are being delivered as interleaved stereo or as split mono pairs. If split mono is coming, you can prepare. If it surprises you after import, the fix requires time you did not budget.
What timecode convention applies? On commercial work, a single delivery batch can contain multiple AAFs with different timecode references mixed together: two-pop, slate, first frame of action. A re-recording mixer in New York regularly receives 10 to 15 AAFs arriving ten minutes before the session starts, each with its own QuickTime reference. Knowing upfront which convention to expect across a batch prevents alignment problems that are genuinely painful to trace after the fact.
Is an EDL available? An Edit Decision List is a separate metadata file that carries information about the edit. When AAF metadata is corrupted or missing, which happens often enough to plan for it, the EDL is the fallback for understanding what picture editorial actually intended. Worth requesting even if you expect not to need it.
NLE Export Settings That Affect Your Import
The behavior of an AAF depends significantly on which application generated it. Here is how the four major NLEs differ, and what settings to confirm before the file is handed off.
A Closer Look at Premiere's Stereo Problem
Premiere's split mono behavior is worth understanding in detail because it affects a significant portion of commercial and corporate AAF workflows.
When Premiere exports stereo content, it does not always deliver a single interleaved stereo file. Instead, it frequently creates a combination of Audio 1 (mono) and Audio 1.L / Audio 1.R on the same named track, depending on how the original clips were captured or structured in the timeline. The result in Pro Tools is a session where mono clips and split stereo pairs are visually indistinguishable until you start auditing them individually.
An independent producer in the Pacific Northwest described this as his daily reality: "I spend a significant amount of time deconstructing, splitting, fixing, and re-interleaving audio before I can even begin mixing." That is time on every project, for work that has nothing to do with the quality of the mix.
The fix requires detecting which files are genuine stereo, which are dual-mono (two identical mono channels), and which are true split pairs that need re-interleaving. It can be done manually. It takes time. It is the most predictable, most avoidable problem in the Premiere-to-Pro Tools pipeline if you know it is coming.
How to Import an AAF into Pro Tools: The Steps
Step 1: Open Your Template Session First
Do not import into a blank Pro Tools session. Import into your facility template session. Your template is the target structure: the folder tracks, routing, bus assignments, I/O, and color coding that define how content should be organized. Starting with a blank session means rebuilding all of that after the fact, which takes longer and introduces more room for error than importing into a structure that already exists.
If you do not have a template session, this is worth building before you do anything else. A proper post production Pro Tools template includes dialogue tracks routed to a dialogue bus, ADR tracks separate from production sound, SFX tracks grouped by type (hard effects, ambience, PFX), music tracks on stereo tracks routed to a music bus, and folder tracks that group related content and feed the correct stems. Every project that uses the template recovers that initial build investment instantly.
Step 2: Go to File > Import > Session Data
This is Pro Tools' import path for AAF files. Not File > Open, which would open the AAF as a new session rather than bringing it into your current session.
Step 3: Configure the Import Options
The import dialog gives you several decisions. These are the ones that matter most:
Audio Media Options: Set this to "Copy from Source Media." This copies all audio files into the session's Audio Files folder, making the session self-contained and portable. Leaving it set to "Link to Source Media" creates a dependency on wherever the original media files are stored. At any facility where storage locations change between projects, this is a risk worth eliminating at import time.
Sample Rate: Verify before confirming. A mismatch between the AAF's sample rate and your session's sample rate will cause timing and pitch issues that are immediately obvious but sometimes attributed to other problems before the source is found.
Import Options: Check what you are bringing in. Pro Tools will ask what session data to import. For an AAF import into an existing template, you generally want audio clips and regions. Be careful about importing routing or I/O assignments from the AAF if you want to preserve your template's routing intact.
Handle Length: Confirm this is set correctly. If handles were included in the export, you should see them in the imported clips. If they appear to be missing or shorter than expected, flag it before starting any organization work.
Step 4: Click Import and Wait
For most projects, import completes quickly. For large sessions with many tracks or external media that needs to be located and copied, it can take several minutes. Do not interrupt the process.
Step 5: Verify Playback Before Doing Anything Else
The moment the session loads, scrub through the timeline. All clips should play back. Timecode should land where you expect it. Handles should be audible at edit points. Video reference, if included, should be in sync. This five-minute verification step catches problems before you have spent an hour organizing a session with corrupt or misaligned media.
AAF Import Settings That Are Frequently Misunderstood
Beyond the main dialog, a few settings trip up even experienced engineers:
"Copy from Source Media" vs. "Link to Source Media" is the most consequential setting in the import dialog. Link keeps the session pointing to original media wherever it lives. Copy brings everything into the session folder. For any facility where storage locations are not guaranteed to be stable, or where sessions are handed off between engineers or rooms, Copy is the correct choice.
Import into existing tracks vs. new tracks. Pro Tools gives you the option to import AAF content into the existing tracks in your template or to create new tracks. Importing into existing tracks requires that the incoming content matches your template's track structure, which is unlikely with a raw AAF. Creating new tracks is the more reliable starting point, even though it means the organization work described below still needs to happen.
Video import. The video reference from the AAF can be imported alongside the audio. Whether to do this depends on your facility's workflow and whether the video codec is already in a format Pro Tools handles efficiently. Importing a high-res QuickTime directly can slow the session. If video needs to be transcoded for playback, do that before importing.
Common AAF Import Problems and How to Fix Them
Importing Multiple AAFs: The Commercial Scenario
Standard Pro Tools AAF import handles one file at a time. For most long-form work, that is fine. For commercial audio post, it is the primary bottleneck.
A producer from our user interviews described the scenario that repeats regularly with 10 to 15 AAFs arriving 10 minutes before the session, each representing a different deliverable length (60s, 30s, 15s, 6s) from the same campaign. Each one has its own QuickTime reference. Timecode conventions are mixed: some use two-pop, some use first frame of action, some use slate. Pro Tools loads them one at a time.
The challenge at that scale is not just organizational. It is positional. Each deliverable needs to land at a specific timeline position, not just be loaded sequentially. A 60s spot might open at 1:00:00:00, the 30s version at 1:07:00:00, the 15s cut at 1:14:00:00. Those positions are deliberate and affect downstream delivery. Getting each one into the right location while maintaining the correct timecode alignment for each version is a task that requires either meticulous manual placement or a tool that can handle deliberate offsets rather than just sequential loading.
An independent mixer who works on multi-video campaigns, described the same need from a different angle as he often works on campaigns with multiple videos that must sound identical, so he puts them into a single Pro Tools session for continuity, same timeline, same bus processing, same reverbs. The layout is intentional. The positions are not arbitrary.
After Import: What the Session Still Needs
Importing the AAF is step one. The session that is now in Pro Tools is a starting point, not a finished state. What it still requires depends on the project, but the consistent work across facilities includes:
Clip-level sorting. Content types are scattered across the session because the picture editor organized by edit decisions, not audio function. Dialogue lives on SFX tracks. Music lands in unexpected places. Sorting requires assessing each clip individually and moving it to the correct position in your template. Scripts that parse track names do not solve this because the names are not reliable. You need to understand what is on each clip.
Stereo/mono resolution. Before routing anything, the stereo content needs to be correctly identified and placed. Split stereo pairs need to be re-interleaved. Dual-mono needs to be identified and handled. This step comes before template alignment, not after it.
Template alignment. Once content is sorted and stereo is resolved, everything needs to be mapped to the facility routing template. Folder tracks, bus assignments, color coding, I/O. The template tracks stay intact. Content is placed inside them. This is where most of the time goes in manual prep work.
Routing verification. Before any mix work begins, trace every signal path. Print tracks, stems, buses. It takes minutes to verify and can save significant time if a routing error is found before the session is in use.
Safety copy. Preserve an untouched version of the session as it arrived from picture editorial, alongside the organized working version. This is the anchor for revision rounds and the answer to "what did editorial actually send?" when something needs to be traced back to the source. Every professional who contributed to fPost's development named this independently. It should be automatic.
Automating the Post-Import Work
The import mechanics described above are consistent and teachable. The post-import organization work is where genuine expertise and significant time both live.
fPost automates the post-import layer. Rather than reading track names to classify content, it uses AI-R content detection to analyze the audio in each clip directly and identify what it is — dialogue, music, or SFX, the three categories AI-R currently detects. It then applies that classification against your open Pro Tools template, placing clips into the correct locations automatically. Stereo handling, including Premiere split mono detection and re-interleaving, is built into the process. A safety copy is preserved without a manual step.
An independent post mixer described his dream goal isn't just 'import an AAF.' It's drag and drop a delivery and immediately get a session that's ready to work. That is what fPost is built toward.
Frequently Asked Questions
How do I import an AAF into Pro Tools?
Go to File > Import > Session Data, select your AAF file, set Audio Media Options to "Copy from Source Media," verify the sample rate, and confirm the import. Import into your facility template session rather than a blank session so the routing structure is already in place when content arrives.
Why does my AAF import show Media Offline errors?
This usually means Pro Tools is looking for audio files that have moved since the AAF was created, or that the import was set to "Link to Source Media" rather than "Copy from Source Media." Use Clip > Relink to locate the files manually, or re-import with the copy option enabled.
Why are my AAF tracks named Audio 1, Audio 2, Audio 3?
This is normal and expected from many NLE exports, particularly Adobe Premiere. The picture editor either did not name tracks or their NLE defaults to generic names. This is the starting point for clip-level sorting after import, not a sign that something went wrong.
How do I fix split mono from a Premiere AAF?
Identify which clips are genuine stereo pairs that were split on export (Audio 1.L and Audio 1.R from the same source), then re-interleave them into a single stereo file. Separately, identify any dual-mono clips where both channels carry identical audio.
Can Pro Tools import multiple AAFs at once?
Pro Tools imports one AAF at a time. For commercial workflows that require loading multiple deliverables into specific timeline positions, that limitation requires either manually placing each import or using a tool designed to handle multi-AAF workflows with deliberate position offsets.
What is the difference between importing an AAF with "Copy" versus "Link"?
"Copy from Source Media" brings all audio files into the session's Audio Files folder, making the session self-contained. "Link to Source Media" keeps the session pointing to wherever the original media files are stored. Copy is almost always the better choice for professional post work, where sessions need to be portable and not dependent on a specific storage path.
What do I do if my AAF does not import correctly from DaVinci Resolve?
Resolve produces the least consistent AAF exports of the major NLEs. If audio is missing, references are broken, or metadata is absent, the most reliable workaround is to export an XML from Resolve and convert it to AAF using a compatible bridge tool, then import from that. Alternatively, request that picture editorial export from a more reliable AAF source if the project allows it.
How long should handles be in an AAF?
A minimum of two seconds is the baseline. Ten seconds is the professional standard for anything that will go through serious dialogue editing. If handles are missing or under two seconds, request a re-export. Finding out at import is the best time, not halfway through the edit.
For facilities looking to reduce the time between AAF import and creative work, fPost automates the clip classification and template alignment steps that follow every import. More at forte-ai.com/fpost.
.png)
