Skip to content

REAPER Render Settings for Streaming

How to make mixes translate cleanly online

Mixing your track to sound great in your DAW is one thing—hearing it get mangled by YouTube or Spotify is quite another. Maybe your transients turn mushy, the stereo image narrows, or the top end suddenly feels like someone put a blanket over your speakers. That’s not your imagination; it’s the extra processing that streaming platforms apply.

Every major service performs some combination of loudness normalisation, lossy compression, and sample-rate conversion to keep playback consistent between tracks. Those steps are helpful for listeners, but they can introduce artefacts if your master isn’t prepared for them.

The good news? By understanding what those platforms do—and choosing smart REAPER render settings for YouTube and Spotify—you can make your mix translate cleanly almost anywhere. In this guide we’ll:

  • Break down how streaming services actually process your audio
  • Confirm practical targets for sample rate, loudness, and true peak
  • Show you how to set up robust REAPER render presets
  • Point you to trusted REAPER educators like Kenny Gioia, Jon Tidey, Myk Robinson, and Adam Steel for deeper dives

If you’re still in the prep stage of your project, it’s also worth starting with a clean, organised session. For that, check out How to Prepare Multi-Tracks for Mixing—it will save you headaches long before you hit Render.

How Streaming Platforms Process Your Audio

Before you choose export settings, it helps to know what happens after upload. Streaming services do not play your file as-is. Instead, they:

  1. Decode your file
  2. Measure and adjust its loudness
  3. Potentially apply extra limiting
  4. Re-encode to their own delivery codec and bitrate

The goal isn’t sabotage; it’s to keep listeners from having to ride the volume knob every track. But if your master is too hot, too clipped, or too heavily limited, this processing can expose every weakness.

Let’s unpack the main factors.

1. Loudness Normalisation (LUFS Targets)

Most platforms normalise to a target level measured in LUFS (Loudness Units Full Scale):

  • YouTube: roughly around −14 LUFS Integrated (analyses often show a band around −13 to −15)
  • Spotify (Normal mode): −14 LUFS Integrated
  • Apple Music (Sound Check): around −16 LUFS Integrated

If your track is louder than the target, it gets turned down; if it’s quieter, it may be turned up slightly or left alone. A master slammed to −10 LUFS won’t actually sound louder online than a tasteful −14 LUFS master—the platform just turns it down by about 4 dB.

Engineer and educator Keith Livingston points out that −14 LUFS is not a mandatory “upload or else” target; it’s simply the level services aim for on playback. The real priority is that your dynamics are controlled and musical so that when the platform adjusts the level, your mix still feels punchy and balanced. Pushing to extreme loudness only to be turned down later can actually lose impact once the dust settles.

Good further reading on this:

If you want to understand the tools used to manage that dynamic behaviour, see Compressor vs. Limiter: Mix Dynamics on this site—it explains how each processor shapes loudness and punch.

2. Codec Conversion (Lossy Formats)

No matter how pristine your original file, streaming platforms almost always deliver a lossy compressed version to listeners:

  • YouTube: AAC or Opus streams (typical bitrates around 128–256 kbps depending on quality and device)
  • Spotify: Ogg Vorbis (≈96–320 kbps depending on plan and settings)
  • Apple Music: AAC around 256 kbps

These codecs dramatically reduce file size, but they can introduce artefacts—especially with:

  • Very bright cymbals and hi-hats
  • Dense high-frequency content (synths, distorted guitars)
  • Hard limiting or clipping
  • Aggressive stereo widening

Lossy encoding can also produce inter-sample peaks, where a WAV file that never exceeded 0 dBFS suddenly clips after conversion to AAC or MP3. That’s why streaming guidelines usually recommend leaving a bit of true peak headroom.

A few helpful resources:

And importantly: always upload a full-quality master (WAV or FLAC), not an MP3 you’ve already compressed. Re-encoding a lossy file just stacks quality loss on top of quality loss.

3. Sample Rate Considerations

