Log In
Sign Up
Menu

FL Studio: Bounce Dry Stems for a Pro Mix Engineer
HTML Mini-Course • FL Studio • Exporting Dry Stems

Bounce dry stems in FL Studio to send to a professional mix engineer

This guided course walks you through exactly how to prepare, export, and package stems so a mix engineer can open your files and start working immediately—without missing plugins, clipping, or timing surprises.

Progress: 0% (0/0 checklist items completed)
Packaging template

1) What “dry stems” means (and what it doesn’t)

Dry stems are exported audio files that give your mix engineer maximum control—without baking in unnecessary processing.

~3 min

Dry stems usually means…

  • Each stem is a separate WAV (kick, snare, bass, lead, etc.).
  • All stems are time-aligned (they all start from the same bar/beat).
  • No “mix bus” or mastering chain printed onto everything.
  • Healthy headroom (no clipping), typically peaking around -6 dBFS to -3 dBFS per stem (not a strict law—just practical).

Dry stems does not always mean…

  • “No effects ever.” Sometimes a sound’s identity is its FX (e.g., special delay throws, guitar amp sim, vocoder).
  • “Everything as a single file.” That’s a full mix, not stems.
  • “Export patterns only.” Mix engineers need full-length files aligned to a common start.
Rule of thumb: If removing an effect would change the instrument (sound design), keep it. If it’s mainly “mix polish” (bus glue, mastering, loudness), remove it.

2) Session prep in FL Studio (before exporting)

Do these steps once to avoid the most common stem problems: missing audio, wrong tempo, clipped stems, and surprises on the master.

~6 min

Set your “project truth”

  • Confirm project tempo and time signature.
  • Set a clear song start (usually Bar 1) and keep it consistent.
  • If you use audio clips, make sure they’re not accidentally time-stretched in weird ways.
  • Save a copy: File → Save as… (e.g., SongName_STEM_EXPORT.flp).

Clean the master

  • Bypass/disable loudness plugins, limiters, clippers, “mastering” EQ, and maximizers on the Master.
  • Leave monitoring tools off the print path (reference plugins, room correction, etc.).
  • If you’re unsure, export a quick “pre-mix” reference first, then remove mastering FX for stems.
Warning: If a limiter stays on the Master, every stem can be “quietly crushed” without you noticing.
Optional but recommended: consolidate audio in one folder

Why engineers love this

  • All audio is in one place, no missing samples.
  • Easy to archive and re-open months later.

In FL Studio you can also export zipped project files, but for stem delivery you’ll typically send WAVs + info file.

3) Route and label your Mixer so stems export correctly

The cleanest stem export comes from Mixer tracks that are clearly named and correctly routed.

~6 min

Best practice routing

  • Each sound/group goes to its own Mixer insert.
  • Submix busses are okay (e.g., DRUM BUS), but don’t double-print unless you intend to.
  • Remove “mystery routing” (random sends, hidden sidechains) unless needed.

Naming conventions

  • Use clear names: 01_Kick, 02_Snare, 10_LeadVox
  • Avoid emojis/slashes that can break file paths on some systems.
  • Decide up front: stems by instrument (Kick, Snare, Bass) vs stems by bus (Drums, Music, Vox).
Common mistake: exporting “split mixer tracks” while multiple instruments share the same Mixer insert. Result: one stem contains several instruments.
Sidechain note (important)

How to handle sidechain compression

  • If the “pump” is part of the vibe, you can print it (keep the compressor active).
  • If you want the engineer to control it, export the dry signal (no compressor) and provide a note: “Kick sidechains Bass at ~4:1, fast attack, medium release.”
  • Always export the sidechain source (e.g., Kick) as its own stem.

4) Export settings for professional stems (WAV)

These settings aim for maximum compatibility and quality for mixing.

~5 min

Recommended WAV settings

  • Format: WAV
  • Bit depth: 24-bit (or 32-bit float if you and your engineer prefer it)
  • Sample rate: match your project (commonly 44.1 kHz or 48 kHz)
  • Dithering: generally off for 24-bit stems (more relevant when going down to 16-bit)
Engineer-friendly: 24-bit WAV, consistent sample rate, no clipping, and aligned start times.

