START HERE
MicDrop carries your phone microphone to Windows over local Wi-Fi. A separate virtual audio cable makes that sound available as a microphone input to Windows apps: select CABLE Input in MicDrop and CABLE Output in the receiving app.
Understand the microphone path
A phone connected to MicDrop (free PC-to-phone Wi-Fi audio app) does not automatically appear as a new Windows microphone. MicDrop receives its audio and plays it into a selected Windows output. A virtual cable joins that output to a recording device that Discord, OBS, and other applications can select.
| Stage | Selection |
|---|---|
| MicDrop on the phone | The built-in microphone; Send microphone enabled |
| MicDrop on Windows | CABLE Input in Phone microphone destination |
| Receiving Windows application | CABLE Output as its microphone/input |
Input and Output are named from the cable's perspective. Audio enters its playback side and leaves its recording side. If those names seem reversed, use the table rather than guessing.
1. Prepare Windows
- Install matching MicDrop builds and pair your phone with the Windows host. iPhone users can follow the iPhone setup guide.
- Install a suitable virtual cable separately, following its vendor's installation and license instructions. MicDrop does not bundle a driver.
- Stop the Windows host before changing its settings. Under Audio, set Phone microphone destination to the cable's playback endpoint, usually CABLE Input (replacing Disabled — desktop playback only).
- Start the host again. Keep Desktop audio source and your normal Windows listening output on speakers or headphones, not on the microphone-return cable.
2. Send the microphone from the phone
Select the phone's built-in microphone first. Enable Send microphone, allow microphone access on the phone, and connect. For microphone-only use, leave desktop playback off. For two-way audio, also enable Play desktop audio and use headphones to reduce acoustic feedback.
The built-in microphone makes a useful baseline: it avoids changing Bluetooth playback into a headset call route during the first test. Once the simple path works, you can test a wired, USB, or supported Bluetooth microphone and compare the reported route.
3. Verify the input before a call
- Open your receiving app's audio settings and select CABLE Output explicitly.
- Record a short private sample or use the application's microphone test. Speak at a normal level and listen back through headphones.
- Mute the microphone in MicDrop by turning off Send microphone (or using the Android notification mute control) and verify the input becomes silent. Turn it back on and repeat.
- Press Stop on the phone and verify that the Windows app no longer receives your voice.
Keep Windows Listen to this device and unnecessary microphone monitoring off. Hearing your own delayed voice is usually a monitoring path to diagnose, not a reason to increase microphone gain.
If the receiving app is silent
Follow the path in order: phone permission and mute, phone connection, host return endpoint, then the application's selected input. If Windows sees a cable signal but one application does not, concentrate on that application's input, permissions, and voice activation settings. If the cable endpoint is absent, check the driver installation before repeatedly pairing the phone.
When moving from microphone-only to duplex, test again. A headset microphone can change the playback route or quality. MicDrop supplies the transport; it cannot make every Bluetooth device support stereo playback and microphone capture at the same time.
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.