Music production involves dozens of format decisions — from the initial recording through mixing, mastering, and distribution to every platform. Get them wrong and you either waste storage on unnecessarily large files or introduce quality degradation that compounds at every stage.

The governing principle is simple: stay lossless until the final delivery step. Every recording, every bounce, every stem, every mix revision should be WAV or AIFF. Lossy compression (MP3, AAC, OGG) happens once — at the very end, when the mastering engineer or distributor converts your lossless master for streaming and download platforms. One generation of lossy encoding is inaudible at modern bitrates. Two or more is not.

This guide covers the complete format pipeline from tracking through distribution, with specific recommendations for each stage.

Session Formats: Recording and Tracking

Every track recorded in your DAW should be WAV (or AIFF on Apple platforms) at 48 kHz / 24-bit minimum. This is non-negotiable for professional work.

ParameterRecommendedAcceptableAvoid
FormatWAVAIFFMP3, AAC, OGG
Sample Rate48 kHz44.1 kHz, 96 kHzBelow 44.1 kHz
Bit Depth24-bit32-bit float16-bit

Why 48 kHz over 44.1 kHz: If any track might be used in video content (music videos, sync licensing, YouTube), 48 kHz avoids sample rate conversion at the video editing stage. If you're producing exclusively for CD release, 44.1 kHz is fine.

Why 24-bit: Recording headroom. At 24-bit, you can record at -18 dBFS average (the widely recommended "sweet spot" that emulates analog levels) and still have 126 dB of clean dynamic range. At 16-bit, the same recording level leaves you with only 78 dB before the noise floor.

Why not 96 kHz: At 96 kHz, file sizes double, disk I/O doubles, and plugin CPU usage increases (some plugins oversample, others process twice as many samples per second). The audio quality benefit for final playback is nil. Use 96 kHz only if your workflow involves heavy pitch-shifting or time-stretching where aliasing might be an issue.

Stem Delivery and Collaboration

