Export Settings That Prevent Mix Problems

Export Settings That Prevent Problems When You Send a Song Out

The safest export settings for sending a song out are clearly labeled WAV files, exported from the same start point, at the project sample rate, with enough headroom, no unnecessary normalization, and no extra dithering unless you are creating a final low-bit-depth master. The goal is not to make the files sound louder before handoff. The goal is to make them open correctly, line up instantly, and give the next person clean material to work with.

Bad exports waste time before the mix, master, vocal edit, or collaboration even starts. The engineer imports the files and the hook is late. The beat is an MP3 but the vocals are WAV. One stem starts at bar 1 and another starts at the first sound. A limiter was left on the stereo bus. The rough mix does not match the stems. The files are named Audio_01 through Audio_47. None of those problems are creative. They are handoff problems.

This guide explains the export choices that prevent those issues. It is written for artists, producers, and home studio owners sending songs to a mixing engineer, mastering engineer, producer, vocalist, or collaborator. The exact menu names vary by DAW, but the principles stay the same: preserve quality, preserve timing, preserve intent, and remove guessing.

The Short Answer

Export full-length WAV stems or mixes from the same timeline start, keep the sample rate the same as the session, use 24-bit or 32-bit float when the files will be mixed later, leave headroom, turn off normalization, avoid master-bus limiting unless it is only for the rough mix, and include one reference bounce plus notes. If the file is going to mastering as a final mix, send a clean stereo WAV without clipping and without a limiter that only exists to chase loudness.

Export choice	Best setting for handoff	Problem it prevents
Format	WAV or AIFF	Lossy artifacts and compatibility issues
Sample rate	Same as the project unless requested	Unneeded sample-rate conversion
Bit depth	24-bit or 32-bit float for mix handoff	Low-resolution exports and premature dither
Start point	Same start for every stem	Timing drift and manual placement
Normalization	Off	Random level changes between files
Master processing	Off for stems unless it is part of the sound	Double limiting, clipping, and baked-in mistakes

If you already know what files to send but need folder structure, use the stem and notes organization guide. This article focuses specifically on the export settings that make those files usable.

Start With the Question: What Is the File For?

There is no single export setting that fits every situation. The right settings depend on what the file will be used for. A rough mix for feedback can be an MP3. A full mix for mastering should be a high-quality stereo WAV. Stems for a mixing engineer should be full-length WAV files that line up. A beat preview for a vocalist may be compressed for quick sharing, but the final beat file should be lossless.

Before exporting, decide which of these you are making:

A rough mix for reference.
A stereo mix for mastering.
Individual stems for mixing.
Dry vocals for editing or tuning.
Wet vocal effects as creative references.
Instrumental, acapella, clean, or performance versions.

That decision matters because each export has a different job. The rough mix should communicate vibe. The stereo mix should preserve the finished mix without clipping. Stems should rebuild the session accurately. Dry vocals should give the engineer control. Wet references should show intent without trapping the whole mix in your rough processing.

Use WAV for Serious Handoffs

When a file will be mixed, mastered, edited, tuned, or used in a release workflow, send WAV unless the person receiving it asks for another lossless format. MP3 is useful for quick listening, but it is not the right source format for professional audio work. It uses data compression that can smear transients, alter high-frequency detail, and create artifacts that become more obvious after more processing.

AIFF can also be acceptable, especially in some Mac-based workflows, but WAV is the safest default for broad compatibility. FLAC can be lossless, but some DAWs and engineers still prefer WAV for speed and certainty. If you are unsure, send WAV and include a rough MP3 only as a listening reference.

For BCHILL MIX mixing work, the cleanest handoff is organized WAV stems with a rough mix and references. The mixing services page asks for clearly labeled stems, a rough mix, and a practical file prep flow so the first pass can focus on the song instead of file repair.

Keep the Sample Rate the Same as the Session

Sample rate is one of the most misunderstood export choices. If your project was recorded and produced at 48 kHz, export at 48 kHz unless the receiving engineer asks for something else. If the session is 44.1 kHz, export at 44.1 kHz. Changing the sample rate at export is usually unnecessary for a mix handoff and can create avoidable conversion.

This does not mean 48 kHz is always better or 44.1 kHz is always wrong. It means consistency matters. A song recorded at 44.1 kHz can be mixed professionally. A song recorded at 48 kHz can be mixed professionally. Problems start when files from the same project arrive in mixed sample rates without explanation, or when a user converts files because they heard a different number was more professional.

If the engineer requests a specific sample rate, follow that request. If not, preserve the project rate. Write it into the folder name or notes if it helps: Artist_Song_48k_24bit_Stems. That gives the next person confidence before opening the files.

Use 24-Bit or 32-Bit Float for Files That Will Be Mixed

For most music handoffs, 24-bit WAV is a strong standard. It gives practical headroom and high resolution without creating unnecessarily large files for every situation. 32-bit float can be useful when exporting internal DAW stems or when the receiving engineer prefers it, especially because it can preserve level information more forgivingly if a file was accidentally printed hot inside the DAW.