Most streaming and video platforms operate internally at 48 kHz, especially for anything involving video.

  • YouTube specifically recommends audio encoded at 48 kHz or 96 kHz, which matches film and broadcast standards.
  • Many aggregators and distributors are now very comfortable with 24-bit/48 kHz as their preferred upload format.

If your project is at 44.1 kHz, services will typically resample it to 48 kHz. Good resampling can be transparent, but it’s still an extra processing step you can avoid by handling it yourself with a high-quality offline export.

Useful references:

Practical takeaway:
Unless you have a compelling reason not to, render your streaming master at 48,000 Hz. It plays nicely with YouTube, TikTok, Reels, and most video workflows—and Spotify, Apple, etc. are perfectly happy with it.

Recommended REAPER Export Settings (YouTube, Spotify & More)

Now that we know what happens to your audio, let’s confirm the REAPER settings that survive the trip through YouTube, Spotify, Apple Music and short-form video platforms.

These recommendations line up well with current industry practice and the guidance from mastering engineers and tools like iZotope and Mastering The Mix.

🎚 1. Sample Rate: 48 kHz

Set your render sample rate to 48 kHz in almost all online scenarios.

In REAPER:

File → Render… → Sample rate: 48000

REAPER will upsample any 44.1 kHz project using its own high-quality algorithm, which is generally preferable to a mystery resampler on the platform’s side.

Why 48k?

  • Matches YouTube’s recommended formats
  • Works cleanly with most NLEs (Premiere, Resolve, etc.) if you’re dropping the audio into video later
  • Accepted without issue by Spotify, Apple Music and most aggregators

If you later need a 44.1 kHz version for CD or legacy uses, you can create that from the 24-bit master.

🔊 2. Bit Depth & File Format: 24-bit WAV (PCM)

For your primary master, export to uncompressed 24-bit WAV (PCM):

  • Format: WAV
  • Bit depth: 24-bit
  • Dither: ON if you’re coming from 32-bit float (REAPER’s internal mix engine)

This is the file you upload or send to your distributor.

Why not upload MP3 or AAC?

  • Every major streaming service will encode to its own lossy format anyway.
  • If you give it a lossy master, you’re asking it to re-encode a degraded source, which often sounds noticeably worse.

This advice is consistent across mastering houses and educators (including Lost Stories Academy and Mastering The Mix): upload lossless, full-resolution audio and let the platform do the compression from that.

If you need small files for reference or sending to clients, render separate MP3/AAC versions—but keep those clearly labelled as “reference only”, and never feed them to the platform as your official master.

📈 3. Loudness Targets: LUFS & True Peak

A sensible one-size-fits-most streaming target looks like this:

  • Integrated Loudness: around −14 LUFS for music streaming (YouTube, Spotify, Amazon, etc.).
    • For Apple Music, −16 LUFS is often cited as their rough Sound Check reference.
  • Short-form video (TikTok/Reels/Shorts): typically −12 to −14 LUFS in real-world practice (creators often master slightly louder here).

Crucially, these are guidelines, not hard rules. Keith Livingston and others stress that you shouldn’t obsess over hitting exactly −14. Anywhere in the −12 to −16 LUFS window—with good dynamics—is workable. Some reputable engineers go as high -8 LUFS on their mastered tracks.

What matters more is:

  • Your track isn’t absurdly out-of-line compared to others
  • You’ve left enough true peak headroom to survive encoding
  • The dynamics feel musical, not crushed

For deeper reading:

True Peak Ceiling

Set your final brickwall limiter to about −1.0 dBTP maximum. Many engineers even prefer −1.0 to −1.5 dBTP for dense or very loud material.

Why?

  • Lossy codecs can cause peaks to rise slightly after conversion
  • A WAV that tops out at −0.1 dBFS can clip above 0 dBFS once encoded

Spotify explicitly recommends leaving at least −1 dBTP (and as much as −2 dBTP for extremely hot masters) to avoid distortion. AES guidelines for streaming also converge on ≤ −1 dBTP as best practice.

