Hotkeys in Streamlabs Desktop let you trigger supported streaming, recording, scene, and source actions from the keyboard instead of opening a menu. To set one up, open Settings > Hotkeys, select the action, click its hotkey field, and press the key combination you want to use.
The exact action available depends on what you are configuring, so a shortcut that works for a microphone or recording control is not automatically available for every source. Streamlabs recommends using at least two keys together to reduce accidental triggers, but you should still test each binding in the context where you intend to use it.
What Hotkeys Do in Streamlabs Desktop
A hotkey is a keyboard combination assigned to an action in Streamlabs Desktop. Once it is assigned, pressing that combination can perform the action without requiring you to move through the application interface.
Streamlabs gives examples such as starting or stopping a stream, muting the microphone, saving a replay, skipping alerts, and showing or hiding a source. The source controls can apply to a particular scene, which makes them useful when you want to change what viewers see without switching scenes manually.
For example, you might assign one shortcut to mute your microphone before speaking to someone nearby. In a different scene, you might assign another combination to hide an alert box while recording a clean section of a devotional, study, or local news presentation. These are separate bindings because the second action concerns a source in a scene rather than a general audio control.
Hotkeys do not create a new function. They provide a faster way to trigger an action that Streamlabs Desktop already exposes in its Hotkeys settings. The available fields and labels are therefore more important than a list of shortcuts copied from another installation.
Do not assume that a binding will work in every application or context. A shortcut may be affected by the active application, another programme using the same combination, keyboard layout, permissions, or the particular Streamlabs action you selected. Streamlabs’ instructions describe the assignment process, not a guarantee that every combination will be accepted or recognised everywhere.
You also do not need a dedicated controller to follow this guide. Streamlabs describes native keyboard hotkeys as an alternative to buying a stream deck. A physical controller can be useful later if you want buttons you can identify by touch, but it is not required for assigning a keyboard shortcut.
If your wider aim is an unattended channel rather than a live production you operate from a desk, hotkeys are only one part of the decision. The comparison in OBS versus cloud streaming for a 24/7 YouTube podcast channel explains the trade-off between keeping a streaming application running on your own computer and using a different operating arrangement.
Open the Hotkeys Settings
Start Streamlabs Desktop and wait for the main window to finish loading. Then follow this path:
- Click the Settings cog.
- Choose Hotkeys in the settings menu.
- Scroll through the available actions until you find the function you want to control.
The important path is Settings > Hotkeys. If you are looking at the editor, Scenes, Sources, or the live control area, you have not yet reached the page where the keyboard combinations are assigned.
The settings page may contain more fields than you need. Global controls are usually near the beginning, while scene and source controls require you to scroll further. Take a moment to identify the action before pressing any keys. This avoids assigning a combination to a similarly named field and then wondering why a different control responds.
Streamlabs’ support guide for setting up hotkeys in Streamlabs Desktop documents this route and the assignment process. Software labels can change between releases, so compare the wording on your screen with the current support guidance rather than relying on a screenshot from an older tutorial.
Before making changes, decide what you actually need the shortcut to do. A small set of memorable bindings is easier to test than a large collection that you rarely use. For a simple channel, microphone mute and one or two scene or source controls may be enough. For a more involved production, you can work through the list methodically and test each action separately.
Choose an Action to Bind
The Hotkeys page groups actions by what they control. Look first for the general function you want, then check whether there is a scene-specific or source-specific version further down the page.
Common examples documented by Streamlabs include:
| Need | Type of action to look for | What to check |
|---|---|---|
| Control your voice | Microphone mute or unmute | Confirm that it affects the intended microphone |
| Control a broadcast | Start or stop streaming | Check which account and output you are using |
| Save material for later | Save a replay or recording action | Confirm that replay or recording is configured first |
| Change what viewers see | Show or hide a source | Select the intended scene and source |
| Manage notifications | Skip an alert | Check that the alert system is active |
| Mark a useful moment | Marker or timestamp action | Confirm where the marker will be stored or used |
These are examples of documented action categories, not a list of universal default bindings. Streamlabs does not provide a reason to assume that a fresh installation has the same shortcuts as another computer, so treat each field as unassigned until you verify it yourself.
For a source action, read the full label before assigning anything. “Show” and “Hide” may refer to a particular source in a particular scene, while “Show/Hide” may toggle the current state. The distinction matters if you want predictable behaviour during a broadcast.
A practical test is to describe the result in one sentence: “When I press this combination, this source in this scene should become visible.” If you cannot complete that sentence, inspect the scene and source selection before binding the key.
Scene and source hotkeys are useful for live layouts, but they do not replace preparation. If you use a 24/7 loop, check the media, scene order, and source visibility before going live. The guide to avoiding duplicate content problems with a 24/7 YouTube stream covers a separate content concern that a keyboard shortcut cannot solve.
Assign a Key Combination
Once you have found the action, click its hotkey field. The field is the area where Streamlabs displays the current assignment, if one exists. With the field active, press the combination you want to use.
Streamlabs recommends a combination of at least two keys to reduce the chance of triggering an action accidentally from another application. A combination such as a modifier key plus another key is generally easier to distinguish from ordinary typing than a single letter. The recommendation is practical guidance, not a promise that a particular combination will be available in every programme or keyboard setup.
Choose combinations that you can remember and press without looking away from the production. Avoid a key that you use frequently for ordinary typing, especially if the action changes a scene, mutes a microphone, or stops a broadcast. Also avoid combinations that are already used by another tool you keep open.
After pressing the keys, look at the field. It should display the combination that Streamlabs registered. If it remains blank, try clicking the field again and pressing the keys more deliberately. If it shows a different combination, remove it and repeat the assignment rather than assuming the first attempt was accepted.
Do not assign the same combination to several actions unless you have deliberately checked how Streamlabs handles that arrangement. When two actions share a binding, the result may not be what you expect, particularly when one action belongs to a scene or source and another is global. A predictable control layout is more valuable than having a shortcut for every possible function.
For a source binding, scroll to the relevant scene and source section and repeat the same process. You may need separate assignments for the same type of source in different scenes. Hiding an alert box in one scene does not mean that an identically named source in another scene has automatically received the same binding.
If the key combination is used by your operating system or another application, Streamlabs may not receive it consistently. A binding can be correctly displayed in the Hotkeys page and still fail when another programme has focus or claims the same keys. Test it in the actual working arrangement rather than only in the settings window.
Review and Save Your Bindings
When you have assigned the first hotkey, review the surrounding fields before moving on. Check the action name, the scene, the source, and the displayed key combination. This is especially important for Show and Hide controls, because a technically valid binding can still point to the wrong source.
Streamlabs’ setup instructions tell you to scroll through the Hotkeys page for individual scenes and sources. Do not stop after assigning a global action if your goal is to control a particular visual element. Work through the relevant scene sections and leave unrelated fields unchanged.
Use a small written control plan if you operate a channel regularly. It can contain three columns: action, key combination, and test result. For example, record “microphone mute”, the combination you chose, and whether the microphone indicator changed as expected. This is more reliable than trying to remember a growing set of shortcuts during a long broadcast.
Test in an order that limits risk:
- Test a reversible action, such as showing or hiding a non-essential source.
- Test the microphone control and confirm the state visually or by monitoring the audio path.
- Test a scene change or alert action if your production uses one.
- Test recording, replay, or stream controls only when you are ready for the action to occur.
A shortcut that triggers an action once is not fully tested. Press it again where the action is reversible and confirm that the second press behaves as expected. For a source toggle, verify both visible and hidden states. For a mute control, check both muted and unmuted states.
Keep the binding plan close to the keyboard if more than one person operates the channel. This is useful for devotional streams, study channels, and local news loops where the operator may return after several hours and need to understand the control layout quickly.
If you plan to move the channel away from a computer that must remain on, hotkeys may become less central to the daily operation. Moving a 24/7 YouTube stream from a PC to a cloud server discusses that operating choice. StreamNeo removes the specific problem of leaving Streamlabs running on your own computer by letting you upload a video, add your YouTube stream key, and have the channel run without that computer, but it does not control Streamlabs Desktop hotkeys.
Troubleshoot a Hotkey That Does Not Work
Start with the documented checks rather than assuming that the key combination itself is defective. First return to Settings > Hotkeys and confirm that the intended field still displays the combination. If it is missing, reassign it and test again.
Next, confirm that you selected the right action. A global microphone binding and a source Show/Hide binding can look similar while affecting different parts of the production. For a source action, verify the scene and source name. If the source is not present in that scene, the shortcut cannot produce the result you expected.
Check whether another application is active or using the same combination. Test with Streamlabs Desktop in focus, then test in the normal arrangement you use while broadcasting. If the shortcut works only when Streamlabs is focused, another application or the operating system may be intercepting it when focus changes. That does not mean the binding is universally available outside Streamlabs.
Also check your keyboard layout and the actual keys being sent. A combination that is easy to press on one layout may produce a different key event on another. Wireless keyboards, remapping utilities, accessibility settings, and remote-desktop sessions can add another layer between the physical key and Streamlabs Desktop.
When Show/Hide does not respond
Streamlabs has published a support page about Show/Hide hotkeys not responding for some source types. Its documented workaround is to turn Dual Output off and on, then test the binding again. Follow the control as it appears in your installed version rather than assuming that the setting is in the same place as it was in an older release.
The support page currently contains conflicting status and date information, so treat the toggle as a documented workaround rather than proof that every installation has the same issue or that the issue has a single permanent status. If the workaround does not help, check the current Streamlabs support article about Show/Hide hotkeys and compare its advice with your installed version.
If the action still fails, remove and recreate the binding, then test a different two-key combination. Keep notes about the scene, source type, Streamlabs version, keyboard layout, and whether Streamlabs had focus. Those details make a support report more useful than simply saying that hotkeys do not work.
Do not change several settings at once. If you disable overlays, replace sources, change scenes, and reassign keys together, you will not know which change affected the result. Revert to a simple test scene with one source, assign one binding, and add complexity only after the basic action works.
When a stream or recording control behaves unexpectedly
For actions that start or stop a stream or recording, confirm that the relevant output is configured before testing. A hotkey cannot substitute for an account connection, an enabled output, or a valid scene and source setup. Test these controls only when you are prepared for a real state change.
For replay and marker actions, verify that the related feature is enabled and that you know where the resulting file or marker is expected to appear. Streamlabs’ tutorial discusses marker and timestamp actions, including a custom title for later editing. The exact result still depends on the feature and output settings in your installation.
If a combination works in Streamlabs but not while another application is selected, use it only in the context where it is reliable or choose a different operating method. The safe conclusion is not that every Streamlabs hotkey works system-wide. It is that the binding works under the conditions you have tested.
Build a Reliable Hotkey Routine
Hotkeys are most useful when they remove a repeated interruption from a process you already understand. Assigning a shortcut to every available field can make a layout harder to operate, particularly when several actions have similar names.
Begin with the controls that prevent a visible or audible mistake: microphone mute, a clean scene or source change, and any alert control you genuinely use. Test those controls during a rehearsal. Then add recording, replay, or marker bindings if they support your editing routine.
Use combinations that have a clear pattern. For example, you might reserve one modifier for audio controls and another for scene or source actions, provided those combinations do not conflict with other software. Do not copy a pattern from another operator without checking which keys are already used on your keyboard.
Keep a fallback method available. If a hotkey stops responding during a broadcast, you should still know how to mute the microphone, change the scene, or hide the source through the Streamlabs interface. A keyboard shortcut is a convenience, not the only route to a critical action.
Review your bindings after changing scenes, renaming sources, updating Streamlabs Desktop, replacing a keyboard, or changing the computer used for production. A quick test before an overnight broadcast is more useful than discovering a broken Show/Hide control after viewers have already seen the wrong layout.
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
Where are hotkeys in Streamlabs Desktop?
Open Streamlabs Desktop, click the Settings cog, and choose Hotkeys. The page contains fields for general controls and, further down, actions associated with individual scenes and sources.
How do I assign a hotkey in Streamlabs?
Find the action you want, click its hotkey field, and press the desired key combination. Streamlabs recommends using at least two keys to reduce accidental triggers, after which you should test the binding in the context where you will use it.
Why is my Show/Hide hotkey not working?
Confirm the scene, source, and displayed binding first, then test with Streamlabs Desktop in focus and check for another application using the same keys. Streamlabs documents toggling Dual Output off and on as a workaround for some Show/Hide problems; consult the current support page if that does not resolve the issue.
Do I need a stream deck to use Streamlabs hotkeys?
No. You can assign and use keyboard combinations directly in Streamlabs Desktop. A dedicated controller is optional if you prefer physical buttons, but it is not required for the setup described here.