Streamlabs Desktop’s hotkeys are keyboard shortcuts you assign in the desktop app. To trigger controls without reaching the computer, you can use a compatible physical control console to activate shortcuts, or use the separate Streamlabs Controller phone app; its documented QR setup connects over your local network.
These routes solve different problems. Start with the Hotkeys panel to see which actions Desktop currently supports, then choose a keyboard, console or phone workflow that suits where you are and how your devices connect.
Choose what you mean by remote control
“Remote” can mean sitting away from the keyboard but still in the room, or controlling a broadcast from another place. A keyboard shortcut is convenient when you are at the computer. A physical console can put selected actions on dedicated buttons, but it still needs to work with the computer and your Streamlabs setup. The Controller app uses a phone, with the ordinary QR connection relying on the phone and computer being on the same local network.
| Approach | Where you trigger it | Connection scope | What you need to check |
|---|---|---|---|
| Desktop hotkey | Keyboard at the computer | Local to the Desktop session | Whether the action appears in Settings > Hotkeys and whether the chosen keys conflict with other software |
| Physical control console | Buttons on an external console | Depends on the console’s integration with Desktop | Current compatibility and setup instructions for the intended device |
| Streamlabs Controller app | Phone | QR setup uses the same local network; internet access is a separate, advanced route | App and Desktop setup, local-network visibility, and firewall access |
None of these methods should be assumed to offer the same actions or connection range. A phone is not simply a wireless keyboard, and a console is not automatically connected by scanning the app’s QR code. Decide what you want to do—for example, mute a microphone from the other side of a small studio—and whether you need to do it outside the local network. Then choose the route that actually meets that need.
If you are trying to operate a stream from a different location, consider the wider setup as well as its controls. Our guide to live streaming video from a remote location covers the planning questions around working away from the usual broadcast position. Remote control by itself does not remove the need to check what the computer and network can reach.
Assign hotkeys in Streamlabs Desktop
Open Streamlabs Desktop, click the Settings cog, and choose Hotkeys. The panel lists the functions for which you can assign shortcuts. Select the field for an action and enter the key combination you want to use, following the interface’s prompts. The exact assignments you see can depend on the current version and available functions, so use the panel rather than a shortcut map copied from an older guide.
Streamlabs’ guide recommends that a hotkey use a combination of at least two keys. The point is to reduce accidental triggers when you use a key in another application. A single key that is harmless while browsing can have an unwanted effect during a broadcast if it is also bound to a stream action. A combination such as a modifier plus another key is easier to distinguish, provided you can press it reliably.
Choose combinations that you can remember under pressure and that do not collide with the shortcuts you already use in games, editing software or other production tools. If you share the computer, make the mapping clear to other operators. Write down the action and its combination near the control position until the layout becomes familiar. This is a working reference, not a substitute for checking the current assignments in Desktop.
Streamlabs’ instructions for setting up hotkeys in Streamlabs Desktop describe the Settings > Hotkeys route and the available categories. Use the current guide if the interface changes, and review the panel again after changing profiles or updating the software. Do not assume that a binding from another computer or an old video tutorial will be present in your installation.
After assigning a shortcut, test it in a quiet session before relying on it live. Check that the intended action occurs, that holding or tapping the combination behaves as expected, and that another programme does not intercept it. If Desktop provides a way to clear or change a binding, use that to resolve a conflict rather than layering more shortcuts on top of an uncertain one.
Choose actions and shortcuts
Streamlabs lists hotkey assignments for stream and recording controls, microphone mute, replay saving, skipping alerts, scene and source controls, and recording markers. The precise functions available to you should be verified in your own Hotkeys panel. It is not safe to infer that every action in the application can be bound, or that every version presents the same choices.
Start with actions where a quick, deliberate trigger matters. For a talk, interview or local news segment, muting a microphone or changing to a prepared scene may be useful. For a recorded class or music programme, a recording marker or replay action may be more relevant. If you run a long loop, a shortcut to start or stop a stream might be worth assigning, but protect it from accidental presses and make sure everyone operating the computer knows what it does.
Separate high-consequence actions from routine ones in your layout. Stopping a stream should not be placed beside a key you frequently hit while typing. If the panel supports the action, use a combination that requires an intentional hand movement. The aim is not to make every command complicated; it is to make the important commands hard to trigger by mistake and straightforward to find when you need them.
Consider how your actions relate to your scene and source setup. A scene-change hotkey is only useful if the destination scene is prepared and labelled clearly. A mute shortcut is only useful if you know which microphone it affects. Test actions one at a time, then test a realistic sequence—for example, switch to a holding scene, mute the microphone, and return to the programme scene. This reveals ambiguous labels and unintended effects before an audience is watching.
For a YouTube broadcast, Desktop controls are only one part of what the audience sees. If a stream is already running and repeatedly dropping, a hotkey will not explain why; our troubleshooting guide for a 24/7 stream that keeps stopping is a better starting point for diagnosing that separate problem. Likewise, check YouTube’s own current guidance where you need to confirm live-stream setup requirements.
Trigger shortcuts with a control console
A physical control console can make selected actions easier to reach: instead of remembering a keyboard combination, you press a labelled button. Streamlabs’ hotkey guide names Stream Deck and Loupedeck as examples of creator consoles that can be used with hotkeys. That is a category-level statement, not confirmation that a particular model, firmware or configuration will work in every setup.
Before buying or configuring a device, check its current compatibility information and instructions for the specific Streamlabs Desktop version and workflow you use. Confirm whether the device triggers keyboard shortcuts, requires a separate profile or uses another supported integration. Do not assume that every button can invoke every Desktop action simply because the device is marketed for streaming.
A useful layout reflects the way you actually operate. Put frequent, low-risk actions in easy reach and make consequential actions visually distinct. Label buttons with verbs such as “Mute mic” or “Holding scene”, not vague names that require you to remember what a symbol means. If another person takes over the broadcast, a clear label can prevent a mistaken press more effectively than a complicated layout.
Keep the underlying hotkey mapping documented. If you change the Desktop shortcut but do not update the console’s corresponding button, the physical control may call the old combination. After any change, check both the Desktop assignment and the console profile, then run the same test sequence you will use during a programme. If the console is unavailable, know how to perform the action from Desktop or the keyboard so you are not dependent on one button.
A console is a good fit when you operate at the computer and want tactile controls for a small set of repeated actions. It is not a way to control a desktop from another city by itself. If the requirement is to use a phone, assess the Controller app separately rather than treating a hardware console and a phone app as interchangeable remote interfaces.
Connect with the Streamlabs Controller app
The Streamlabs Controller app is a separate phone-based method. For the documented QR connection, the phone and the computer running Streamlabs Desktop need to be on the same local network. This is normally the home, studio or venue network, not an arbitrary internet connection from somewhere else. The QR code does not make the app’s ordinary local connection work across any distance or network.
Streamlabs’ Controller app connection guide says to update the app, connect the phone to the same local network as the computer, and open Settings > Remote Control in Desktop to display the QR code. In the phone app, open Remote Control and scan it. The guide also identifies network conditions that can block discovery: access-point isolation, guest Wi-Fi settings that prevent clients from reaching the local network, and the computer’s firewall. Check those conditions if the phone cannot connect.
For example, a creator may have the computer on the studio router while the phone is on guest Wi-Fi. Both devices appear to have internet access, but that does not mean they can see each other locally. Put the devices on a network that permits local communication, and allow Streamlabs Desktop through the computer’s firewall as appropriate. Avoid changing router or firewall settings that you do not understand; involve whoever manages the network if it belongs to a venue or workplace.
If the connection still fails, Streamlabs suggests steps such as generating a new API key in Remote Control settings, restarting, and trying each Wi-Fi band when the router offers more than one. Treat these as troubleshooting suggestions, not guaranteed fixes. Change one thing at a time, reconnect using a fresh QR code if needed, and return the network to its previous state if a change does not help.
There is also a distinct internet-access route in Streamlabs’ instructions. It involves first establishing the local connection, forwarding external router traffic to port 59650 on the Desktop computer, then choosing Remote > Manual Connection in the mobile app and entering the public IP address. This is not the same as scanning the QR code over local Wi-Fi. Streamlabs warns that it may require advanced network knowledge, and a dynamic ISP address can change. Only consider it if you genuinely need access beyond the local network and understand the security and network implications; ask a knowledgeable network administrator rather than opening router access casually.
If you mainly want to run a recorded video continuously rather than operate a desktop from a phone, that is a different production need. StreamNeo turns an uploaded video into a YouTube live stream, so the computer can be switched off instead of needing a person nearby to manage Desktop controls. It is YouTube-only, and it does not replace Streamlabs for a production that depends on changing scenes or operating a live desktop setup.
Test controls before going live
Test with the same account, computer, network and operator who will be present for the broadcast. Check each hotkey from the Hotkeys panel, each physical button from its intended console profile, and the phone app from the network where it will be used. This keeps three distinct control paths distinct and helps you locate a failure without guessing whether the problem is the shortcut, the console mapping or network visibility.
Make a short rehearsal checklist. Confirm that the intended scene is active, the microphone state is visible, and the actions you need are available. Trigger one action at a time and confirm the result in Desktop. Then practise the sequence you expect to use, including recovery from a wrong scene or accidental mute. If an action could interrupt the programme, rehearse it while the stream is not public or in a suitable test setup.
For a phone connection, verify that the QR pairing still works after reconnecting the phone or restarting Desktop, and that the devices remain on a network where local communication is allowed. Do not assume that an app paired at home will remain connected on venue Wi-Fi or a mobile hotspot. If you rely on the internet manual-connection route, confirm the current public IP and router arrangement with the person who manages them; a change in ISP address can affect access.
Keep a fallback available. If the phone loses its local connection, can you still reach the computer? If a console profile fails, can you use the keyboard binding or Desktop interface? If the computer is across the room, can someone on site perform the necessary action? A control method is useful only if it fits the likely failure points in your actual setup.
For YouTube specifically, check the broadcast in YouTube’s own Live Control Room as well as Streamlabs Desktop. A button press that appears to work locally does not by itself confirm that YouTube is receiving the expected feed. Our guide to YouTube Live Control Room showing no data covers that separate signal-checking problem. Keep control testing and delivery monitoring as two parts of the rehearsal.
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
Can I control Streamlabs Desktop with hotkeys from another room?
You can assign keyboard shortcuts in Desktop and use them from a keyboard connected to the computer. A physical console may make selected actions easier to trigger, subject to its compatibility and configuration. Neither setup alone means you can control the computer over the internet.
Does the Controller app’s QR code work away from my local network?
The documented QR setup uses the same local network for the phone and the Desktop computer. Streamlabs describes internet access separately through manual connection and router port forwarding, which involves additional network configuration and may require advanced knowledge. Do not treat the QR code as an internet connection method.
Do hotkeys work with every Stream Deck or Loupedeck?
Streamlabs names Stream Deck and Loupedeck as examples of creator consoles that can be used with hotkeys, but that does not establish support for every model or configuration. Check the current instructions for your chosen device and confirm how it triggers the shortcuts you assigned. Test the complete mapping before using it in a live programme.
Which controls should I set up first?
Start with the actions you need most and can test safely, such as microphone mute or a prepared scene change. Use combinations of at least two keys, as Streamlabs recommends, and keep consequential actions easy to distinguish. Verify every assignment in your current Hotkeys panel rather than relying on a default map.