OBS Not Recording Microphone Audio? Here Are 8 Fixes (Step-by-Step)

You hit record, finish a full take, and open the file to find silence where your voice should be. OBS recognized your microphone, the session ran without errors, and yet the audio track is empty. This is one of the most common recording failures in OBS Studio, and it almost always traces back to a configuration mismatch rather than broken hardware. Work through the eight fixes below in order and stop as soon as audio returns.

Why OBS Isn’t Capturing Your Microphone Audio?

Each cause below is independent. A single mismatch can produce total silence even when the rest of your setup is correctly configured. Scan this list to get oriented, then start at Fix 1.

• Wrong input device selected: OBS is listening to the wrong source, or “Default” resolved to a different device

• Mic not assigned to an active recording track: The mic is audible in a stream but its track is excluded from the local recording file

• Audio Monitoring set to Monitor Only: Audio plays in your headphones but is never written to the output file

• Volume muted or fader zeroed in OBS: The Audio Mixer is silencing the signal before it reaches the output

• OS microphone permission blocked: Windows or macOS is preventing OBS from accessing the device entirely

• Exclusive Mode conflict on Windows: Another application has locked the audio input device

• Sample rate mismatch: OBS and the audio driver are running at different rates, producing silent or corrupted input

• Wireless receiver hardware issue: The transmitter is muted, unpaired, or the receiver is not recognized by the OS

Fix 1 — Select the Correct Microphone Input Device in OBS

OBS does not record audio unless a microphone is selected. The "default" input setting often causes this problem in OBS. It follows whatever the OS currently designates as the system input, and that can change silently when a new USB device is connected or a system update resets audio preferences.

Steps:

1. Open OBS and go to Settings > Audio.

2. Locate the Mic/Auxiliary Audio dropdown (slots 1 through 4 are available). Click the dropdown for slot 1.

3. Replace “Default” with your microphone’s specific device name, for example “Headset Microphone (Realtek)” or “USB Audio Device.”

4. Click OK to save, then return to the main OBS window.

5. Look at the Audio Mixer panel. Speak into the microphone and watch for green levels on the mic channel’s VU meter. Movement on the meter confirms the device is correctly selected and receiving a signal.

6. If the meter stays completely flat after selecting the named device, the problem is upstream of OBS. The OS is either not recognizing the microphone or the hardware is not transmitting. Continue to Fix 5 or Fix 8.

For Hollyland LARK MAX 2 users: Before opening OBS, check Windows Sound settings under the Recording tab (or macOS System Settings > Sound > Input) to find the exact name the receiver uses when connected via USB-C. It typically appears as “LARK MAX 2” or “USB Audio Device.” Match that name precisely in the OBS dropdown. Misidentifying the device from a list of similarly named USB inputs is one of the most common failure points with wireless receivers.

For Hollyland LARK M2users: Plug the USB-C dongle receiver in before launching OBS. Confirm it appears under Recording Devices rather than Playback devices in Windows Sound settings before attempting to select it in OBS.

Fix 2 — Assign the Microphone to the Correct Recording Track

OBS records audio to numbered tracks (Tracks 1 through 6). Your microphone must be assigned to an active recording track. It is often missed during OBS setup. A mic may appear active in the audio mixer. It can also sound normal during live streaming. The local recording may still miss microphone audio completely. This happens when the recording track is not enabled.

Steps:

1. In the Audio Mixer, find your microphone channel. Click the gear icon on that channel to open its advanced settings. Alternatively, right-click the source in the Sources list and select Advanced Audio Settings.

2. Locate the row for your microphone in the Advanced Audio Settings window. Look at the Tracks column, which shows checkboxes for Tracks 1 through 6.

3. Note which tracks are currently checked (for example, Track 1).

4. Go to Settings > Output and click the Recording tab.

5. In the Audio Track section of the Recording tab, confirm that the same track numbers checked in step 3 are also enabled here. If Track 1 is checked for the mic but disabled in the Recording output, that track is not written to the file.

6. Enable the matching track, click OK, run a short test recording, and review the playback.

Note: Stream tracks and recording tracks are configured separately in OBS. A microphone that performs perfectly during a live broadcast may still be absent from the local recording file if the track assignment was only configured for the stream output and not the recording output.

Fix 3 — Correct the Audio Monitoring Mode

Audio Monitoring in OBS controls whether a source’s audio is sent to your headphones, written to the recording file, or both. The “Monitor Only” mode is the most damaging configuration mistake for recording. It routes audio to your headphones so everything sounds correct in your ears during the session while writing nothing to the output file.

Steps:

1. In the Audio Mixer, locate your microphone channel.

2. Click the gear icon on the channel and select Advanced Audio Settings.

3. Find the Audio Monitoring column for your microphone source.

4. Compare the three modes and select the one that matches your intent:

