How to Test a Microphone on Linux and Ubuntu

You can test a microphone on Ubuntu or most other Linux distributions without installing extra software. The quickest check is the input level meter in the system sound settings. A short recording played back through your speakers or headphones gives a more complete result. This guide covers both methods, how to judge the result, and what to do if the mic stays silent.

Before you start

Connect the microphone and confirm any hardware mute is off. Many headsets, USB mics and laptop keyboards have a physical mute switch or key. If you use a headset with a single combined jack, the computer may need to detect it as a headset rather than headphones only.

The methods below run locally on your computer. The settings meter only displays the live signal. Command-line recordings are saved as ordinary files in the folder you choose and stay there until you delete them. Browser-based microphone testers work differently. Before using one, check whether it processes audio only in the browser or sends it to a server, and read its privacy terms rather than assuming either.

It also helps to know which sound server your system runs. Recent Ubuntu releases use PipeWire, which includes a compatibility layer for PulseAudio tools. Older releases use PulseAudio directly. Commands from the ALSA utilities (arecord, aplay, alsamixer) work with either.

Step-by-step instructions

Method 1: Check the input level in Sound settings

• Open Settings and go to the Sound section. On Ubuntu with GNOME you can also search for Sound in the Activities overview.
• Find the Input area and choose your microphone from the input device list. Laptops often show both an internal mic and any connected headset or USB mic, so pick the one you want to test.
• Make sure the input volume slider is not at zero and the input is not muted.
• Speak at a normal volume and watch the level indicator next to or below the input device. It should move as you talk and drop back when you stop.
• While you are here, check that the correct output device is selected so you can hear your test recording later.

The layout of the Sound panel varies between Ubuntu and GNOME versions, and other desktops such as KDE Plasma, Xfce or Cinnamon have their own audio settings. The idea is the same in each: select the input device, set its volume, and watch the meter.

Method 2: Use PulseAudio Volume Control for a detailed view

If the built-in panel shows too little detail, the PulseAudio Volume Control app (pavucontrol) is available in the Ubuntu repositories and also works on PipeWire systems. Install it with sudo apt install pavucontrol and open it. The Input Devices tab shows a live meter for each microphone, a mute button, and the port in use. The Recording tab shows which applications are currently capturing audio and from which device. The Configuration tab lets you change the card profile, which matters for Bluetooth headsets.

Method 3: Record and play back a test clip in the terminal

• List capture devices with arecord -l. Note the card and device numbers of your microphone.
• Record a five-second clip with the default input: arecord -d 5 -f cd test-mic.wav. The cd format records 16-bit stereo at a 44100 Hz sample rate.
• To record from a specific device, add it explicitly, for example arecord -D plughw:1,0 -d 5 -f cd test-mic.wav, replacing 1,0 with the card and device numbers from the list.
• Play the clip back with aplay test-mic.wav.
• On PipeWire systems you can use pw-record test-mic.wav and pw-play test-mic.wav instead. pw-record keeps recording until you press Ctrl+C.
• Delete the file with rm test-mic.wav when you no longer need it.

On PulseAudio or PipeWire systems, pactl list sources short shows available input sources by name. That helps you confirm which source is the default when several are connected.

Check the output

Listen to the recording through headphones if possible, because speakers can mask quiet problems. A good result has clear speech at a comfortable volume, no clipping or crackle on louder words, and a low hiss between phrases.

• Too quiet: raise the input volume in Sound settings or pavucontrol, or move closer to the mic.
• Distorted on loud sounds: the input level is too high. Lower it until loud speech no longer peaks the meter.
• Constant hum or hiss: listen for background noise from fans, chargers or cables, and try another port or a different microphone.
• Sound only in one ear: many mics are mono. Recording in stereo with the cd format can place the signal in one channel, which is normal for a test file.
• One device works in the test but not in an app: the app may be using a different input device than the system default.

A local test confirms that the system receives a usable signal. It does not measure frequency response or compare against a reference microphone. For video calls, also run the call app's own audio check, since apps may apply their own noise suppression and gain control.

Common problems and next steps

The meter does not move at all

Confirm the correct input device is selected and not muted, then check for a hardware mute. Open alsamixer in a terminal, press F6 to choose your sound card, and press F4 to show capture controls. Make sure the capture channel is enabled and its level is above zero; the space bar toggles capture on many cards. If arecord -l does not list the microphone, the system is not detecting the hardware. For USB mics, try another port or cable.

The microphone works in tests but not in one application

Check the input setting inside the application first. Snap and Flatpak apps need permission to record audio. For a snap, snap connections followed by the app name shows whether the audio-record interface is connected. For Flatpak apps, review the app's permissions in your desktop settings or a permissions manager. Browsers ask for microphone access per site, so check the site permission if a web call cannot hear you. Some desktop versions also include a microphone access switch under Privacy settings.

A Bluetooth headset microphone is missing or sounds poor

Many Bluetooth headsets offer a high-quality playback profile without a microphone and a separate headset profile that includes one. In Sound settings or the pavucontrol Configuration tab, switch the headset to a profile that includes the microphone, then test again. Audio quality in that mode depends on the headset and the codecs both devices support.

Audio stopped working after an update or configuration change

On PipeWire systems, restarting the user audio services often clears a stuck state: systemctl --user restart pipewire pipewire-pulse wireplumber. On PulseAudio systems, pulseaudio -k restarts the server. Neither command removes your settings. If the problem persists, unplug and reconnect the device, reboot, and repeat the recording test to see whether the mic is detected at the ALSA level.