Find AAF turnover risks before the handoff.
AAF Preflight inspects the structure and metadata visible inside an uploaded AAF. It separates passed checks, warnings, failures, and items that cannot be verified from the AAF alone so an assistant editor knows what deserves attention.
What AAF Preflight checks
The preflight confirms that a supported top-level timeline can be read and identifies the exporting application when that information is available. It reviews source references, timeline structures, empty or filler-only tracks, source filenames, source and record timecode, and visible video or audio format metadata.
Warnings call attention to mixed formats and other conditions that may be valid creatively but deserve review before turnover. The checklist is deliberately compact so the significant exceptions do not disappear inside a long technical dump.
What an AAF cannot prove
An AAF can carry locator text and media references, but it cannot prove that an external drive is mounted, a referenced file exists, media is online, or the picture and sound play correctly. AAF Ledgers labels these checks as not verifiable instead of guessing.
Preflight also cannot replace watching the sequence, checking a reference export, or importing the turnover into the destination application. It is an additional inspection step that helps teams focus their manual review.
Use preflight with a turnover checklist
Run Preflight before delivering an AAF, then review the warnings alongside the production’s normal handoff requirements. Confirm sequence version, frame rate, raster, start timecode, track layout, handles, reference picture, destination settings, and the actual media package outside AAF Ledgers.
- Resolve failed structural checks before delivery.
- Review warnings against the intended creative timeline.
- Confirm external media separately.
- Download the report while the seven-day reporting window is active.
AAF workflow questions
Does a passed preflight guarantee the AAF will import?
No. It confirms the checks AAF Ledgers can perform from the uploaded file. Destination software versions, external media, plug-ins, effects, and local system conditions can still affect an import.
Why are some checks marked not verifiable?
AAF Ledgers avoids treating locator text as proof that media exists or is playable. Checks that require the external media or destination system remain explicitly unverified.
Can Preflight inspect both picture and sound tracks?
Yes. A user can select automatic, video, audio, or combined track reporting when processing the AAF.
Turn your next AAF into a report your team can review.
Invited teams can test the complete private workflow with no card required.