First check what viewers cannot hear: sound from a game or video on your phone, your voice, or Streamlabs alert sounds. They use different audio paths, so a working microphone does not prove that game audio is captured, and an alert that plays on your phone may not be included in the stream.
On iPhone or iPad, Streamlabs says to disconnect headphones so sound from the phone speakers can reach its microphone. On Android, check Streamlabs Mobile’s Main Menu > Streaming Settings > Audio Settings and add an Internal Audio source. Neither is a universal fix; first identify the missing source, then test the relevant path.
Identify the missing sound before changing settings
Ask a viewer to listen to a recent YouTube replay, or make a short test stream and check its replay. Listen for three separate things: the game or video, your voice, and alert sounds. If you are monitoring the broadcast yourself, use another device with its volume low enough not to feed the stream back into the phone microphone.
A phone can play a game clearly while sending only your voice to the broadcast. It can also capture the game but have a muted microphone, or play an alert locally without including it in the live mix. Write down which of the three is absent and whether it is absent for the full test or only at particular moments. That simple distinction prevents unrelated setting changes.
Check that YouTube is showing the right live broadcast or replay. A go-live error, a missing event, and a silent audio source are different faults. If the stream never reached YouTube, there is no viewer audio to diagnose yet; if the video is present but one source is silent, continue with that source’s checks below.
It is also worth separating phone playback from captured audio. Hearing a sound through your own headphones or speaker tells you that the phone is playing it, not that Streamlabs has routed it to the live programme. Confirm what a viewer hears rather than relying on the phone’s monitoring alone.
Check game or video sound on iPhone and iPad
Streamlabs’ iOS guidance describes an acoustic route: the phone speaker plays the game or video sound, and the phone microphone picks it up. Disconnect wired and Bluetooth headphones for the test. Then play the content at a reasonable speaker volume and make a short test stream or recording. If viewers can now hear it, the headphone setup was preventing speaker sound from reaching the microphone.
This is not the same as Android’s Internal Audio source. The iPhone or iPad is using its microphone to hear speaker output, so the microphone may also pick up room noise, handling noise or other people nearby. Keep the phone stable and the microphone opening unobstructed. Streamlabs’ mobile-game guidance specifically warns that a hand covering the microphone can interfere with capture.
In Streamlabs, inspect Streaming Settings > Audio Settings and Screen Capture Settings for the audio controls available in your app version. The labels and options can differ by version. Its iOS screen-capture guide describes screen-capture audio controls, including volume, as well as audio settings. Raise a source only if its control is available and clearly relevant; do not assume a volume slider can change how iOS routes every sound.
Retest with headphones still disconnected. If the game sound is present but voice is not, move to the microphone checks rather than changing screen-capture settings again. If neither is present, confirm that Streamlabs has the necessary microphone and screen-capture access, and check the app’s current instructions. A permission prompt or toggle can affect a source, but changing permissions is not a guaranteed remedy for every missing sound.
If speaker-and-microphone capture is unsuitable—for example, because room noise is unacceptable—do not assume an accessory will convert the setup into direct internal capture. Streamlabs’ documented iOS guidance is not an assurance that all games, video apps or devices expose audio in the same way. Test the actual content and setup you intend to use.
Add Internal Audio on Android
On Android, open Streamlabs Mobile’s Main Menu > Streaming Settings > Audio Settings and add an Internal Audio source. Streamlabs identifies that source as the Android path for game sound. Make a short test with the actual game or video open, and check the resulting YouTube audio rather than judging only by what the phone plays locally.
If the app offers source or screen-capture controls, confirm that the expected audio source is enabled and has an audible level. Settings names can vary across app versions, so use the source’s purpose rather than looking for a particular screenshot. Streamlabs’ mobile settings and Android audio guidance covers the relevant settings. Adding Internal Audio is a specific Android check, not a promise that every app or device will provide sound to the stream.
Try the test without headphones as well. Streamlabs recommends disconnecting headphones when capturing mobile game sounds and voice. Its FAQ also notes a limitation involving Android alert sounds and internal audio in the headphone scenario it describes; do not extend that note into a claim about every Android phone, game or app version. A test without headphones can help isolate the route, but it does not prove that all sources will be captured.
If one game is silent but another works, record that difference. It suggests you should check the app-specific behaviour and Streamlabs’ current support material before rebuilding the whole broadcast setup. Likewise, if the test recording has game audio but YouTube does not, note where the sound disappears and investigate the broadcast path separately.
For a stream built around a prepared video rather than live phone gameplay, it may be useful to distinguish capture from playback. Guides to looping prerecorded videos on YouTube Live and streaming an archive in order cover different ways to send prepared material. They are not substitutes for the mobile source checks here, but they can help you decide whether the phone is the right part of your workflow.
Check voice mute and input selection
If viewers cannot hear you, check the Streamlabs mute control first. Confirm that the microphone is not muted in the app, then inspect the selected input if your version exposes one. Speak a short test phrase and ask a viewer to confirm it in the replay. Keep this test separate from game audio: one source can work while the other is silent.
Temporarily disconnect Bluetooth headphones or microphones and test with the phone’s built-in microphone. Streamlabs’ FAQ reports Bluetooth microphone and headphone issues, while external microphone compatibility depends on the phone. If the built-in microphone works, reconnect one accessory at a time and test again. That identifies whether an accessory changes the selected input or disrupts capture; it does not establish that every Bluetooth device is incompatible.
Check that you are speaking towards an unobstructed microphone opening and that the phone is not buried under a case, hand or stand. If voice is very quiet rather than absent, make a controlled test closer to the phone before changing other audio settings. Avoid speaking louder and adjusting multiple controls at once: a simple before-and-after test makes it easier to tell what changed.
If the built-in microphone is still silent, check the app’s microphone access in the phone settings and restart the test after any change. This is a diagnostic step, not a guaranteed fix. If the phone’s own voice recorder also cannot capture speech, the issue may be outside Streamlabs; if only the live stream is silent, give support the app version, phone model, selected input and test result.
Troubleshoot alert sound separately
When game sound and voice are audible but alerts are not, inspect the alert itself. Confirm the alert is enabled and configured to play on the stream as intended, then check that its sound file uses a format Streamlabs lists as supported: AAC, MP3 or WAV on iOS; WAV, MP3, AAC or OGG on Android. A file in another format may fail even though the game source is working.
Trigger a test alert and listen to the stream replay. Do not treat a sound heard on the phone as proof that viewers received it. Check the alert’s selected sound, volume and playback settings, and make sure the event you expect actually triggers the alert. Keep this test distinct from a game or video test so that a working Internal Audio source does not distract from an alert configuration problem.
Streamlabs documents an Android limitation for capturing alert sounds through internal audio in the headphone scenario described in its FAQ. If that resembles your setup, test without headphones and consult the current FAQ for the app version. Do not infer that the same limitation applies to all Android alerts, or that a change to headphones will restore every alert.
Separate audio capture from going live
If Streamlabs says it is live but YouTube shows no broadcast, or the app cannot create the live event, treat that as a go-live problem rather than a sound-source problem. Streamlabs’ YouTube mobile setup guide discusses account readiness and the initial livestream setup. Check YouTube’s current live streaming help for account eligibility and setup requirements.
A Streamlabs notice dated September 3, 2026 reported that earlier YouTube Mobile go-live issues had been resolved after updates. That notice does not diagnose or resolve audio capture. If your broadcast is visible and moving but lacks game sound, return to the iOS or Android source checks above instead of treating an older event-creation workaround as an audio fix.
For a new YouTube broadcaster, distinguish account setup from a fault in a stream that is already live. Follow the current official account instructions if YouTube says live access is unavailable. If the broadcast is active but silent, note whether voice, game sound or alerts are missing and test each source as described. This keeps a platform eligibility problem from being confused with a phone capture problem.
Retest and confirm what viewers hear
Change one thing at a time, then make a short test using the same game, video, microphone and alert that failed. Ask a viewer—or check the saved replay from another device—to confirm the specific sound. Listen at an ordinary volume and at the moment the source should be active. Keep notes such as “iPad, headphones removed, game audible, voice quiet” rather than “audio fixed”; the former tells you what changed and what remains to solve.
If the sound is intermittent, note when it drops: after connecting Bluetooth, after switching apps, when an alert fires, or when the screen capture changes. Repeat the test once with the relevant condition removed. Do not change several permissions, accessories and volume controls together, because that leaves you without a reliable cause-and-effect check.
When you contact Streamlabs support, include the phone model and operating system, Streamlabs Mobile version, whether headphones were connected, the audio source selected, and what a viewer heard in the test. Include whether YouTube showed an active broadcast. These details help separate a source-routing question from a microphone, alert or go-live fault.
If your goal is a continuous channel made from prepared video rather than a phone game, a different workflow may be easier to test and maintain. For example, keeping a YouTube radio stream running with your computer off addresses continuity rather than mobile audio capture. A continuous YouTube podcast setup on a home computer is another route when you need control over a prepared programme. Neither solves the specific Streamlabs phone issue; use it only if it suits the channel you are building.
If an unattended repeat broadcast is the part that keeps failing after the content and YouTube channel are ready, StreamNeo removes the need to leave your own computer running by turning an uploaded video into a YouTube live stream. It is YouTube-only, so it is not a replacement for streaming mobile gameplay or for diagnosing an audio source in Streamlabs.
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 viewers hear my voice but not the game on iPhone?
Voice and game sound are separate sources. Streamlabs’ iOS guidance relies on the phone microphone hearing sound from the speaker, so disconnect headphones and test the game at a reasonable speaker volume. If the test still fails, inspect the available screen-capture audio settings and check the specific game’s behaviour.
Where is Internal Audio in Streamlabs Mobile for Android?
Open Main Menu > Streaming Settings > Audio Settings and add an Internal Audio source. Then test the game or video in a short broadcast and confirm the sound in the replay. App labels and source behaviour can vary, so adding it is a step to test, not a guarantee.
Why can viewers hear the game but not me?
Check Streamlabs’ mute control and selected input, then disconnect Bluetooth accessories and test with the built-in microphone. If that works, reconnect accessories one at a time. External microphone compatibility depends on the phone, so a microphone that works elsewhere may not be the input Streamlabs is using.
My alerts are silent, but the game and voice work. What should I check?
Inspect the alert configuration and confirm its sound file uses a format Streamlabs lists for your operating system. Trigger a test alert and check what the stream replay contains, not just what you hear locally. Alert playback is a separate path from game audio, and headphone behaviour should be tested rather than assumed. +#+#+#+#+#+