To make one app play through a different speaker, headset or monitor in Windows 11, open Settings > System > Sound > Volume mixer, find the app under Apps, and select its Output device. If sound is still missing, check that app’s volume and mute state, then confirm that Windows can see the device.
This changes the playback route for that app, not the microphone input and not necessarily the system-wide default. The steps can direct sound to an available endpoint; they cannot make a faulty or unavailable device work.
When to Change an App’s Output Device
Use the per-app setting when most of Windows plays through the right device but one programme does not. For example, system sounds may come from your monitor while a browser playing a lesson continues through laptop speakers. Choosing the headset for the browser can correct that mismatch without changing where other apps play.
This is also useful when you deliberately want different apps on different outputs: a meeting app on headphones and music on room speakers, for instance. Whether this arrangement is practical depends on the devices connected and the controls in each app. Not every app appears in the mixer at every moment, and an app may offer its own output selector as well.
Keep the scope of the setting in mind. The system default output is Windows’ general playback destination. The app’s Output device in Volume mixer is a separate choice that can differ from that default. Changing one is not the same as changing the other. If all sound is going to the wrong destination, start by checking the default output in Sound settings; if only one app is affected, begin with that app’s mixer entry.
A live-channel operator might notice the distinction while previewing a video: desktop audio or a browser preview can be routed to headphones without changing the route used by other programmes. This Windows setting is only about local playback. It does not select a microphone input or, by itself, change the audio sent by a YouTube broadcast. For preparing the source video itself, see this checklist for whether a video file is ready for a 24/7 stream.
Microsoft’s instructions for fixing app audio when system sounds work describe this per-app route and note that apps can use a different output device from the system default. Use the app-specific control when the problem is limited to one programme; use the system output control when several apps are affected in the same way.
Open Windows 11 Volume Mixer
On Windows 11, open Start > Settings > System > Sound, then select Volume mixer. Under Apps, look for the programme whose sound you want to redirect. The route is in Settings rather than the older taskbar mixer workflow used in Windows 10.
If you prefer, open Start and search for Volume mixer, then open the matching sound setting. The Settings path is useful to know even if you search, because it makes clear that you are in the Windows sound controls rather than an app’s own settings.
The app generally needs to be open and producing, or recently have produced, audio for its entry to be useful. Start the app, play a short sound, and return to Volume mixer if you do not see it. Keep the relevant programme open while testing. The list is about apps with playback activity, not a permanent catalogue of every programme installed on the computer.
If the app is listed but its controls are not visible at first, expand or inspect its row. Windows presents app controls separately from the System sounds entry. Do not use System sounds as a substitute for the app’s own row: changing the wrong row can leave the programme’s route untouched.
For a local business or study channel, this can be a simple way to send a browser preview to a headset while leaving notification sounds on the laptop speakers. If the computer is also used for an always-on stream, changing a desktop app’s playback destination should not be confused with changing the source or route of a broadcast. For a separate setup that does not depend on leaving a PC on, this guide to a 24/7 language-learning stream without a PC covers a different operating choice.
Choose the App’s Output Device
In Volume mixer, find the affected app under Apps. Use the Output device control in that app’s row to select the intended speaker, headset, monitor or other available output. The choice applies to that app, so it can be different from the device shown as the Windows default.
After selecting the device, return to the app and test playback. A brief test is better than assuming the menu selection fixed the problem. If the sound now comes from the intended endpoint, the route is working for that app. If not, check volume and mute state before changing several other settings at once.
The available choices depend on what Windows currently detects. A headset that is disconnected, a monitor that is off, or an audio adapter that has not been recognised may not appear as a usable choice. Select an entry that corresponds to the connected device you actually intend to use. Names can be similar, particularly when a computer has built-in speakers, a display with speakers and a USB headset.
Some apps maintain their own playback-device setting. If the Windows selection appears correct but the app still uses another output, inspect the app’s audio or playback preferences. Avoid assuming that every programme handles routing identically. The Windows mixer is the direct per-app control, but app-specific settings can also matter to the final result.
If your goal is to make all programmes use the same device, choose the default output in Windows Sound settings instead. That may be simpler for a computer that is always docked to one speaker system, but it affects the general route and is broader than the app-specific change. Make the narrower change when one programme alone needs different treatment.
Check the App’s Volume and Mute State
A correctly selected output can still appear silent if the app is muted or its individual volume is low. In the app’s row in Volume mixer, check its volume slider and mute control. Raise the slider enough to test, and make sure the speaker or mute icon does not indicate that the app is muted.
Check both places that may control loudness: the app’s own playback control and its Windows mixer volume. A video player can be muted inside its page or window while Windows shows an ordinary slider. Conversely, the app can have its own volume turned up while Windows has reduced or muted the app in the mixer. Test with a known audible clip, then adjust one control at a time.
Do not use a system-wide volume change as the first response to silence from one app. It may make other programmes unexpectedly loud while leaving the affected app muted. The aim is to establish whether the app itself is producing sound and whether its own Windows level is audible, before moving on to device detection.
If the app is audible on one output but not another, that is useful information: it suggests the app can play sound, while the selected endpoint or its connection still needs checking. It does not prove the hardware is faulty. Return to the app’s Output device selection and try another connected endpoint only as a diagnostic comparison, not as a reason to buy new hardware.
Confirm the Selected Device Is Available
Open Settings > System > Sound and review the available output devices. Check that the device you selected is present and enabled. If it is missing, Windows cannot route the app to it through the mixer at that moment. Reconnect the headset or adapter, wake or turn on the display or speaker as appropriate, and check the device list again.
For a monitor connected by HDMI or another display connection, confirm that Windows detects the display and that its audio endpoint appears. For a USB headset, check the physical connection and try a different port if that is practical. These checks establish whether Windows sees an output device; they do not guarantee that a damaged cable, speaker or headset will produce sound.
Microsoft’s guide to audio problems when no sound plays from speakers or headphones identifies detection and driver issues among possible causes when an output device does not appear. If the device is absent, use Windows’ own troubleshooting guidance and the device maker’s support information rather than assuming the app mixer is at fault.
If the output is listed and selected but the app remains silent, restart the app after confirming the route, then test again. If sound fails across multiple apps, the issue may be system-wide rather than isolated to one app. Microsoft also lists Windows Audio and Windows Audio Endpoint Builder services, and audio drivers, as follow-up troubleshooting areas. These are further checks, not the first thing to alter for a single muted app.
Keep changes reversible. Note the device that was selected before testing, and restore it if another programme’s behaviour changes unexpectedly. A per-app route and a system default are different settings, but a clear before-and-after test helps identify which change made a difference.
Windows 10 Version Notes
Windows 10 uses an older documented workflow, so do not assume that its controls will look like the Windows 11 Settings page. Microsoft’s instructions describe right-clicking the taskbar Volume icon and choosing Open Volume mixer to inspect an app’s volume. For the output device, right-click Volume, open Sounds, and use the Playback tab to check whether the intended device is set as Default. Then return to the mixer and check the app’s volume and mute state.
That legacy sequence is not the same as selecting a distinct per-app output from Windows 11’s Volume mixer. In Windows 10, the Playback tab primarily lets you set the system default. If your Windows 10 installation or audio driver presents different controls, the exact screen may vary; use the labels and options visible on your version rather than expecting every system to match a screenshot.
A useful comparison is:
| What you want to change | Windows 11 route | Windows 10 documented route |
|---|---|---|
| One app’s playback destination | Settings > System > Sound > Volume mixer, then the app’s Output device | The legacy instructions check the default in Sounds > Playback and app volume in Open Volume mixer; this is not the same per-app picker |
| General output for Windows | Settings > System > Sound, then choose the output device | Sounds > Playback, then set the intended device as Default |
| App mute or level | App row under Apps in Volume mixer | Open Volume mixer from the taskbar Volume icon |
Windows 10 support ended on 14 October 2025, according to Microsoft’s Windows 10 support page. You can still use its existing controls, but do not take an old tutorial as evidence that the operating system remains supported. Check Microsoft’s current guidance for your situation, especially if device detection or driver behaviour is part of the problem.
If you are operating an always-on channel from a Windows computer, keep playback troubleshooting separate from broadcast continuity. A local app’s output route helps you hear a preview; it does not keep a stream running if that computer is shut down. This guide to looping a YouTube live stream with VLC discusses a PC-based route, while a channel intended to run without a local machine has different requirements.
Keep the Change Narrow and Testable
For a clean diagnosis, make one change and listen before moving to another. First confirm that the app is active and audible, then select its output, check its individual volume and mute state, and confirm that the chosen endpoint appears in Windows. This order keeps you from changing the system default, app preferences and device settings all at once and then not knowing which one mattered.
If the problem began after connecting a new headset or display, test whether Windows lists that endpoint before investigating more complicated causes. If the endpoint is available, select it for the affected app and play a short sample. If it is not listed, work on connection and detection first. If several apps have no sound, broaden the check to system output and Microsoft’s audio troubleshooting steps.
For a channel that uses a Windows PC for playback, previewing and monitoring, this setting can make it easier to listen privately without redirecting every sound on the computer. It is not an audio repair tool and does not guarantee sound from a faulty or unavailable device. Where the practical issue is that a local PC must remain on for a continuous broadcast, that is a separate operating decision; the bhajan livestream setup guide explains the no-PC approach.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
How do I change the audio output for one app in Windows 11?
Open Settings > System > Sound > Volume mixer. Under Apps, find the app and select the intended device from its Output device control, then test playback.
Why is one app using the wrong audio device?
The app may have a per-app output choice that differs from the Windows default. Check its row in Volume mixer and, if needed, the app’s own playback preferences; then confirm the chosen device is connected and available.
What should I check if the app is still silent?
Check the app’s Volume mixer slider and mute state, then make sure Windows detects the selected output device. If more than one app is silent, check the system output and follow Microsoft’s broader audio troubleshooting guidance.
Does this change my microphone input?
No. These steps concern playback output for an app or the system default, not microphone input. They also cannot make a faulty or unavailable output device produce sound.