Hotkeys, transitions and Studio Mode workflow

Run a show without touching the OBS window: global hotkeys, transition choices, and the preview-to-program workflow Studio Mode provides.

Hotkeys are global

OBS hotkeys registered in Settings → Hotkeys fire while another application has focus, which is the point: you switch scenes from inside the game. Choose combinations a game will never use. Function keys with a modifier, or keys on a stream controller mapped to unused combinations, are safer than bare letters.

The hotkeys worth setting first

One per scene you switch to live.
Mute and unmute for the microphone. Push-to-talk and push-to-mute are separate bindings.
Start and stop recording, and start and stop the replay buffer.
Save replay, if you use the replay buffer for highlights.

Transitions

Cut is instantaneous and correct for switching between camera angles of the same moment. Fade is the safe default for scene changes. A stinger transition plays a video with an alpha channel and switches the scene at a frame you nominate; set that transition point by frame or by millisecond so the cut happens while the animation covers the screen.

Studio Mode

Studio Mode splits the interface into Preview on the left and Program on the right. You arrange, resize and correct a scene in Preview while the audience keeps seeing Program, then press Transition to push it live. It is the difference between an audience watching you drag a source into place and an audience seeing a finished shot appear.

Two details make it usable in practice: bind the transition to a hotkey so you never reach for the mouse, and remember that filters and audio changes take effect immediately on both sides. Studio Mode isolates the layout, not the audio.

Profiles versus scene collections

A profile stores output, encoder, audio device and hotkey settings. A scene collection stores the scenes themselves. They switch independently, so one set of scenes can be used with a high-bitrate recording profile and a lower-bitrate streaming profile without rebuilding anything. Switching profiles while live is not possible, so make the choice before you start.

Troubleshooting

This OBS-Studio.net editorial guide covers Troubleshooting (hotkeys-transitions-and-studio-mode). It is original explanatory writing for creators configuring OBS Studio. Verify version-specific behaviour in Help → About and in official OBS Project documentation when release notes differ.

Nothing changed

Confirm you edited the active profile. Streaming services and recording tabs are separate in Advanced output mode.

Regarding Nothing changed: For Troubleshooting (hotkeys-transitions-and-studio-mode), keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Nothing changed: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Nothing changed: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Nothing changed: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Nothing changed: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Nothing changed: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Nothing changed: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Nothing changed: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Works once then fails

Re-select windows/games after the target app restarts. Some captures bind to a process instance.

Regarding Works once then fails: For Troubleshooting (hotkeys-transitions-and-studio-mode), keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Works once then fails: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Works once then fails: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Works once then fails: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Works once then fails: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Works once then fails: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Works once then fails: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Works once then fails: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Crashes

Safe Mode → clean profile → add pieces back. Check whether a plugin update coincided with the failure.

Regarding Crashes: For Troubleshooting (hotkeys-transitions-and-studio-mode), keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Crashes: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Crashes: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Crashes: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Crashes: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Crashes: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Crashes: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Crashes: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Ask for help

Provide OBS log, OS, GPU, and exact capture method. Avoid unpaid "optimizer" tools that rewrite OBS settings blindly.

Regarding Ask for help: For Troubleshooting (hotkeys-transitions-and-studio-mode), keep scenes simple while validating the core path, then add overlays and filters once the Stats dock stays clean.

Regarding Ask for help: Document the working profile name, encoder, canvas resolution, and capture method so you can restore them after an OBS or GPU driver update.

Regarding Ask for help: If behaviour changes after an update, launch Safe Mode to isolate third-party plugins, then re-enable modules one at a time.

Regarding Ask for help: Prefer wired ethernet for live streaming tests, and measure sustained upload with headroom rather than relying on a single speed-test spike.

Regarding Ask for help: When comparing settings, record short local samples with identical content so differences are visible without inventing synthetic FPS claims.

Regarding Ask for help: Keep browser sources and animated overlays modest; expensive HTML can raise rendering load even when the encoder itself is fine.

Regarding Ask for help: Match plugin builds to your OBS major version and architecture, and uninstall leftover DLLs from older major versions before reporting bugs.

Regarding Ask for help: Use Studio Mode when rehearsing transitions so you can preview the destination scene before it goes program.

Checklist

Confirm OBS version and OS permissions
Change one setting at a time
Test with representative content for several minutes
Read the Stats dock before going live
Export a scene collection backup after a working setup

Editorial notes

Download statistics and community rating counts are intentionally omitted. Prefer official project pages and GitHub releases. This page does not claim measured benchmark FPS for hardware. Re-check platform bitrate and codec limits on the destination site before a public broadcast.