START HERE
Connect the phone microphone through MicDrop and a Windows virtual cable, then select CABLE Output as Discord’s input. Open the Discord & VB-CABLE routing checklist for a copyable signal diagram, and keep Discord’s output on your listening headphones.
If the input fails outside Discord too, use the Windows microphone checklist to separate device, permission, and application problems.
Decide where the call will run
This guide is for Discord running on the Windows PC, with the phone acting as its microphone through MicDrop (free PC-to-phone Wi-Fi audio app). If you only need a call on your phone, using Discord directly on the phone is simpler. MicDrop is useful when the desktop session, game, or recording workflow needs the phone's audio input.
Complete the phone microphone setup first. Verify a short recording from the Windows cable input path before changing Discord. This separates a transport problem from a Discord configuration problem.
1. Choose Discord's input and output
- Open Discord's User Settings → Voice & Video.
- Set its input device to CABLE Output when using VB-CABLE. This is the recording side receiving MicDrop's returned microphone.
- Choose your actual listening device as the output. For desktop audio streamed back through MicDrop, choose the same Windows playback device that the host captures.
- Start with the phone's built-in microphone, and connect headphones for listening if you use two-way audio.
Do not choose CABLE Input as Discord's listening output in this arrangement. That sends the call back into the cable being used as the microphone and can feed other people's voices back to them.
2. Run a private microphone test
Use Discord's Mic Test / Let’s Check control to hear a sample through the selected output, then stop testing. Keep the level low and use headphones. Test speech at the distance you will actually use, including the beginning and end of quiet sentences.
Mute on the phone by turning off Send microphone (or using the Android notification mute control) and confirm the input stops, then turn it back on. Finally press Stop in MicDrop. Checking both controls matters: a microphone meter that moves is only evidence of sound arriving, not evidence that your mute workflow works.
If Discord cannot hear you
- Nothing reaches Windows: check the phone's microphone permission, selected microphone, mute state, and the Windows host's return endpoint, or test CABLE Output directly in the online microphone test.
- Windows receives it but Discord is silent: reselect CABLE Output and check Discord's input volume and Voice Activity/Push to Talk choice.
- The private test works but a channel does not: check local mute, server mute, channel permissions, and any Push to Talk key requirements.
- The browser version alone fails: check the browser's microphone permission and the device it supplies to Discord.
If it echoes or speech gets cut off
Echo often means an extra path is open: phone speakers feeding the microphone, Windows listening to the cable, or a mixer monitoring it into captured desktop audio. Remove that loop before changing noise suppression.
If sentence beginnings disappear, compare a Windows recording with Discord's test. If only Discord clips them, investigate its activation threshold or voice processing. If both recordings clip, investigate upstream. Change one processing option at a time; stacking several automatic gain or noise-removal stages makes the result harder to explain. For persistent clipped words, continue with the Discord microphone cutting-out guide; to keep Discord teammates separate from a broadcast mix, see separating Discord audio in OBS.
For a Bluetooth headset, compare playback before and after opening its microphone. A call-route quality change can happen on the phone even when Discord itself uses a Windows virtual device. See the Bluetooth microphone guide for that case.
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.