If you have ever installed a screen recorder or a streaming tool and suddenly noticed a new microphone in your sound settings that does not physically exist, you have met a virtual audio device.
It sounds like a hack. It is actually a documented, supported part of how macOS audio works — and once you understand it, a lot of otherwise-confusing audio software makes sense.
What it actually is
macOS handles audio through Core Audio. Every input and output your Mac knows about — built-in mic, USB interface, AirPods, HDMI out — is represented to the system through a driver.
Apple provides a supported way for software to register its own audio device with the system, called an AudioServerPlugIn (also referred to as a HAL plug-in). A virtual microphone is exactly that: a small driver that tells Core Audio "I am an input device," and then supplies audio samples from software instead of from a physical capsule.
The important consequence: apps cannot tell the difference. Zoom, ChatGPT's voice mode, Discord, OBS, QuickTime, Google Meet — they all just ask Core Audio for a list of inputs. A virtual mic appears in that list next to your real hardware, and gets selected the same way.
Why that's useful
Because it creates a stable seam between "what your apps see" and "what is physically plugged in."
Normally those are the same thing, which means every hardware change is an app problem. Unplug the mic you had selected in Zoom, and Zoom falls back to something else — often the built-in mic, often without telling you. Anyone who has spent the first ninety seconds of a meeting being told "you sound far away" has lived this.
With a virtual device in between, apps point at the virtual device once. Behind it, physical microphones can be added, removed, swapped, or reprioritised, and no app ever needs reconfiguring. The dropdown in Zoom never has to change again.
Common jobs virtual audio devices do:
- Processing. Apply noise reduction, EQ, or compression before your voice reaches the app — useful when the app itself gives you no controls.
- Routing. Send system audio somewhere it normally cannot go, like capturing playback into a recording.
- Combining or selecting sources. Present several physical mics to apps as a single input.
- Stability. Give apps one device that never disappears, regardless of what is physically connected.
How installation works — and why it asks for permission
Because a virtual device is a system-level component, installing one is not a normal drag-to-Applications affair. The driver goes into a system location, and macOS restarts the audio daemon (coreaudiod) so the new device is recognised.
You should expect an admin prompt. That is correct and unavoidable for this class of software.
What you should not accept is vagueness about it. Reasonable things to demand from anything installing a virtual audio device:
- It tells you clearly, before installing, that a system audio component is being added.
- It ships a real uninstall path that removes the driver — not just the app.
- It does not silently reroute audio you did not ask it to touch.
Virtual mic vs. Aggregate Device
These get conflated constantly, so: an Aggregate Device is Apple's built-in way to bundle several real devices into one multi-channel device. It exposes each source as its own channel. It performs no processing and makes no decisions.
A virtual microphone is a software device backed by code, which can do arbitrary processing and present whatever it likes — typically a normal mono or stereo stream that any app reads correctly.
Put simply: an Aggregate Device hands your app a bundle of channels and hopes it copes. A virtual mic hands your app one finished signal.
SoundMesh installs a virtual device called SoundMesh Virtual Mic. Behind it, SoundMesh watches up to 8 real microphones and continuously routes whichever one hears you most clearly. Apps see one input that never changes; your microphones can change all they like. Audio is processed locally on your Mac.
The privacy question worth asking
Any software sitting in your microphone path deserves scrutiny. The questions that actually matter:
- Is audio processed on-device, or uploaded? Local processing means your voice never leaves your machine.
- What permissions does it request beyond the microphone? A mic utility has no business asking for Screen Recording, Camera, or Accessibility access. Treat those requests as a red flag.
- Can you stop it instantly? There should be an obvious way to release every microphone stream without uninstalling anything.
Virtual audio devices are ordinary, supported macOS technology — not a workaround, not a jailbreak. Understanding what they are makes it much easier to judge which ones deserve a place in your audio chain.