Audio Repair and Restoration
How to fix clipped and distorted audio in REAPER (and how much you can actually recover)
Published July 28, 2026
Clipping flattens the tops of your waveform and permanently deletes that part of the signal, so no tool fully restores it. If the clipping is light and occasional, a declip tool can rebuild a believable curve over the flat spots and get you a usable take. Free option: Audacity’s Clip Fix. Paid option: iZotope RX De-clip. REAPER has no stock declipper, but its stock plugins can make mild clipping less harsh. If the waveform looks like a solid block, the audio is not recoverable and re-recording is the honest fix.
Clipped and distorted audio is one of the most disheartening things to find after a take, because it usually means the moment is already gone. The first question is not which plugin to reach for. It is whether the recording can be saved at all. This article covers how to tell, what REAPER can and cannot do with stock plugins, which declip tools actually help, and how to stop it happening next time.
What clipping actually is
In a digital recording, 0 dBFS is the ceiling. When the incoming signal tries to go louder than that, the converter cannot represent it, so it simply flattens every peak at the maximum value. Those flat tops are not quiet or distorted versions of the original peaks. They are missing. The waveform detail that would have been there was never stored, and that is why clipping is so hard to undo.
Flattening the peaks also adds new high-frequency harmonics that were not in the original sound. That is the crackly, fuzzy, or crunchy edge you hear on a clipped vocal or a distorted interview. So a clipped recording has two problems at once: information is gone, and unwanted harshness has been added on top.
Deliberate analog-style saturation or soft clipping rounds the peaks gently and can sound warm, which is why it is used as an effect. Hard digital clipping squares the peaks off abruptly and almost always sounds bad. When people say a recording is “clipped,” they usually mean the harsh digital kind.
First, check how bad it is
How much you can recover depends almost entirely on severity, so look before you process.
Zoom in on the loud parts
In REAPER, zoom into the waveform at the loudest words or hits. Occasional peaks with short flat tops are the salvageable kind. Long stretches where the wave is a solid rectangle, sometimes called a “brick,” are not.
Listen to how constant it is
A few crackles on the biggest peaks is a light problem. Continuous fuzz through whole phrases means the signal was slammed for a long time and there is very little clean audio underneath.
Decide before you invest time
If a quick look shows mostly brick-walled waveform, be honest with yourself early. No plugin invents detail that was never captured, and re-recording will beat hours of repair.
The honest limits
Before any fix, here is what declipping and repair will not do, so you can set expectations:
- It will not perfectly restore the original sound. Declip tools make an educated guess at the missing curve, they do not recover the real data.
- It will not rescue heavily or continuously clipped audio. If the waveform is a solid block, the damage is permanent.
- It will not remove distortion that is baked into a loud, already-mastered file. That harshness is part of the render, not a layer you can peel off.
- It will not fix the performance timing or tuning. It only addresses the clipping.
With that framed honestly, mild clipping is often fixable enough to use, and that is worth doing.
What REAPER’s stock plugins can and cannot do
REAPER does not ship with a dedicated declipper, so its stock plugins cannot rebuild the missing peaks. What they can do is make mild clipping sound less offensive, which is sometimes all you need for a background or spoken part. Think of this as damage control, not restoration.
1. Turn down the clipped moments with clip gain
If only a few words clipped, the simplest move is to lower just those sections. Split the item around the loud part and reduce its item volume, or draw a volume envelope down over the peak. This does not un-clip the audio, but it stops the harsh peak from jumping out of the mix.
2. Tame the added harshness with ReaEQ
Clipping adds energy up high. A gentle high-shelf cut or a low-pass in ReaEQ, starting somewhere around 6–10 kHz and adjusted by ear, can soften the crackle. You are trading some brightness for less fizz, so use the least amount that helps and judge it in the full mix.
3. Smooth the edges with gentle saturation
A touch of saturation from a stock JS effect, or gentle multiband control with ReaXcomp, can round off the hard edges so they read as texture rather than a spike. This is masking, not repair. It can make a rough take passable, but it will not make it clean.
These stock moves reduce how bad clipping sounds. They do not restore the lost signal. For anything more than mild, occasional clipping on a non-critical part, a real declip tool will do far better.
Declip tools that actually reconstruct
A true declipper looks at the flat-topped peaks and interpolates what the curve probably looked like, drawing a plausible arc back over the gap. This is genuine reconstruction rather than masking, and it is the right tool when the clipping is light.
The free route: Audacity Clip Fix
Audacity is free, and its Clip Fix effect rebuilds lightly clipped peaks by interpolating the missing curve. Export the clipped section from REAPER as a WAV, open it in Audacity, and run Effect then Clip Fix. It has two settings: a Threshold of clipping (how close to maximum counts as clipped, default around 95 percent) and an amount to reduce amplitude so there is room for the rebuilt peaks to sit under 0 dBFS. Then bring the repaired file back into REAPER. Clip Fix only works well on mild, occasional clipping, and it assumes the top and bottom of the wave clipped at the same level, so a DC-offset correction first can help if only one side rebuilds.
The reconstructed peaks are taller than the flat tops they replace. If you do not leave headroom, the rebuilt curve would clip again immediately. Pulling the level down a few dB gives the new peaks somewhere to go.
The paid route: iZotope RX De-clip
If you do a lot of repair, iZotope RX includes a De-clip module that reconstructs clipped peaks and runs as a plugin you can load directly on a REAPER track or item. You set a threshold (or let it suggest one), preview, and process. It handles more severe cases more gracefully than a free interpolator, though it still cannot recover audio that was clipped into a solid brick. Other third-party declippers exist too. Name any of them, the same rule holds: lighter clipping restores better than heavy clipping.
A realistic workflow
- Diagnose. Zoom in. Occasional flat tops, keep going. Solid brick, stop and plan a re-record.
- Declip the light stuff. Run Audacity Clip Fix, or RX De-clip if you have it, on the affected section. Leave a little headroom for the rebuilt peaks.
- Clean up what is left. A small high cut in ReaEQ and gentle saturation can soften any residual edge.
- If it is stock-only and mild, lower the clipped moments with clip gain and tame the harshness, and accept it is damage control.
- If it is a brick, re-record. It is faster and it will sound better than any repair.
| Severity | What you hear | Realistic fix | Likely result |
|---|---|---|---|
| Light, occasional | Crackle on the loudest peaks only | Clip Fix or RX De-clip, then a small high cut | Usually usable |
| Moderate | Fuzz on several words or hits | RX De-clip, or stock damage control for non-critical parts | Sometimes usable |
| Heavy / brick | Continuous distortion, blocky waveform | Re-record | Not recoverable |
Stop it happening again
Clipping is far easier to prevent than to repair, and prevention is free. The fix is headroom.
- Set your input gain for peaks around
-12to-6 dBFS. Do a loud test take and turn the interface gain down until the biggest moments land there. That leaves margin for an unexpected loud word or hit. - Give a less predictable source more room. If a singer or guest gets loud without warning, aim lower and leave closer to
12 dBof headroom. - Record in 24-bit. A quieter recording in 24-bit still has plenty of resolution, so there is no reason to push levels toward
0 dBFSwhile tracking. - Watch the interface, not just REAPER. If the red clip light on your audio interface flickers, the signal is clipping before it even reaches the DAW, and no software setting can undo that.
Getting recording levels right is part of a clean signal path from the start. If your headphones also lag while you track, that is a separate issue covered in how to fix recording latency in REAPER.
Clipping deletes the peaks of your waveform, so no plugin fully restores it. Check severity first. Light, occasional clipping can be rebuilt with a declip tool like Audacity Clip Fix or iZotope RX De-clip, and REAPER’s stock plugins can soften mild cases. A brick-walled waveform is gone, so re-record it. Then prevent the next one by tracking with peaks around -12 to -6 dBFS.
Sources
- Cockos, “ReaPlugs” and REAPER User Guide (current version 7.78, July 2026) - REAPER’s bundled plugins (ReaEQ, ReaXcomp, JS effects); no stock declipper is included. reaper.fm/reaplugs, reaper.fm/userguide
- Audacity Manual, “Clip Fix” - reconstructs lightly clipped peaks by interpolation; Threshold of clipping and reduce-amplitude settings; effective only on mild clipping. manual.audacityteam.org/man/clip_fix.html
- iZotope, “How to repair a distorted audio track” - De-clip reconstructs clipped peaks; light clipping restores far better than heavy clipping. izotope.com
- Avid, “Gain staging guide” - recording with headroom below
0 dBFSto prevent clipping. avid.com