How to export stems in Logic Pro (manually, and in one click)

Exporting stems in Logic Pro is not hard. It is just slow, and there are a handful of ways to get it quietly wrong. I have delivered stems for hundreds of library tracks, and most of the mistakes I have made were not in the mix. They were in the export: a missing send, a mastered stem that should have been raw, a sample rate nobody asked for.

This guide covers the manual way first, including the traps. Then it shows the one-click way with QuickStem, which is what I use now.

What a stem actually is

A stem is a submix of related tracks, bounced to a single audio file from the start of the song to the end. Drums, bass, guitars, keys, vocals, FX. Every stem has the same length and start point, so when someone drops them all into a new session at bar one, they line up and sum back to the mix.

That last part matters. Individual tracks exported one by one are not the same as stems. More on that below.

Part 1: the manual method

Step 1. Prep the session

Do this before you touch the export menu. It saves you from re-exporting later.

  • Consolidate and clean up. Delete unused tracks, empty regions and muted takes you do not need. If a track is muted and you do not want it in the stems, delete it or make sure it stays muted.
  • Name your tracks. Logic uses track names for the exported file names. "Audio 14" tells nobody anything. "Lead Vox", "Kick In", "Pad Wide" will.
  • Check routing, sends and buses. Know which tracks feed which aux buses. Reverb and delay on sends live on an aux, not on the source track. If you want the vocal reverb in the vocal stem, you need to handle that deliberately (see the gotchas).
  • Check tails. Set the cycle or project end point past the last reverb and delay tail. If the song ends at bar 97 and the hall reverb rings for four seconds, the export needs to cover that.
  • Decide on master-bus processing. If the delivery wants unmastered stems, bypass the limiter and any mastering chain on the stereo out before you export.

Step 2. Group tracks into stems

Logic's Track Stacks are the easiest way to organise this. Select the tracks that belong together, press Command-Shift-D, and pick a Summing Stack. A Summing Stack routes the child tracks through a single aux, which is what you want for a stem. A Folder Stack does not sum audio, so it will not give you one file per group.

If you already mix through buses (Drum Bus, Vox Bus, and so on), those aux channels are your stems.

Step 3. File > Export > All Tracks as Audio Files

This is Logic's built-in stem exporter. Go to File > Export > All Tracks as Audio Files (Command-Shift-E). You get a dialog with these options:

  • Save Format: WAVE, AIFF or CAF. Most deliveries want WAV.
  • Bit Depth: 16, 24 or 32-bit float. Use 24-bit unless told otherwise.
  • Multi-Threading: leave it on.
  • Range: the whole project, or the cycle area if you set one.
  • Bypass Effect Plug-ins: exports the raw track with no inserts. Usually off for stems.
  • Include Volume/Pan Automation: keep this on so the stems reflect the mix.
  • Normalize: set to Off for stems. "Overload Protection Only" is a safe alternative. Never fully normalize stems or they will not sum correctly.
  • Export as: One File per Track, or One File per Channel Strip. The second option is the one that includes your Summing Stack auxes.
  • Add resulting files to: untick this unless you want the stems back in the project.
  • Pattern: the file naming pattern. You can insert the track name, track number, project name and more.

Pick a folder, hit Export, and wait. Logic bounces each track in real time or faster, depending on your plug-ins.

Bounce in Place vs Export

People mix these up. Bounce in Place (Control-B) renders a region or track to a new audio track inside the session. It is for freezing a part or committing a sound, not for delivery. Export writes files to disk for someone else. Use Export for stems.

The other option is manual: solo one stem bus, File > Bounce > Project or Section (Command-B), name it, repeat for every stem. This is the method that gives you the most control over master-bus processing and naming. It is also the method that takes an hour per song.

The gotchas

These are the ones that have cost me re-deliveries.

1. Sends and bus effects are not in the track export. When you export tracks as audio files, each file contains that track's inserts and automation. It does not contain the reverb that lives on Aux 3 via a send. The aux gets its own file. If the client wants "vocals with reverb," you either bounce the vocal bus with the reverb returned into it, or you deliver the FX aux as its own stem and tell them.

