If your Streamlabs Talk Studio YouTube broadcast has no sound, first identify whether viewers cannot hear you, a guest, or audio from shared content. Those sources use different capture paths, so changing an unrelated setting can leave the real fault untouched.
Start with the Talk Studio controls and the browser permissions for the source that is silent. Streamlabs Desktop has its own audio troubleshooting steps, but they are not Talk Studio controls and should only be used if Desktop is actually part of your broadcast setup.
Identify which sound is missing
Before changing settings, listen to the broadcast as a viewer would and describe the missing sound precisely. Is your voice absent while a shared video is audible? Can viewers hear you but not a guest? Is the whole programme silent, including a tab or computer sound you meant to share? Each answer points to a different path.
A simple source check prevents a common detour: do not troubleshoot the host microphone when only a shared browser tab is silent. Likewise, if guests can hear you in the studio but the audience cannot, check whether your host input is selected and whether it is muted, rather than changing the guest’s settings.
| What viewers cannot hear | First path to check | A useful distinction |
|---|---|---|
| Host voice | Browser microphone permission, mute state, selected input | Talk Studio captures your microphone through the browser. |
| Guest voice | Guest’s on-stream status and their microphone | A guest waiting in the queue is not yet part of the programme. |
| Shared video, tab, or computer sound | Share-specific audio option and relevant screen-recording permission | Sharing a picture does not necessarily share its sound. |
| Everything, or the wrong broadcast destination | Selected live destination and a short test | A destination issue is different from a microphone-routing issue. |
If you can, ask someone to listen on a second device or in a separate browser session. Your own studio may let you hear local monitoring or a source preview that does not prove the YouTube audience is receiving it. Make one change at a time, then check that same source again; otherwise, you will not know which adjustment mattered.
For a prerecorded loop, the source file itself can also be part of the chain. That is a different workflow from Talk Studio’s live microphone and guest paths; a guide to checking a video file before a YouTube loop stream can help when the sound is embedded in a local video rather than captured from a shared tab.
Check the host microphone and browser permission
Talk Studio runs in a browser, so the browser must be allowed to use the microphone you intend to speak into. If a permission prompt appeared when you joined the studio, confirm that you allowed access. If there was no prompt, or permission was previously denied, use the site controls next to the browser address bar to review the microphone permission. Streamlabs’ Talk Studio getting-started guide describes checking browser device permission from the lock icon and refreshing when needed.
After changing a permission, refresh the studio if the browser does not begin using the microphone. Rejoin only if a refresh does not restore access. Check that the microphone is connected and available to the computer, then return to Talk Studio rather than opening unrelated operating-system audio tools first.
The microphone selection is in Talk Studio: click the arrow beside Mute and choose the intended input and output devices. The wording matters. If you have a laptop microphone and a USB microphone, the browser might have permission to use one while Talk Studio is pointed at the other. Select the device you actually intend to speak into, unmute, and speak at a normal level while checking whether the studio responds.
If the host is muted, selecting the correct device will not make the voice audible. If you are not muted and the browser permission is granted but the wrong microphone is selected, changing only the permission may also achieve nothing. Work through those checks separately: permission, selected input, then mute state.
Do not assume a new microphone is needed simply because your YouTube stream has no audio. A device replacement is relevant only if the current input is unavailable or faulty after you have confirmed browser permission and device selection. If another application is already using the mic, close it as a basic isolation step, then test Talk Studio again.
Check the guest microphone and mute state
A guest’s audio has its own condition: being connected to the studio is not necessarily the same as being included in the broadcast. Streamlabs states that a guest’s microphone will not sound until the guest is moved from the queue to Show on stream. Check that status before asking a guest to change their computer or browser settings.
If the guest is already shown on stream, ask them to check their own mute state and microphone selection. They may need to confirm browser permission on their device, just as you do for the host input. Keep the checks on the guest’s side focused on their microphone: a host’s input selection cannot select or unmute a guest’s device.
A useful test is to have the guest speak while you listen to the studio, then have a second person check the YouTube playback during a short test. If the guest is audible in the studio but absent from the broadcast, verify Show on stream and the destination test before changing guest hardware. If they are not audible in the studio either, check their mute state, browser permission, and chosen input.
Guests can also be audible at one point and then disappear after a change in who is on screen. Recheck the guest’s on-stream status whenever the production layout changes. Treat this as a broadcast inclusion check, not evidence that the guest’s microphone has failed.
Check shared screen, tab, or computer audio
Screen sharing commonly sends a picture without sending the sound that accompanies it. When you start a share, look for the audio option supported by that share method, such as Share System Audio or Share tab audio, and enable it if you need viewers to hear the computer or browser content. The available option can depend on what you chose to share, so do not expect one universal toggle to appear for every share type.
For example, if you are presenting a YouTube clip in a browser tab, sharing that tab with its audio option is a clearer test than sharing the whole screen and assuming all computer sound will follow. If you are sharing a desktop application, check for the system-audio option in the screen-share flow. Then play a short piece of known audio and listen to the broadcast separately.
On a Mac, Streamlabs’ screen-sharing guide says to add Chrome under System Settings > Privacy & Security > Screen Recording; the browser may need to be relaunched before the permission takes effect. This is a screen-sharing permission, distinct from microphone permission. Granting microphone access does not automatically allow a browser to capture screen or system audio.
If you are adding background audio through Talk Studio’s screen-sharing workflow, consult that guide for the supported method and file types. It identifies MP3 and WAV for background-audio upload. Do not assume another format is supported without checking the current instructions. More importantly, an uploaded background track is not a fix for a silent shared tab if the actual aim is to capture the tab’s sound.
If the share contains moving images but no audio, change only the share’s audio capture choice first. If audio is absent from all sources, return to the host and guest checks rather than repeatedly toggling share permissions. The capture path should match the sound you are trying to send.
Verify Talk Studio input, output, and YouTube destination
Talk Studio’s arrow beside Mute is where you choose preferred audio input and output devices. Confirm the input is the microphone you intend to use. Check the output as well if you cannot hear other participants or monitor the studio locally, but remember that an output-device problem for you does not by itself establish that viewers receive no broadcast audio.
Next, verify that YouTube is configured as a destination and actually selected in the go-live flow. Streamlabs’ getting-started documentation explains that destinations are added under Profile Picture > Account Settings > Destinations, then selected when choosing where to go live. A missing or unselected YouTube destination is not proof of an audio-routing fault; it is still worth ruling out if the audience is hearing a different broadcast or nothing from the intended channel.
Keep the diagnosis in proportion. If the correct YouTube destination is selected and the host, guest, and shared-source tests point to the right local audio, do not keep switching devices at random. The next useful step is a controlled test that separates what Talk Studio shows locally from what YouTube playback receives.
If you are building a continuous prerecorded programme rather than presenting live, capture and delivery decisions differ from Talk Studio. The practical distinction is similar to the one in a playlist-to-YouTube Live workflow: a file’s audio and a live microphone are separate sources, and success in one path does not prove the other path is working.
Run a short test broadcast
A brief test helps establish whether the failure is in the studio, the broadcast path, or the viewer’s playback. Tell the audience or collaborators that you are testing, choose the correct YouTube destination, and speak a few sentences. If a guest is part of the programme, bring them on stream and ask them to speak. If shared content matters, play a short clip with its audio option enabled.
Listen from a second device or ask someone outside the host computer to check. Test one source at a time: host voice first, then guest, then shared content. That order makes it easier to tell whether a later source is masking the original fault. Keep the test short and avoid judging it from the host’s own local monitoring alone.
If the studio appears to receive a source but the YouTube audience still hears silence, note exactly which source was tested and which device you used to check playback. The material available for this guide does not establish a Talk Studio-specific YouTube Studio diagnostic procedure for this symptom. Check the current official YouTube live guidance and diagnostics rather than assuming a Talk Studio setting is responsible.
A test also catches the wrong-destination problem. Verify that the stream you are monitoring is the one you intended to send to YouTube, rather than an old playback or a different live session. If the host is audible but the guest and shared audio are not, return to those individual branches instead of repeating the entire setup.
For a 24/7 channel, a short test before a scheduled programme is more useful than discovering a missing source hours later. If the show uses a prepared video rather than live presenters, check that the programme file itself contains the intended audio; checking codec and frame rate before a loop stream is a separate file-readiness task, not a Talk Studio microphone fix.
Keep Streamlabs Desktop advice in its own lane
Streamlabs Desktop and Talk Studio are different products with different controls. A Desktop troubleshooting article may refer to an audio mixer, Desktop capture devices, audio-management software, or Windows exclusive-mode settings. Those are not verified Talk Studio controls. Do not search for a Desktop mixer inside Talk Studio or assume its device-selection steps apply to a browser studio.
If your actual workflow is Streamlabs Desktop, use the separate Desktop audio capture troubleshooting article as Desktop-specific advice. It discusses checking mute state, audio-management utilities, Windows exclusive-mode priority, and manual device selection for Desktop capture. Streamlabs’ separate live-stream audio quality guidance also concerns Desktop capture and operating-system differences; it does not turn those steps into Talk Studio instructions.
There is a practical reason to keep the products distinct: a browser-based microphone permission problem will not necessarily be changed by adjusting Desktop capture, and a Desktop capture device setting will not necessarily exist in Talk Studio. If you use both products in the same production, write down which application sends each source to the broadcast. Then troubleshoot only the path that carries the missing sound.
For an always-on prerecorded channel, a Desktop workflow may be appropriate if you need its specific capture and production controls and can maintain that setup. A 24/7 church stream using OBS on a VPS describes a different operating model; it is not a remedy for a missing Talk Studio microphone. Choose a workflow for the job, not because a setting name sounds similar.
When you have confirmed the file and channel are ready, the remaining decision is how you want to operate the broadcast.
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
Why can I hear myself but YouTube viewers cannot?
Local monitoring does not prove that the same audio is reaching the YouTube broadcast. Confirm the correct microphone is selected and unmuted, then test playback from a second device on the intended YouTube stream. If Talk Studio appears to receive your voice but the audience does not, check current YouTube diagnostics separately rather than applying Desktop settings to Talk Studio.
Why can viewers hear me but not my guest?
First make sure the guest has been moved from the queue to Show on stream. If they are already on stream, have them check their mute state, browser microphone permission, and selected input on their own device.
Why does my screen share have no sound?
Sharing a screen or tab does not always include its audio. Enable the relevant Share System Audio or Share tab audio option when available; on Mac, also check Chrome’s Screen Recording permission and relaunch the browser if needed.
Should I follow Streamlabs Desktop audio steps in Talk Studio?
No. Desktop guidance describes controls and capture paths for Desktop, not verified Talk Studio settings. Use the Talk Studio browser permission, Mute device selection, guest status, and share-audio checks unless Desktop is actually part of the workflow.