In this guide
First establish whether the typing is entering a live call or is already in a saved recording. Improve the microphone-to-voice balance before increasing suppression, test quiet words while typing, and preserve timing when cleaning a recorded video.
To stop keyboard noise in your microphone, first select the correct microphone, improve its position relative to your mouth and keyboard, then test your calling application's noise suppression. A filter that makes a pause quiet can still damage words while you type. If the clicks are already in a recording, use an editing or separation workflow instead of changing live microphone settings.
There are two different jobs here. A meeting participant needs less typing sent to the call now. A video editor needs to repair a saved take without moving its dialogue out of sync. Saturalabs handles the second job through uploaded recordings; it does not install a virtual microphone, suppress a live call, or change your Zoom or Teams account.
Find where the keyboard noise enters
Check the microphone selected inside the application, not just the device selected by your operating system. A webcam or laptop microphone may still be active after you connect another microphone. Make a short self-test with the input you intend to use, and listen to that result rather than judging only a moving level meter.
| What happens | What to check first |
|---|---|
| Typing is loud even when you are not speaking | Input selection, microphone position and the app's suppression setting. |
| Typing is quiet in pauses but returns under speech | A gate may be opening, or suppression may not distinguish the overlap. Include simultaneous speech and typing in the test. |
| Desk taps produce a low thump | Compare microphone support and desk contact separately from the sound of keys in the room. |
| A saved recording contains key presses over a word | Keep the original and evaluate the exact overlap with local editing or source separation. |
| Only remote listeners hear the problem | Test the actual calling application. A local monitor may be hearing a different point in the processing path. |
Improve the voice-to-keyboard balance before turning up filters
Move the microphone closer to the speaking position when your microphone's instructions permit it, and keep it away from the keys. Then set a suitable recording level again. Turning gain down alone also makes the voice quieter; changing the geometry first gives you something different to compare.
RØDE's keyboard-noise guidance suggests a close speaking position of roughly 5–10 cm for its described setup and discusses reducing gain after positioning. Treat that as a starting point for a compatible microphone, not a universal distance. Check which side or end of your microphone is meant to face your mouth, and listen for breath noise or distortion as well as typing.
Compare one change at a time. Keep your normal speaking level and type the same short phrase. If practical with your existing setup, compare the microphone's current desk support with a position that changes its contact with the desk. Do not assume an expensive replacement microphone is necessary before you establish whether the problem is input selection, placement, room sound or mechanical contact.
Check Zoom's microphone mode for a live meeting
In the Zoom Workplace desktop app, open Settings and locate Audio. Review the microphone selection and the Microphone modes area. Zoom's official settings reference describes Noise removal as the default processing option. It also explains that Original sound for musicians turns noise suppression off. A music-oriented setting is therefore not an automatic solution to keyboard noise in an ordinary spoken meeting.
Try the normal noise-removal path, then compare speech with and without typing. Do not select a stronger setting merely because the pause becomes quieter: check the beginning of a quiet sentence and the last consonant too. Menu names and available controls can vary with app version, device and administrator permissions. Use the linked current reference if your screen differs.
Check Microsoft Teams noise suppression
For the Teams desktop workflow, Microsoft's noise-suppression instructions point to Settings and more, then Settings, Devices, and the Noise suppression control. The documented in-meeting route is More actions, Settings, then Audio settings. Microsoft says the selected suppression setting carries over to later calls.
Verify the input and repeat the same typing-and-speech test after changing it. Mobile controls are documented separately; do not assume every desktop, browser and phone has the same menu or level choices. A suppressed key press does not prove that all of your quiet speech is still being transmitted.
Use the same short test for every adjustment
Record yourself or use a suitable private test session. Keep the microphone, speaking level and keyboard task consistent, and make the comparison at a similar listening volume. This sequence is a repeatable evaluation method, not a measured demonstration or a promise that any named filter will remove your keyboard.
- Quiet speech: Say a complete sentence at your quietest normal level, without typing. Check the first word, breaths and the ending.
- Typing alone: Type a short phrase while you are silent. This checks what happens in pauses.
- Speech plus typing: Repeat the spoken sentence while typing. This is the important overlap check.
- Return to silence: Stop both and listen to the transition. Check for pumping, abrupt muting or a delayed return of room sound.
Keep the setting that gives the most useful compromise for the actual call, rather than the most dramatic silence. When listening instead of speaking, muting the microphone is another way to avoid sending typing. Remember to unmute before answering; it is not a repair for an already recorded click.
If the keyboard clicks are already recorded
Keep a copy of the original and locate a pause, a quiet word and a typing overlap. For clicks confined to pauses, lowering just those intervals in an editor may be enough. Preserve the intervals' duration if the recording accompanies video. Avoid turning every pause into digital silence without listening to the surrounding room tone.
The free local noise gate can lower quiet passages in a short MP3 or WAV while retaining the decoded timing. It cannot recognize keys: a loud clack may open the gate, and typing beneath a louder voice may remain. The silence remover does something different by shortening gaps. That changes later time positions and is unsuitable when the picture or other tracks remain unedited.
For repeated clicks overlapping wanted material, the recorded keyboard-noise workflow lets you describe the typing and inspect Background audio for the remaining mix. If the objective is speech alone, compare a voice-targeted attempt from the original and inspect Isolated sound. Separation can remove wanted consonants or leave clicks; a quieter background is not enough if the sentence is damaged. AI WAV downloads have account and credit requirements.
For a screen recording, retain the source start time and follow the audio replacement and sync guide. Do not put a shortened pause-removal export under unchanged video and expect the dialogue to stay aligned.
Why keyboard noise can remain after suppression
A key press can overlap the same moment as a quiet syllable. A level threshold cannot decide which source you wanted, and a model-based filter still has to estimate what belongs to speech. More processing can trade a smaller click for altered speech. Compare the result against the original rather than treating a lower noise floor as proof of a better recording.
If the voice was clipped, extremely faint or masked by a loud clack, a cleaner take may be more useful than another processing pass. Use the cleanup-method comparison to separate live suppression, level-based gating, noise reduction and recorded-source isolation before choosing another tool.