Reproduce it first: watch the meter and waveform while you stay silent
Noise is not one problem. A steady hiss, a low hum at a fixed pitch, random crackles and pops, a voice that sounds robotic or underwater, and audio that drops out every few seconds all have different causes in different parts of the chain. Lumping them together as 'my mic is noisy' is why so much advice fails. The first job is to listen carefully and put the noise in the right category. This guide assumes the microphone is picking you up but the result sounds bad. If nothing registers at all, start with our guide on a microphone that is not working; if your voice is clean but faint, the guide on a microphone that is too quiet comes first.
Open our mic test, allow microphone access, and then say nothing. Hold still, hold your breath for a moment, and watch the input level meter and the real-time waveform for ten seconds or so. In a quiet room a healthy microphone sits almost motionless near the bottom of the meter and the waveform is close to a thin flat line. If the meter hovers a little way up even in silence, or the waveform is a band of constant thickness rather than a line, there is continuous electrical noise riding on the signal. That is the fingerprint of hiss or hum.
The opposite pattern is a meter that stays quiet and then jumps sharply and irregularly, with the waveform showing thin vertical spikes or brief gaps where the signal simply vanishes. Those are crackles and dropouts, and they usually come from a bad contact or interrupted data rather than from anything acoustic. A useful trick is to gently wiggle the cable and touch the area around the plug while watching the waveform. If the spikes appear in time with your hand, the cause is physical and you have already narrowed it down enormously.
Finish with the short record and playback feature: speak a few normal sentences and listen back. The meter and waveform reveal how big the noise is and what shape it has, but the garbled, robotic or underwater varieties change the character of your voice rather than adding something on top, and only your ears can judge that. The recording is processed entirely in your browser and is never uploaded, so repeat it after each change below and compare like with like.
Classify by sound: hiss, hum, crackle, robot voice, cut-outs
Constant hiss, the sound of air escaping, is almost always a gain problem. Every microphone and preamplifier generates a little noise of its own, and the more input volume or microphone boost you apply, the more that self-noise is amplified along with your voice. The 3.5 mm input on inexpensive motherboard audio is a frequent offender because its preamp is not especially quiet, and on USB microphones noise on the USB power line can add to the floor. If backing the boost off a step and moving the microphone closer to your mouth clearly reduces the hiss, you have confirmed the category.
A low hum or a steady buzz at one pitch is electrical interference. The classic cause is a ground loop: the microphone or audio interface and the computer are earthed through different paths, and the tiny voltage difference between those two grounds becomes audible. A poorly shielded 3.5 mm cable draped over a power adapter or power strip does the same thing, and a laptop that is silent on battery and hums the moment the charger is plugged in is the textbook case. If you are on a laptop, unplug the charger and test again. Hum that vanishes on battery power points squarely at the charger or the grounding.
Crackles, clicks and pops are momentary interruptions of the signal. On the physical side the usual suspects are a loose 3.5 mm jack, a cable whose internal conductors are about to break, and a USB port or hub that cannot supply steady power. On the digital side, a sample-rate mismatch between the device and the app, or an audio driver that fails to deliver data on time, produces regularly spaced ticks or short dropouts. As a rule of thumb, noise that responds to moving the cable is physical, and noise that gets worse when the computer is busy is digital.
A robotic, underwater or smeared voice is rarely the microphone itself; it is a transport or processing problem. It appears when USB bandwidth is saturated or the CPU is too busy to process audio in time, when a Bluetooth headset drops to its low-quality hands-free profile, and when noise suppression in Discord, Zoom, Teams or a tool such as NVIDIA Broadcast is working too hard and removing parts of your voice along with the noise. Regular cut-outs every few seconds or minutes usually trace back to wireless interference, USB selective suspend, or the computer's power management putting the device to sleep.
Isolate the cause: port, cable, device, app, driver, in that order
Once you know what kind of noise you have, change one variable at a time and see whether the noise follows. Start with the changes that take seconds. Move a USB microphone or a wireless headset's dongle to a different USB port, and prefer a port on the back of the motherboard over a hub, a monitor's USB ports, or the case's front panel. For a 3.5 mm microphone, switch from the front jack to the rear one. If the noise changes the instant you change ports, the port's power or its contacts are involved.
Next, the cable. If your microphone or headset uses a detachable cable, swap it for another. If there are extension cables or adapters in the path, remove all of them and connect directly. Longer and cheaper cables pick up more interference. Then test the device itself by plugging the same microphone into a different computer, or a phone, and running our test there. Noise that travels with the microphone belongs to the microphone or its cable; noise that stays behind belongs to the original computer, its ports, its power supply, its drivers or its software.
After that, the app. Our test shows you the signal much as the browser receives it from the operating system, with none of the voice processing a call app adds, which makes it a good reference point. If it sounds clean here but turns robotic or crackly only in one particular program, that program's processing settings are the cause. If the noise is already present here, it is entering the chain below the application layer, in the hardware, the operating system or the driver. The driver comes last, once hardware and applications have been ruled out.
Software fixes: switch off enhancements, match sample rates, drivers, power saving
For diagnosis, temporarily disable every piece of voice processing you can find. On Windows, the classic Sound control panel's Recording tab leads to the device's properties, where some devices show an Enhancements tab or options for noise suppression and echo cancellation. In your call apps, turn off automatic gain control, noise suppression and echo cancellation, then record again. These features hide noise, but pushed too far they also hollow out your voice and create the underwater effect, and when several programs run them at once each one reprocesses the output of the others with strange results. With everything off, the true character of the noise becomes clearer and the cause is easier to pin down.
Regular ticking or short dropouts often come from mismatched sample rates. In the Windows Sound control panel, open the microphone's properties and look at the Advanced tab: the Default Format field shows a value such as 44100 Hz or 48000 Hz. If that differs from what your playback device, your call app or your audio interface's control software is using, the conversion between them can glitch. Set them all to the same value; 48000 Hz is a safe choice for calls and streaming. The exclusive-mode options on the same tab govern whether one program can seize the device and lock others out, which is worth checking at the same time.
Newer is not automatically better where drivers are concerned. Sometimes the generic driver installed by Windows Update is less stable than the one published by the motherboard or microphone manufacturer, and sometimes the reverse is true. If the noise started right after a driver update, roll it back from Device Manager rather than hunting for something newer. Most USB microphones and headset dongles work without any extra driver at all, but if a manufacturer's utility is installed, check that it has not switched on effects of its own.
Cut-outs every few seconds or minutes very often involve USB selective suspend. In the Windows Power Options control panel, open the advanced settings of your active power plan, expand USB settings and set USB selective suspend to Disabled. In Device Manager, the Power Management tab of each USB Root Hub has a checkbox allowing the computer to turn the device off to save power, which you can clear as well. Laptops in particular sometimes misbehave after sleep or after the screen turns off; unplugging and replugging the device fixes it for the moment, but the power management settings above are the lasting cure.
Hardware fixes: isolators, cables, power and placement
If a hum or buzz has been confirmed as a ground loop, the fix is to break the ground connection somewhere in the signal path. For analog 3.5 mm connections there are small inline adapters sold as ground loop isolators, which sit between two cables and block the noise current without affecting the audio. For USB microphones and audio interfaces, a USB isolator does the equivalent job. One caution: USB isolators support different USB speeds depending on the model, and some are not suitable for devices that need high-speed transfer, so check which USB speed your microphone requires before buying.
Shorter, better-shielded cables are the general rule. Cheap 3.5 mm extension leads in particular tend to be poorly shielded and behave like antennas for interference. Routing matters too: keep audio cables away from power adapters, power strips, the back of the monitor and the computer's power supply, and do not bundle them alongside mains cables. The microphone body itself can pick up interference from a monitor, a wireless router or a phone that is charging, so try moving it a hand's width or more away from those.
Hiss and crackle caused by unstable USB power respond well to a powered USB hub, one with its own mains adapter. Power from a computer's USB port is shared among everything connected to it, and a hub with its own supply gives the microphone a steadier source. The reverse is also true: if your microphone shares an unpowered hub with a webcam and an external drive, the hub itself may be the problem, so compare against the microphone plugged directly into a motherboard port. For wireless headsets, move the dongle from the back of the computer to the front, or better still onto the desk on a short USB extension, to shorten the radio path to the headset and reduce dropouts.
Signs that the microphone itself is failing
If you have worked through the isolation steps and the noise still follows the microphone, meaning it sounds the same on another computer, through another cable and on another port, the fault is most likely in the microphone or its fixed cable. Sound that cuts out or crackles when you flex the cable just behind the plug or where it enters the microphone body is the classic sign of internal conductors breaking. With a detachable cable you simply replace the cable; with a fixed one, repair or replacement is the realistic option.
A condenser microphone that suddenly hisses far more than before, or whose sensitivity drops sharply, may have a moisture problem. Capsules used in humid rooms, or positioned where a lot of breath reaches them, can absorb enough moisture to raise their noise floor, and a few days in a dry place sometimes restores them. Dynamic microphones are far less sensitive to humidity, but a hard drop can damage the internal element and leave the sound thin or noisy.
On headsets, crackling from the hinge where the boom rotates is a common sign of age. If the sound changes every time you move the joint, the contacts inside have worn, and while cleaning may help for a while it tends to come back. Leave our test running with the waveform visible and move the hinge and each section of the cable one at a time; you will see exactly which point triggers the spikes, which is useful evidence when deciding between a repair and a replacement.
To summarise the whole method: listen and classify the noise, then change the port, the cable, the device and the app one at a time to see which side the noise follows, then address software processing, sample rates and power management, and finish with hardware such as an isolator or a powered hub if the electrical side needs it. Repeating the same measurement in our mic test at each step, with the level meter, the waveform and a short recording, turns guesswork into something you can see and hear.