In REAPER, you can use ReaLimit or a third-party limiter with true-peak detection and oversampling. Set:

  • Ceiling: −1.0 dBTP
  • Oversampling: ON (if available)
Dynamic Range

Streaming normalisation actually rewards more dynamic mixes. If you squash everything to −8 LUFS and then it gets turned down to −14, it still sounds flat and lifeless—just at a lower level.

Many modern masters for streaming aim for at least DR 8–9+ (a healthy dynamic range) so that the music still breathes. Both Mastering The Mix and iZotope highlight that a balanced, well-controlled dynamic range is more important than hitting a particular LUFS number.

If you want to understand how compressors and limiters can help you keep that sense of movement while still controlling peaks, circle back to Compressor vs. Limiter: Mix Dynamics.

🎧 4. Auditioning Lossy Compression (Optional but Recommended)

Because so much of streaming is about lossy codecs, it’s smart to preview what your mix will sound like after compression.

REAPER doesn’t have a built-in “live codec preview” plugin, but you can mimic the effect:

  1. Open File → Render…
  2. Change Output Format to MP3, OGG, or another lossy type
  3. Choose a bitrate similar to your target platform (e.g. 256 kbps AAC for a YouTube-style check)
  4. Render a quick test, then listen critically

Ask yourself:

  • Do cymbals or S sounds go crunchy or lispy?
  • Does the stereo image collapse or become phasey?
  • Does the limiter sound like it’s working harder after encoding?

If you hear ugliness, adjust the mix or master: tame harsh highs, ease back on wideners, or back off the limiter a touch. Then re-render your 24-bit WAV and upload that.

Helpful tools and educators here include:

REAPER Export Preset Examples

To make this repeatable, save your favourite settings as presets in REAPER’s Render dialog. Then your “streaming-ready master” is only two clicks away.

🎥 Preset: “YouTube Upload – WAV Master”

  • Sample rate: 48,000 Hz
  • Channels: Stereo
  • Format: WAV, 24-bit PCM
  • Limiter ceiling: −1.0 dBTP
  • Target loudness: around −14 LUFS Integrated

This is also perfect for general music distribution and most video-focused platforms.

🎶 Preset: “Spotify / Streaming – WAV Master”

Same as the YouTube preset:

  • 48 kHz, 24-bit WAV
  • Around −14 LUFS, −1 dBTP ceiling

Spotify (and most other platforms) will normalise on playback, so a single “streaming master” is usually all you need.

📱 Preset: “Short-Form Video (TikTok / Reels / Shorts)”

  • Sample rate: 48,000 Hz
  • Format: 24-bit WAV
  • Loudness: −12 to −14 LUFS, depending on content and genre
  • Limiter ceiling: −1.0 dBTP

Short-form feeds are often louder and more chaotic, so it’s common to push a touch hotter—but you still don’t need to go brickwall-insane.

🎚 Preset: “Client Preview – 256k AAC”

  • Sample rate: 48,000 Hz
  • Format: AAC at ≈256 kbps

Use this preset only for quick previews or email-friendly files. Your actual upload should still be the lossless 24-bit WAV.

While you’re creating presets, it’s also worth giving your project a clean export structure. How to Name Your Tracks offers a practical system for labelling channels and exported files so that multi-tracks, stems, and masters all stay obvious and organised.

Export Workflow Tips (Step-by-Step)

Here’s a streamlined process you can follow every time.

1. Finalise Your Mix

  • Check in both stereo and mono (use a mono utility on your master).
  • Listen loud and quiet on a couple of different speakers or headphones.
  • Fix any harshness, piercing elements, or out-of-control low end now.

If you haven’t already, use How to Prepare Multi-Tracks for Mixing as a pre-flight checklist for session cleanliness.

2. Open the Render Dialog

File → Render…

  • Render bounds: Entire project (or time selection for a specific version)
  • Output file name: e.g. Artist_SongName_Master_48k24.wav

