START HERE
Route the phone microphone into a Windows virtual cable with MicDrop, then add an Audio Input Capture source in OBS using CABLE Output. Open the OBS & VB-CABLE routing checklist to verify every endpoint before going live.
Get a clean input before opening the stream
OBS needs an audio input it can capture. With MicDrop (free Wi-Fi phone microphone app), the phone sends its microphone to the Windows host, the host plays it into a virtual cable, and OBS records the cable's other end. Follow the phone microphone guide to establish that path first.
Begin with the phone's built-in microphone and microphone-only mode. Put the phone on a stable surface near the speaker, away from keyboard vibration. This keeps your first test focused on one microphone path rather than a combination of desktop playback, speakers, and open microphones.
1. Add the source in OBS
- Connect the phone in MicDrop with Send microphone enabled.
- In OBS, add an Audio Input Capture source and give it a recognizable name such as Phone mic.
- Select CABLE Output when using VB-CABLE.
- Speak and check that this source's meter responds. Record a short local sample and listen back.
Use explicit device selection instead of Default for this test. A change to the Windows default input should not silently turn your “Phone mic” source into a different microphone.
2. Capture the microphone once
If the same cable is already selected as a global Mic/Aux device in OBS, adding it again as a scene source can duplicate it. Use one intentional capture route. Likewise, if you capture desktop audio globally and also capture an application's audio separately, check whether that application is being recorded twice.
OBS provides per-application audio capture on supported Windows systems. Its official guide explains how to separate applications and avoid duplicate desktop capture. That is useful for a cleaner stream mix, but it is separate from getting the phone microphone into OBS.
3. Keep monitoring under control
For the first test, leave audio monitoring off for the phone microphone and judge the saved recording. Monitoring into a Windows output that MicDrop sends to the phone can return your voice to you with delay. If the phone speaker is active, it may also feed back into the microphone.
If live monitoring is needed, choose its destination deliberately, use headphones, and verify that destination is not creating a loop. Do not solve a loop by turning the microphone gain down until your voice is inaudible.
4. Check levels and synchronization
Record normal speech, louder speech, and a short silence. If the meter hits its maximum or the recording sounds harsh, reduce gain before adding filters; if you export a WAV test clip, you can check channel peaks and quiet sections locally in the WAV file inspector. Establish an unprocessed baseline before introducing a gate, compressor, or noise suppression so you can tell which stage changes the sound.
If you also record video, use a visible clap or another clear event in a local recording to assess audio/video alignment, and compare monitoring headphone delay with the audio sync & delay check. Such a check estimates alignment in that recording; it is not a calibrated measurement of MicDrop's one-way latency. A fixed synchronization adjustment can help a consistent offset, but it cannot correct unpredictable dropouts or changing delay.
Before going live
Test phone mute (turning off Send microphone or using the Android notification mute control) and Stop, switch between the scenes you will use, and verify the intended audio tracks in a saved recording. Lock the phone for a separate test long enough to reveal background restrictions. Keep a known working microphone option available if your beta setup fails during a stream. Once your phone microphone works cleanly in OBS, continue with OBS microphone filters, balancing mic, game, Discord, and alerts in OBS, fixing OBS audio echo, recording separate OBS audio tracks, or aligning OBS audio and video sync, and verify your rehearsal clip in the live stream LUFS loudness checker.
Sources & version notes
Checked against the documentation below on November 13, 2026. App labels and platform support can change; use matching MicDrop builds and check the current release notes. These are setup guides, not new hardware benchmark results.