5. Select Monitor and Output if you want to hear your voice while recording. Select Monitor Off if you only want to capture the mic without headphone feedback.

6. Click Close, run a short test recording, and confirm audio is present on playback.

Most users who encounter this issue were experimenting with monitoring settings to reduce latency or echo and accidentally switched from “Monitor and Output” to “Monitor Only” without realizing the change prevents the audio from being saved.

Fix 4 — Unmute the Microphone and Restore Volume in OBS

Even when the input device, track assignment, and monitoring mode are all correct, the signal can be silenced within the Audio Mixer itself. This check takes under a minute.

Steps:

1. In the Audio Mixer, locate your microphone channel.

2. Check the volume fader. It should sit at or near 0 dB. A fader dragged fully to the left sends zero signal to the output.

3. Check the speaker icon below the fader. A red or crossed-out icon indicates the channel is muted. Click once to restore it.

4. Click the gear icon and select Filters. Review any active filters. A Gain filter set to a strongly negative value can reduce the signal below the recordable threshold. Adjust or remove the filter to restore normal signal levels.

For Hollyland LARK MAX 2 users: If the OBS fader is correctly positioned but the VU meter still shows no signal, check the physical mute button on the transmitter body. A solid green LED indicates the transmitter is active and sending audio. A red LED or blinking red state means the transmitter is muted at the hardware level, independent of any OBS setting. Press the mute button once to toggle back to active. A muted transmitter sends no audio to the receiver regardless of how OBS is configured.

Fix 5 — Grant OBS Microphone Access in Windows or macOS

If the system blocks access, OBS still shows the device. The signal will remain completely flat despite selection. This permission can change after system updates. But security policies may also revoke microphone access without warning.

Windows 10 / 11

1. Open Settings > Privacy & Security > Microphone.

2. Confirm that Microphone access (the top system-level toggle) is turned On. If this is off, no application on the system can use the microphone.

3. Scroll down to Let desktop apps access your microphone and confirm it is also turned On. OBS Studio runs as a desktop application, not a Microsoft Store app, so this toggle governs whether it can receive input.

4. Close Settings and restart OBS completely. A settings refresh within OBS is not sufficient. The application must be fully closed and reopened.

5. Return to OBS and check the Audio Mixer VU meter for activity.

macOS

1. Open System Settings > Privacy & Security > Microphone.

2. Find OBS in the application list and toggle permission to On.

3. If OBS does not appear in the list, it has not yet requested permission. Launch OBS with a microphone connected, and macOS will display a permission prompt. Click Allow.

4. Restart OBS after granting permission. macOS does not apply microphone access to an already-running application session.

5. Confirm VU meter activity in the Audio Mixer after restarting.

Fix 6 — Disable Exclusive Mode on Windows

Windows Exclusive Mode allows a single application to take full control of an audio input device. When an app holds this control, every other application, including OBS, receives no signal from that device and typically receives no error message either.

Steps:

1. Open Control Panel > Sound.

2. Click the Recording tab.

3. Right-click your microphone and select Properties.

4. Go to the Advanced tab.

5. Uncheck Allow applications to take exclusive control of this device.

6. Click Apply, then OK.

7. Close any applications likely to claim the device first: Discord, Zoom, Microsoft Teams, or browser-based calling tools running in the background.

8. Reopen OBS and run a short test recording.

Fix 7 — Match the Sample Rate Between OBS and Your Audio Device

A sample rate mismatch between OBS and the OS audio driver can cause OBS to receive corrupted input or complete silence. The two most common rates, 44.1 kHz and 48 kHz, are frequently set inconsistently across applications and system settings.

Steps:

1. In OBS, go to Settings > Audio and note the current Sample Rate value (typically 44100 Hz or 48000 Hz).

2. On Windows: Open Control Panel > Sound > Recording tab. Right-click the microphone, select Properties > Advanced, and set the Default Format sample rate to match OBS. Setting both to 48000 Hz is recommended as it is the more widely supported standard for USB audio devices.

3. On macOS: Open Audio MIDI Setup (found in Applications > Utilities). Select the microphone in the left panel and verify the Format sample rate matches what OBS is set to.

4. Click OK on Windows, or close Audio MIDI Setup on macOS.

5. Restart OBS. Sample rate changes apply only after a full application restart.

For Hollyland LARK MAX 2 users: The LARK MAX 2 receiver outputs audio natively at 48 kHz / 32-bit Float. Set OBS Settings > Audio > Sample Rate to 48 kHz to match. A mismatch at this point is a known cause of silent recordings when working with 32-bit Float USB audio devices.

Fix 8 — Wireless Microphone Not Working in OBS: Hollyland LARK MAX 2 Diagnostic

