START HERE
Share the actual application producing the sound, then confirm that your client supports audio capture and that any sound-sharing permission was granted. Ask a viewer to check the stream's own volume. A working voice call does not establish that screen-share audio is working.
Check the client before changing audio devices
Discord's current Go Live documentation lists audio capture in Windows and macOS desktop clients, Chrome, and mobile clients. That help article still states audio sharing is unavailable on Linux, though Discord rolled out whole-desktop Wayland/PipeWire audio sharing on the Linux desktop client in 2026 (with per-application Linux audio still evolving). Browser support is not interchangeable: a browser capable of joining voice calls may still lack the required application-audio sharing path.
For the macOS desktop app, Discord documents application and game sound sharing on macOS 13 or later. Check the operating-system version before following old instructions that ask you to install a legacy capture component. If the platform itself is unsupported, reinstalling your headset driver is not a useful first step.
Use a known sound and the correct window
- Open one ordinary application with a sound you are allowed to share. Confirm it is audible locally.
- Stop the existing share and choose that application's current window in Discord.
- When the browser or client offers an audio-sharing toggle (including Windows’ Also share system audio switch when sharing an entire screen instead of a single application), enable it for the selected source. In Chrome, a tab share with audio is a useful test for browser content.
- Ask a viewer to listen while you temporarily mute your microphone. They should still hear the application.
This avoids a misleading success where the microphone merely picks up your speakers. Do not use protected subscription video as the baseline: restricted media can behave differently from a normal game or a local test clip. Do not try to defeat the service's protection.
A game's launcher and its running game may be different processes. Re-select the actual game after it opens rather than continuing to share the silent launcher.
Read the permission or error message
Discord identifies Sound Sharing Issues (1001) as failure to capture application audio and directs users to allow its sound-sharing permission when prompted. Grant only the permission needed for the share you intend to make. Microphone permission is a separate control.
On macOS, review the screen/system-audio capture permission requested by the current client in System Settings, then fully quit and reopen Discord if the operating system asks you to restart it. On a managed work computer, ask the administrator about a blocked permission rather than disabling security controls.
If Discord shows an explicit unsupported-OS error, keep that code. It is more useful than repeatedly swapping otherwise working input devices.
Distinguish a sender problem from a viewer problem
Have two viewers compare the same sound if possible. Each should open the shared stream, check its player volume, and confirm Discord's selected output reaches their headphones. The stream volume and another person's voice volume are separate things to inspect.
If one viewer hears the sound, keep the sender's known working configuration while fixing the other viewer's playback route. If nobody hears it, share a different ordinary application. A second application working narrows the issue to how the first application is captured, not to your entire microphone setup.
If sound starts and then breaks up
First test a voice call without sharing. Then start a modest share and compare. If the added share consistently introduces problems, reduce its resolution or frame rate where your client offers that control and close unnecessary demanding applications. Keep the same participants and source so you can tell whether the lighter workload changes the result.
If the share remains silent after a client update or route change, fully quit Discord and restart the source application before selecting its window again. Avoid resetting every voice setting at once; it can erase a useful working configuration without identifying what changed.
Verify the two paths separately
Finish with three checks: application sound while your mic is muted, speech while the application is quiet, and both together at usable levels. Restart the share once to confirm the result survives source selection.
If it still fails on a supported client, record the OS and Discord version, selected application, permission/error message, and whether another application or viewer works. Send those details through Discord's support process. For a microphone that also cuts out without a share, continue with the separate voice troubleshooting guide. If you are sending an OBS scene into Discord instead of sharing a single window, see how to route audio alongside OBS Virtual Camera.
Sources & version notes
Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.