Practical Mixing

How to prepare and export your vocals for a mixing engineer in REAPER

By StudioRescue Editorial

Published September 13, 2026 · Updated September 13, 2026

Quick answer

Send your mixer a dry vocal: bypass your own EQ, compression, de-esser, and reverb before you export, so the engineer can build the sound from a clean start. Export as WAV or AIFF, 24-bit, at your session’s sample rate (usually 44.1 or 48 kHz), not MP3. Make every file start at the same point so the tracks line up when they are dropped in, and keep each part as one continuous file. In REAPER, the reliable way is File → Render with Source set to Stems (selected tracks), Bounds set to Entire project, and your mixing plugins bypassed first. Put everything in one clearly named folder with a rough reference mix and a short note listing tempo and key. When in doubt, ask the mixer what they want before you render.

Handing a song to a mixing engineer for the first time is where a lot of home singers get stuck. You finished the take, and now someone is asking for “dry stems at 24-bit” and it sounds like a foreign language. It is simpler than it seems. A stem is just one track, or a group of tracks, bounced to a single audio file for mixing. Your job is to give the engineer clean files that line up and sound like the performance you meant, and nothing more. Get that right and you get a better mix back, faster.

This guide covers the vocal side specifically, since that is usually what a home recordist is sending, but the same rules apply to any stem. If you just want the mechanics of REAPER’s Render dialog in general, start with the general guide to exporting audio from REAPER. This piece is about the handoff: what to send, in what shape, and what to leave off.

Send it dry, and send a reference too

“Dry” means without your mixing processing. Before you export, bypass the EQ, compression, de-essing, saturation, and reverb on the vocal, whether that is your vocal chain or a few plugins you added by ear. A mixer wants to make those calls themselves, in the context of the whole mix, and they cannot undo processing that is already baked into the file. A dry vocal gives them room to work; a heavily processed one boxes them in.

That said, dry does not mean lifeless. Keep the parts of the sound that are decisions rather than mix moves: your comp, your timing edits, and any tuning you consider part of the performance. If you are unsure whether a particular effect is essential to the vibe, leave it off the main stem but also print a second version with it on, and say so in your file names.

Always include a reference mix: a bounce of your song in its most finished state, with your rough processing left on. The engineer uses it to hear what you were going for, so the mix that comes back sounds like your song rather than a stranger’s. An MP3 is fine for the reference, since it is only for listening.

Talk to the mixer first

Everyone works a little differently. A one-line message asking for their preferred format, sample rate, bit depth, and whether they want dry, wet, or both saves you from rendering everything twice. It is the single easiest way to avoid a redo.

Use the right file format

Deliver lossless files. Use WAV or AIFF at 24-bit, set to the same sample rate as your session, commonly 44.1 kHz for music or 48 kHz if the project started life alongside video. Do not send MP3 for the actual stems: MP3 throws away audio data to save space, and that loss cannot be recovered once the mixer starts adding EQ and compression on top.

Leave headroom and do not maximize. Turn off any Normalize option in the Render dialog for stems, and do not put a limiter on the vocal to make it loud. A dry stem that peaks a few dB below the top is exactly what a mixer wants. Loudness is their job, not something to bake in now.

Make everything line up

This is the detail that quietly wastes the most time when it is missed. Every file you send should start at the same moment, so that when the engineer drops them all onto tracks at the project start, they line up perfectly without nudging anything. The way to guarantee that in REAPER is to render over the whole timeline rather than just the part that has audio.

Render the entire project length. Set the render Bounds to Entire project so every stem shares the same zero point, including tracks that start with silence before the first line.
Do not trim the start. If there is a count-in or a bit of lead-in silence, leave it. A little silence at the front and back is helpful, not a problem.
One continuous file per part. A vocal that is really a comp of many small takes should go out as a single unbroken file, not a pile of fragments. If your lead is a comp made of many takes, render it so it prints as one clean track.

Watch out

REAPER’s Consolidate/Export dialog has an option to skip silent sections and write a separate file for each chunk of audio. That is handy for tidying up a project you keep working in, but it is the wrong choice for a handoff, because the pieces will not line up on their own. For sharing, keep each part as one full-length file.

Two ways to export dry in REAPER

There are two clean routes, and which one you want depends on whether you have edits and processing to deal with.

1. Render stems with your plugins bypassed (recommended)

This is the reliable choice, because it prints exactly what plays back, including your comp, fades, and timing, while leaving off the mix processing you switch off.

Bypass your mixing FX

On the vocal track, turn off the EQ, compressor, de-esser, and reverb you added. Leave any pitch or timing edits you want to keep.

Select the vocal tracks and open Render

Select the tracks you want as stems, then open File → Render. Set Source to Stems (selected tracks), which writes one file per selected track.

Set bounds and format

Set Bounds to Entire project, format to WAV, bit depth to 24-bit, and the sample rate to match your session. Then render.

