Practical Mixing
How to use REAPER's stock limiter without squashing your track
Published October 16, 2026
REAPER's stock brickwall limiter is ReaLimit, and the thing to understand before you touch it is that it works by transferring your threshold up to your ceiling. Lower the threshold and the whole track gets louder, not just the peaks. So set the ceiling first (try -1.0 dB), then lower the threshold only until the loudest moments show a few dB of gain reduction, and stop. Most squashed home masters are the result of one control being pulled much further than the track could take. It is very fixable, because nothing has been baked in until you render.
Almost every home producer hits the same wall. The mix sounds fine, you render it, you play it next to a released track, and yours is noticeably quieter and smaller. The obvious move is to put a limiter on the master and push it. That does make the track louder. It also, past a certain point, makes it flat, breathless and tiring, and most people cannot tell exactly where that point was.
This article is about the limiter that already ships with REAPER, what each of its controls actually does according to the official manual, and how to find the point where you should stop. It is deliberately not a full mastering guide.
What ReaLimit actually does
ReaLimit ships with REAPER, so there is nothing to install. Add it to the FX chain of your master track, as the last plugin in the chain.
The REAPER User Guide describes the mechanism plainly, and it is worth reading twice because it explains the squashing problem on its own. ReaLimit lets you set a threshold and a ceiling, and it then transfers sound from the threshold to the ceiling. Sound that comes in at the threshold goes out at the ceiling. No signal can leave above the ceiling, and anything above the threshold is compressed.
The manual's own worked example: if the threshold is set to -6 dB and the ceiling to 0 dB, the overall signal is boosted by +6 dB to carry the threshold up to the ceiling, and input above -6 dB is compressed so it peaks at exactly 0 dB.
The threshold control is a loudness control, not a safety control. Dropping it by 6 dB turns everything up by 6 dB and then flattens whatever that pushed past the ceiling. That is the whole squashing mechanism in one sentence, and it is why “just pull it down until it is loud enough” goes wrong.
Set it up in this order
Put it last on the master
ReaLimit goes at the end of the master track's FX chain. If anything else sits after it, that plugin can push peaks back above your ceiling and the ceiling stops meaning anything.
Set the ceiling, and leave it
Start at -1.0 dB. This is the only control you set once and stop thinking about. It decides the highest level that can leave the plugin.
Lower the threshold slowly
Play the loudest section of the track, not the intro. Lower the threshold until the meter shows a few dB of reduction on the biggest moments and nothing at all in the quiet parts.
Bypass and compare
Toggle the plugin off and on. If the limited version sounds louder but less exciting, you have gone too far. Raise the threshold until the life comes back.
Why the ceiling is not 0 dB
A sample peak of exactly 0 dBFS is not the same as the actual peak of the waveform between samples, and lossy encoding on streaming platforms can push a file slightly over. Spotify's own guidance for artists is to keep true peak below -1 dB, and below -2 dB if your master is louder than their normalization target, because louder tracks are more prone to distortion when encoded. Leaving a dB of room costs you nothing you can hear.
ReaLimit has a True peak option, which the manual describes as choosing whether to show true peak, a more accurate reading than plain peak. Turn it on so the number you are reading is the one that matters. Double-clicking either fader restores it to its default value, which is a quick way out if you lose your place.
Release is in dB per second, not milliseconds
This one catches people out, because most limiters elsewhere label release in milliseconds and a lot of writing about ReaLimit repeats that assumption. In ReaLimit the release field is expressed in dB/sec: it governs how quickly the limiter stops working once the signal drops back below the threshold.
The manual gives the two failure modes directly. Too long and you will hear audible pumping, where the whole track breathes in time with the loudest elements. Too short and you get distortion artefacts. If you are not sure, leave it where it starts and fix loudness with the threshold instead. Release is a control to reach for when you have already heard a specific problem, not one to set preemptively.
The remaining controls
| Control | What the manual says it does | Practical starting point |
|---|---|---|
| Threshold | Signal at this level is transferred up to the ceiling; anything above it is compressed | Lower only until you see a few dB of reduction at the loudest moments |
| Brickwall ceiling | The hard limit; no signal can be output above it | -1.0 dB for streaming, lower if your master is loud |
| Release | How quickly limiting stops after the signal falls below the threshold, in dB/sec | Leave at its default until you hear pumping or distortion |
| Constant gain | Manages threshold and ceiling so that either will be moved relative to the other | Off while you are learning, so you can see the two controls act independently |
| True peak | Whether to show true peak, a more accurate reading than peak | On |
| Performance | High quality (the default) or low latency | High quality for rendering; low latency only if it is causing monitoring delay while you track |
| Metering | Which channels are displayed; the manual notes this affects display only, not processing | Leave on All |
There is also an in and out mode on the right-click menu offering stereo, multi-mono and multi-stereo. In stereo mode all channels are compressed based on an analysis of them summed together, in multi-mono each channel is analysed and compressed separately, and in multi-stereo each pair is treated independently. For an ordinary stereo song or voice track, stereo mode is what you want, because it keeps the two sides moving together.
The manual points out that ReaLimit is not confined to the master. It can be used on folders to glue or push up a submix, or on individual tracks carrying pre-mixed or bounced stems. A gentle instance on a busy drum or backing-vocal bus is often more useful than more limiting on the master.
How much gain reduction is too much
There is no universal number, and anyone who gives you one is guessing. What is reliable is the method: judge it by what you hear when you bypass, not by the number on the meter.
A useful working budget for a home mix is to keep reduction into single digits on the loudest moments and to see the meter resting at zero through the quieter sections. If the limiter is working constantly from start to finish, it has stopped being a limiter and become a loudness effect, and the cost shows up as a track that sounds smaller the longer you listen.
If you need a lot of reduction to reach a level you are happy with, the honest read is that the limiter is being asked to fix the mix. Pull it back and look at the balance first. If vocals are the part that keeps disappearing, setting the vocal level against the instrumental solves more than the limiter will.
Why chasing loudness is mostly self-defeating
The reason your track sounds quieter than a released one is usually not that you need more limiting. It is that you are comparing at matched fader positions rather than matched loudness, and streaming platforms remove most of the difference anyway.
Spotify normalizes playback to -14 LUFS under the ITU 1770 standard, applying negative gain to tracks mastered louder than that and positive gain to quieter ones. So a track crushed to be loud is turned back down on playback, and what survives the turn-down is the reduced dynamic range you paid for it with. The measurement that decides this is loudness over time, not peak level, which is why a limiter alone is a poor tool for the job.
If you want to know what your track actually measures rather than guessing, install a free LUFS meter and read the integrated value over the whole track. For spoken word the target is a different number entirely, covered in the podcast loudness guide.
What a limiter will not do
- It will not fix a mix that is out of balance. Limiting an unbalanced mix makes the loudest element louder relative to everything else, which usually makes the balance worse rather than better.
- It will not undo clipping or distortion that is already in the file. Damage recorded on the way in is a repair job, not a mastering one. See how to fix clipped and distorted audio in REAPER.
- It will not add width, depth or excitement. Those come from arrangement, mix decisions and the recordings themselves.
- It will not make a quiet, thin mix sound full. It will make a quiet, thin mix louder and still thin.
- It will not guarantee your track survives encoding if the ceiling is at
0 dB. That is what the headroom is for.
Used carefully, a limiter catches the few peaks that are stopping you raising the overall level, and buys you a modest amount of loudness without an audible cost. That is the whole job. It is a last small step, not the step that makes a home track sound professional.
If it still does not sound right
- It sounds louder but duller. You are limiting too hard. Raise the threshold until the transients come back, and accept the lower level for now.
- The whole track breathes or pumps. Release is too slow for this material, or you are asking for far too much reduction. Reduce the amount first, then adjust release.
- There is a gritty edge on loud moments. Release may be too fast, producing distortion artefacts. It can also be clipping upstream, so bypass the limiter and check whether the edge is already there.
- The render is louder than what you monitored. Check that nothing sits after ReaLimit in the master chain, and check whether any render-time normalization is enabled. The render settings guide covers where those options live.
- It is still quieter than commercial tracks. That is expected and largely irrelevant once platform normalization is applied. Compare at matched loudness before you decide you have a problem.
ReaLimit transfers your threshold up to your ceiling, so the threshold control is really a loudness control. Set the ceiling to about -1.0 dB, turn on true peak, then lower the threshold only until the loudest moments show a few dB of reduction and the quiet parts show none. Bypass often. If you need heavy limiting to be satisfied, the mix is the thing to fix, not the limiter.
Sources
- Cockos, Up and Running: A REAPER User Guide v7.81, section 16.14 “ReaLimit: The Brickwall Limiter”, pages 335 to 336 – threshold and ceiling transfer behaviour and worked example, release expressed in dB/sec and its pumping and distortion failure modes, Constant gain, True peak, Performance, Metering affecting display only, the stereo, multi-mono and multi-stereo modes, and the note that ReaLimit is not confined to the master. Retrieved October 16, 2026. reaper.fm/userguide
- Spotify for Artists, “Loudness normalization” – playback normalized to
-14 dB LUFSper the ITU 1770 standard, negative gain applied to louder masters and positive gain to quieter ones, true peak guidance of below-1 dBand below-2 dBfor masters louder than the target. Retrieved October 16, 2026. support.spotify.com
No listening tests or measurements are claimed in this article. Settings are given as starting points to adjust by ear, not as universal values.