What SoundSwitch does
SoundSwitch is an open-source project by Jeroen Pelgrims (the maintainer is known on GitHub as Belphemur). The project site calls it a free, open-source Windows app for switching audio playback and recording devices instantly, using global hotkeys, per-app rules, profiles and notifications. The GitHub repository lists it under the GPL-3.0 license.
The core idea is cycling. You pick which devices should be in the rotation, and each press of the hotkey moves to the next one. Only the devices you choose are cycled, so you won't land on something like your monitor's tinny speakers by accident.
Typical rotations include:
- Output: laptop speakers, monitor audio and headphones.
- Input: the built-in microphone, a headset mic and a USB microphone.
MakeUseOf also reported that the app used under 30 MB of memory while running in the background. That is one writer's observation, not a benchmark. Your footprint may differ.
Setup in a few steps
The project's quick start has you right-click the tray icon, open Settings, and tick the devices you want on the Playback and Recording tabs. In practice:
- Install SoundSwitch and launch it. On first launch you land in the settings menu.
- Right-click the tray icon (it may sit behind the "up" arrow) and open Settings.
- On the Playback tab, select the output devices to cycle through. On the Recording tab, do the same for microphones.
- Keep the default hotkeys or assign your own.
- If you want it running after every boot, tick the option to start automatically with Windows.
Default shortcuts
| Action | Default hotkey |
|---|---|
| Cycle playback devices | Ctrl + Alt + F11 |
| Cycle recording devices | Ctrl + Alt + F7 |
| Mute the default microphone | Ctrl + Alt + M |
Double-clicking the tray icon also cycles playback devices by default. When a microphone is muted, a persistent banner stays on screen as a reminder.
If a hotkey does nothing, a few checks are worth running. Confirm the app is running in the tray. Confirm at least two devices are ticked on the relevant tab. Check that another program hasn't claimed the same key combination. That last one is a general hotkey-conflict possibility, not something the project documents.
Profiles: the best feature
MakeUseOf's author called the Profile tab his favorite feature. A profile saves a combination of devices and activates it on a trigger. His examples were a meetings profile (preferred speakers plus microphone) and a gaming profile (headset plus its mic).
The project's documentation lists a broader set of triggers than the article does. An application profile switches your sound settings when a given app has focus. One example is Spotify playing only on speakers while a game uses the headset. Hotkey triggers use custom key combinations, and several profiles can share one hotkey and cycle through automatically. The GitHub README also documents window-title matching, startup triggers and a tray-menu option. It says profiles can restore the previous audio settings when they deactivate.
Multimedia vs. communications devices
Windows keeps two defaults: one for multimedia and one for communications. An app that asks for the communications device receives the Default Communication Device. The project says SoundSwitch changes the communications default only when you enable that in Settings. So switching playback with the hotkey may not move your calling app. If Teams or Zoom ignores a switch, check this setting first. Profiles can set playback, communications, recording and recording-communications devices separately.
The command-line interface
SoundSwitch ships a separate executable, SoundSwitch.CLI.exe. The official CLI documentation shows these commands:
SoundSwitch.CLI.exe switch --type Playback
SoundSwitch.CLI.exe switch --type Recording
SoundSwitch.CLI.exe profile --list
SoundSwitch.CLI.exe profile --name "Gaming"Beyond those, the CLI documentation covers:
- Microphone mute control, including a toggle.
- A
devicescommand that lists the devices in your cycle. - A
settingscommand that opens the settings window. - A
statuscommand that shows the current defaults and the last profile triggered. - A
--jsonflag on all commands for scripting.
Two caveats from the documentation matter for automation:
- The main app must be running. The CLI talks to it, so it is not a standalone replacement. Documented errors include SoundSwitch not running, invalid profile names and a missing default microphone.
- "Active Profile" can be stale. The status command reports the last profile explicitly triggered. It may not reflect changes made through Windows sound settings.
For everyday switching, a hotkey is simpler. The CLI is more useful for scripts, Stream Deck-style launchers or scheduled tasks. Which of those fits depends on your setup.
Release status and caution
The project's releases page shows v7.3.2 as the latest stable release, dated August 31, 2026. One prerelease sits ahead of it:
- v7.4.0-beta.1 (October 19, 2026) added banner customization and native Windows dark-mode support.
Most people should stay on the stable build unless they want those features. The release notes for v7.3.0 and v7.3.2 also describe crashes and a device-list bug in earlier versions. They show the project updates quickly, so keep the app current. The README says SoundSwitch checks GitHub for updates, with Silent, Notify or Never modes.
Who should install it, and who shouldn't
SoundSwitch suits anyone who regularly alternates between headphones, speakers, USB mics and headsets. That includes remote workers, streamers and gamers.
It is a routing tool only. It won't repair a missing driver, a dead device or poor audio quality.
Newer Windows 11 builds also have a built-in shortcut for the output panel. Pressing Ctrl + Win + V opens the Sound Output panel directly. That helps with outputs, but it doesn't give you microphone cycling, profiles or app-triggered switching. If you only swap outputs occasionally, the built-in route may be enough. If you juggle microphones or want automation, SoundSwitch fills the gap.
Bottom line
SoundSwitch fixes a small but persistent Windows irritation. It is free, open source and quick to configure, and its documentation backs up the MakeUseOf account of hotkeys, profiles and CLI. Treat the memory figure as one person's observation. Stick to the stable release unless you want the beta features.
Correction (October 25, 2026): The release-status section originally listed v7.3.3 (September 1, 2026) as the latest stable release and v7.4.0-beta.2 (October 25, 2026) as a prerelease. The project's releases page shows v7.3.2 (August 31, 2026) as the latest stable release and v7.4.0-beta.1 (October 19, 2026) as the latest prerelease; neither v7.3.3 nor v7.4.0-beta.2 appears there.