Mumble

Last reviewed Aug 26, 2026 · 845 words

A Mumble server for 20 people idles at under 30 MB of RAM, pushes roughly 70 kbit/s per talking user, and gets voice from mouth to ear faster than Discord because it never leaves your network path for someone else's. It has been doing this since 2005 under a BSD-3-Clause licence. What it will not do is be Discord: text chat is an afterthought, there is no video, no screen share, no bots ecosystem, and the desktop client looks like 2010. Decide whether you want a voice server or a community platform and the choice makes itself.

One port, one config file, done in ten minutes

The server component is historically called Murmur and is packaged as mumble-server on Debian and Ubuntu. Install it, set the SuperUser password, and clients can connect:

sudo apt install mumble-server
sudo mumble-server -supw 'a-long-superuser-password'

Everything lives in /etc/mumble-server.ini (older packages call it murmur.ini). The lines worth changing on day one are serverpassword= to keep strangers out, welcometext= because it is the first thing users see, users= for the cap, and bandwidth= if you want to force lower per-user bitrate on a slow uplink. The server listens on TCP and UDP 64738; open both, because voice goes over UDP and falls back to TCP with a latency penalty if UDP is blocked.

For Docker the official image is mumblevoip/mumble-server, configured through environment variables such as MUMBLE_CONFIG_SERVER_PASSWORD and MUMBLE_SUPERUSER_PASSWORD, with the SQLite database on a volume. Either way the catalogue's 128 MB minimum is generous; the process is tiny.

Latency is the product

Mumble uses the Opus codec at low frame sizes, and its clients let you drop the audio frame size to 10 ms. On a LAN or a nearby VPS that gives a round trip you cannot perceive, which is why it survived in competitive gaming and among musicians who need to talk over a mix. Positional audio, where a teammate's voice comes from where they are on the map, works through game plugins and remains a feature nothing else self-hosted offers. If your use is a guild's raid night or a rally-driving stream where a half-second of lag ruins the call-out, this is the reason to run it.

The cost is that the quality is only as good as the path. A VPS in the same country as your players, wired connections, and UDP open on every router in between are the whole tuning guide. Place the server badly and Discord's global relay network will beat you.

Access control that does not need accounts

Mumble authenticates users with client certificates. On first connect a client generates a self-signed cert, and the server ties the username to that cert when the user registers. There is no email, no password database to leak, and no identity provider to integrate; a user who loses their cert loses their registered name and gets a new one. Channels carry ACLs with groups, so a "staff" group can have a locked channel while visitors sit in a lobby. The only account with a password is SuperUser, which is for administration, not talking.

This is a poor fit for an organisation that wants SSO from Authentik or a single directory for everything, and a good fit for a friend group that wants zero admin.

What it does not replace

The text side is a per-channel chat log that supports links and images and little else. There are no threads, no history search worth using, no voice messages, no reactions. For a community that lives in text and drops into voice occasionally, run Mumble next to a real chat server; Rocket.Chat or Mattermost for the text, Mumble for the room where the game happens. For a community that wants one app with both, Revolt is the Discord-shaped self-hosted option, though its voice is nowhere near Mumble's. Video calls are a different category again; the communication category has the conferencing tools.

Mobile clients exist (Mumla on Android, an official iOS app) and work, but the desktop client is where the fine audio controls live, and the dated interface is a real barrier for people who have only ever used Discord. Expect to walk each new user through the audio wizard once.

What I'd do

For a gaming group or a band, run mumble-server on the cheapest VPS in the region where most of you live, set a server password, open 64738 on TCP and UDP, and stop; you are done and it will run for years unattended with the SQLite database in your normal backup. Pair it with whatever text chat the group already uses rather than fighting Mumble's. For anything that needs video, screen share or a moderated public community, pick a different tool and keep Mumble for the voice channel, which is the one job it still does better than everything else.