Good naming—again, see How to Name Your Tracks—saves you from “FinalMix_RealFinal_v7.wav” syndrome.

3. Set Format & Options

  • Sample rate: 48,000 Hz
  • Channels: Stereo
  • Output format: WAV, 24-bit PCM
  • Dither: On if rendering from 32-bit float

If you’ve saved a preset (e.g. “YouTube Upload – WAV Master”), simply select it and most of these will be recalled automatically.

4. Check Loudness & True Peak

  • Insert JS: Loudness Meter/Peak or a third-party meter like Youlean Loudness Meter on the master.
  • Play the full song to capture Integrated LUFS, Short-Term LUFS, and True Peak.
  • Aim for around −14 LUFS Integrated and ≤ −1.0 dBTP.

If you’re way off:

  • If LUFS is much higher (e.g. −9), ease off the limiter and/or mix bus gain.
  • If LUFS is far lower (e.g. −20) and that’s not an artistic choice, you may bring up your overall level while keeping peaks in check.

5. Engage True Peak Limiting

On your master bus:

  • Use ReaLimit or another limiter with true-peak mode.
  • Set ceiling around −1.0 dBTP.
  • Enable oversampling if available.

Listen carefully to your loudest sections. If you can hear the limiter pumping or dulling the mix, back off the threshold or adjust upstream compression.

6. Render the WAV

Click Render and let REAPER export your 24-bit WAV.

Once it’s done:

  • Drag the WAV back into a fresh REAPER project or onto a new track.
  • Null-check or compare to your mix bus output to ensure there are no surprises.
  • Listen from top to tail to make sure tails and fades are intact.

7. Optional: Codec & Loudness Penalty Check

  • Render a quick MP3/AAC/OGG from the same master and listen for artefacts.
  • Use Loudness Penalty (https://www.loudnesspenalty.com) or Youlean presets to see how much different platforms will turn your track up or down.

If YouTube shows a trivial penalty (e.g. −0.5 dB) and Spotify shows something similar, you’re in the sweet spot. If it’s −7 dB, you probably mastered way too hot and may want to reclaim some dynamics.

8. Upload with Confidence

Now you can confidently upload your 48 kHz / 24-bit WAV to YouTube, your distributor (for Spotify/Apple/etc.), or your short-form platforms. You’ve:

  • Matched common streaming loudness expectations
  • Left true-peak headroom for codec conversion
  • Delivered a lossless master
  • Checked for harsh codec artefacts ahead of time

At this point, the platform is doing relatively light lifting instead of rescuing a problematic master.

My Final Thoughts

Streaming platforms will never sound exactly like your uncompressed mix in a treated room—and that’s okay. We’re trading a little bit of perfection for the ability to reach listeners everywhere, instantly (and yes, share an unreasonable number of cat videos).

By taking control of your render settings in REAPER, you’re working with the algorithms instead of against them. A solid 48 kHz / 24-bit WAV, a sane loudness range, and a true-peak ceiling around −1 dBTP put you right in the lane that YouTube, Spotify, Apple and others expect.

These aren’t abstract theories; they’re echoed by engineers and educators who live in this space every day—people like Kenny Gioia, Jon Tidey, Adam Steel, Myk Robinson, and Keith Livingston. Their combined message is consistent:
Focus on clarity and dynamics, export the best-quality master you can, and let the platforms handle the rest.

Once you’ve saved your presets, rendering becomes an easy, repeatable part of your workflow rather than a fresh puzzle every time. You get to spend more energy on the music and less on guesswork.

I’d Love to Hear Your Thoughts…

  • Which platform gives you the most trouble when it comes to mix translation—YouTube, Spotify, Apple Music, or something else entirely?
  • Have you created your own REAPER render presets for different platforms? If so, what settings have worked best for you?

Share your experiences (and any horror stories you’ve tamed) in the comments—I’d love to hear what’s worked in your world.

Tags:

Leave a Reply

Your email address will not be published. Required fields are marked *