The screen share has a picture, but the audience hears no programme audio

Seeing the screen does not establish an audio track

A browser screen-capture session can provide picture without programme audio. The Screen Capture API allows an optional audio track, and availability depends on the browser, operating system and selected surface. A request for audio does not guarantee that the returned capture includes it. Test the audience's actual sound rather than assuming a moving preview proves the whole presentation is shared.

Use material you are authorised to present and share. A screen-sharing capability does not grant redistribution rights for a film, sports programme or subscription catalogue. For a technical check, use a short nonprivate sample you own or an appropriately authorised test clip. Keep account menus and unrelated desktop content outside the selected surface.

A hypothetical training presentation

Suppose a presenter shares a lesson tab. Participants can see the moving picture and hear the presenter's microphone, but not the lesson soundtrack. The microphone result proves the conversation path works, not that programme audio was captured. Ask participants to distinguish these sounds instead of reporting only that audio works or does not work.

Inspect the sharing application's documented source and audio choices. Sharing a tab, window or entire display can offer different supported audio options. Do not assume the control labels or availability match another operating system's tutorial. Record the chosen surface and browser when reporting the result. Avoid changing the video's selected soundtrack until the capture path is understood.

Keep the microphone and shared sound separate

Turning up the speakers so a microphone can hear the lesson is a different acoustic route and can create echo or poor intelligibility. It is not equivalent to a supported captured audio track. Use the application's documented sharing workflow and test it at a comfortable level. If the supported platform cannot share the required audio, choose another authorised presentation method rather than hiding the limitation.

Before an important session, test both speech and programme sound with a participant. Confirm that the intended source is heard and that private notifications are not included unexpectedly. A local preview cannot fully substitute for an audience-side check because it may not represent the transmitted mix.

Repeat the actual presentation sequence

After adjusting a documented control, start the share, play the sample and ask for separate confirmation of picture, microphone and programme audio. Stop sharing when the test ends. If changing sources during a session is required, test that transition too; an initial successful tab does not establish that every later window includes sound.

A precise report identifies the selected capture surface, audio option, browser and which sound reached the audience. This gives support a concrete capture task instead of an unsupported claim that the streaming source has no soundtrack. It also makes the presenter's eventual workflow understandable to anyone helping run the session.

Questions answered

If participants hear my microphone, should they hear the video too?

Not necessarily. Microphone capture and programme-audio sharing are separate paths.

Does requesting screen audio guarantee a track is available?

No. Browser, operating system and selected surface support determine what can actually be captured.

Sources & further reading

Official references for the subjects discussed. Service terms and device software can change.