How to record audio

The essential answer

To record audio, select a microphone your device can use, allow the recording app or browser to access it, start capture, speak at a normal distance, stop, and play the file. The recording succeeded if you can understand your own words on playback at a normal listening volume. Seeing a microphone in a device list only means the system detected hardware. A moving meter only means some signal arrived. Neither proves the clip is clear or usable.

You can capture with the voice-recorder or voice-memo app that comes with most computers and phones, or with a web page that asks the browser for microphone access. The same permission and input-selection steps apply when you are checking a mic before a call. Camera access is a separate permission and does not record sound. A clean local clip also does not prove how you will sound to someone else on a live call.

What you need before you start

• A microphone: the built-in mic on a laptop or phone, a USB microphone, a headset boom, or earbuds that include a mic.
• A recorder: a system voice-memo or sound-recorder app, or a browser page that captures microphone input.
• Microphone permission for that specific app or site, in both the operating system and, for web tools, the browser.
• A quiet enough room that speech is not buried under fans, traffic, or other talk.
• Headphones for the playback check, so loudspeakers cannot feed back into the mic and fake a successful take.

Unmute hardware switches on headsets and confirm the OS and the app are not muted independently. If you use Bluetooth, give the earbuds a moment to connect and then re-select them as the input; the computer may still be pointed at the built-in mic.

Record on a Windows PC

• Open the built-in recorder (Voice Recorder or Sound Recorder, depending on the Windows version) or another app you already use to capture sound.
• If Windows prompts for microphone access, allow it. If capture stays silent, open system privacy settings, find Microphone, and turn access on for that app.
• Open the input or device list and choose the mic you intend to use. Skip display audio, HDMI devices, unused webcam mics, and virtual cables unless you know you need them.
• Speak while watching the input meter. Movement means the selected device is receiving signal. A still meter means the wrong device, a mute, a denied permission, or a disconnected mic.
• Start recording, say a short sentence at the distance you will actually use, then stop.
• Play the clip. Success is hearing that sentence clearly, without harsh breakup and without having to force the volume unusually high.

Record on a Mac

• Open Voice Memos, or in QuickTime Player choose a new audio recording.
• Allow microphone access if prompted. If the app never hears you, open System Settings, then Privacy & Security, then Microphone, and enable the app.
• Choose the correct input in the app or in Sound settings. Built-in, USB, and headset mics appear as separate devices.
• Record a short sentence and play it back. Success is the same as on Windows: intelligible speech in the file, not only a bouncing meter.

Record in a browser

• Open the page that records and wait for the browser’s microphone permission prompt. Allow it. A dismissed or blocked prompt looks like a dead mic even when the hardware is fine.
• If you blocked access earlier, open that site’s permissions in the browser and switch the microphone to Allow, then reload.
• If the page shows an input menu, select the same physical mic you just confirmed in system settings.
• Record a short sentence and play it in the page, or save the file and play it in a local player.

Browser permission and operating-system permission are stacked. Both must be on. The browser prompt only covers that site; it does not replace the OS privacy toggle, and a successful browser recording does not mean a separate call app is using the same device.

Record on a phone

• Open the phone’s voice-memo or recorder app. On the first launch, allow microphone permission.
• Hold the phone at a typical speaking distance. Covering the bottom edge or case cutout often muffles or kills the take.
• Start, speak a short sentence, stop.
• Play the clip with the ringer or media volume up and the phone unmuted. Success is clear speech in the playback, not only a waveform on screen.

How to tell detection, activity, and a real recording apart

Check	What it establishes	What it leaves untested
Microphone detection	The device appears in the system, browser, or app input list.	Whether any sound is arriving, whether it is your voice, and whether a saved file is usable.
Input activity	A meter or waveform moves when you speak, tap the mic, or make noise.	Whether the signal is the intended mic, whether words are intelligible, and whether a call app is using this same input.
Playback of a saved clip	The recorder wrote audio you can understand at normal listening volume.	How you will sound to someone else on a live call, after that service’s processing, or on a different network.

Use playback as the pass/fail test for recording. A moving meter with a silent file usually means the wrong device, an output path instead of an input, or a muted channel. Loud but muffled or harsh playback means the mic is receiving sound and the problem is placement, gain, wind, a covered port, or the mouth being too close.

If the recording is silent, quiet, or distorted

• Silent file, no meter movement: confirm the mic is plugged in or paired, unmuted, selected as the input, and allowed in both OS privacy settings and the app or browser. Then speak again.
• Meter moves, playback is silent: you may have recorded a different device than the one that showed activity, or the player is routed to a muted output. Switch output to headphones and open the file in a second player.
• Quiet but understandable: move closer, speak at conversation level, or raise that device’s input gain in system sound settings. Recapture rather than only boosting a near-silent file, which also boosts hiss.
• Harsh, crackling, or clipped: move back, lower input gain, and avoid brushing the mic. Recapture. Boosting a clipped take will not restore the missing peaks.
• Robot, dropouts, or delay on a Bluetooth headset: wait until the headset is fully connected, re-select it as input, or use a wired or built-in mic for the test.
• Sound from the room but not your voice: the selected input may be a webcam mic across the desk, a conference speaker, or an open laptop mic while you are wearing a headset. Choose the headset explicitly.

No single input-level number fits every microphone, operating system, and room, and no verified target in decibels was supplied for a stated setup. Treat the file as the measurement: speech should be easy to hear at a normal headphone or speaker volume, and the waveform, if the app shows one, should not be a flat line or a constant brick of peaks. Recapture after each change; adjusting a bad take is a poor substitute for a clean one.

What a local recording does not prove

A good clip on disk confirms that this computer or phone, this permission set, and this input can capture intelligible sound. It does not confirm camera video, virtual call backgrounds, or photo backdrops. It does not confirm that a meeting app has the same device selected, that echo cancellation will behave on the call, or that the other party’s connection will carry your voice. After the local test, open the call app you will actually use, choose the same microphone there, and do that app’s own audio check if it offers one.