Skip to main content
← Answers Hub
Answer

What Formats Does Export Flow Support?

Export Flow reads WAV, AIFF, MP3, FLAC and M4A, and renders to WAV 24-bit at 48k or 44.1k, WAV 16-bit at 44.1k, or MP3 320. It embeds metadata and applies your naming and folder structure. Preflight checks names and metadata, not the audio itself.

What Formats Does Export Flow Support?

Direct answer: Export Flow reads WAV, AIFF, MP3, FLAC and M4A, and renders to one of four targets: WAV 24-bit/48k, WAV 24-bit/44.1k, WAV 16-bit/44.1k, or MP3 320. It embeds the metadata a client requires and applies their naming template and folder recipe. AAC is not supported in either direction.

Worth knowing up front: preflight validates names, metadata and collisions — it never opens the audio, so there are no loudness, true-peak or clipping checks.

What Export Flow reads and targets

Accepted inputs.wav · .aif / .aiff · .mp3 · .flac · .m4a
Delivery profile targetsWAV 24-bit/48k · WAV 24-bit/44.1k · WAV 16-bit/44.1k · MP3 320
Not supportedAAC, in either direction

If you have seen AAC listed for Export Flow anywhere, that was wrong and this page is the correction.

Key Shift Pro reads WAV and AIFF and writes WAV and MP3 — it renders and converts the pitched output in the same pass it names and organises it.

What runs at export time

  • Rendering to the target format — WAV via Apple’s native audio engine, MP3 320 via a bundled encoder
  • Metadata embedding — the fields the client’s profile marks as required
  • Naming templates and folder recipes, with live preview before you commit
  • Filename parsing that infers track, mix type, version, BPM and key
  • Required-deliverable checklists — full mix, alt mix, instrumental, no drums, TV mix, stems
  • Preflight — duplicate outputs, illegal characters, missing required fields
  • Delivery to Dropbox or Google Drive, with the result recorded in the delivery ledger

What preflight does not check

This is the honest boundary, and it matters if you are relying on it as a last line of defence. Preflight validates strings and structure, not sound. It does not check:

Loudness / LUFSNot analysed. The engine ships without loudness analysis.
True peak or clippingNot detected
Sample rate or bit depth of the sourceNot verified against the target
DurationNot checked
Whether the file playsNot opened

If a library specifies −14 LUFS integrated, Export Flow will render, name and deliver a file that misses it without complaint. Check loudness in your DAW or metering chain before you hand off.

Which format should you send?

Send WAV unless the recipient asks for something else. Music libraries, publishers and post houses almost always specify uncompressed audio, and WAV is the least likely to be rejected on technical grounds. 24-bit/48k is the most common professional target; 16-bit/44.1k is what you use when a client specifically asks for CD spec.

Use MP3 only for review copies — the version a client listens to on their phone to approve a direction. Sending a lossy file as a final master is exactly the delivery mistake Export Flow exists to prevent.

Set the target on the client’s delivery profile and Export Flow renders to it — you do not need to bounce a separate version per destination.

Format is only half of a delivery spec

A format on its own does not make a file deliverable. The same brief usually also specifies sample rate, bit depth, naming convention and required metadata — and a WAV that is correct in format but wrong in naming still gets bounced.

That is the part Export Flow does today: naming rules come from the client’s profile, required deliverables and metadata fields are checked against their spec, and preflight runs before anything leaves your machine. What it will not yet do is write the metadata into the file for you.

Frequently asked

Does Export Flow support AAC?

No. AAC is not accepted as an input and cannot be produced as an output. Accepted inputs are WAV, AIFF, MP3, FLAC and M4A.

Can Export Flow convert my file to another format?

Yes. It renders to WAV at 24-bit/48k, 24-bit/44.1k or 16-bit/44.1k, or to MP3 320 — whichever the client’s delivery profile specifies.

Does Export Flow write metadata into my files?

Yes. The fields a client’s profile marks as required are embedded into the rendered file at export time, and preflight flags any that are missing before you deliver.

What formats does Key Shift Pro accept?

WAV and AIFF, and it writes WAV and MP3. It reads uncompressed sources because pitch-shifting operates on uncompressed audio, then converts the output for delivery.

What sample rates and bit depths can I deliver?

Delivery profiles target 24-bit at 48 kHz, 24-bit at 44.1 kHz, or 16-bit at 44.1 kHz. MP3 320 is available as a profile target for reference copies.

Authority hubs

Next step

Ready to put this into practice?

Kora is the system this path is built around.

A project-lifecycle platform purpose-built for music workflows — project tracking, delivery validation, and client relationship continuity in one place.