MuteMe · Setup & support
Set up OBS Studio with MuteMe
Connect MuteMe to OBS Studio’s built-in WebSocket server, then choose which audio sources your mute button controls.
- OBS Studio
- 28 or later
- Platforms
- Windows, macOS and Linux
- Connection
- Local WebSocket
Enable the OBS connection
Open WebSocket settings
Open OBS Studio and select Tools → WebSocket Server Settings. OBS 28 and later includes the server; you do not need an extra WebSocket plugin for a current release.
Enable the server and authentication
Enable the WebSocket server and keep authentication enabled. Use the generated password or set a strong, unique password. Note the password without posting it in screenshots or support messages.
Check the port
The WebSocket 5 default port is 4455. Keep it unless you have deliberately chosen another port, then save the OBS settings.
Connect from MuteMe
Open MuteMe settings and choose App Sync Settings. If OBS Studio is missing, select Modify, enable it, and return to the integration list. Expand OBS Studio and set Sync Level to Level 3 for two-way mute status. Keep the MuteMe app running.
Enter the connection details
Under OBS Connection, set Host to
127.0.0.1orlocalhost, Port to the value shown in OBS, and Password to the OBS WebSocket password.Apply the settings
Select Apply after changing the values. OBS must be running with its WebSocket server enabled. Saving settings alone does not prove the connection or audio routing works; perform the check below.
Choose what the button mutes
In current MuteMe releases, the OBS panel has an Audio Source area with Mute/unmute target choices. Select Refresh if you have added or renamed sources in OBS.
- Automatic: MuteMe chooses the first microphone input it finds.
- Named sources: select the listed source or sources you intend to control.
- All OBS audio sources: controls every audio source listed in the panel, which can include more than your microphone. Choose this only if you want that behavior.
If your version does not show these choices, update MuteMe. Make sure the intended microphone is actually routed through OBS’s Audio Mixer; a successful WebSocket connection alone does not create an audio source.
Check the mixer and device
Use a private test
With OBS open and the intended source in its mixer, toggle your MuteMe device. Check the mute state of that source in OBS. If your installed version detects OBS only during recording or streaming, use a short local test recording rather than going live to test.
Check the return direction
Change the target source’s mute state in OBS and confirm MuteMe follows at Level 3. When controlling several sources, verify the group behaves as you intend before using it on a stream.
Keep the local connection private
Using 127.0.0.1 or localhost sends MuteMe’s connection to the same computer. This does not by itself restrict every address on which the OBS server might listen. Keep authentication enabled, avoid router port forwarding, and do not expose the server publicly for this setup.
MuteMe stores the OBS password locally without encryption. Use a dedicated password, not one reused for another account. If endpoint security or company policy blocks the local connection, ask your administrator to review that connection; do not disable your firewall or antivirus.
Troubleshoot the connection
MuteMe cannot connect
Check that OBS is open, the WebSocket server is enabled, the host points to this computer, and port and password match exactly. Re-enter the password if it changed in OBS, then apply the settings. Restart both apps if the server was just enabled or reconfigured.
Connected, but the wrong source changes
Check Audio Source in MuteMe, refresh the list, and confirm the selected name matches the intended OBS mixer source. Review the difference between Automatic and All OBS audio sources. Check Level 3 if changes made in OBS do not return to MuteMe.
WebSocket settings are missing
Check your OBS version. The server is bundled with OBS 28 and later. Get a current supported build from the official OBS download page.
Permissions or Linux packaging questions
OBS needs the operating-system permissions required by its own capture sources, such as microphone or screen capture on macOS. Those are separate from MuteMe’s WebSocket connection; this integration does not itself require MuteMe Accessibility permission. On Linux, use an installation method documented by OBS for your distribution. OBS lists Flatpak as an official option, so do not assume a Flatpak install is unsupported. If a managed or sandboxed environment blocks the connection, review its permissions with your administrator.
We're here to help
Still need a hand?
The best way to contact us is through the Support tab in the MuteMe app. Include your operating system, MuteMe app version, meeting app and what you have already tried.