At a glance: Handles are extra audio kept beyond each clip's cut points when an AAF is exported, invisible on the picture editor's timeline and essential on the audio side, where every fade, crossfade and room tone fill is built from them. There is no standard length: published specifications range from 50 frames to a full minute, with ten seconds the safest default when nobody tells you otherwise. The setting is off or hidden by default in every major NLE, it is specified in frames rather than seconds in most of them, and a handle can never be longer than the source recording actually contains. This guide covers what handles are for, the frames and seconds arithmetic per frame rate, and where each application hides the switch.
A clip on your timeline ends exactly where you cut it. The question handles answer is what happens to the audio beyond that point when the edit leaves your NLE.
With handles, each exported clip carries extra source audio past both cut points, so the person mixing can open the edit up. Without them, every clip ends at the frame you trimmed to, and the mix inherits your edit as a set of hard walls. Nothing about the cut looks different in either case, which is why the setting gets missed: the cost is invisible until someone downstream reaches for material that is not there.
What the Audio Side Actually Does With a Handle
Four operations consume handles, and they account for most of what dialogue editing physically is.
Crossfades and smoothing. A cut between two takes almost always needs a fade across it, and a fade needs material on both sides of the cut point. A clip with no handle cannot be faded, only butted, and a butted dialogue edit is audible.
Room tone. The quiet stretches between lines carry the sound of the room, and the dialogue editor extends and loops that tone to fill holes. The usable tone often sits well away from the cut, which is the case that justifies long handles: ten seconds of handle exists so tone can be pulled from a pause nowhere near the edit.
Overlaps and perspective. Reaction breaths, the tail of a line under a cut, a door that closes just after the trim point. The material either side of your edit is frequently the material the sound editor wants.
Fixing the edit itself. Where a cut lands badly for sound, a frame or two of slip fixes it, and slipping needs somewhere to slip to.
None of this changes your cut. Handles are read from the source files at export time; your timeline stays exactly as you built it.
Why the Published Numbers Disagree So Much
Ask what the standard handle length is and the published answers refuse to converge. In Production Expert's April 2024 panel of seven audio professionals, checked August 2026, one asks for 75 frame handles and another for 125. A dubbing mixer answering the same question on Creative COW recommends 50 frames as a default. A sound editor's guide for picture editors on DVXuser specifies 240 frames. Henri Rapp's delivery guide asks for a minimum of five seconds and prefers ten, the Austin facility Soundcrafter publishes six seconds, Production Expert's own DaVinci Resolve export guide suggests six to ten, and in an Avid Community thread a working editor requests a full minute on both sides. All checked August 2026.
The spread is not confusion. The number depends on what the receiving team intends to do, and different work needs different amounts. Two seconds covers fades and small slips. Five to ten covers serious dialogue editing, where room tone gets hunted well away from the cut. A minute is what someone asks for when they expect to rebuild scenes, and they are implicitly accepting the file size that comes with it. Nobody is wrong; they are describing different jobs.
Which is why the only reliable answer is the one the delivery spec conversation produces: ask the person receiving the file. If you cannot ask, ten seconds costs little at export and covers every ordinary case.
The Frames and Seconds Arithmetic
Most NLEs take the handle value in frames, most humans think in seconds, and the conversion depends on the frame rate. This is where a spec gets silently halved: 50 frames is two seconds at 25 fps and well under two seconds of protection at 29.97.
| Handle | At 24 fps | At 25 fps | At 29.97 fps |
|---|---|---|---|
| 2 seconds | 48 frames | 50 frames | 60 frames |
| 5 seconds | 120 frames | 125 frames | 150 frames |
| 10 seconds | 240 frames | 250 frames | 300 frames |
At 23.976 the frame counts match the 24 fps column, because the values are timecode seconds rather than wall clock seconds. When a spec arrives in frames, convert it at your project's frame rate before assuming it matches your idea of a second.
Where Each NLE Hides the Setting
No major NLE ships with useful handles on by default, and in three of the four the control is gated behind another setting entirely.
| NLE | Where the setting lives | The trap |
|---|---|---|
| Avid Media Composer | Export As AAF, handle length field | Off by default; must be set explicitly on every export preset |
| Adobe Premiere Pro | AAF export dialog, handle frames field | The field stays inactive until Render is set to trim audio files rather than copy complete files |
| DaVinci Resolve | Deliver page, add handles | It historically sat only under the Video panel even though it governs audio; recent versions show it in both, which is why it gets missed |
| Final Cut Pro, via X2Pro | X2Pro preferences, handle length | The LE edition does not trim at all, and when trimming fails the whole source clip goes in silently |
Two of these deserve a sentence more. The Premiere gate is documented in a Creative COW thread where a dubbing mixer walks an editor through it, checked August 2026: with Render on copy complete audio files, handles are meaningless because every clip already carries its entire source file, and the handles field only wakes up in trim mode. And the X2Pro behaviour, described on Marquis Broadcast's own support forum, checked August 2026, cuts the other way: when the tool cannot trim, it embeds the whole original clip rather than failing, so the AAF works but balloons. The per application export settings are covered in our guides for Premiere, DaVinci Resolve and Final Cut Pro.
The Two Limits Nobody Mentions
A handle cannot contain audio that was never recorded. The handle is read from the source file, so it can only be as long as the material either side of your cut actually is. A take where the director called cut a beat after the line has a short tail whatever your export setting says, and a clip trimmed from a longer take has whatever that take holds. This is also why handles do not rescue an edit built from clips with no air around them, which is a cutting decision covered in our guide to editing for sound.
Handles cost file size, and the cost scales with the number. Every second of handle on every clip is real audio embedded in the AAF. On a normal programme at ten seconds the file stays perfectly manageable. At the extremes it does not: in the Avid Community thread cited above, an export with one minute handles embedded came out around 4 GB. That is the trade the minute-long spec accepts, and it is worth knowing it is a trade rather than a malfunction.
A related symptom runs the other way. An AAF that comes out suspiciously small, a few megabytes for an hour of material, almost always means the media was linked rather than embedded, and the handles question is moot because the audio itself is not in the file.
Checking What Actually Went Into the File
The export dialog tells you what you asked for. It does not tell you what you got, and the failure modes above, the inactive Premiere field, the wrong Resolve panel, a trim that silently fell back to full clips, all produce a file that looks fine from the NLE side. This is the gap the AAF Checker exists for, and it sits exactly between your export and your send.
The free AAF Checker reads the file you are about to send and reports what a Pro Tools import will find: whether the media is embedded and readable, the sample rate, the frame rate and the timecode. It takes seconds and needs no account. What it does not do is judge your handle length; whether two seconds or ten is right for this delivery is between you and your mixer, and the four questions worth asking them are one conversation long.
Frequently Asked Questions
How long should audio handles be?
Ask the person receiving the file, because published specs run from 50 frames to a full minute and the right answer depends on the work they plan to do. If you cannot ask, ten seconds is the safe default: it covers fades, slips and room tone hunting, at a file size cost most projects never notice.
What are handles in an AAF export?
Extra source audio kept beyond each clip's cut points, invisible in your edit and available to the audio team for fades, room tone and edit fixes. Without them every clip ends exactly at your trim point and the mix cannot open anything up.
Why does my AAF have no handles even though I set a value?
Usually one of the per NLE gates. In Premiere the handles field does nothing until Render is set to trim audio files. In Resolve the setting historically sat under the Video panel of the Deliver page even for an audio-only AAF, and recent versions show it in the Audio panel too, so set it and check it in both. Re-export with the right gate open rather than raising the number.
Why is my AAF so large?
Embedded media times handle length. Every second of handle on every clip is audio inside the file, so long handles on a long programme multiply quickly, and a trim that silently failed can embed entire source clips. Large is usually correct behaviour; suspiciously small is the one to worry about, because it means the media was linked rather than embedded.
Can handles be added after the AAF is exported?
No. Handles are read from the source files at export time, so the only fix for a delivery without them is a re-export from the original project with the setting active.
Do handles work on material that was cut tight in the original recording?
Only up to what the recording contains. A handle cannot be longer than the source take, so a line recorded with no air around it delivers short handles regardless of the export setting.
The AAF Checker reads any AAF and reports what a Pro Tools import will find, before you send it. Free for macOS at forte-ai.com/aaf-checker.