The important point is to avoid sending 16-bit stems for a professional mix unless there is a specific reason. 16-bit is common for final CD-style delivery, not ideal for files that will receive more processing. It gives the engineer less room to work and can force dither decisions too early.

If you are sending a finished mix to mastering, 24-bit WAV is usually safe unless the mastering engineer asks for 32-bit float. If you are sending individual tracks for mixing, 24-bit or 32-bit float is better than 16-bit. If you are sending a quick demo, MP3 is fine, but label it as a demo.

Do Not Dither Every Export

Dither is not a magic quality button. It is a specific process used when reducing bit depth, such as going from a high-resolution master to a 16-bit delivery format. If you apply dither repeatedly during every export, stem bounce, rough mix, and revision pass, you are adding a process that does not belong at every stage.

For stems or files that will be mixed later, avoid dithering unless the receiving engineer asks for it. Keep the files at 24-bit or 32-bit float and let the final mastering or delivery stage handle any required bit-depth reduction. This keeps the handoff cleaner and avoids stacking dither unnecessarily.

A simple rule works: if the file is still going to be processed, do not treat it like the final consumer master. Keep it clean. Keep it high resolution. Let the final stage make final-stage decisions.

Export Every Stem From the Same Start Point

Timing alignment is more important than most export settings because a perfectly high-resolution stem is still a problem if it lands late. Every stem should start from the same exact point on the timeline, even if the track does not play until the second verse. If the ad-lib file starts at its first ad-lib, the engineer has to guess where it belongs. If it starts at bar 1 with everything else, it lines up instantly.

This matters for vocals, harmonies, beat stems, effects throws, transitions, background layers, reverse effects, risers, and printed reverbs. It also matters for songs that do not start with sound. If the song has two bars of count-in silence, keep the same start for every file.

The safest export habit is full song length, same start, same end. That makes the files bigger, but it prevents timing mistakes. If you want a full explanation of what to include in a professional handoff, use the stem delivery guide.

Turn Off Normalization Unless It Is Specifically Requested

Normalization changes file levels automatically. That can be useful in some audio prep contexts, but it is usually not helpful for stems being sent to a mix engineer. If every stem is normalized independently, the level relationship between tracks changes. A quiet harmony may become almost as loud as the lead. A percussion detail may become exaggerated. A print that was supposed to be tucked back may arrive too loud.

Leave normalization off for stems. Preserve the balance you created in the session. The engineer can adjust level intentionally after importing. If you normalize everything, the first step becomes undoing a level decision that should not have happened.

For a stereo rough mix, normalization is also usually unnecessary. If the rough is quiet, that is okay. It is a reference. The goal is to show arrangement, effects ideas, and emotional direction, not to compete with mastered songs.

Leave Headroom Instead of Printing Loudness

Headroom prevents clipping and gives the next stage room to work. When sending stems, individual files should not be clipping. When sending a stereo mix for mastering, the file should not hit 0 dBFS or rely on a limiter that only exists to make the bounce louder. A mix can be emotionally exciting without being pushed to release loudness before mastering.

A practical stereo mix target is leaving several dB of peak headroom, often with peaks around -6 to -3 dBFS. This is not a law. It is a useful safety range. The mastering engineer can turn up a clean mix. They cannot fully remove harsh clipping or a limiter that crushed the mix bus before delivery.

For stems, the exact peak level of each file matters less than avoiding clipping and preserving the intended relationship. If the snare is naturally peaky, that is fine. If the vocal is printed through a limiter that flattens every phrase, that is not a clean mix handoff.

Separate Dry Files From Wet References

Vocals create the most export confusion. Many artists send only wet vocals because the rough mix sounds exciting. Then the engineer cannot remove a bad reverb, harsh delay, over-compression, or heavy tuning artifacts. Other artists send only dry vocals and forget to show the creative effects that define the song.

The best handoff is usually both:

Dry lead vocal with no heavy printed effects.
Wet rough or wet effect print if the effect is part of the creative idea.
Separate doubles, harmonies, ad-libs, and effects throws when possible.
Notes explaining which wet effects are required and which are only references.

If a delay throw is a hook moment, print it as a separate effect reference or note the timestamp. If a distorted vocal is a sound design choice, include the printed version and a dry backup if possible. If the reverb was only added to make the rough mix feel less dry, do not force the engineer to use it.

Print Master-Bus Processing Only When It Is Part of the Sound

Master-bus processing can be helpful while producing, but it can create trouble during handoff. A limiter, clipper, stereo widener, or aggressive bus compressor can change every stem or mix in ways that are hard to undo. If the processing is only there to make the rough louder, remove it before exporting stems or a pre-master mix.

There are exceptions. If a sound depends on a special bus effect, print a reference. If the entire beat was built through a specific texture chain, the engineer may need to hear that. But for most mix handoffs, send clean stems and include the loud rough separately.

