REAPER Audio Workflows

Why your REAPER render sounds different from the project (and how to find the cause)

Published November 16, 2026 · Updated November 16, 2026

Quick answer

A render is not a recording of what came out of your speakers. REAPER runs the mix again and writes the result to a file, and some things you hear during playback are deliberately left out. The most common cause is a plugin in the Monitoring FX chain, such as headphone or room correction, which the REAPER user guide says does not show up in renders. After that, check the render Source, any muted or soloed tracks, the Bounds, the Channels and format, Postprocess normalize, and whether a plugin behaves differently when rendered offline. Most cases come down to one setting, not the mix itself.

Forum answers to this question usually name one cause, and it is often the wrong one for your project. The checks below are in order of how often they explain an obvious difference and how quick they are to rule out. Work down the list and stop when you find it.

Everything here comes from the official REAPER user guide (version 7.85) unless it says otherwise. Menu names can shift between versions, so if a label does not match yours exactly, look for the nearest equivalent.

First, name the difference

Listen to the render and the project back to back and decide which of these you are hearing. It points you to the right check.

What you hear in the renderCheck first
Different tone overall, often more or less bass or top end1. Monitoring FX
A part is missing, or only one track is there2. Source, mute and solo
The ending is cut off, or a reverb tail is missing3. Bounds
Thinner, hollow, or something disappears; highs sound swishy4. Channels and format
Clearly louder or quieter than the project5. Postprocess normalize and limit
One effect or instrument sounds wrong, or different every time6. Offline rendering

1. Check the Monitoring FX chain

REAPER has a separate FX chain that sits on your hardware outputs, after the master. Open it with View, Monitoring FX, or hold Shift and click the FX button on the master track. The guide is direct about it: these FX do not show up in renders, do not affect the metronome and are not stored in the project file. It suggests using the chain for analysis plugins or to compensate for the acoustics of your room.

So if you mixed with a headphone or room correction plugin here, everything you heard was corrected, and the file is not. That is by design. The correction belongs to your listening setup, not to the song, and a listener's speakers will not have it.

What to do depends on what is in there:

2. Check the Source, and anything muted or soloed

Open File, Render (Ctrl+Alt+R) and look at Source. For a normal export it should be Master mix, which the guide says sends the output of the master track to one file, including master volume, pan, mute, FX and automation.

Other source options render something different on purpose:

Then look at the mixer. A Master mix render contains whatever reaches the master, so a track you muted to check something, or a solo you forgot to clear, ends up in the file too. Clear all solos and confirm every track you want is unmuted before you render.

3. Check the Bounds and the ending

Bounds decides how much is written. Time selection renders only the highlighted range, so if the selection stops where the last note stops, the reverb or delay tail after it is cut. Entire project is the safer choice for a finished song.

If the end is still cut short, the guide notes that with Entire project, markers named =START and =END define where the render starts and stops. Put an =END marker after the last tail has died away. Then listen to the last few seconds of the new file, not just the start.

A related case: if you render a section from the middle of a song and the reverb or delay that should already be ringing at its start is missing, turn on 2nd pass render. The guide says it plays the audio once before rendering so that FX tails are applied.

4. Check Channels, sample rate and format

Dither only applies when you reduce bit depth, for example to 16-bit for CD. It is a subtle change and, in our view, unlikely to explain a difference you can hear plainly.

5. Check Postprocess normalize and limit

The Postprocess button in the Render dialog can normalize the file to a loudness or peak target and add a brickwall limit. If it is on, the file's level is changed after the mix, so it will not match your master meter. A brickwall limit on top of an already loud mix can also flatten it.

Louder almost always sounds better on first listen, and quieter sounds worse, even when nothing else changed. Before you judge the tone, make sure both are playing at the same level. The reasoning is the same as in level-matching a plugin before you A/B it.

To see what the file will measure without writing it, click Dry Run (no output). The guide describes a stats window showing the waveform, loudness statistics and any clipping.

6. Check for plugins that behave differently offline

By default REAPER renders at Full-speed, faster than real time. The guide adds a short warning that some plugins might perform and sound different when rendered offline. If one effect or instrument sounds wrong in the file and everything else is fine, change the speed setting to Online render, which plays the mix in real time while rendering, or try 1x offline, and render again.

Some plugins also do not produce identical output on every pass. Sound On Sound's REAPER Q&A points out that modulation effects whose cycle is not tied to the transport, and instruments that pick samples at random, will differ slightly each time. A small variation like that is normal. If a sample-based instrument is missing notes at the very start of a queued render, the guide lists an option to delay the queued render so samples can load.

How to compare the two fairly

Comparing a file in a music player against the project in REAPER mixes up two questions. To separate them, enable Add rendered items to new tracks in the Render dialog so the file comes back into the project. Solo that track and bypass the master FX with the master track's FX enable/disable button, so the master chain does not process the render a second time. Sound On Sound flags exactly that doubling as a common reason a re-imported render does not match.

Now switch between the project (render track muted, master FX on) and the render (solo on, master FX bypassed). Monitoring FX affect both equally here.

Change one setting at a time

Changing four render settings at once and re-rendering tells you the problem is gone, not what caused it. Change one, render, compare, then move on. When the settings are right, save them with the Presets button so the next export starts from a known state.

What these checks will not fix

Takeaway

Open Monitoring FX first, because anything there is heard but never rendered. Then confirm Source is Master mix with no stray mutes or solos, Bounds cover the whole tail, Channels are stereo, the format is a WAV at the project rate, Postprocess is doing only what you asked, and offline rendering is not changing a plugin. Compare the render back inside REAPER with the master FX bypassed before you decide anything else is wrong.

Sources

  1. Cockos, Up and Running: A REAPER User Guide v7.85 (November 2026, official HTML edition), read November 16, 2026. Section 6.13 Hardware Output FX Monitoring (View, Monitoring FX or Shift-click the master FX button; these FX do not show up in renders, do not affect the metronome and are not stored in the project file); 21.3 Rendering A Project (Source, Bounds including =START and =END markers, Sample Rate, Channels, On or Off-Line Speed, Resample mode, Postprocess normalize and brickwall limit, 2nd pass render, Dither, Presets, Delay queued render to allow samples to load, Add rendered items to new tracks, Dry Run, and the note that some plug-ins might perform and sound differently if rendered offline); 21.4 Dry Run Render Stats and Options; 21.5 Render to File: Source Options (Master mix, Selected tracks, Selected tracks via master, Selected media items); FX Enable/Disable toggle button for bypassing a track's FX. dlx.reaper.fm/userguide/html
  2. Matt Houghton, "Q. Why aren't my rendered and live plug-in sounds nulling?", Sound On Sound, April 2025: modulation and randomised plugins differ between passes, and a re-imported render routed through the same bus is processed twice. soundonsound.com
  3. Community context only, not technical proof: recurring forum threads in current search results about renders and exports not matching playback, across REAPER and other DAWs (for example homerecording.com, Steinberg, Ableton and Toontrack forums), show the problem is common and that answers usually name a single cause.

All sources checked on November 16, 2026. Render dialog labels are as described in the v7.85 guide and can change between versions. The comparison method above is a StudioRescue workflow built from the documented options, not a procedure from the guide, and was not tested on a specific project for this article. No link above is an affiliate link.