In this guide
First find out whether the fault is in the recording, the exported file, or the playback setup. Channel extraction, fades, gain, noise reduction, source isolation, and waveform repair solve different problems. Keep the original and test the method on the exact damaged passage.
Why turning down clipped audio does not undo the damage
These four-second synthesized tones demonstrate one specific digital operation. They contain no recorded speech, music performance, AI processing or repair. Start at a comfortable volume. The files are not loudness matched; a quieter result is not proof of repair.
Clean synthetic tone
A 440 Hz sine at amplitude 0.25, with short outer fades. Stored sample peak: -12.04 dBFS.
Download WAV · 384,044 bytesGain doubled, then clipped
The clean samples doubled, then limited at ±0.25. The flattened peaks are already below file full scale. Stored sample peak: -12.04 dBFS.
Download WAV · 384,044 bytesClipped copy turned down
The stored clipped samples multiplied by 0.5. Its peak is lower, but the flattened shape remains. Stored sample peak: -18.06 dBFS.
Download WAV · 384,044 bytesThe common-scale plots show about two cycles from the middle of each file. The last copy is about 6.02 dB lower in sample peak than the clipped copy, yet its plateaus remain. Peak readings alone cannot diagnose all earlier overload; they also do not measure true peak or perceptual quality.
Each file is mono, 48 kHz, 16-bit PCM WAV, four seconds long. Read the exact generation method and limits or download the measurements and plotted samples. These three original WAVs and their measurements are available under CC0 1.0. They are separate from the audio test-file ZIP.
Audio repair online starts with identifying the fault. A file that will not open, a voice that only plays on the left, and a clipped word need different solutions. Uploading each to a source separator does not make them the same problem. First compare the original recording, the exported copy, and your playback setup.
Keep the untouched source. Note the timestamp and the word or sound that is wrong, then work on a copy. The goal is a useful recording with the wanted detail intact, not simply a quieter background.
Check whether the file or the playback setup is at fault
- Replay the same passage. Check the exact timestamp rather than comparing unrelated moments.
- Try another player and output. A fault that follows one pair of headphones or one app needs a playback investigation. A defect repeated at the same point across setups is stronger evidence that it is in the recording.
- Compare source and export. If the original is clear and only the delivery file is broken, return to that export step before applying cleanup.
- Check the separate tracks. An original microphone track or another take may be more useful than processing a mixed soundtrack.
A screenshot of a waveform cannot settle every diagnosis. Listen to the surrounding sentence, transient, or musical phrase as well as the suspected fault.
Match the problem to a repair method
| Problem | First check or treatment | What it cannot promise |
|---|---|---|
| File will not open | Compare another player and inspect a supported WAV header; re-export from a valid original if available. | A header report does not reconstruct missing file bytes. |
| Audio only on one side | Check headphones and routing, then inspect the existing left/right channels. | Extracting a channel does not recover a microphone that was never recorded. |
| Click at a new cut | Move the boundary or test a short edge fade. | An outer fade does not repair a damaged sound in the middle. |
| Recording too quiet | Measure the level and consider a deliberate gain change. | Gain raises noise too and leaves quiet/loud word differences intact. |
| Steady hiss or fan | Test noise-profile reduction when a matching noise-only sample exists. | More reduction can damage wanted speech or music. |
| Music or another source over speech | Try a focused source-isolation test and compare both outputs. | Separation can retain interference or remove wanted detail. |
| Clipped or distorted wanted sound | Find a cleaner take or test a dedicated repair method. | Lowering gain or describing clipped words does not reconstruct their peaks. |
When a recording will not open
Check that the transfer completed and compare the source's actual byte size with the received copy. Changing a filename extension is not conversion. If an editor can still open a valid original, make a new export rather than repeatedly editing the suspect copy.
The free WAV inspector reads supported RIFF/WAVE headers and reports stored encoding, rate, channels, declared duration, and actual bytes. It can flag certain truncated or unsupported layouts. It does not rewrite a broken header, recover absent samples, or establish that every reported file will play correctly. Read the WAV format guide for what those fields mean.
Saturalabs' online separation flow needs a supported, readable recording. It is not a corrupted-file recovery service.
Fix one-sided sound before estimating a source
A stereo file may have one useful microphone channel and an empty second side. The free channel splitter lets you preview and download the existing sides separately. Keep the useful side as mono if that fits your edit. Averaging it with silence instead halves its sample amplitude.
Check the one-ear troubleshooting workflow before discarding a side. When both speakers share the same channel, selecting it keeps both voices; channel extraction does not separate them.
Repair an edit click or a very short damaged region
If a click appeared only after cutting a clip, inspect the new boundary first. The free fade tool can soften a supported recording's outer edges. It does not find clicks automatically, crossfade an internal join, or replace damaged samples in the middle. The edit-click guide helps choose between moving the cut, fading an edge, and editing a join.
For a tiny defect inside otherwise usable audio, a dedicated editor may estimate a replacement from neighboring samples. Audacity's Repair effect is limited to selections of 128 samples or fewer and requires surrounding audio. At 48 kHz, 128 samples is about 2.67 milliseconds. It is not a tool for recreating a missing word or a long dropout.
Treat clipped peaks separately from background noise
Compare the clean, clipped and attenuated examples above. The clipping threshold in this controlled demonstration is below full scale. A damaged recording can therefore have a low sample peak after an earlier overload or gain change; an absent full-scale clipping warning is not a clean bill of health.
A prompt such as “the clipped words” does not tell a separator how to rebuild the original waveform. Lowering a distorted file's level makes the distortion quieter along with everything else. It does not undo clipping that already happened.
First play the unchanged source at a lower device volume and through another playback setup. If only loud playback is distorted, investigate the output path before altering the file. If the distortion follows the same words across players, compare the source and an earlier export to locate where it appeared.
Compare another microphone, an earlier export, or another take. For a repair experiment, Audacity's Clip Fix documentation describes estimating clipped regions and says it is most likely to help light clipping. That is a dedicated reconstruction attempt, not evidence that all distortion can be repaired. Listen to the wanted sound after the treatment, including consonants and transient attacks.
Reduce noise or separate an overlapping sound
For steady hiss or fan noise, a noise-profile tool can use a section containing only that background. Audacity's Noise Reduction guide recommends restrained reduction and listening to the removed residue for pieces of the wanted sound. A noise-only pause that does not match the difficult passage is a weak reference.
For music or a distinct sound overlapping dialogue, try describing the wanted speaker in the voice isolator. Review Isolated sound for that source and Background audio for the remaining mix. If the whole scene needs to survive except its music, the music-removal workflow explains targeting the music and reviewing the remainder instead.
Source isolation estimates audible parts of a readable mix. It can leave bleed, lose wanted detail, or introduce artifacts. Compare the hard overlap and the quiet sentence ending, not only a pause that became silent. The cleanup method chooser helps distinguish these cases from gates and local repairs.
AI separation accepts MP3, WAV, MP4, or MOV up to 50 MiB (52.43 MB). AI WAV downloads require an account and sufficient credits, with the cost shown in the product. The separate local utilities above are free without an account or audio upload; their supported formats and duration limits appear on each tool.
Measure levels after choosing a usable recording
The free peak normalizer applies one linked gain, while the LUFS meter measures integrated loudness and sample peak. Neither is a declipper or a noise-removal tool. An adjustment that raises a voice also raises noise still in the same recording.
Make one change at a time. Save the source filename, timestamp, method or prompt, and chosen result. Compare the final working copy in its actual edit and retain the original so a later export does not become your only source.
Common questions
Can every audio problem be repaired online?
No. Missing samples, heavily clipped speech, severe masking, and corrupt files can exceed the available evidence. Look for a valid original or another take before repeating processing.
Is audio normalization the same as audio repair?
Normalization changes an overall level. It does not recreate a clipped peak, fill a dropout, or independently change noise relative to speech.
Can a quieter result still be worse?
Yes. Check that names, breaths, word endings, musical cues, and wanted ambience remain useful. Less audible noise is not enough if essential detail disappeared.
