If OBS appears to pause when you minimise a window, first check whether you minimised OBS Studio itself or the app OBS is capturing. Those are different problems: hiding OBS’s interface normally does not change the selected scene, while minimising a captured browser, game or other target can affect what its source delivers.
Before changing settings, compare OBS’s preview with the live picture in YouTube Studio or on another device. A frozen local preview alone does not prove that YouTube has stopped receiving the stream; the result depends on your operating system, OBS version and capture method.
Identify which window was minimised
The word “minimised” can describe two separate actions. You might minimise the OBS Studio window to clear your desktop, or minimise the browser, game, media player or other window that appears in an OBS scene. Write down which one you did immediately before the symptom. If you are not sure, repeat the test and minimise only one window at a time.
An OBS scene is made from sources, such as a display, a particular window, a game or a capture card. The source is what OBS uses to build the picture it sends out. Hiding the OBS interface is not the same as hiding or changing a source. Conversely, minimising the app being captured can change what a window-capture source can show, even if OBS remains open and its stream connection is active.
Record what “pause” means in your case. Does the OBS preview stop updating? Does the picture on YouTube freeze while audio continues? Does YouTube playback stop altogether, or does OBS report that its stream has disconnected? Those observations point to different causes. A brief pause in one display is not enough to identify a dropped broadcast.
For example, if a devotional channel shows a browser playing a slideshow, test what happens when you minimise that browser while leaving OBS visible. Then restore it and minimise OBS instead. If only the first action changes the picture, investigate the browser capture source. If the second only hides OBS from your desktop, there may be no stream problem at all.
A small note helps avoid chasing several causes at once: record the window you minimised, the source type, the time of the test and what you observed in OBS and on YouTube. If you later need help, those details are more useful than saying only that “OBS paused”.
Check OBS’s interface and system-tray behaviour
If you want OBS out of the way while it runs, look for the system-tray settings in OBS. OBS’s overview guide explains that the system-tray icon is required for hiding OBS to the tray. Some versions also include an option worded along the lines of “Always minimize to system tray instead of task bar”. Labels and locations can differ between versions, so use the settings shown in your installed build rather than following an old menu path blindly.
The tray option changes where the OBS interface goes when you minimise it. It does not choose a different source, keep a captured app visible, or establish that YouTube is receiving a healthy picture. Treat it as a way to keep your workspace clear, not as a capture fix. OBS’s overview guide describes scenes, sources and the tray at a general level; check your own version for the current interface details.
Test the tray behaviour while watching a separate display of the output. Start with OBS visible and note the preview. Minimise OBS to the tray, then check the YouTube feed from a phone or another device. Restore OBS and confirm it is still streaming. If the remote feed continues, hiding the interface was not the cause of an interruption, even if the preview is no longer in front of you.
Do not confuse minimising with closing OBS. Closing the application, signing out or shutting down the computer can end a locally operated broadcast. If you are unsure whether OBS is still open, look for its tray icon and check its stream status when you restore the window. Avoid ending a process simply because the main window is not visible.
Diagnose the captured app or target window
If the picture changes only when you minimise the app shown in the scene, restore that app and repeat the test. If the image returns, the evidence points towards the source or the target window’s behaviour, rather than OBS’s interface. A window-capture source is tied to a selected window; when that window is minimised or no longer draws its contents in the expected way, the captured image may stop changing or become blank. That behaviour is not identical for every app or platform.
Check the source selected in the scene and make sure it still points to the intended window. Apps can open a new window, change titles or switch between a launcher and the actual content window. If the source is attached to the wrong target, it may look like a pause when the app changes state. Restore the content window, check the source properties, and test again before replacing settings elsewhere.
Also check whether the source is visible in the active scene. OBS’s source visibility controls affect whether a source is included in the output. A source accidentally hidden, covered by another source, or absent from the active scene can produce a different symptom from a captured app that stops updating. The OBS guide to scenes and sources is a useful reference for checking what the scene contains.
If your channel plays a prerecorded file from an OBS media source, that is a different arrangement from capturing a separate media-player window. The file source may continue inside OBS without the player window being visible. If a loop itself ends or fails to restart, diagnose that separately; see the notes on an OBS media source ending after one video. Do not assume a minimized-window problem when the source is actually a file that has reached its end.
For a clear comparison, make a short test with the target window restored, then minimise it, then restore it again. Keep the scene, source and stream the same throughout. If you change several source properties at once, you may fix the symptom without learning which change mattered, and the same problem can return later.
Test a source suited to the content
OBS offers different kinds of sources because the thing you want to show can be a particular window, a game or a whole display. Choose based on the content, not on a promise that one capture method will always work. OBS’s documentation explains adding sources to a scene, but compatibility and behaviour still depend on the app and operating system.
| What you want to capture | A source to test | What to watch for |
|---|---|---|
| One ordinary app window | Window Capture | Does the picture change or go blank only when that target is minimised? |
| A game | Game Capture, where supported | Does the game still appear when focus changes or the game is minimised? |
| The whole desktop or a fixed visual layout | Display Capture | Does the output show the expected desktop when the target app is minimised? |
| An external camera or console output | The appropriate capture-card source | Is the external source still supplying a picture independently of OBS’s interface? |
Use this as a test matrix, not a guarantee. Game Capture is intended for game content, but a particular game, graphics setup or OS may behave differently. Display Capture can include more of the desktop than you intend, including notifications or unrelated windows. Window Capture is more selective, but its result can depend on how the target app draws its contents. Consider privacy before broadcasting an entire display.
To compare sources fairly, make a duplicate scene or note the original source settings before changing anything. Try one suitable source at a time while keeping the target content and test conditions consistent. If Display Capture works but Window Capture does not, that narrows the issue to the window-capture path; it does not establish that Display Capture is the best permanent choice for every use.
If you are broadcasting a radio-style programme from a playlist rather than capturing a player window, OBS’s media source or a purpose-built playback workflow may be a better fit. A different workflow has its own setup and restart behaviour to check. The practical distinction is whether OBS is capturing an app’s visible window or receiving media directly as a source. For another approach to a fixed audio stream, see this guide to setting up a YouTube radio stream with FFmpeg.
Verify the feed outside the local preview
A local preview is one view of the stream, not the only evidence of what viewers receive. Test with a private or unlisted broadcast if appropriate for your channel, then watch the live output in YouTube Studio’s Live Control Room or on a second device. YouTube’s live-streaming help covers encoder streams and the live control workflow. Check the current official guidance for the controls available to your account.
Keep the test simple. Start the stream with the target app visible and note the picture and audio on the second device. Minimise only OBS and check again. Restore OBS, then minimise only the captured app and check again. If possible, have someone at another location observe the feed, since a second device on the same network can still be useful for comparison but may not reproduce every viewer’s conditions.
Compare what you see rather than relying on a single status label. A preview may freeze while YouTube continues to play, or the preview may look normal while YouTube reports a problem. Check OBS’s stream status and the YouTube Live Control Room for signs of an actual disconnect or degraded feed. If the remote picture freezes but audio continues, note that separately from a full playback stop. The distinction helps decide whether to investigate capture, encoding, network delivery or the receiving device.
YouTube recommends testing encoder settings before a real broadcast. Use a controlled test to check the exact scene and source you intend to run, including the minimise action that triggers the report. Avoid experimenting during an important live programme if a private test can answer the question first. Keep a record of the result so you do not later mistake an unverified local observation for a confirmed outage.
A practical checklist is: which window moved, which source was active, whether OBS still showed an active stream, and what the second device played. If YouTube continues to show motion and sound while the local preview appears stuck, do not make disruptive changes solely on the strength of the preview. If the second device also stops, collect more evidence before changing several settings.
Account for your OS, OBS version and capture method
Capture behaviour is not identical across Windows, macOS and Linux, nor across every OBS release and graphics configuration. The precise setting name can change, and a source available on one system may not behave the same way on another. The general distinction remains useful: hiding the OBS interface and minimising a captured target are separate actions, but the appropriate source test is specific to your setup.
Before asking for help, note your operating system, OBS version, source type, the app being captured and the exact action that triggers the symptom. Include whether the local preview, YouTube playback or both changed. If the problem happens only with one target app, name it; if it happens with every source, say so. These observations make support more focused than a list of settings changed at random.
If OBS indicates rendering or encoding lag, treat performance as a separate possibility. A demanding scene or output configuration can affect the stream, but the fact that a window was minimised does not by itself prove that the computer is overloaded. OBS’s streaming guide advises testing settings and system capacity. Check OBS’s own statistics and diagnostics before reducing quality or changing unrelated settings.
When the fault persists, save an OBS log from the session in which it occurred and follow the current OBS support instructions for sharing it. The log can provide context about sources and output state that a screenshot cannot. Include a short reproduction sequence: start stream, minimise the named window, observe the named symptom, restore the window. Do not share stream keys or other credentials in a public support post.
If the stream must continue while you use the computer for other work, a local OBS workflow means the computer and its running session remain part of the operating arrangement. StreamNeo can remove the need to keep OBS open on that computer for a prerecorded-file broadcast by letting you upload the video and provide the YouTube stream key, so minimising a desktop app is no longer part of that particular workflow. It is YouTube-only; it is not a fix for a live camera or a need to capture changing desktop content.
For a longer-running channel, first decide whether the source is a fixed video or a live app that must remain interactive. The trade-offs differ: a desktop capture gives you a live view of changing content, while a file-based broadcast avoids dependence on the player window but cannot show a live desktop. A guide to running recorded exam-preparation videos from the cloud discusses that recorded-file use case. Keep the workflow aligned with the content you actually need viewers to see.
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 a frozen OBS preview mean YouTube stopped receiving the stream?
No. The preview is local, so check the live picture and sound in YouTube Studio or on another device before concluding that the broadcast stopped. Compare those results with OBS’s stream status.
How do I keep OBS running in the background while streaming on YouTube?
Use the system-tray behaviour available in your OBS version to hide its interface, and confirm that OBS remains open and streaming. This only hides the OBS window; it does not make a captured browser or game continue to display the same image when minimised.
Why does my OBS stream freeze when I minimise a game or browser?
The active source may depend on the target window continuing to draw its contents. Restore the app, repeat the test, then try an appropriate Game Capture or Display Capture source if it suits the content and your system.
What should I send OBS support if the stream still stops when minimised?
Include your OS and OBS version, the capture method, which window you minimised, and whether the preview, YouTube playback or both stopped. Reproduce the issue, save the OBS log from that session, and follow OBS’s current support guidance for sharing it.