Audio fades — Delivery workflow

Worked example

Fade last.

A reliable order is trim, then adjust volume, then fade, because trimming after a fade moves the ramps into the wrong place and a volume change before a fade keeps them smooth. Keep each step as a separate named file such as intro-trim.wav and intro-fade.mp3.

Pick the export to match the next stop. If a video editor will place the clip under a voiceover, send WAV so they can re-fade it on their own timeline; if the clip goes straight onto a podcast feed, a 192 kbps MP3 is plenty.

Imagine a café podcast with a 12-second theme: fade 0.5 seconds in, then use a 2-second fade for the closing 10-second outro. Write those two values into a short checklist so every new episode starts from the same recipe.

A common mistake is adding a fade here and a second fade in the editor, which makes the start disappear twice. Decide where the fade lives, and tell the person receiving the file whether it is already baked in.

A fade also stops a clip from looping smoothly, because the loop point becomes a dip in volume. If the audio must repeat in a game or on a shop display, deliver an unfaded copy for looping and a faded copy for one-shot use. Add the fade length to the file name too.

Clip with abrupt boundary

Gradual level transition

Keep an unfaded master; a faded file cannot be turned back into one with a longer or shorter ramp.