A good folder can include both:

RoughMix_Limited_ForReference.mp3
MixStems_Clean_NoLimiter_48k_24bit.zip

That naming tells the engineer exactly what is creative direction and what is source material.

Name Exports So a Stranger Understands Them

Export settings do not end at the bounce window. File names are part of the handoff. A file called Audio 12.wav might technically be high quality, but it still creates confusion. Use names that describe role, section, and version when needed.

Weak file name	Better file name	Why it helps
vox.wav	01_Lead_Vocal_Dry.wav	Identifies the main vocal and effect state
hook2.wav	07_Hook_Harmony_High.wav	Shows section and vocal role
beat final.wav	00_Beat_Stereo_Reference.wav	Separates reference beat from mix stems
fx.wav	14_Vocal_Delay_Throw_Wet.wav	Shows it is a creative effect print

If you are sending a larger session, read the guide to preparing session files for a mixing engineer. Export settings and folder organization work together.

Check the Export Before Sending

The most reliable export workflow includes a test import. Create a blank session. Import the stems. Place them all at the same start point. Press play. If the song does not rebuild correctly, the export is not ready to send.

Then check these items:

Do all files open without errors?
Do all stems start at the same point?
Does the rough mix line up with the stems?
Are there missing vocals, ad-libs, effects, or beat parts?
Are any tracks clipping?
Are wet effects clearly labeled?
Does the folder include tempo, key, references, and notes?

This test takes a few minutes and can save a full revision cycle. It also protects you from sending the wrong version. If you export from BandLab, the same principles apply; the BandLab stem export guide covers that DAW-specific handoff.

Keep a Clean Version History

Version control matters because export mistakes often happen when old bounces and new files live in the same folder. Do not overwrite your only copy of the session right before sending files. Save a separate project version for delivery, then export from that version. If the engineer asks a question later, you can reopen the exact session state that created the stems.

Use version names that make sense outside your own computer. A folder called New Final Final is not helpful. A folder called Artist_Song_MixHandoff_v1 is clear. If you revise the export because a file was missing, call the new folder v2 and explain what changed. That prevents the engineer from mixing the wrong folder or combining files from two different exports.

Common Export Mistakes That Cause Problems

Most export problems come from trying to make the files sound finished instead of making them useful. A clean export does not have to be loud, hyped, or polished. It has to be accurate.

Avoid these mistakes:

Sending MP3 stems for a professional mix.
Exporting each stem from its first sound instead of the same start point.
Changing sample rate for no reason.
Sending 16-bit stems when 24-bit or 32-bit float is available.
Normalizing every file independently.
Leaving a limiter on the master bus for clean stems.
Sending only wet vocals with no dry backup.
Forgetting the rough mix and reference tracks.
Not testing the exported files before upload.

When in doubt, send cleaner files and better notes. A good engineer can add polish. They cannot always remove baked-in clipping, missing timing, or a reverb print that covers the lead vocal.

A Simple Export Checklist

Use this final checklist before sending the song out:

Save a new project version before exporting.
Confirm the project sample rate.
Decide whether you are sending stems, a stereo mix, or both.
Export WAV files at 24-bit or 32-bit float for mix handoff.
Export every stem from the same start point.
Turn off normalization.
Remove master loudness processing from clean source exports.
Include dry vocals and wet references where needed.
Name every file clearly.
Import the files into a blank session to confirm they rebuild correctly.
Zip the folder and include rough mix, references, tempo, key, and notes.

The best export settings are boring because they create no drama. The files open. They line up. They sound like the session. The engineer knows what each file means. That is what gives the next stage room to focus on tone, balance, emotion, and release quality.

FAQ

Should I export stems as WAV or MP3?

Use WAV for stems, mixes, vocals, and anything that will be professionally mixed, mastered, edited, or processed. MP3 is fine for a quick listening reference, but it should not be the main source format.

Should I export stems at 24-bit or 32-bit float?

Both can work. 24-bit WAV is a strong default for many music handoffs, while 32-bit float can be useful for internal DAW exports or when the receiving engineer prefers it. Avoid 16-bit stems unless requested.

Should all stems start at bar 1?

Yes, in most handoffs every stem should start from the same timeline point, even if the sound enters later. This lets the receiving engineer import the files and line them up without guessing.

Should I leave my limiter on when exporting?

Leave loudness limiting off for clean stems and pre-master mixes unless that limiter is a deliberate part of the sound. Send a limited rough mix separately if it shows the intended energy.

Do I need to dither stems?

Usually no. Dither is mainly for reducing bit depth at a final delivery stage. For files that will be mixed or mastered later, keep them at 24-bit or 32-bit float and avoid unnecessary dither.

How do I know if my exports are correct?

Import them into a blank session, line them up at the same start point, and play the song. If the rough mix and stems match timing, nothing clips, and every part is labeled, the export is likely ready.