Remove Background Noise in Audacity: The Noise Profile Walkthrough

Why Audacity asks for a noise profile

Audacity does not decide what noise looks like. It asks you to show it. The noise profile is a short sample of the recording where only the background is present, and it teaches the reduction filter which frequencies belong to the room rather than the voice. Without that sample, the tool has to guess, and guessing usually means removing parts of the speech along with the noise.

That design is why Audacity's manual describes noise reduction as best suited to constant noise and recommends keeping the applied amount modest. A steady hiss, a fixed hum, or a stable fan bed gives the profile something consistent to learn. A door slam or a passing car does not, because those events never repeat in the same way.

The workflow below assumes you have a recording and a few free seconds at its start or end that contain no speech. If the file has no noise-only section, record ten seconds of room tone before the next take; it makes every future cleanup easier.

The exact workflow, step by step

The sequence is short, and the order matters:

1. Open the recording and save a copy as your working file, leaving the original untouched.
2. Find five to ten seconds where only the background is audible, with no speech, clicks, or movement.
3. Select exactly that section with the mouse.
4. Open Effect > Noise Reduction and click Get Noise Profile. The dialog closes; Audacity has learned the profile.
5. Select the entire track with Ctrl+A (Cmd+A on macOS).
6. Reopen Effect > Noise Reduction. Start with a conservative reduction amount rather than a strong one.
7. Click Preview, listen to a quiet pause and a consonant-heavy sentence, then apply only if the voice survived.

Choosing the noise sample correctly

The profile is only as good as the sample, and the manual's guidance is easy to get wrong in practice: the selection must contain only the noise, with no speech, breath, or clicks, and it should come from the same part of the session as the material you are about to clean. A profile taken before someone moved the microphone may not match the file's later sections.

Ten seconds is a comfortable default. Shorter samples can miss variation in the bed; much longer ones mostly add time. If the recording has no suitable section, choose the quietest few seconds you can find, accept that the profile is approximate, and keep the reduction lighter to compensate.

What the controls actually do

The dialog's three controls ask different questions. The reduction amount sets how much level the filter removes at the learned noise frequencies; higher values remove more and risk more voice. Sensitivity decides how aggressively the filter treats sounds similar to the profile. Frequency smoothing spreads the reduction across neighboring frequencies so the result sounds less like a comb.

The practical translation: leave sensitivity and smoothing near their defaults at first, and change only the reduction amount between passes. One variable at a time makes the comparison meaningful, and the manual's advice about restraint makes more sense after you have heard an over-reduced voice once. If a pass does not sound right, return every control to its default before the next attempt, so the new result is not contaminated by the last experiment.

Reading the artifact signs

A few textures tell you the pass went too far. Watery or swirling consonants mean the filter is chasing speech detail. A hollow, thin voice means the reduction cut into the body of the sound. Pumping, where the background seems to open and close around phrases, means the profile no longer matches the noise across the whole file.

The fix for all three is the same: undo the effect, return to the original, and run a lighter pass. If even a light pass produces artifacts, the file is a candidate for a different tool rather than more reduction; the artifact-recovery pattern in fixing metallic voice after noise reduction applies here too.

Undo, iterate, compare

Audacity applies the effect to the working file, which is exactly why the first step of the workflow says to save a copy. Ctrl+Z undoes the pass, and when a second attempt is needed, run it from the original rather than stacking reduction on an already-reduced track.

The comparison file matters just as much when the result seems good. Keep the original open in a second window and switch between the same three moments; the difference between quieter and better is easiest to hear side by side rather than from memory.

Gate versus reduction in Audacity

Audacity also ships a noise gate, and the two get confused constantly. A gate silences audio below a threshold, which means it cleans the pauses but leaves the steady bed untouched while someone is speaking. A reduction filter lowers the bed underneath the speech. The gate manual is explicit about its trade-offs: set the threshold too high and it will cut breaths and the quiet tails of words.

If your recording's problem is a bed under dialogue, the gate is the wrong tool alone. If the problem is a noisy pause between clean sentences, the gate can be the right finishing touch after a light reduction.

One useful order for a stubborn file: reduce the steady bed lightly first, then check whether a gate is needed at all. Many recordings gain nothing from a gate once the bed is lower, and every extra processor is another chance to clip a breath or a word ending.

When a lighter online pass beats a long Audacity session

Audacity rewards patience. Finding the noise sample, tuning the pass, and checking artifacts can take twenty minutes for a file that a single-purpose tool handles in a few. Neither path is better in general; they fit different jobs.

For one file with a steady bed, a SimpleClean pass with an Original/Cleaned comparison gets you a decision quickly, and the free-tools comparison lays out when each route makes sense. For a series that needs identical settings every week, Audacity's control is worth learning, and the six-step workflow covers the shared discipline both routes depend on.

Export and compare

The export step is where a good pass becomes a usable file:

1. Listen once more before exporting, with the same three passages you previewed.
2. Export a WAV when the destination allows it, or the highest-quality format that fits the workflow.
3. Name the exported file clearly as the cleaned version and keep the untouched original beside it.
4. If the cleaned version fails the listening check later, redo the pass from the original rather than processing the processed file.

What neither approach fixes

Reduction and gates both work on what is present in the file. They cannot repair a clipped syllable, a dropout, or two people talking at once, and a room's echo is a reflection problem rather than a noise problem. If the recording's main issue is a roomy, hollow sound, the echo versus reverb diagnostic is a better first stop than another reduction pass.

Prevention before the next recording

The cheapest cleanup is the one the recording does not need:

• Move the microphone closer and lower the gain to match.
• Record ten seconds of room tone at the top of every take.
• Turn off fans and appliances that add a steady bed.
• Keep each take as its own file so a failed experiment never contaminates the source.

Related guides

The same profile logic applied to a single tone is covered in removing hum from audio online, and how to remove background noise from audio walks the six-step version of this workflow for any tool.