OBS documents Window Capture for the League lobby and Game Capture for the actual match. Configure the two scenes separately, then test switching into and out of a practice game before relying on automation.
Use the correct source for the League client and the active game, then rehearse manual or automatic scene switching through a full practice cycle.
In this guide
Before you start
- Windows, League of Legends and OBS 31.1+ for the documented switcher workflow.
- A practice session where you can enter and leave a game without disrupting others.
Treat the client and the match as separate targets
A working lobby capture does not prove the match will appear in the same source. League uses separate client and game windows in the documented OBS workflow. Build a Lobby scene and a Match scene so each has a clear capture responsibility and a useful fallback if the other is not ready.
The official OBS guide specifies Window Capture for LeagueClientUx.exe and Game Capture for League of Legends.exe. It also describes the built-in Automatic Scene Switcher for OBS 31.1 and later. Establish both pictures manually before adding the switching rule.
Prepare a complete round trip
Use training or another suitable practice mode to make the actual game process available. The capture target cannot be selected reliably from the launcher alone. Keep a safe holding scene available while you build the setup and avoid testing the first automatic handoff during a public match.
Write the expected sequence: lobby visible, game starts, match becomes visible, game ends, lobby returns. Include the moments when a window closes or loses focus. The switcher should be judged against this complete sequence, not only the first successful entrance into the game.
Get both scenes working before automation
Capture the lobby
Create the Lobby scene with Window Capture targeting LeagueClientUx.exe. Check that the client updates when you navigate harmless lobby screens.
Look for: The scene shows the client rather than a frozen or unrelated window.
Capture the active match
Enter a practice game, create the Match scene and add Game Capture targeting League of Legends.exe. Record a short movement sequence.
Look for: The actual match picture works independently of lobby capture.
Rehearse the handoff, then the switcher
First switch manually through Lobby, Match and back. If automating, open Tools → Automatic Scene Switcher and map the focused client window to Lobby and the game window to Match. Check the fallback when a window is absent, activate the switcher and repeat the round trip.
Look for: The automatic changes match the expected sequence and the return to lobby is verified.
Check what happens when you use another window
During the practice cycle, briefly use the other applications you normally need, such as chat or notes. Observe whether the switching behavior remains appropriate. A rule based on window presence or focus should be understood in the actual operating routine, including the moments between the client and game.
If the automatic result is unpredictable, leave automation inactive and use a deliberate manual scene change while investigating. A reliable manual handoff is a useful baseline. Keep the exact rule settings with your notes so you can explain which condition caused an unwanted switch.
Verify continuity without duplicating the game sound
Listen to the recorded round trip. Check that the microphone remains where intended and that the game or client audio enters the mix once. Scene switching can make a routing gap more noticeable, but adding several overlapping desktop and application captures can create a different problem.
After an update, run the practice sequence again if the window names or process behavior change. Keep the two source targets explicit and preserve the working manual scenes. The finished setup should make both the active game and the return to client predictable, including the less exciting moments between them.
Still stuck?
The lobby works but the match scene is blank.
Enter an actual practice game and select its League of Legends.exe window in Game Capture; the client target is a separate process.
Sources & references
Based on the linked first-party OBS documentation checked on 4 November 2026. The exercises and acceptance checks are editorial workflows for you to run; no hands-on OBS session or hardware benchmark is claimed.
- OBS — League of Legends Capture Guide ↗Checked 2026-11-04
Spotted something out of date? Let Alex know.
How we put our guides together ↗