The work is executed in the page through browser workers, WebAssembly, Web Audio, or WebGPU as stated.
Noise Remover
Bring the voice forward. Reduce room noise, hiss, and low-level background texture in recordings.
Before and after previews appear here.
What does noise remover do?
Noise removal estimates speech and background texture frame by frame. SoundTools runs the RNNoise neural filter on 10 millisecond frames in a dedicated WebAssembly worker, then blends the filtered and original signals.
A real local processor, not a decorative upload box
RNNoise WebAssembly runs after you choose a source and explicitly start the operation. The audio samples remain in browser memory; SoundTools does not send the selected media to an application endpoint.
Set the reduction mix from a light cleanup to the fully filtered signal, then compare the original and processed players. Results remain available for preview and download only in the current tab. Closing or refreshing the page releases those temporary objects.
How to use noise remover
- 01
Choose the local source
Open a compatible file in the dedicated workbench at the top of this page. The browser validates and decodes it without an upload step.
- 02
Set the useful controls
Set the reduction mix from a light cleanup to the fully filtered signal, then compare the original and processed players.
- 03
Process, check, and export
Run the local processor, inspect the status and preview, then save Noise-reduced WAV when the result is ready.
What this tool actually does
Clear limits are part of a useful tool. These values describe the processor currently running in this page.
Runtime and model assets may be downloaded, but the selected file is not attached to those requests.
The dedicated workbench exposes only formats it can actually produce in the current browser.
Useful reasons to open noise remover
- Voice memos
Reduce steady fan, room, or device noise behind speech.
- Interview cleanup
Improve intelligibility before editing or transcription.
- Remote-call excerpts
Clean one local recording without handing it to a cloud service.
Questions about this tool
Answers based on the current browser processor—not promises about a future version.
01Is my audio uploaded for processing?
No. Audio samples stay in browser memory. The page may download a codec or model asset, but it does not send the selected file with that request.
02Why can the first run take longer?
This tool uses RNNoise WebAssembly. A browser may need to download and initialize that runtime before the first operation; later runs can reuse cached assets.
03Can I preview the result before saving?
Yes. Audio-producing tools expose local result players, while analysis and transcription tools show their detected data before download.
04What happens when the browser is unsupported?
The workbench reports the missing capability instead of uploading the media or pretending that processing is still running.