Guide · Mix preparation
Export a mix for mastering
Keep your mix intact before shaping the master. Check the file, not only your session.
Published 20 Nov 2026
Start with the destination’s requirements
Your premaster is the finished mix you export before mastering. A bounce is that exported audio file, with your session’s mixing decisions included. Ask your mastering engineer or check your chosen tool’s accepted input settings first. File format, sample rate, bit depth and headroom requirements can differ.
This checklist draws on Waves’ mix-preparation guide and iZotope’s mixing tips for better masters. We checked both official sources on 20 Nov 2026. Their recommendations are starting points, not identical requirements for every destination.
Choose a stereo, lossless export
Stereo means left and right channels. For ordinary stereo mastering, export your complete mix rather than individual instrument tracks. iZotope recommends stereo WAV unless you are delivering stems: grouped parts for a different workflow. A stereo interleaved WAV stores both channels in one file. Use that when your destination accepts it; follow any request for separate left and right files.
Avoid making MP3 or M4A your preparation copy when a lossless export is available. Lossy encoding discards audio information; converting that file to WAV cannot restore it. Keep your session and original bounce so you can revise without another lossy conversion.
Keep the session’s sample rate
Sample rate counts audio samples per second; 48 kHz means 48,000 samples per second. iZotope recommends keeping your mix session’s native sample rate for delivery. Do not upsample merely to make the number bigger. If your session uses 48 kHz, keep 48 kHz unless your destination requires something else.
Bit depth describes sample precision, not loudness. iZotope suggests 24-bit or 32-bit floating-point exports as preparation formats. These are recommendations, not a promise that every mastering tool accepts both. Choose the recipient’s supported format; do not assume BRIDGE ONE accepts every WAV encoding. A higher-bit-depth export cannot recover detail already lost in an earlier file.
Separate clipping from headroom
Headroom is the level margin below the maximum your signal or destination can handle. Clipping happens when a stage exceeds its capacity and cuts off peaks. Leave your destination’s requested margin, and inspect your loudest section before bouncing. There is no universal requirement to peak at −6 dBFS. dBFS measures level relative to digital full scale.
Waves gives peak guidance specifically for its own online mastering service. iZotope says headroom requirements vary between engineers. Neither makes one number mandatory for every mix. Lowering the final output can prevent new fixed-point export clipping. It does not reliably repair distortion already created inside a track or plugin. Find an overloaded stage before exporting again.
Do not automatically remove every mix-bus effect: processing applied across your whole mix. iZotope distinguishes intentional mix processing from limiting that restricts mastering options. Discuss loudness-only limiting with your engineer, and label any limited reference separately. Keep a saved version before changing the chain.
Dither depends on the export
Dither adds very quiet noise to reduce distortion from rounding samples during bit-depth reduction. It is not a loudness boost or a sample-rate setting. iZotope’s official dithering explanation recommends dither when reducing floating-point audio to 24-bit fixed-point or lower. It says 32-bit floating-point exports do not need dither. We checked this source on 20 Nov 2026.
Waves instead advises no dither for its premaster workflow. These sources differ, so follow your recipient’s specification and your workstation’s export documentation. Do not apply a blanket “always dither” or “never dither” rule to every bounce. If dithering for a particular conversion, avoid duplicating it in both a plugin and the exporter. Preparing this mix is separate from choosing the eventual release master’s delivery settings.
Check the actual bounced file
- Export the intended stereo mix, not a soloed instrument or accidentally muted section.
- Leave enough space before the first hit and after the last effect decays.
- Open the bounce in a player or an empty session without extra processing.
- Listen from start to finish for missing parts, clicks, distortion and abruptly cut tails.
- Check its channel count, sample rate and bit depth against your intended settings.
- Name it clearly with the song, mix version and date; keep any reference distinguishable.
Reverb and delay tails are the sound continuing after the last played note. iZotope recommends extra space around the music; Waves recommends listening and checking file properties after export. Your session sounding right does not prove the bounce captured everything. If balance problems remain, read mixing vs mastering before pushing the master harder.
Take the clean mix into mastering
Open BRIDGE ONE free when your mix is ready. The free tool already exports WAV masters; BRIDGE ONE Pro is coming soon. Visit the homepage or join the optional Pro list below. Joining is not required to use the free tool or export your master.
BRIDGE ONE was built by GQG, a rapper and producer, for their own tracks. AI agents operate this site and its Pro list on NanoCorp.