Help Center

c Expand All C Collapse All


Absolutely! We have an open roadmap and a place to submit feature requests, here:

You can submit a new feature request there, or upvote existing requests to let us know you also want that feature.

Currently, MuteDeck supports Zoom and Webex when they are set to the English language. We have more on the way.

Check out our roadmap to see which apps we are going to support. You can also request support for a different app.


Yes, we have license plans available for bulk purchases. Please contact us to get the ball rolling, thanks!

The mute feature is free always; for the additional features to control your video, sharing, and a quick meeting exit, you need a license. When you first install MuteDeck, you get a 14-day trial of all features.

You can purchase a license from After the order is completed, you’ll instantly receive a license code. When asked, please create an account. If you have an account, you can find your license key in your profile.

The license code can be entered into the MuteDeck software via the settings:

Applying a license to MuteDeck

The MuteDeck software is licensed per computer and you can activate two computers with one license. For example, if you install MuteDeck on two computers (work and personal), you only need one license. If you install it on three computers, you need two licenses.

If you’d like to purchase multiple licenses for your team, please contact us, we have some team-friendly rates available.


The Loupedeck plugin for MuteDeck is an awesome way to connect your Loupedeck to MuteDeck and control your meetings with physical buttons.

The Loupedeck plugin syncs the meeting status to your Loupedeck and lets you quickly mute, or control other aspects of the meeting.

Here’s a walk-through of how to install and use the plugin with your Loupedeck

The Stream Deck plugin for MuteDeck is an awesome way to connect your Elgato Stream Deck to MuteDeck and control your meetings with physical buttons.

The Stream Deck plugin syncs the meeting status to your Stream Deck and lets you quickly mute, or control other aspects of the meeting.

Here’s a walk-through of how to install and use the plugin with your Stream Deck


During the continuous development of MuteDeck, we often review existing features and design for new features and options. By enabling the Send Anonymous Usage Stats option, you can help us understand how MuteDeck is used and lets us know which features matter most to you.

Disabled by default, MuteDeck will ask whether it can enable the collection of usage stats and send it to us when it first starts.

No data is collected or reported that can connect your identity to it. To be as transparent about what we collect, here’s what is collected and sent to


  1. Computer ID
    • Random generated string when your computer is installed. Here’s an example: 8B510C4A-BB24-5450-B1B0-BECC5F092DE6
  2. CPU Architecture
    • Whether MuteDeck is running on 32bit, 64bit, or another architecture.
  3. Kernel Type & Version
    • Shorthands for the type of system, like ‘winnt’ for Windows and ‘darwin’ for MacOS.
  4. Product Name & Version
    • Longer name for the type of system, like ‘Windows 11 Version 2009’ or ‘macOS Monterey (12.6).’
  5. MuteDeck Version
    • The version of MuteDeck that’s running.
  6. MuteDeck Licensed
    • Whether MuteDeck is licensed (but not the license itself.)


Events is a list of button presses that lets us know which buttons are being used the most. Per event, this is what is collected and sent to

  1. Event Date
  2. Event Type
    • This can be “mute”, “video”, “share”, “record”, or “leave.”
  3. Context
    • In which context the event type is run. This can be “system,” “zoom,” “webex,” or software that will be supported in the future.
  4. Via API
    • Tells us whether the event was triggered via MuteDeck’s API, which means it’s run via Stream Deck, Loupedeck, or another form of remote API. This can be “yes” or “no.”

The MuteDeck software checks your computer to see if Zoom or Webex is running. If it’s running, it scans the user interface to see what buttons are present. I.e., it looks for the Mute button and if it’s there, it means you’re unmuted. If the Unmute button is there, it means you’re on mute.

When MuteDeck detects an active call, it mirrors the buttons with the active status of that feature. When you press unmute on Zoom or Webex, it detects this and changes the button inside MuteDeck. When you press mute on MuteDeck, it sends a simulated click to Zoom or Webex and detects whether the mute was successful.

Microphone Control as a Fallback

MuteDeck currently supports Zoom or Webex detection for all buttons (mute, video, share, leave). If a Zoom or Webex call is not found, MuteDeck falls back on the microphone you’re using. This means you still have mute control with any conference call software, which is pretty awesome!

If you’re curious about how that looks, here’s an example from Microsoft Teams:


The MuteDeck software has an open API that you can use to get the status of each button (mute, video, etc.) and control the buttons as well. This RESTful API is the way to integrate with MuteDeck and built something cool that reacts to or controls your meeting status.

When the MuteDeck software is running, it runs a local web server where the API lives. You can find the API endpoints and built-in documentation, here: http://localhost:3491/

The list of API endpoints on that page tells you the URLs to approach and what HTTP method to use. To retrieve the status, use a GET. And to change the mute, video, or another status, use a POST method.
For example, reading out the status can have this output:

GET http://localhost:3491/v1/status
     "control": "system",
     "mute": "inactive",
     "record": "disabled",
     "share": "disabled",
     "status": 200,
     "video": "disabled" 

This output tells you that mute is controlled by the system (so no Zoom call) and that mute is inactive, i.e. you are audible.

Let’s look at an example where there is a Zoom call active:

GET http://localhost:3491/v1/status 
    "call": "active",
    "control": "zoom",
    "mute": "active",
    "record": "inactive",
    "share": "inactive",
    "status": 200,
    "video": "active"

Here we see that the control is with zoom, mute is active (people can’t hear you) and the video is active.

Please let us know when you build something with the API, as we’re dying to know what awesome creations are out there. ?

By default, MuteDeck only activates the API server on your local computer, mostly for security reasons. For example, no external person can tell MuteDeck to end your call when it’s listening to only your computer.

For some integrations, you need to be able to use external devices to read MuteDecks’ status. So, if you need to have the API server listening on the external network as well, you can do so by setting an hidden option. Here’s how.

Shut down MuteDeck and do the following:


Open the registry editor and browse to this path: HKEY_CURRENT_USER\Software\MuteDeck\MuteDeckIn the window with the settings (like keep_on_top, start_at_login) listed, right click and create a new String Value. Name it as api_listen_on_all_ips and modify its value to true.



Open a window and run these commands:

defaults write ~/Library/Preferences/com.mutedeck.MuteDeck.plist "api_listen_on_all_ips" 1
defaults read ~/Library/Preferences/com.mutedeck.MuteDeck.plist "api_listen_on_all_ips"

The last command reads the settings file and shows the value, which should be 1. To disable listening on all IPs, run the same commands only with a 0 instead of 1.

After the setting is set, start MuteDeck again and it will listen on the external network.

Note: this option is available from version 0.99 and above.

When MuteDeck does not recognize the call application, mostly because we don’t support it yet, it falls back on the microphone input you’re using. Mute visibility and control still works. ?

Here’s an example:

No call detected

When using the mute button in an app that we don’t yet support, you will still go on mute. Most apps can recognise that and will display a message. Here’s an example with Microsoft Teams, where the microphone is muted:

MS Teams muted message

MuteDeck is on a continuous loop to detect and find the status of Zoom. To balance the resources the software needs (CPU usage) and performance, we’ve put this loop on a 1-second delay. So, every second the call status gets updated, which can seem like a delay when you’re paying attention to the buttons. We’ve found that this design is the sweet spot and is the best balance.

This may change in the future, but we want to be absolutely sure that the software does not interfere with your computer’s resources and has a very small footprint.

Subscribe for Updates

© 2022 MuteDeck. All Rights Reserved