M4A audio export — Delivery workflow

Worked example

Deliver an M4A as a named, versioned file with the master kept beside it, and check that the receiving app or platform accepts the format.

The downloaded name follows the source with the mode added, for example voiceover-m4a.m4a. Rename it before sending, with a version and bitrate: voiceover_v3_192k.m4a. When an editor opens a folder of twenty clips, a name like that tells them which one is the approved take and which settings it used.

M4A plays natively on Apple devices, most Android phones and many web players, and many podcast and video hosts accept it, but not every system does. Before you upload, read the destination current guide for accepted formats and the maximum file size. A common mistake is assuming that every platform takes M4A just because the phone does.

For a hand-off to a video editor, a 48 kHz setting keeps the sample rate aligned with typical video projects, while a plain listening copy can stay at the source rate. If the recipient needs lossless audio or cannot decode AAC, send WAV instead and say why in the message.

Repeatability matters when you export every week. Write down your chosen bitrate, sample rate and channels once, for instance 192 kbps, keep source, stereo, and check the first and last ten seconds of each file before it leaves your machine. If the recipient reports a problem, ask which app or device opened the file before re-exporting.

Accessible source audio

M4A export

Keep the original source until the client has confirmed the M4A works, because a re-encode cannot be undone.