2. Master-bus processing. Export All Tracks bypasses the stereo output chain. That is good for stems. It is bad if you expected your stems to sound like the mastered mix. For mixes and instrumentals, you still need a separate Bounce from the stereo out, with and without the mastering chain as needed.

3. File naming. Logic's pattern gives you the track name. It does not give you the library's naming convention. If the spec says Title_Instrumental_Drums.wav and your track is called "Drum Bus," you will be renaming files by hand or writing a macro.

4. Sample rate. Logic exports at the project sample rate. If you work at 44.1k and the library wants 48k, you have to convert the project (or convert the files after) and check the result. Decide this before you export, not after.

5. Tails. If a track ends before the project end, Logic still writes the file to the full length, which is what you want. But if your project end marker is too early, every tail gets chopped. Check it once per session.

6. Instrumental and alt mixes. Export All Tracks does not make an instrumental. That is another manual bounce with the vocal muted. Same for a no-lead version, a TV mix, or anything else on the spec.

Add it up and a typical library delivery (full mix, instrumental, two unmastered versions, eight stems, named correctly) is somewhere between 12 and 15 separate bounce operations. Per song.

Part 2: the one-click way

This is why I built QuickStem. It is a Mac app that drives Logic Pro through Apple's Accessibility API, the same way you would with a mouse: solo, bounce, mute, next. It never touches your audio files, and it verifies the session is unchanged when it finishes.

Here is the workflow:

  1. Open your session in Logic and open QuickStem. It scans the mixer and routing and finds your stem structure: the buses, the stacks, the sends.
  2. Review the scan. Keep the groups it found, or combine channels into custom stems. Decide if the FX returns are their own stem or folded in.
  3. Choose your mix versions. Full Mix, Instrumental, Unmastered Full Mix, Unmastered Instrumental, plus any custom mixes you want. For the unmastered versions, pick which master-bus plug-ins to bypass.
  4. Set your naming. Build the file naming convention the library asked for. Save it as a template with the mix list and settings so next time it is one click.
  5. Hit Bounce All. QuickStem runs the whole delivery and sorts the output into STEMS, MIX DELIVERABLES and DOCUMENTS folders.

Got five songs to deliver? Add them to the batch queue and let it run overnight.

QuickStem Plus adds Smart Click + Cues (a stereo file with click left and spoken section cues right, built from your song structure) and Lyric Transcription, which turns the lead vocal into a lyric sheet you review before approving.

QuickStem runs on macOS 14 or later and Logic Pro 11 or later (verified on Logic Pro 12). It is signed and notarized by Apple, and one licence covers two of your own Macs. Ableton Live and Pro Tools versions are coming.

Learn more on the QuickStem product page, or buy QuickStem for $49 or QuickStem Plus for $79 before the opening sale ends November 30. Every purchase includes one free Soundwall master.

FAQ

What is the fastest way to export stems in Logic Pro? For a single session, File > Export > All Tracks as Audio Files with "One File per Channel Strip" gets you the raw stems quickly. For complete deliveries with mixes, instrumentals and custom names, an automation tool like QuickStem is faster because it runs every bounce for you.

Should I export stems with or without the master-bus processing? Ask the client. Most mix engineers and libraries want unmastered stems with no limiter on the stereo out. Full mixes are usually delivered both mastered and unmastered. QuickStem lets you pick which master-bus plug-ins to bypass per version.

Why don't my stems sum back to the mix? Usually one of three things: normalization was on during export, send effects on aux buses were not included, or the master-bus chain was adding gain and compression that the stems do not have. Turn normalization off and account for your sends.

What bit depth and sample rate should stems be? 24-bit WAV at the project sample rate, unless the spec says otherwise. Many libraries ask for 48k/24-bit. Check before you start so you are not converting afterward.

Does QuickStem work with Logic Pro 12? Yes. It is verified on Logic Pro 12 and supports Logic Pro 11 and later on macOS 14 and later.


Author: John Coggins is the founder of Soundwall Studios in Westlake Village, CA, a songwriter and producer with 1,000+ works registered with ASCAP and a long-time Extreme Music writer. He built QuickStem because he was sick of bouncing stems one at a time for library deliveries.

Previous
Previous

Stem delivery for music libraries: the spec checklist composers actually need

Next
Next

QuickStem vs Auto-Bounce: which Logic Pro stem exporter fits you?