If you have completed Fixes 1 through 7 and OBS still shows no signal, the problem may not be inside OBS at all. Wireless microphone systems add hardware issues that OBS cannot detect. These include receiver recognition by the system. They also include transmitter pairing status and input gain level. Physical mute switches can also block the signal completely. This section covers a complete hardware diagnostic for the Hollyland LARK MAX 2, with a parallel checklist for Hollyland LARK M2 users.

Step 1 — Confirm the Receiver Is Recognized as an Audio Input Device

1. Connect the LARK MAX 2 receiver to your computer using the USB-C cable.

2. Check the receiver LED. 

3. On Windows: Open Settings > Sound > Input. “LARK MAX 2” or “USB Audio Device” must appear as a listed input source before OBS can detect it. If the device is absent, try a different USB port (preferably USB 3.0), replace the cable, or reinstall the USB audio driver through Device Manager > Universal Serial Bus controllers.

4. On macOS: Open System Settings > Sound > Input and confirm the device is listed there.

5. Once the device appears in OS audio settings, return to OBS Settings > Audio and select it by name in the Mic/Auxiliary Audio dropdown.

Step 2 — Verify Transmitter–Receiver Pairing Status

1. Check the LARK MAX 2 transmitter LED. A solid blue LED means the unit is paired and actively transmitting audio. A blinking blue LED or any red state means the transmitter is searching for the receiver or has lost the connection.

2. If the transmitter is unlinked, hold the pairing button on both the transmitter (TX) and receiver (RX) simultaneously until both LEDs show solid green, confirming the link is restored.

3. Keep in mind that the LARK MAX 2 supports up to 340 meters line-of-sight range. Walls, metal surfaces, and nearby 2.4 GHz RF sources such as Wi-Fi routers can interrupt the signal and produce silence in OBS without generating any warning or error message.

Step 3 — Check Gain Level and AI Noise Cancellation in the Hollyland App

1. If pairing is confirmed but the OBS Audio Mixer VU meter still shows near-zero activity, input gain may be the issue. Open the HollyAudio App (LarkSound app) on iOS or Android and connect to the LARK MAX 2.

2. Navigate to the Dynamic Gain section and select from Low to Mid or High. Watch the OBS Audio Mixer VU meter in real time. You can also adjust gain levels from the “Set gain to” section for each transmitter. A visible waveform confirms audio is now flowing through the full chain. 

3. Check the AI Noise Cancellation setting. In some environments, an aggressive noise cancellation setting can attenuate a voice signal that the algorithm misclassifies as background noise, particularly in quiet rooms with low input gain. Toggle NC Level off in the app and retest in OBS to determine whether it is affecting the signal.

LARK M2 — Quick Checklist for Compact Receiver Users

• Plug the LARK M2 USB-C dongle receiver into an available USB-C port. Use the included USB-A adapter if needed.

• Confirm Windows or macOS lists the dongle as an audio input device under Sound settings, not only as a playback device.

• LARK M2 transmitter LED: solid blue means the unit is transmitting. A red LED indicates the transmitter is muted or the battery is depleted. A long press powers the unit off or on.

• If the dongle is still unrecognized, test a different USB port and confirm the transmitter is powered on and within range.

Frequently Asked Questions

Q: My mic shows up in OBS, but the VU meter has no movement at all. What does that mean?

The device is recognized by OBS, but the signal is zero before it arrives. The most likely causes are a muted transmitter on a wireless mic, a Windows Exclusive Mode lock from another application, or input gain set to minimum on the hardware itself. Check Fix 4 for OBS-level mute and volume, and Fix 8 for wireless hardware mute state.

Q: Why does my microphone work in Discord and Zoom but not in OBS?

When a mic functions in one app but not another, Windows Exclusive Mode is the most probable cause. Discord or Zoom may be holding the device and blocking OBS from receiving input. On macOS, permission may have been granted to communication apps but not to OBS specifically. Review Fix 6 for Exclusive Mode and Fix 5 for OS-level permissions.

Q: Does OBS record the microphone and desktop audio on the same track or separate tracks?

Track assignment is fully configurable using Tracks 1 through 6. By default, OBS places all audio sources on Track 1, but you can separate the microphone and desktop audio into individual tracks for more flexible editing in post-production. See Fix 2 for the complete track configuration walkthrough.

Q: My wireless microphone receiver doesn’t appear in OBS’s device list at all. How do I get it to show up?

OBS can only list devices the operating system has already recognized as audio inputs. Check Windows Sound > Input or macOS System Settings > Sound > Input first. If the receiver is absent from those OS panels, the issue is with USB connection, cabling, or driver recognition rather than any OBS setting. See Fix 8, Step 1 for a full diagnostic path.

Conclusion

Most OBS microphone recording failures come down to four configuration mistakes. Wrong input device, missing recording track assignment, incorrect monitoring mode, or a blocked OS permission. Each takes a few minutes to identify and correct. For wireless mic users, confirm the hardware state first, such as the mute button, pairing, and gain level, before adjusting anything inside OBS.