Drop your audio file here
or click the button below to browse
Choose Audio FileMP3, WAV, OGG, M4A ยท Max 30MB
Gaps shorter than this are left alone, to avoid choppy speech.
Analyzing and processing your audio...
Automatically detect and remove quiet sections from your audio. Works instantly in your browser โ no upload, no account needed.
or click the button below to browse
Choose Audio FileMP3, WAV, OGG, M4A ยท Max 30MB
Gaps shorter than this are left alone, to avoid choppy speech.
Analyzing and processing your audio...
This tool detects quiet or silent sections in an audio file and removes them, producing a tighter recording with dead air trimmed out. Choose a sensitivity threshold, preview the result, and download the cleaned-up audio.
Processing happens entirely in your browser using the Web Audio API โ your audio is never uploaded to a server.
The threshold determines how quiet a section needs to be before it's considered silence. A lower threshold only removes near-total silence, leaving quiet background noise intact โ safer if your recording has soft passages you want to keep. A higher threshold removes more โ including quiet breathing, faint background noise, or soft speech โ which can tighten a recording further but risks cutting parts you wanted to keep if set too aggressively. The minimum duration setting prevents very brief natural pauses (like the gap between words) from being removed, which would otherwise make speech sound unnaturally choppy.
There's no universal "correct" threshold โ the right setting depends heavily on how your specific recording was made. A recording made in a very quiet room with a good microphone close to the speaker will have a low noise floor, meaning even a conservative threshold can effectively detect true silence. A recording made in a noisier environment, or with a microphone further from the speaker, will have more background noise present even during "silent" moments, meaning a low threshold might not detect those moments as silence at all. If your first attempt removes too little, try increasing the threshold gradually; if it removes too much โ cutting into quiet speech, or making the recording feel unnaturally tight with no breathing room โ reduce the threshold or increase the minimum silence duration, and re-process the original file again.
It's worth knowing that aggressive silence removal changes more than just the length of a recording โ it changes its pacing and feel. Natural speech includes pauses for breath, thought, and emphasis; removing all of these can make a recording feel rushed or even slightly unnatural, like the speaker never pauses to breathe. For podcast-style content, a moderate amount of silence removal โ tightening obviously long pauses while preserving natural conversational rhythm โ usually produces a better listening experience than removing every possible gap. If your goal is simply to cut a long recording down to a more manageable length rather than to create a highly polished edit, a more conservative setting that removes only clearly excessive pauses is often the better choice.
Automatic silence detection works well for clearly separated speech with distinct pauses, but recordings with continuous background noise, music, or overlapping sounds may not have "true" silence to detect. After processing, review the result โ if too much or too little was removed, adjust the threshold and minimum duration and try again.
After removing silence, you might want to trim the start or end further with Audio Trimmer, or compress the result with Audio Compressor.
Background noise that's above the silence threshold won't be detected as silence. If results aren't as expected, try adjusting the threshold to better match your recording's noise floor.
The minimum duration setting helps avoid this by only removing gaps longer than natural pauses between words. If results sound choppy, try increasing the minimum duration.
You can re-process the original upload with different settings as many times as needed before downloading.
The processed audio is exported as a WAV file.
No, processing happens entirely within your browser.