A black screen between gaming videos usually appears because the outgoing scene has ended before the next scene has a visible, working source. The reliable way to hide that gap is to switch first to a prepared holding scene, then preview and deliberately send the next game scene live.
A Cut or Fade only controls how scenes change. It does not repair a hidden source, an incorrect capture input, or a game that the encoder cannot see. This guide uses OBS as the example, but the same logic applies to other scene-based encoder software.
Prepare a visible holding scene
Create a scene whose only job is to give viewers something intentional to watch while one game closes and the next one starts. Name it clearly, such as Changing games, Next gameplay starting, or Please wait.
The scene does not need to be elaborate. A static image, a colour background, or a text source is enough. You might use a simple branded card with the channel name and the next video title. For a devotional or local-language channel, the message can be written in the language your viewers expect. For a gaming channel, a dark background with the next game's name is usually clearer than an empty desktop.
In OBS, scenes are compositions made from sources. The OBS sources guide documents sources such as images and colour sources, which are useful because they do not depend on a game, browser tab, or media file remaining open.
Make the holding scene visible before you need it. In the Sources panel, check that the image, colour, or text source has its visibility enabled. If you have several sources, make sure the holding message is not covered by a full-screen source above it. OBS displays sources higher in the list above sources lower down, so the order can change what viewers see.
A holding scene is not a cure for every black screen. It solves a specific presentation problem: viewers see a known-good scene while you close the first game, launch the next one, or wait for a capture source to become ready. If the holding scene itself is black, solve that configuration issue before using it on a live channel.
Use a local recording to test it. Start recording, switch to the holding scene, wait long enough to represent a real game change, and then stop the recording. Watch the file from the beginning. This catches a transparent image, an unexpectedly hidden source, or text placed outside the canvas before the audience sees it.
Build and layer the next game scene
Keep each game in its own clearly named scene. For example, use Game A, Game B, and Intermission rather than several scenes all called Live. Clear names matter when you are switching quickly or handing operation to another person.
A game scene commonly contains a game capture source, a camera source, alerts, a logo, and overlays. Add them deliberately. The game capture should occupy the intended part of the canvas, while decorative elements should not cover it unless that is intentional. If an overlay is full-screen and opaque, it can make a working game capture look like a black output.
Before a live switch, open the game and confirm that the capture source is receiving it. A scene can exist correctly while its capture source receives no picture. This is particularly important when changing from one game to another, because the new title may use a different display mode, executable, window, or capture method.
Do not assume that copying the old scene is always enough. A duplicated scene may retain a source configured for the previous game. Review the source properties and the visible source list for the new scene. If the game is running in a window, confirm that the selected window is the one you intend to show. If the game is full-screen, check that the chosen capture method supports the way the game is running on your system.
The exact fix for a failed capture depends on your operating system, game, permissions, graphics configuration, and capture method. Avoid changing several unrelated settings at once. First establish whether the source is visible in the scene, then whether it is receiving the game, and only then investigate more specific compatibility issues.
If your channel uses prerecorded gameplay rather than an operator changing scenes manually, the same preparation still helps. A useful guide to the wider workflow is making an always-on gaming channel from prerecorded gameplay. It covers the channel model; this article focuses on preventing the visible gap between scenes.
Preview with Studio Mode
Studio Mode separates the scene you are preparing from the scene viewers are currently seeing. The live output remains on one side while the next scene is shown in preview on the other. This gives you a place to inspect the next game before committing it to the stream.
Select the next game scene and look at the preview. Check that the game is present, the layout is correct, the camera is framed properly, and no full-screen source is hiding the capture. If the preview is black, do not send it live simply because the transition is ready. Return to the scene and source checks.
Studio Mode does not automatically verify that a capture source works. It shows you the result of the scene you selected. You still need to examine the picture and, if necessary, the source properties and the game itself. A black preview is useful evidence that something needs attention, not a confirmation that the setup is safe.
A practical handoff looks like this:
- Switch from the current game to the holding scene.
- Launch or select the next game.
- Select the next game scene in Studio Mode.
- Wait for a visible picture in preview.
- Check the layout and source order.
- Send the prepared scene live with the chosen transition.
If you operate a long-running channel alone, rehearse this sequence until it is unremarkable. The goal is not to switch faster. The goal is to give yourself enough time to see whether the destination scene is genuinely ready.
You can operate the sequence with OBS scene buttons or hotkeys. A physical controller can make the buttons easier to identify, but it does not replace the checks. Elgato’s OBS Studio integration documentation describes actions for scenes, Studio Mode, source visibility, and transitions. Treat such hardware as a control convenience, not as a fix for a failed capture source.
Switch with Cut or Fade
Once the holding scene is live and the next game is visible in preview, choose how to reveal it. A Cut changes immediately. It suits a quick handoff where the destination is already ready and you do not want viewers to see a blend between the two scenes.
A Fade changes gradually over its configured duration. It can make a game change feel less abrupt, especially if the holding card has text or music and you want the next scene to appear gently. It does not make a missing destination source visible. If the next scene is black, a Fade can simply turn the holding scene into a black scene more slowly.
OBS documents built-in transitions including Cut and Fade in its Studio Overview. Check the selected duration rather than assuming the previous setting is appropriate. A very short fade may look like a cut, while a longer one may leave viewers watching an unnecessary blend.
| Choice | What viewers see | Use it when | What it cannot do |
|---|---|---|---|
| Cut | The destination appears immediately | The next game scene is ready and you want a direct handoff | It cannot repair a black or hidden source |
| Fade | The holding scene blends into the destination | A softer change suits the channel pace | It cannot make an unreceived game capture work |
Test the complete route rather than testing the transition in isolation. Record Game A → holding scene → Game B, then watch the recording. Confirm that the holding content remains visible for the whole preparation period and that Game B appears cleanly at the end.
For an always-on channel, a deliberate pause is usually better than a hurried switch. Viewers can understand a short holding card. They cannot understand why a black screen appeared without explanation, particularly if the stream continues for several minutes.
Check source visibility and capture input
If black output persists, stop treating it as a transition problem. Work through the active scene from the outside in.
First, confirm which scene is live. It is easy to prepare Game B in preview while Intermission remains on the live output. Studio Mode intentionally keeps those views separate, so look at the live side before deciding that the wrong scene has failed.
Next, inspect source visibility. A hidden eye icon, a disabled source, or a source placed outside the canvas can produce an empty-looking result. Check the source list from top to bottom. A full-screen image, colour source, browser source, or overlay above the game capture can cover the picture underneath it. Temporarily hide the suspected covering source and see whether the game appears.
Then check the capture input. Is the source pointed at the correct game or window. Is the game open. Has it changed from windowed to full-screen mode. Is another copy of the game running. Does the capture source show a picture in the scene before you switch it live.
Keep the diagnosis narrow. If a known-good image appears in the same scene but the game does not, the scene canvas and output are probably functioning, while the game capture deserves attention. If neither the image nor the game appears, review scene selection, source visibility, layer order, and the output path before changing game-specific settings.
Do not delete and rebuild the whole scene as a first response. A duplicate scene can make it harder to see which source is wrong. Instead, take notes, change one setting, and check the preview again. If you are working on a production channel, record the test locally so you can compare the result without relying only on a small preview window.
The YouTube Live Control Room guide is useful for separating encoder-side checks from YouTube-side controls. YouTube Studio can manage the broadcast and its settings, but it cannot make an incorrectly configured game capture source produce a picture.
Confirm the intended scene is live
A clean preview does not prove that viewers are seeing the same scene. Before switching, identify the live programme area and the preview area. After switching, look again at the live side and confirm that it now contains the holding scene or the intended game scene.
If you operate with hotkeys, avoid assigning similar shortcuts to several scenes. A shortcut that sends you to the wrong scene can look like a capture failure when the real problem is an unexpected scene selection. Buttons with explicit names are easier to audit than a row of unnamed controls.
For a remote or cloud-based workflow, confirm the final output in YouTube Studio as well as in the encoder. YouTube describes live streaming for gaming and directs creators to YouTube Studio for live setup and management in its live streaming overview. The platform view may not update at precisely the same moment as the local preview, so allow time for the handoff to appear before repeating the switch.
When a channel must run while your computer is switched off, uploading the file once and handing the YouTube stream key to StreamNeo removes the need to keep a local scene-switching computer running for that file-based broadcast. You still need to check the video, stream settings, and YouTube status before relying on the channel, and this does not replace capture troubleshooting for an OBS gaming workflow.
For a broader comparison of local and hosted approaches, see OBS and a cloud streaming service compared. The important distinction here is operational: OBS gives you direct scene and capture controls, while a file-based cloud workflow is suited to prepared video rather than live game capture.
Diagnose persistent black output
Use this order when the holding scene or game scene remains black:
- Check the live scene. Confirm that the scene currently sent to viewers is the one you think it is. Studio Mode can leave a different scene in preview.
- Check for a known-good source. Add or reveal a simple image, colour, or text source. If that appears, the scene can render a source and the game capture is the next suspect.
- Check visibility. Make sure the source is enabled and not hidden.
- Check layer order. Move the game capture above sources that may cover it, or temporarily hide those sources.
- Check the input. Confirm that the selected game or window exists and is actually displaying the game.
- Check the game state. Look for a loading screen, minimised game, changed display mode, or a different running instance.
- Test before going live. Use Studio Mode and a local recording to verify the complete sequence.
A black holding scene points to a problem with that scene's own source or output. A visible holding scene followed by a black game scene points more specifically towards the destination scene, its source visibility, its layer order, or its capture input. That distinction prevents you from repeatedly changing transitions when the transition is not the cause.
For a 24/7 channel, write down the exact working sequence after you resolve it. Include the scene names, which source is the game capture, which source provides the holding card, and what you check before switching. This is especially useful if another person takes over the channel overnight.
The same discipline helps with other long-running failures. For example, if a media source stops at the end of a file rather than showing a black screen during a scene change, the troubleshooting path is different. The guide to fixing an OBS media source that is not looping covers that separate problem.
Do one full rehearsal before the next public broadcast. Start with the first game, move to the holding scene, prepare the second game in preview, switch it with the selected transition, and watch the recording. A short rehearsal can reveal a wrong scene, hidden source, bad layer order, or unready capture input while there is still time to correct it.
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
Will Fade prevent a black screen?
No. Fade controls the visual change between two scenes, but it cannot repair a destination scene with a hidden source or failed game capture. Prepare a visible holding scene and verify the next scene in preview before switching.
Does Studio Mode confirm that game capture is working?
No. Studio Mode lets you inspect the scene you are preparing before sending it live. You must still check whether the capture source is visible and receiving the intended game.
What should viewers see while I change games?
Use a dedicated holding scene with a static image, colour, or text source. A clear message such as “Changing games” tells viewers that the stream is still intentional while the next game loads.
Should I buy a Stream Deck for this workflow?
It is optional. It can make scene and transition controls easier to trigger, but it cannot correct a wrong scene, hidden source, incorrect layer order, or failed game capture.