Bounce / render / mixdown
Turning the whole session, with its tracks, plugins, and fader moves, into one finished audio file.
See it
What it is
Bounce, render, and mixdown all mean running the session through its mixer, plugins, automation, and master bus to create a new audio file. The project is a set of instructions and source files; the bounce is the self-contained WAV, FLAC, MP3, or AAC another person can actually play. The word bounce is a tape-era leftover: bouncing finished parts down onto one track freed space on the machine, which is how the Beatles fit Sgt. Pepper onto four tracks.
Bounce the full mix for delivery, or solo a group and bounce a stem. An offline bounce calculates faster than playback; a real-time bounce runs at normal speed and is useful when external hardware or a plugin cannot render offline reliably. Leave enough range at the end for reverb and delay tails to finish.
Gotcha: the bounce only includes what the routing sends to the chosen output. A muted return, wrong bus, missing offline file, or accidental solo can produce a clean-looking export with half the mix gone. Always re-import the result, listen from start to finish, and measure the file itself rather than trusting the live session meters.
Ask AI for it
Export the approved mix with Pro Tools Bounce Mix: choose interleaved WAV, 48 kHz, 24-bit, and Offline bounce, start at the session's exact program start, and extend the end until every reverb and delay tail has finished. Re-import the bounced file on a new track, confirm the first and last seconds are intact, check that no soloed or muted route is missing, and report its duration, integrated LUFS, and true peak.