From AAF to mix-ready.
Automatically.

Yes. fPost automates Pro Tools session prep end to end: its on-device AI-R engine detects the content of each clip, matches your own Pro Tools session template, and returns a session that is named and organized, ready to mix. It works from an AAF or an existing PTX session.

fPost supports AAF files exported from Avid Media Composer, Pro Tools, Adobe Premiere Pro and DaVinci Resolve. Final Cut Pro does not export AAF directly, so it is not supported natively, but a short guide shows how to convert a Final Cut export into an AAF for use with fPost.

Everything that Pro Tools can carry in an AAF survives: fades and crossfades, automation, clip names, and supported plugins and effects are all preserved. Track folder grouping does not come across, because the AAF format does not support it. fPost preserves what is there and never alters the original files.

No. fPost never writes to your original AAF or media. It extracts the AAF and media information temporarily into a local folder purely to analyze it, then builds a new Pro Tools session, so your handoff files stay untouched and you can re-run an import safely.

fPost converts the sample rate so your audio plays back at the correct pitch and speed in your session. Video frame rates are kept as they are, not changed. Matching your session to the source still avoids surprises, but a sample-rate mismatch will not silently push your audio out of sync.

fPost Studio classifies clips into the macro categories dialogue, music and sound effects and lands them in your template. Suite adds deeper recognition down to micro categories such as sync dialogue, instrumental music and foley, plus multi-AAF import, splitting one AAF across sessions and per-clip metadata. Suite launched in July 2026.

fPost places clips using on-device content recognition, not brittle track-name matching. The AI-R engine classifies each clip by what it actually contains and lands it in the correct folder and name within your template, so missing or inconsistent names from the editor do not break the prep.

Studio covers AAF import, session reorganization, template matching, naming, macro-category recognition and standard support. Suite adds micro-category recognition, multi-AAF import, split-across-sessions, per-clip metadata, 24-hour priority support and fully offline use. Both are one seat and sold monthly, yearly or as a Lifetime license: Studio EUR 49/month, EUR 288/year or EUR 1,199 once; Suite EUR 59/month, EUR 348/year or EUR 1,399 once. Enterprise adds floating licenses, a license server, an SLA and volume pricing.

No. Your plan, its price and your renewal date stay exactly as they are. You can see them, and download fPost, in your user area.

Your audio stays private on every plan: fPost processes everything on-device through the AI-R engine, so nothing is uploaded. Working fully offline, air-gapped rooms included, is part of fPost Suite and Suite Lifetime; Studio connects to the internet to verify your license. This suits facilities handling embargoed film and TV under NDA.

fPost requires Pro Tools 2024.3 or later and macOS 13.5 or later. There is a single installer that runs on both Apple Silicon and Intel Macs, so you do not need to pick a build. fPost Suite also works fully offline.

Yes. fPost has a 7-day free trial with no credit card. It starts at your first in-product sign-in and expires on its own with no auto-charge; add a card later only to buy. Before importing, the free AAF Checker lets you confirm an AAF will import cleanly at no cost.