When sending individual tracks or stems to a mixing engineer, collaborator, or remixer, the format matters:

  • Format: WAV, always. Not FLAC (some DAWs don't import FLAC directly), not MP3 (quality loss), not your DAW's native format (Logic/Ableton/Pro Tools session files aren't interchangeable).
  • Sample rate and bit depth: Match your session settings. If you recorded at 48/24, export stems at 48/24. Never upsample (44.1 → 48) or increase bit depth (16 → 24) for stems — this adds data without adding quality.
  • Start point: All stems should start at the same point (bar 1, beat 1, or session start). This ensures the mixing engineer can drop all files into a new session and they align perfectly. Export from the start of the session, not from where audio first appears.
  • Naming convention: Clear, consistent names. "01_Kick.wav", "02_Snare.wav", "03_Bass_DI.wav", "04_GTR_Left.wav". Numbered prefix ensures correct ordering in file browsers.

For transferring large stem packages (a 40-track session can easily be 5-10 GB as WAV), compress as ZIP or use cloud storage. ZIP doesn't alter the audio data — it's fully lossless file-level compression.

Mixing: Working Format and Bounces

During mixing, your DAW processes audio internally in 32-bit or 64-bit float. The source files are 24-bit WAV, but every plugin, fader movement, and bus summing happens at float precision. This provides unlimited headroom — intermediate stages can exceed 0 dBFS without clipping.

When you export (bounce) a mix:

  • Mix revisions: WAV, 48 kHz, 24-bit (or 32-bit float). Keep every revision. Storage is cheap. "Mix_v3_vocal_up_1dB.wav" is worth the 50 MB when the client asks you to go back to "the version from last Tuesday."
  • Print stems (grouped submixes for mastering): WAV, matching session settings. Common stems: drums, bass, guitars, keys, vocals, effects. The mastering engineer may want these for parallel processing or if the mix needs targeted adjustments.
  • Pre-master mix: WAV, 48/24 or 48/32f. No limiting, no final processing. Peaks at -3 to -6 dBFS to give the mastering engineer headroom. This is the file you send to mastering.

Never bounce to MP3 or AAC during production. Not for reference mixes, not for client previews, not for "quick checks." Lossy bouncing introduces artifacts that may mask or mimic mixing issues. If you need to send a quick reference, bounce to WAV and let the recipient's playback handle any necessary transcoding.

The Mastering Chain: Format at Every Stage

Mastering is where format decisions have the most downstream impact, because the mastering output is what reaches listeners.

Mastering Input

Accept: WAV or AIFF, 44.1-96 kHz, 24-bit or 32-bit float. Reject: anything lossy. The mastering engineer needs the best possible source material. If a client sends an MP3, the mastering session starts with compromised audio that can't be recovered.

Processing

All processing happens at 32-bit or 64-bit float internally. EQ, compression, limiting, stereo enhancement, and loudness optimization — all at full precision. The mastering engineer's session doesn't touch the file format until the final export.

Output Formats

The mastering session produces multiple deliverables:

  • CD master: WAV, 44.1 kHz, 16-bit (with dither — TPDF or noise-shaped). This is the Red Book standard. ISRC codes embedded if applicable.
  • Hi-res master: WAV or FLAC, 48-96 kHz, 24-bit. For hi-res stores (Qobuz, HDtracks) and hi-res streaming (Apple Music Lossless, Tidal HiFi Plus). No dither needed when staying at 24-bit.
  • Digital distribution master: WAV, 44.1 kHz, 16-bit or 24-bit. This goes to your distributor (DistroKid, TuneCore, CD Baby), who handles encoding to MP3, AAC, Vorbis for each streaming platform.
  • Archive master: WAV, session sample rate, 24-bit (or 32-bit float). The highest-quality version for your archives. Encode to any target from this.

Distribution: What Each Platform Receives

When you upload through a distributor, they handle the encoding:

PlatformYou UploadThey Encode To
SpotifyWAV or FLAC, 44.1+ kHz, 16/24-bitOGG Vorbis 96-320 kbps
Apple MusicWAV or FLAC, up to 192 kHz/24-bitAAC 256 kbps + ALAC lossless
Amazon MusicWAV or FLACMultiple tiers including FLAC lossless
YouTube MusicWAV or FLAC (via video upload)AAC 128-256 kbps
TidalWAV or FLAC, up to 96 kHz/24-bitFLAC (HiFi), AAC (standard)
BandcampWAV or FLAC, 16-24 bitMP3 V0, FLAC, AAC, OGG, WAV (buyer chooses)

The takeaway: always upload the highest quality lossless master you have. Let the platforms handle encoding to their target formats. Never upload MP3 to a distributor — they'll re-encode it, compounding artifacts.

Sample Libraries and Plugin Compatibility

If you work with sample libraries (Kontakt, Splice, Loopmasters), format compatibility matters:

  • WAV: Universal. Every sampler, every DAW, every plugin reads WAV. Deliver samples as WAV.
  • AIFF: Common in Apple-centric workflows. Most samplers read AIFF natively. Logic and Apple Loops use AIFF.
  • FLAC: Growing support but not universal. Kontakt doesn't natively read FLAC as of recent versions. Convert to WAV before loading into samplers.
  • MP3/OGG: Some game engines (Unity, Unreal) import these directly for compressed audio assets. For music production, never use lossy samples — artifacts in source material become amplified through processing.

When creating your own sample libraries: 48 kHz / 24-bit WAV is the standard. Include tempo and key information in filenames or metadata. Trim start and end points cleanly. Normalize to -1 dBFS peak if providing one-shots; leave dynamic range intact for loops.

Session Backup: Formats and Strategy

Your production files are the raw material from which everything else derives. Losing a session with 40 tracked instruments is losing months of work. Backup strategy by format:

  • Session files (.als, .ptx, .logicx, .rpp): Platform-specific, not interchangeable. Back up to at least two locations.
  • Audio files (WAV/AIFF): These are the actual recordings. Back up separately from session files — they're the irreplaceable part.
  • Bounce archive: Every mix revision, every mastered version. WAV for active projects, FLAC for long-term archival (50% smaller with zero quality loss).
  • Plugin presets and recall sheets: Document your processing chain. If a plugin update breaks compatibility, you'll need to recreate settings.

Storage math: A typical album session (40 tracks × 4 minutes × 48 kHz × 24-bit) is roughly 10-15 GB. With mix revisions and bounces: 20-30 GB. A 4 TB external drive holds 130-200 album projects. Invest in two drives — one working, one backup.

Converting Production Audio Files

Common production conversions: preparing stems from mixed formats, converting for distribution, creating reference copies.

Key conversions: WAV to FLAC (archival) | FLAC to WAV (importing into DAW) | WAV to MP3 (reference copies) | AIFF to WAV (cross-platform stems) | WAV to AAC (Apple reference) | FLAC to MP3 (promotional copies) | MP4 to WAV (extracting audio from video)

The format pipeline for music production is WAV in, WAV through, and WAV/FLAC out — with lossy encoding happening exactly once at the final distribution step. Every deviation from this principle risks introducing artifacts that compound through the production chain. Storage is cheap; re-recording a session because you discovered artifacts in your only copy is not.

Need to prepare audio for distribution or archival? Convert WAV to FLAC, FLAC to WAV, or AIFF to WAV — free at ChangeThisFile.