One thing to know: rendering a stem this way includes whatever track effects are still active, so the bypass step matters. If you leave a plugin on, it prints into the file.

2. Consolidate the raw recordings

If your vocal has no processing to strip and you just want the untouched recordings, File → Consolidate/Export tracks writes one file per track that is a copy of the source media, and it deliberately does not include track effects or track volume. That makes it a fast way to export genuinely dry files. Because it copies the source media rather than the playback, it is best when your take is simple; if you have comped or tuned the vocal and want those edits baked in, use the render method above instead so nothing is lost. Either way, keep the whole-project length so the files still line up.

Package it so nothing gets lost

Once the files exist, a few minutes of tidying makes you the client every mixer likes.

Name your tracks before you render. REAPER uses the track name in the file name, so a folder of Lead, Double L, Double R, Harmony, and Ad libs is far easier to work with than Track 1 through Track 5.
Group sensibly, or keep parts separate. Stacked backing vocals or doubles can go out as a single grouped stem, or as individual files if you want the mixer to balance them. When unsure, separate files give more flexibility.
One folder, clearly labeled. Put the stems, the reference mix, and your note in a single folder named for the song. If you are sending both dry and wet versions, keep them in clearly marked subfolders.
Add a short note. List the tempo in BPM, the key, the sample rate and bit depth, and which files are dry versus printed. It takes a minute and answers the questions the mixer would otherwise have to ask.

Check your own work

Before you send anything, drag your stems onto fresh tracks in an empty REAPER project, all starting at the same point. If they line up and, with the vocal against your instrumental, sound like your reference, the handoff is clean. If not, fix it now rather than after the mixer has flagged it.

Common mistake	Why it hurts the mix	What to do instead
Stems with your full chain printed on	The mixer cannot undo your EQ, compression, or reverb	Bypass mixing FX and export dry, plus a wet reference
MP3 files	Lossy data is gone before mixing even starts	WAV or AIFF, 24-bit, session sample rate
Each file trimmed to its own audio	Nothing lines up when imported	Bounds set to Entire project so all files share a start
A comp exported as many fragments	Tedious to reassemble, easy to misalign	Render the comp as one continuous file
Files named Track 1, Track 2	The mixer wastes time guessing what is what	Name tracks before rendering; add a spec note

What this will not do

Good file prep makes a mix go smoothly. It does not do the mixer’s job, and it cannot rescue a few things.

It will not fix a weak take. Sending it dry actually exposes timing, pitch, and noise problems more clearly, so fix obvious issues before you export rather than hoping the mix hides them.
It will not recover quality lost to MP3. If the only file you have is a lossy export, the detail a mixer needs is already gone.
It will not help if the files do not line up. Misaligned stems are the fastest way to turn a paid mix into a back-and-forth.
It cannot easily be undone once printed. Heavy tuning or an effect baked into the stem is difficult for the mixer to reverse, so decide what is performance and what is a mix move before you render.

A realistic expectation

Clean, dry, aligned stems will not make an average performance sound like a hit, but they give the mixer the best possible starting point and remove every avoidable obstacle. That is genuinely what separates an easy mix from a frustrating one, and it is entirely in your control.

A quick order to follow

Ask the mixer for their preferred format, sample rate, bit depth, and dry or wet.
Tidy the session: name tracks, clean obvious noise, and set levels roughly where you want them. Leave good headroom.
Bypass your mixing FX on the vocals, keeping only the edits and tuning you consider part of the take.
Render stems with Source set to Stems, Bounds set to Entire project, 24-bit WAV at your session rate.
Bounce a reference mix with your processing on, as an MP3 or WAV.
Package and check: one named folder, a spec note, then import the stems into an empty project to confirm they line up.

Takeaway

To hand your vocals to a mixing engineer from REAPER, export them dry by bypassing your mixing plugins, as 24-bit WAV or AIFF at your session’s sample rate, with Bounds set to Entire project so every file lines up from the same start. Keep each part as one continuous file, name everything clearly, and include a reference mix plus a short note with tempo and key. When in doubt, ask the mixer first, and check your stems in an empty project before you send.

Sources

Cockos, REAPER User Guide (current version 7.79, released August 17, 2026) - the Render dialog, where Source can be set to render selected tracks as separate stem files (which include that track’s effects), and Bounds can be set to the entire project; and the Consolidate/Export Tracks dialog, which writes one file per track as a copy of the source media and does not include track effects or track volumes. reaper.fm/userguide
Cockos, REAPER (current version 7.79) - render to WAV and other formats at selectable bit depth and sample rate, with per-render loudness and dry-run statistics. reaper.fm
Danny Echevarria, “A Guide for Producers Preparing Files for Mix Engineers,” The Pro Audio Files - stems as consolidated per-track files, agreeing format and sample rate and bit depth with the engineer, matching start and end points so stems line up, printing dry stems by disabling effects, clear file naming, and including a reference mix. theproaudiofiles.com/preparing-files-for-a-mix-engineer