“OBS loses focus” does not, by itself, explain why YouTube radio audio has stopped. First identify whether YouTube is playing in an ordinary browser, in a window or display OBS captures, or inside an OBS Browser Source; then use the relevant OBS mixer meter to see where the signal disappears.
If the meter keeps moving while you hear silence, investigate monitoring and your listening device. If it stops, inspect the player, capture source and routing instead. These setups behave differently, so there is no single focus setting that fixes every case.
Identify which window or source plays the audio
Start by locating the actual YouTube player. It may be in Chrome, Brave or another regular browser; OBS might be capturing that browser window or the whole display. Alternatively, the player itself might be an OBS Browser Source. Those are three distinct arrangements, even if the visible result is the same radio stream.
Write down which arrangement you have before changing anything. If YouTube plays in an ordinary browser and OBS is not capturing its audio, the browser can continue playing while you work in OBS, but the sound you hear locally does not necessarily enter the broadcast. If OBS captures the browser or desktop audio, the capture route matters. If the player is embedded in a Browser Source, its playback and OBS source behaviour are the relevant path.
Also distinguish switching focus from minimising a window, locking the computer, changing virtual desktops, resizing a browser, or allowing the computer to sleep. A report that something stopped after one of those actions does not establish that every focus change causes the same fault. Note exactly what action preceded the silence, and whether the browser player itself paused or only the stream preview lost sound.
For a 24/7 radio channel, keep the test simple: use the same browser, player, OBS scene and capture sources you normally rely on. If your programme is built from tracks with planned transitions, first confirm the playlist is actually playing; our guide to adding crossfade between tracks in a 24/7 Indian music stream covers that separate source-side concern. A silent gap between tracks is not necessarily an OBS focus problem.
Switch away from OBS and watch the relevant mixer meter
Open OBS’s Audio Mixer and identify the meter that should receive the YouTube sound. Depending on your setup, it may be a desktop-audio source, an Audio Output Capture source, or audio associated with another configured capture route. The meter is more useful than whether the OBS preview looks active: it tells you whether OBS is receiving level at that source.
Start the radio, wait for audible programme material, then switch to the window or task you suspect triggers the fault. Watch the meter while you do it. If it continues to respond in time with the music or speech, OBS is still receiving audio at that point. If it falls silent, the interruption is earlier in the chain or the selected capture source is no longer receiving the intended audio.
Do not infer too much from a single quiet moment. A spoken introduction may have a pause, and a track may have a quiet passage. Test with a section that has steady sound, and compare what happens before and after switching focus. If you can, note whether the YouTube player’s progress continues as well as whether the meter moves.
OBS’s Audio Mixer guide explains the mixer controls and meters. Use it to confirm which mixer channel you are watching and what its monitoring controls mean. Avoid changing several settings at once: if the sound returns, you will otherwise not know which change mattered.
If the meter moves, check local monitoring or listening
A moving mixer meter means the signal reaches that OBS source; it does not prove that you are listening to the same signal locally. OBS separates source input from monitoring. The monitoring control routes audio through the monitoring device configured in OBS, while the stream mix is a different destination. You can therefore have a live signal in the mixer and silence in your headphones without a capture failure.
First check the operating system’s selected output device. A headset may have disconnected, Bluetooth may have switched profiles, or the system may have selected a monitor or another output. Then check the volume of OBS and the browser in the operating system’s application mixer, if available. Application-level volume and system output selection can affect what you hear, so make the test on the computer and output you actually use.
In OBS, check the monitoring device and the source’s monitoring mode. Do not turn monitoring on blindly as a supposed fix for the broadcast: it is for local listening, and an inappropriate route can make audio audible twice or create feedback. If you are not monitoring the source, rely on the mixer meter and a controlled recording or private test rather than treating headphone silence as proof that viewers receive no sound.
A practical check is to play the radio, confirm the meter moves, then listen through the output device selected by the system. If that is silent, switch to a known working output and check application volume. Restore your intended listening setup afterwards. Keep the broadcast source and local monitoring route distinct in your notes; that makes the next fault easier to diagnose.
If the meter moves but a local recording or the stream’s audio is still absent, check whether the source is muted, excluded from the relevant track, or routed differently from what you assumed. The mixer display is a useful boundary, not a guarantee that every downstream output is correct. The OBS audio sources documentation describes source types and device capture; compare its terminology with the source names in your scene.
If the meter stops, inspect the captured source and its routing
When the relevant meter stops, identify what that source is supposed to capture. Check that the intended device or source is selected, enabled and present in the current scene. A desktop output capture, a scene-level output capture and a browser-window capture do not necessarily receive the same sound. If you have changed headphones, audio interfaces, browser outputs or scenes since the setup last worked, re-check the selected device rather than assuming OBS followed the change.
OBS documents Audio Input Capture and Audio Output Capture as scene-level sources on Windows and macOS. On Linux, the available capture choices include ALSA and PulseAudio sources. The options and names vary by operating system, so follow the source type shown in your version of OBS rather than copying a menu path from another platform. The Audio Sources guide is the primary reference for those distinctions.
Check for duplicate device routing before adding another source. OBS warns that selecting the same device in Settings → Audio and again as a scene source can produce echo. Removing a duplicate may fix doubled sound, but it is not a universal remedy for a meter that stops; the important task is to establish which route is intended and confirm that it receives the player’s audio.
For a captured browser window, test whether the browser continues to play when you switch away. Look at the YouTube player itself, not only the OBS preview. If playback has paused or frozen, OBS may have lost a capture of a player that is no longer advancing. If the player continues but the OBS meter stops, investigate capture selection, source visibility and audio routing.
There is a narrow user report worth treating cautiously. An OBS Studio issue report describes Windows 11, OBS 32.1.2, Chrome or Brave, and Window Capture or Display Capture, with playback reportedly freezing after a resize or bringing the browser forward. The reporter mentions a D3D9 ANGLE backend setting or capturing a different window as workarounds on that system. This is one report, not an official diagnosis or a general fix. Only consider it a lead if your setup closely matches, and preserve a way to undo any change.
If you are capturing a browser window for more than audio, our guide on sharing your screen while streaming on YouTube can help distinguish the visible capture from the audio path. A visible browser in the preview does not prove that its audio is reaching the mixer, and a black or stale preview does not by itself tell you whether the player is still audible.
Check Browser Source playback if applicable
If the YouTube player is an OBS Browser Source, it is not the same as a Chrome window captured by Window Capture. Review the source’s properties and determine whether it is meant to play audio, whether it is active in the current scene, and whether the source is muted or routed as expected. Test the mixer channel associated with that source while switching away from OBS.
A separate OBS issue report concerns stuttering of Browser Source video or animation when OBS loses focus on Windows 11. It is a user report about a different symptom; it does not establish that focus loss causes an audio-only YouTube stream in a Browser Source to stop. Do not apply its allegation of process throttling as a diagnosis without evidence from your own setup.
The useful distinction is what continues: does the Browser Source’s meter move, does the player appear to advance, and can you hear the sound through the configured monitoring route? If video animation stutters but audio continues, that is not the same failure as the mixer signal stopping. If the meter stops, inspect the source and its audio route; if it moves, return to the local listening checks.
Keep a note of the source URL and source properties if you are testing a Browser Source, so you can restore them. Avoid replacing the source or rebuilding the scene until a small, reversible test identifies a likely cause. A change that makes an animation look smooth is not evidence that the audio path is fixed.
Retest with the same playback setup
After one targeted change, repeat the original sequence: start the same YouTube radio, wait for steady audio, switch away from OBS in the same way, and watch the same mixer meter. Confirm separately whether the browser or Browser Source continues, whether OBS receives a signal, and whether you hear it locally. A useful test should say which of those observations changed.
If the sound still stops, restore the previous setting and test another single possibility. Record the operating system, OBS version, browser, source type and exact action that reproduces the silence. Those details help distinguish a player pause from a capture change or a monitoring issue, and they make a support request more useful than “OBS loses focus”.
For long-running channels, test the actual operating arrangement before leaving it unattended. That includes the intended scene, audio device, browser output, monitoring route and the way you switch between tasks. A short successful test cannot promise that a setup will never fail overnight, but a repeatable test and a clear source map make it easier to notice which part needs attention.
If your programme is a fixed video loop rather than a live browser player, the playback and capture design may be different. The guide to running a 24/7 Hindi songs stream with FFmpeg discusses another way to arrange a pre-recorded music stream; it is not a fix for an OBS capture fault, but it can help clarify whether your channel needs an interactive desktop at all.
When the ongoing problem is that the computer must remain on and its local playback or capture chain must remain intact, consider whether that dependency is necessary for your format. StreamNeo removes that particular burden for a pre-recorded file by letting you upload it and provide your YouTube stream key, then run the broadcast with your computer switched off; you still need to verify that the file and channel are ready, and it is a YouTube-only service. It does not diagnose an OBS configuration or help if your programme depends on a live browser, desktop interaction or a changing source.
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
Does OBS stop YouTube audio whenever I click away?
No. Clicking away does not identify the playback arrangement or prove that audio has stopped. Check whether YouTube plays in a regular browser, a captured window or display, or an OBS Browser Source, then watch the matching mixer meter.
The mixer meter moves, but I cannot hear the radio. Is the stream silent?
Not necessarily. A moving meter shows that OBS receives a signal at that source, while local monitoring and the stream output are separate routes. Check the OBS monitoring device, system output and application volume, then verify the broadcast route independently.
Should I add another audio capture source if the meter stops?
Only after confirming which device or source should carry the sound. OBS notes that selecting the same device globally and again as a scene source can cause echo, and available source types vary by operating system. Use the audio sources guide to match the source to your setup rather than adding captures at random.
Could the browser or OBS Browser Source be the cause?
It could be, but the reported cases are narrow and not universal diagnoses. Test whether the player itself continues and whether the relevant meter moves; browser playback freezing, captured audio stopping and Browser Source stuttering are different symptoms.