FL Studio export approach

  1. Go to File → Export → WAV.
  2. Select Song mode (not Pattern) unless you’re intentionally exporting patterns.
  3. Enable Split mixer tracks to generate one WAV per Mixer insert.
  4. Choose a dedicated export folder: SongName_Stems.
Should you normalize stems?

Usually: No

  • Normalization changes your internal balance and can make gain staging harder.
  • Instead, lower your Mixer tracks so they don’t clip and leave headroom.

5) Tails, start point, and perfect alignment

Your engineer should be able to drag stems into any DAW and hit play—everything in sync with clean endings.

~5 min

Alignment rule

  • All stems should start at the same timestamp (usually 0:00 / Bar 1).
  • Even if an instrument comes in later, its file should still begin at the start so it lines up.

Tail rule

  • Include reverb/delay tails that belong to that stem.
  • Don’t cut off decays. Add a little extra time at the end.
  • If you used long ambient FX, make sure export length captures them.
Heads up: If you export only “what’s audible,” stems may be different lengths and won’t align by default in the engineer’s session.
Quick test: verify alignment before sending

60-second verification

  1. Create a new empty project.
  2. Drag all stems in at the start.
  3. Press play: it should sound like your rough mix (minus master limiting).

6) What to leave on vs. remove (so “dry” stays musical)

Print sound design; avoid printing final mix/master processing unless requested.

~6 min

Typically REMOVE (for dry stems)

  • Master limiter/clipper/maximizer
  • Master “glue” compression intended for loudness
  • Master EQ for overall tone shaping
  • Reference plugins / monitoring correction in the print path
Don’t print mastering unless the engineer specifically asks for “processed stems.”

Typically KEEP (sound-defining)

  • Instrument amp sims (guitar/bass) if that is the tone
  • Creative FX: chorus/phaser/bitcrush if part of the patch
  • Vocal tuning effects if artist expects that sound
  • Special throws (e.g., one-shot delay at end of hook)

If unsure, export two versions: LeadVox_DRY and LeadVox_FX.

Reverb & delay: sends vs. printed effects

Best-of-both worlds

  • Export main stems fairly dry (minimal space FX).
  • Also export dedicated FX return stems like FX_Reverb, FX_Delay if your vibe depends on them.
  • Make sure FX stems are aligned from the start like everything else.

7) Export checklist (trackable)

Tick these off as you go. Your completion updates the progress bar at the top.

~8 min

Project + routing

Levels + processing

Export settings

Final verification

8) Quick knowledge check

A short quiz to catch the mistakes that make engineers email you back asking for re-exports.

~3 min
Q1: What’s the safest way to make sure stems line up in any DAW?
Q2: What should you usually remove from the Master when exporting dry stems?
Q3: If your mix vibe depends on a big reverb send, what’s a great compromise?

9) Packaging and delivery (what to send)

Send a clean folder + a simple info note so your engineer can start instantly.

~4 min

Recommended folder structure

Example:
SongName_MixDelivery/
├─ 01_STEMS_WAV/
│  ├─ 01_Kick.wav
│  ├─ 02_Snare.wav
│  ├─ 03_Hats.wav
│  ├─ 04_Bass.wav
│  ├─ 05_Keys.wav
│  └─ 10_LeadVox.wav
├─ 02_FX_STEMS_OPTIONAL/
│  ├─ FX_Reverb.wav
│  └─ FX_Delay.wav
├─ 03_REFERENCES/
│  ├─ RoughMix.wav
│  └─ RefTrackLinks.txt
└─ SongInfo.txt

What to put in SongInfo.txt

  • Song name + version
  • BPM, time signature, key (if known)
  • Sample rate / bit depth
  • Any “must-keep” creative notes (e.g., “Vox delay throw in hook bar 9”)
  • Reference tracks (links) + what you like about them
You can zip the whole folder and upload via Drive/Dropbox/WeTransfer (whatever your engineer prefers).
Pro tip: Include a rough mix that represents your intent (vibe, arrangement, special moments). Engineers use it like a map.
Optional extras your engineer may ask for
  • Instrumental stems, acapella stems
  • Alternate vocal comps
  • MIDI files (if they need to re-trigger virtual instruments)
  • DI tracks for guitars/bass alongside amped versions
Made to embed Single-file HTML No external assets

You can paste this HTML directly into your website. If you want it to match your site’s branding, swap the CSS variables in :root (colors, radius, etc.).