ProblemViewers can see the stream but cannot hear the shared content. If call voices are missing or nobody hears your microphone, use the related guides. Capture availability depends on the client; video does not guarantee that a mode captures audio.

Discord screen share has video but no audio

Check whether one viewer or everyone has no stream audio. Then compare the client and application capture without confusing shared audio with microphone input.

Try this first

1 quick checks · ~5 min

  1. Check who cannot hear the shared contentComparing viewers determines which end to investigate.

Find your situation

See all the clues. Choose the one that matches what you observe.

Diagnostic signals

ObservationOnly one capture mode sends audio
This points to the capture target or mode, not a microphone or whole-system failure.

Step-by-step solutions

01

Check who cannot hear the shared content

Comparing viewers determines which end to investigate.

  1. Ask viewers to distinguish the shared app’s sound from your voice. Use non-private audio you can recognize locally. If one hears it and another does not, start with the affected viewer’s controls.

  2. If everyone confirms silence, or only one viewer is available, check viewer controls first and continue with the broadcaster’s client. One viewer alone cannot establish that the failure is universal.

02

Check that stream’s mute and volume controls

Stream controls are separate from the broadcaster’s microphone.

  1. The affected viewer should check whether the stream is muted and inspect its stream volume. Then compare the same content while another viewer confirms they still hear it.

  2. If other applications are also silent, check that viewer’s device output; on Windows use the sound guide. If only Discord voices are missing, use the call-audio guide. Do not reinstall the broadcaster’s client when other viewers hear correctly.

03

Check the client before trying to repair capture

A platform limitation is not fixed by reinstalling drivers.

  1. Discord documents audio capture on Windows desktop, macOS desktop, the Chrome browser, and mobile clients. Audio sharing is unavailable on Linux. If that is the broadcaster’s system, end this repair path and use an available authorized supported client.

  2. On a supported client, check whether the source application plays sound locally. If not, resolve its playback first; on Windows, all apps being silent belongs with system sound troubleshooting. If the app plays sound, continue with capture comparison.

04

Compare application and display sharing with the same content

Change one variable to see whether silence depends on what is captured.

  1. On the supported client, share the intended application or window, then the whole display where those options exist. Keep the same local sound and viewers. Review any audio-sharing option shown by the current client; do not assume every client offers identical controls.

  2. If one target works and the other does not, use the one that meets your need and record the difference for support. Do not conclude that windows always have audio or displays never do: the result describes this client and content combination.

  3. If neither works and the app plays locally, check client updates and retry after closing it normally. Do not change microphone settings or install virtual audio drivers for a capture problem you have not yet narrowed down.

Next step

Still not working?

With a supported client, working local audio, and silence confirmed by multiple viewers without a useful target difference, contact Discord with the system, version, app, and results. Do not chain driver reinstalls or audio-subsystem changes.

Sources

Documentation behind this guide. Editorial recommendations are identified separately.

Source review: . A documentation review, not a physical hardware test.

Related problems