A good review file should represent the mix accurately, play reliably on the recipient’s system, and make it easy to give useful feedback. This guide covers the export choices, checks, and delivery details that help you send a stereo mix without confusion.
1. Prepare the mix and agree on the target
Before opening the export window, confirm what the reviewer needs. A producer may want an unmastered mix with headroom, while a client might prefer a louder reference that is easier to compare with commercial tracks. If the recipient has a file specification, follow it; if not, choose a straightforward high-quality format and state what you sent.
Do a final pass in the session:
- Confirm the intended master bus, stereo output, and processing are active. Check that no alternate output, solo, or mute state is changing the balance unexpectedly.
- Listen through the full arrangement, including the intro, transitions, breakdowns, and ending. A short export can miss a late automation change or a reverb tail cut off at the end.
- Check for clipping or unintended distortion on the master output. A peak below 0 dBFS is a sensible digital ceiling for a review file; if the mix is being sent for mastering, leave additional headroom rather than pushing a limiter simply to make it louder.
- Save the session before exporting, and note which mix version you are sending. This makes it easier to reproduce or revise the file later.
Do not make a new mix decision solely to hit an arbitrary peak or loudness number. A review export is meant to communicate the current mix. If you change the master level or processing for a louder reference, keep a separate version and label it clearly.
2. Choose a format and export settings
For detailed review, an uncompressed PCM WAV file is a broadly compatible choice. AIFF is also uncompressed and can work well, though WAV is often the simpler default when the recipient has not specified otherwise. MP3 or another compressed format is convenient when file size or quick mobile playback matters, but lossy encoding can alter transient detail and produce artifacts. Keep a high-quality uncompressed master of the review export even if you also send a compressed copy.
| Setting | Practical default | When to choose differently |
|---|---|---|
| File type | WAV, PCM | Use AIFF if requested; use a compressed copy for convenient listening or limited transfer capacity. |
| Sample rate | Match the session or recipient specification | Convert only when delivery requires it; avoid repeated sample-rate conversions. |
| Bit depth | 24-bit PCM for an unmastered mix | Use 16-bit PCM when specifically requested; apply proper dithering when reducing bit depth. |
| Channels | Interleaved stereo | Use separate mono files only if the recipient requests split channels. |
| Normalization | Off in most review exports | Enable only when requested and understood; it changes the output level and can affect peaks. |
The exact menus and labels depend on your DAW and version. Look for its audio export or render settings and confirm the choices before starting the export.
Sample rate and bit depth
If you are sharing a mix for production feedback, keeping the session sample rate avoids an unnecessary conversion. If the reviewer or next stage specifies another rate, export once at that target using the DAW’s high-quality conversion option. Do not change the session rate just to create one review file unless your workflow requires it.
Bit depth describes the resolution of PCM samples. For a mix that may still be processed, 24-bit PCM is a useful default. If you need to provide a 16-bit version, use the DAW’s dithering option when reducing from a higher bit depth, following its documentation. Dither is not a substitute for adequate mix headroom, and there is usually no need to dither at intermediate stages if you are still exporting at the session’s working bit depth.
Stereo interleaving
A typical stereo review file is a single interleaved file containing left and right channels. Check that your export range and routing produce two channels. If the file comes out mono, inspect the export channel setting and master routing before trying to widen the mix with processing. A mono compatibility check can be useful, but it does not replace a correctly routed stereo export.
3. Set the export range and render
Choose the complete musical range, not simply the visible portion of the timeline. The export should include the first audible event and enough space after the final note for natural decay, such as reverb, delay, or a cymbal tail. If your DAW offers a selection range, loop region, or markers, verify that it covers the intended song from start to finish.
A reliable sequence is:
- Set the range from just before the first sound to after the final decay. A small amount of silence at the start is acceptable if it preserves an intentional pickup or makes playback easier to cue.
- Check that the selected range does not include unwanted count-ins, scratch takes, or long empty space. If a count-in is useful for the reviewer, include it intentionally and mention it in the message.
- Select the stereo master output and the intended render mode. Real-time export can be useful if a project uses hardware inserts or external gear that cannot be captured during offline rendering; otherwise, offline rendering is commonly faster. Consult the DAW and device documentation when external processing is involved.
- Keep the intended master-bus processing active. Do not accidentally export a pre-fader or alternate bus unless that is the requested deliverable.
- Render to a known folder, then wait for the DAW to finish writing the file before moving or renaming it.
If the DAW offers options for including effect tails or stopping at the selection boundary, choose the behavior that preserves the full ending. If you are unsure how that setting behaves, render a short test around the ending and inspect it before exporting the entire mix.
4. Check the exported file outside the session
A successful render message does not guarantee the file is complete or correct. Play the export in a separate audio player, or import it into a new empty session, rather than checking only the DAW’s timeline playback. This can reveal an incorrect range, a silent channel, a truncated ending, an unexpected format conversion, or a file saved to the wrong location.
Listen to the entire file once if possible. At minimum, check the opening, a representative dense section, the quietest or most exposed section, and the ending. Confirm that:
- Both left and right channels play and the stereo image behaves as expected.
- The beginning is not clipped and the ending retains its decay.
- The file is not silent, corrupted, or unintentionally much quieter or louder than expected.
- There are no export-only clicks, dropouts, or unexpected changes to effects and automation.
- The duration and filename match the intended version.
Inspect the file’s properties in your player or operating system to confirm its format, sample rate, bit depth where displayed, and channel count. Some players do not show every detail; if a specification matters, check it in a tool that reports audio file properties or re-import the file into your DAW. Metadata displays can be incomplete, so use the DAW’s export settings and a second check together.
Do not judge the mix only on laptop speakers or only through a visual waveform. Check at a comfortable level on a familiar playback system, and use headphones or another system as a secondary perspective if available. Review the mix itself separately from the technical file checks: a correct file can still contain a balance or arrangement issue, and a pleasing playback system cannot reveal every compatibility problem.
5. Name and organize review versions
Use a name that identifies the song, version, and purpose without making the recipient guess. For example:
SongTitle_Mix_v03_Review_2026-11-11.wav
Use dates or version numbers consistently.
Avoid names such as final.wav, final2.wav, or newest_mix.wav; they become ambiguous once revisions accumulate.
If you send both a full-resolution WAV and a compressed listening copy, make the formats obvious in the filenames.
Keep the exported file in a project folder alongside the session version or delivery notes, but do not overwrite the previous review version. A simple organization might be:
Mixes/Review/for files sent for feedbackMixes/References/for loudness or alternate playback copiesMixes/Approved/for the version the team has accepted
These names are only examples. A smaller project may need only a clear filename and one folder. The important thing is that you can identify exactly which export the feedback refers to and recover the earlier version if needed.
6. Send the file with useful context
Choose a transfer method that preserves the file without converting it. Direct attachment can be convenient for a small compressed copy, while a file-sharing link is often better for a larger WAV. Check that the recipient has access to the link and that the upload has completed before sending the message. If the sharing service offers streaming previews, tell the recipient to download the original if they need to assess the full-resolution file.
Include concise context that helps the reviewer focus:
- Song title and mix version.
- File format and whether it is an unmastered mix, a reference-limited copy, or another variant.
- The feedback deadline, if one has been agreed.
- A few focused questions, such as whether the vocal level feels balanced or whether the low end translates on other systems.
- Any known temporary issue, such as a guide vocal or a section that is not yet edited.
Avoid sending multiple unlabeled versions and asking the reviewer to guess which one is current. If comparisons are useful, identify the difference between each file and keep playback levels reasonably consistent. A louder version can seem better simply because it is louder.
7. Troubleshoot common export problems
The file sounds mono or one-sided
Check the master output assignment, channel format, and any bus routing that could leave one side empty. Confirm the export is set to stereo interleaved. If the DAW has a mono render option, make sure it is not selected. Re-export a short section and listen to both channels before rendering the full arrangement.
The ending cuts off
Extend the export range beyond the last note and enable effect-tail handling if available. Some DAWs stop exactly at the selection boundary, even when reverb or delay continues. If a hardware effect is part of the signal path, real-time rendering may be necessary; consult the device and DAW manuals for its capture requirements.
The file clips even though the session did not
Check whether the export applies normalization, a different master bus, or a format conversion that changes peaks. Look at the rendered file’s peak level and listen for distortion. Lower the appropriate output stage or disable unintended normalization, then export again. Do not assume a meter reading before the master chain represents the final file.
The file is too large to send
Keep the full-resolution WAV as the reference copy. You can create a separate high-quality compressed listening copy if the recipient only needs convenient playback, or use a file-sharing service that accepts larger files. Tell the recipient which copy to use for detailed review. Avoid repeatedly compressing an already compressed file; export both versions from the session when possible.
The recipient reports a format problem
Ask for the precise requested format and settings, then create a new export from the session. Confirm the sample rate, bit depth, channel layout, and filename before sending. If a player cannot open the file, try a standard PCM WAV export and verify it in another player; avoid converting through several formats, which can add unnecessary processing.
8. Adapt the workflow to your setup
A home-studio computer, interface, and DAW can produce a reliable review mix without specialized delivery hardware. The main limitation is the signal path: external analog processors, hardware inserts, or a separate recorder may require real-time capture and careful gain staging. Follow the manufacturers’ instructions for connecting and operating equipment, and verify that the recorded result includes the full stereo output.
If you are exporting on a computer with limited storage, render to a drive with enough free space and confirm the file finished writing before disconnecting it. For a laptop, connect power and avoid interrupting the session during a long real-time capture. If you use a portable recorder instead of a DAW export, check its input level, stereo mode, file format, and recording duration, then play the recording back before delivery.
For the next review round, keep the same export settings unless the feedback process calls for a change. That makes comparisons easier and helps everyone distinguish mix revisions from playback-level or format differences.