Bounce and Export in Logic Pro: WAV, MP3, Stems, Settings
A practical export checklist for finished mixes, quick MP3s, collaborator stems, and release handoff folders.
Export mistakes are boring until they cost a deadline. The most common ones are simple: wrong range, clipped output, missing reverb tail, MP3 sent where WAV was needed, or stems named so badly nobody knows what they are.
A good Logic Pro bounce is a checklist. The creative work is done; now the file has to be useful.
Quick answer
If you are in Logic Pro right now, do not start by opening every menu. Save the project before bouncing. Set the exact start and end range. Then move through the four checks below in order.
The order matters because exporting work usually breaks earlier than it looks. A wrong track, region, input, bus, or range can make the last setting look guilty when it is only receiving a bad setup.
Use this as the short version before reading the full guide.
- Set the bounce range: The bounce should start before the first sound and end after the final delay or reverb tail.
- Choose the right format: Use WAV or AIFF for serious delivery, mastering, collaborators, and archives.
- Check loudness and clipping: Play the loudest section and watch the stereo output.
- Name files for another human: A useful filename includes song, version, date, and purpose.
Before you start
- Save the project before bouncing.
- Set the exact start and end range.
- Check the stereo output for clipping.
- Decide whether the destination needs WAV, MP3, stems, or all three.
A clean pass from start to finish
Run this as one clean pass, not as disconnected tricks. Begin with the first checkpoint: set the bounce range. Then move to the second: choose the right format. Those two checks make the project readable before you make detailed changes.
After that, use the next two checkpoints as the decision stage: check loudness and clipping, then name files for another human. This is where you stop guessing and let the screen show whether the sound, timing, routing, or edit is behaving the way the song needs.
If you change more than one thing at once, write down what you changed or save a new version. Logic Pro is fast enough that a session can go from fixed to confusing in under a minute. Small, named moves are easier to trust later.
1. Set the bounce range
The bounce should start before the first sound and end after the final delay or reverb tail. Do not let the last region edge cut off the mix.
Use cycle range or project end markers deliberately.
2. Choose the right format
Use WAV or AIFF for serious delivery, mastering, collaborators, and archives. Use MP3 for quick listening copies.
If someone asked for WAV, do not send MP3 because the file is smaller.
3. Check loudness and clipping
Play the loudest section and watch the stereo output. If it clips, fix the mix or output gain before export.
Normalization is not a substitute for understanding your level.
4. Name files for another human
A useful filename includes song, version, date, and purpose. The file should make sense without opening the project.
For stems, include track groups or roles clearly: Drums, Bass, Music, Lead Vocal, BGV, FX.
Decision table
| Destination | Format | Notes |
|---|---|---|
| Mastering | 24-bit WAV/AIFF | Leave headroom if requested |
| Quick approval | MP3 | Small file, not archive |
| Collaborator | WAV stems | Same start point for all files |
| Archive | WAV plus project | Keep version and date clear |
Checkpoint table
| Checkpoint | What should be true | If it is not true |
|---|---|---|
| Set the bounce range | Use cycle range or project end markers deliberately. | Back up and fix the setup before continuing. |
| Choose the right format | If someone asked for WAV, do not send MP3 because the file is smaller. | Do the smaller edit instead of rebuilding the whole part. |
| Check loudness and clipping | Normalization is not a substitute for understanding your level. | Check what is selected, then repeat the change deliberately. |
| Name files for another human | For stems, include track groups or roles clearly: Drums, Bass, Music, Lead Vocal, BGV, FX. | Use the mixer or playback context as the final judge. |
Before and after check
Before the change, make one short playback pass and name the exact problem in plain words: late entrance, dull vocal, wrong input, harsh consonant, missing output, messy routing, clipped bounce, or whatever the session is actually doing. If you cannot name it, you are not ready to fix it yet.
After the change, play the same section at the same volume. Louder almost always sounds better for ten seconds, so level-match when you are judging exporting decisions. The useful question is not whether the edit is impressive. It is whether the part sits better without pulling attention away from the song.
Check the edges of the fix. In Logic Pro, a repair can solve the center of a problem while damaging the bar before it, the breath after it, the bus return, or the export tail. A good before/after pass includes a little lead-in and a little space after the moment you changed.
If the after version only feels better while you are watching the screen, take a break and listen again without touching the mouse. Visual neatness is helpful for editing, but the final test is still playback. Keep the version that makes the project easier to finish.
What not to chase yet
Do not chase polish before the basic workflow is stable. For this topic, the first two checkpoints have to make sense before you worry about the smaller details: set the bounce range, then choose the right format. Fancy settings cannot rescue a confused source.
Do not copy numbers blindly from another session. Buffer sizes, EQ points, quantize strength, compression timing, send levels, and bounce choices all depend on the material. Use examples as starting points, then move the control until this project sounds and behaves correctly.
Do not keep editing because the tool is available. Logic Pro gives you enough control to over-fix almost anything. Stop when the problem is gone and the performance still feels like a performance.
What good looks like
The exporting workflow is working when you can explain what changed without pointing at a random plugin window. If the fix depends on luck, the session is not stable yet.
After the main pass, close the editor you were using and play the section from a few bars before the change. A good edit survives context. A bad edit only sounds correct when the screen is zoomed into the problem.
Keep one version before the major change and one version after it. Logic Pro projects can move quickly, and a clean fallback saves more time than trying to reverse a dozen tiny edits later.
If it still feels wrong
If the result still feels wrong, return to the signal chain. Ask whether the source is clean, whether the region edit is correct, whether the track is routed where you think it is, and whether the mixer confirms what your ears are telling you.
Do not add another processor just because the current one did not solve the issue. In Logic Pro, many problems are earlier than the plugin slot: wrong input, messy region boundaries, doubled monitoring, over-quantized MIDI, or a bus that is louder than the dry track.
When you get stuck, simplify the project. Mute everything except the source and the one track or aux it depends on. If the problem disappears, bring the session back one group at a time until the conflict shows itself.
Common mistakes to avoid
- Cutting off the reverb tail. Fix it by returning to the first visible control in the chain and confirming it before you touch a plugin.
- Sending MP3 as the master file. Fix it by listening to the section in context, then changing only the thing that fails the playback test.
- Exporting stems from different start points. Fix it by saving a version, making the edit smaller, and checking whether the song still feels natural.
- Using unclear names like final-final-v7-new.wav. Fix it by simplifying the session view until the routing, region, or setting is obvious again.
Practice pass
Bounce three files from the same project: full WAV, MP3 reference, and four grouped stems. Re-import them into a blank project. If they line up and make sense, your export workflow is solid.
When to move on
You are done when the change helps the song at normal listening volume. Not when the screen looks tidy, not when every meter behaves perfectly, and not when the analyzer is pretty.
Print or bounce a short reference after the fix. Listening outside the edit screen catches problems that are invisible while you are staring at regions, lanes, and meters.
Sources checked
This draft was checked against current Apple Logic Pro documentation and release notes before writing. Source links used for version-sensitive claims on May 16, 2026:
FAQ
Should I export WAV or MP3 from Logic Pro?
Use WAV or AIFF for masters, collaborators, and archives. Use MP3 for quick sharing only.
What bit depth should I bounce?
24-bit WAV is a common delivery choice for mixes and mastering handoff. Match client or distributor specs when they provide them.
How do I avoid cutting off reverb tails?
Set the bounce end after the tail fully fades, not exactly at the final region edge.
Can Logic Pro export stems?
Yes. Export tracks or regions as audio files when collaborators need separate parts.
