Most great mixes today happen between people who never met in person. Remote mixing is the default, not a workaround—but the workflow trips people up because the old in-the-room habits don’t translate cleanly.
Mixing
How to Mix a Song Remotely Without Losing Your Mind
- Bounce dry stems, label them properly, and include a rough mix as a north star.
- Give notes by timecode, not paragraph—“1:23 vocal too dry” beats five sentences.
- Async beats sync. Plan one revision round, then walk away from the session.
7 min readApr 10, 2026
By Mario Stjepanovic, founder of Muselink.app
Paragraph 1
How Do You Export Stems That Line Up in Any DAW?
Every stem starts at zero. Bounce each track from the very first bar of the session, even if the part doesn't come in until the second chorus. That leading silence is what makes drag-and-drop alignment work — the engineer drops your files at 0:00 in whatever DAW they run and everything locks. Stems that start where the audio starts turn into a puzzle with no reference edges.
Export 24-bit WAV at your session's native sample rate. Don't upsample — 44.1 stays 44.1. No MP3s, ever; compression artifacts get baked into the mix. And leave headroom: peaks around -6 dB, nothing clipping, no limiter on any stem. A hot stem forces the engineer to undo your gain staging before they can start.
Print what needs printing. Let reverb and delay tails ring out fully instead of cutting the bounce at the last note. Render soft synths to audio — the engineer probably doesn't own your plugins. And keep mono sources mono: a mono vocal exported as a stereo file just doubles the download for nothing.
What Should Go in the Notes File With Your Stems?
One plain text file in the stems folder answers the questions the engineer would otherwise DM you about: BPM, key, session sample rate, and any tempo changes. Add the song length and where the sections land — knowing the drop hits at 1:04 saves real time when notes start flying later.
Then draw the map of what's sacred. If the pitched vocal effect is the hook, say so — otherwise a well-meaning engineer might 'fix' it. Flag what's printed on purpose versus what's accidentally wet. The rough mix shows the vibe; the notes file explains which parts of that vibe are non-negotiable.
Confess the known issues upfront. The click at 2:14, the noisy guitar DI, the verse vocal recorded on a different mic — the engineer will find them anyway. Saying it first saves them detective hours and tells them you actually listened. Zip the whole folder as one archive named like artist_song_stems_v1.
How Do You Choose Reference Tracks That Actually Help?
Match the instrumentation density, not just the genre. A sparse trap reference tells an engineer nothing useful about your ten-layer indie arrangement. Pick songs with a similar element count and a similar era of loudness — a 1990s record breathes in a way no modern master does, and chasing both at once fails.
Use one vibe reference and one translation reference. The vibe reference says how the record should feel — vocal placement, space, tone. The translation reference is a song you know behaves on every system: car, earbuds, phone speaker. Together they tell the engineer where to aim and what the low end has to survive.
Level-match before you compare. Commercial masters are several dB louder than any unmastered mix, and louder always reads as better. Turn the reference down until the two feel equally loud, then judge. Skip this and every A/B will make your mix sound worse than it actually is.
What Words Should You Use When Giving Mix Feedback?
A short shared vocabulary beats paragraphs. Muddy means low-mid buildup — the mix feels congested. Boxy is a honking midrange, like the song is playing in a cardboard room. Harsh lives in the upper mids where cymbals and vocal esses start to hurt. Thin means missing body; boomy means a low end that hangs too long. Ten words like these cover most of what you'll ever need to say.
Talk placement, not plugins. Closer or further, wider or narrower, brighter or darker, wetter or drier — every one of those maps to a concrete move the engineer already knows how to make. 'Pull the vocal closer in the chorus' is actionable in a way 'the vocal feels off' never will be.
Name the feeling and the element, then stop. 'The chorus doesn't lift after the second verse' is a great note. 'Add 2 dB at 10k on the master bus' is a bad one — you've prescribed the surgery instead of describing the symptom, and you might be wrong about the cause. Describe what you hear; let the engineer choose the tool.
How Do You Keep Revision Rounds From Dragging On?
Never write notes from a single listen on a single system. Play the mix on your main setup, then earbuds, then a car or a phone speaker. Problems that only exist on one system usually aren't mix problems at all. Notes written from three systems find the real ones.
Then wait a day. Fresh ears kill half the notes you would have sent the night the mix landed. Batch everything that survives into one timestamped list — and if collaborators are involved, merge everyone's notes into a single list with one person sending it. Engineers can't mix toward three contradicting voices.
Agree on what a revision even is. Balance, tone, and level tweaks are a revision. New arrangement ideas, replacing performances, or 'what if the bridge were different' is a new job — scope it and price it separately. When v2 lands close, approve it and start the next track. Momentum finishes catalogs; tweaking doesn't.
What Files Should the Engineer Deliver Back?
The standard package is two files: the main mix as a full-resolution WAV at the session sample rate, and a mastering-ready version with the bus limiter off and roughly 6 dB of headroom. That second file is what a mastering engineer actually wants — a slammed mix leaves them nothing to work with.
Alternate versions are cheap during mixdown and expensive after sign-off. Instrumental, acapella, a clean edit, a performance mix with backing vocals but no lead — each is minutes of work while the session is open and a paid recall once it's archived. Ask for the ones you'll plausibly need before the mix starts.
Ask about the session itself. Who keeps the project file, how long stems stay archived, and what a recall costs in a year when a sync opportunity needs an instrumental you forgot to request. Engineers vary on this; you want the answer in writing before it matters.
How Do You Trust a Mix Engineer You've Never Met?
Sending your whole song to a stranger feels exposed, and that instinct deserves respect rather than dismissal. The practical answer is the same as sharing any unfinished work: control the scope. Stems for one song is a bounded risk. Your catalog, your sessions, and your unreleased ideas stay with you.
Put the terms in the chat before the files move: revision count, deliverables, deadline, payment or split, and how the credit reads. None of this needs a lawyer — a few plain sentences both people agreed to settle ninety percent of future disputes before they exist.
Start with one song, not the EP. A first remote collab tests communication as much as it tests ears — how they take notes, how they hit deadlines, how the v2 responds to your list. Get one track through the full loop above, and you've likely found the engineer for the next ten.
Stop chasing collabs in the DMs.
Upload a 10–15 second snippet and match with creators who already like your sound. Free during early access.
Get Early AccessStep by step
Bounce a stereo rough mix as the brief
Capture the vibe and balance you hear in your head and send it with the stems. The engineer aims at your rough.
Strip processing and send dry stems
Remove bus compression, EQ, and reverb on send unless they're integral to the sound. The engineer needs raw material, not your mix recreated.
Label every stem with role and source
Format: 01_LeadVox.wav, 02_AdLib1.wav, 03_BassDI.wav. Numbering enforces order; named roles save guessing.
Include two reference tracks with specific callouts
'Reference A for vocal presence, reference B for low-end weight' gives the engineer a north star.
Give notes by timecode
'1:23 vocal too dry' beats long paragraphs. Timestamped one-liners get acted on; paragraphs get lost.
Limit revisions and lock loudness target upfront
Plan one revision round, two max. Decide -14 LUFS for streaming or -8 to -10 for club-ready before the mix starts.
Common questions
- What sample rate and bit depth should I send stems at?
- Whatever your session already runs at, exported as 24-bit WAV. Don't upsample — converting 44.1 kHz to 96 kHz adds file size, not quality. Note the rate in your notes file so the engineer's session matches yours from the first import.
- Should I send MIDI files along with my stems?
- No — print every virtual instrument to audio before you send. The engineer almost certainly doesn't own your exact synths and plugins, so MIDI alone plays back wrong or not at all. If a sound might need re-voicing later, mention it in the notes and offer the MIDI on request.
Topics
remote mixingonline mixing workflowsend stems to mix engineer
MORE COLLABORATORS
Find More Collaborators
Find Mix Engineers
Connect with mix engineers who make your recordings sound professional. Hear their work first, match, and get your song ready for release.
Learn moreFind Producers
Upload your sound, get matched with producers who fit your style.
Learn moreFind Beatmakers
Connect with beatmakers who craft the instrumentals your music needs. Match by sound — from trap to lo-fi to boom bap and beyond.
Learn moreFROM THE BLOG
Read More From the Blog
Production · 7 min read
The Best DAW for Online Music Collaboration in 2026
Logic, Ableton, FL Studio, Pro Tools—most arguments about “the best DAW for collaboration” miss the point. The DAW barely matters if you send stems.
Read articleProductivity · 2 min read
How to Stay Consistent as a Music Producer and Beat Burnout
Trying to do everything alone makes it easy to burn out. Here’s how small ideas, collaborators, and the right tools keep your creative streak alive.
Read article