STREAMING GUIDE / STREAM TOOLS

Stream Deck OBS audio controls: make mute mean what you expect

Build a small, testable control page before adding complex macros. Confirm what reaches viewers instead of trusting a button label alone.

START HERE

Install the official OBS Studio plugin in Stream Deck, assign its audio action to the correct OBS source, and test the change in a recording. A source mute affects that OBS route; it does not necessarily mute the hardware microphone, Discord, or a second capture of the same device.

1. Define what each button is supposed to control

Write three short labels before configuring anything: Mic to stream, Game to stream, and Alerts to stream. Those describe destinations. A vague label such as “Mic off” can be misleading if Discord or another recording application still receives the microphone.

This guide concerns Elgato's official OBS Studio integration. It is different from a generic keyboard-shortcut action, a third-party WebSocket plugin, or a Wave Link control. You do not need to expose OBS to the internet to make a local audio mute button work.

2. Connect the official integration

Install or update Stream Deck from Elgato and add the official OBS Studio plugin from its marketplace. Elgato explains that integration has two components: the action plugin in Stream Deck and the companion plugin loaded by OBS. Installing only an action icon does not prove the OBS-side component loaded.

For OBS 30.1 or newer, Elgato's current troubleshooting guidance calls for Stream Deck 6.5.2 or newer. Check current supported releases before updating, close OBS during installation, and reopen it afterward. Portable OBS installations need Elgato's separate portable setup instructions.

If Stream Deck reports Waiting for OBS, first repair that connection using Elgato's official checklist. Changing your OBS audio devices cannot repair a missing control plugin.

3. Map one microphone action and prove its target

  1. Open the intended OBS scene collection and give the microphone source a recognizable name.
  2. Add the official OBS audio mixer action to one Stream Deck key. Select the intended source and any collection options offered by your plugin version.
  3. Speak while watching that specific OBS source. Press the key and confirm its output mute state changes; press again and confirm recovery.
  4. Make a local recording containing “before mute,” a muted interval, and “after mute.” Listen back.

If the microphone remains audible during the mute interval, search for another capture of the same device, a monitored copy in desktop audio, or a second application supplying a mixed feed. The button may be working correctly on its target while a different route stays open.

4. Keep monitoring separate from the audience mix

OBS 32.1+ (and 32.2+ without the legacy Monitor Only dropdown) uses independent output-mute and monitor controls. Hearing your microphone locally after muting its audience output does not necessarily mean the mute failed. Conversely, silence in your headphones does not prove the outgoing microphone is muted.

Use the saved recording to establish each control's effect. If you need to mute Discord as well, add a separately named action for Discord or use its own mute control; do not present an OBS-only key as a global privacy switch.

With a Stream Deck model that has dials and a compatible action, you can assign OBS source-level adjustment. Keep the range conservative and compare a spoken test before and after. A volume change is not a substitute for a verified mute, and increasing a fader cannot recover speech already clipped earlier in the audio path.

5. Add controls without creating accidental state changes

Add one new button at a time, keeping scene switching separate from audio until both are reliable. Where an action supports explicit on/off states, use those for predictable multi-action sequences. A toggle can reverse an already-correct state if you press it twice or begin from a different state.

Put stream-stop and recording-stop actions away from frequently used mute keys. Elgato documents a hold requirement for supported stream and record actions; consider it when an accidental press would interrupt a session. Do not experiment with a start-stream action while configuring an audio button.

After renaming sources, changing scene collections, or importing a profile, revisit the action's target. A familiar-looking key may still refer to an old source or collection.

Run a short control rehearsal

Record this sequence: microphone on, microphone muted, game muted, scene change, microphone restored, and one alert. Check that each change affects the intended source and no other one. Also test the separate communication app if it must have a coordinated mute.

Restart both applications and repeat the microphone check. Keep this small working profile as your fallback before creating more complex controls. If a state icon and recording disagree, trust the actual audio result and investigate the target or duplicate path.

Sources & version notes

Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.