Simple Voice Chat and Geyser: can Bedrock players talk?

Simple Voice Chat with Geyser works for your Java players, but not for your Bedrock players. Geyser lets Bedrock players onto your Java server, but they can’t install the Simple Voice Chat mod, and its makers say a voice chat inside Bedrock is impossible due to technical limitations. Java players keep talking as usual. For Bedrock friends you need a community add-on that works through a browser or a separate app, or a voice call next to the game.

Below: what each side hears, how to run Geyser and Simple Voice Chat on one server without port clashes, and what to check when voice chat stays silent. As of 27 October 2026: Simple Voice Chat 2.6.26, and Geyser for Java 26.3 and Bedrock 26.30 to 26.52. Bedrock 26.60 is planned for today.

Can Bedrock players use Simple Voice Chat?

Not directly. Simple Voice Chat is a mod, and everyone who wants to talk needs it in their own game, on Fabric, NeoForge, Forge or Quilt. That’s also true when your server runs the Paper plugin. Bedrock can’t load Java mods. The Simple Voice Chat FAQ is clear: it works on Java Edition only, and a voice chat in Bedrock Edition is impossible due to technical limitations.

Geyser doesn’t change that. It translates between the two games, and according to GeyserMC it emulates a Java client, so your server thinks a Bedrock player joined from Java. To your server, that player looks like a Java friend without the voice chat mod: allowed in, but without voice.

What Java players hear and what Bedrock players miss

• Java players with the mod hear each other up to 48 blocks away by default (max_voice_distance), and up to 24 blocks when someone whispers. They can also talk in groups, which can have a password.
• Bedrock players hear none of that and can’t speak. The rest of the game works as usual: building, farms and chat.
• Keep force_voice_chat off. With this setting on true, the server kicks every player without the mod. That includes every Bedrock player. The default is false.

Set up Simple Voice Chat next to Geyser

Both run fine on one Paper server, as long as each has its own port. GeyserMC says no other program may use the Geyser port, over either protocol, and names voice chat mods as an example. The Simple Voice Chat makers say the same from their side.

1. Count your ports. In the game panel, go to Network, under the Actions heading. At the bottom it shows, for example, Using 1 of 2 allocations. A Java plan comes with one extra port. Geyser plus voice chat needs two, so open a ticket for the second one.
2. Create the ports with Create Allocation and type geyser and voicechat under Add notes, so you know which is which.
3. Set up Geyser in plugins/Geyser-Spigot/config.yml: under bedrock, set port to your Geyser port, leave clone-remote-port on false and set transport to nethernet. The full steps are in Install Geyser.
4. Set up Simple Voice Chat in plugins/voicechat/voicechat-server.properties: put your voice chat port after port= and leave bind_address empty. See Simple Voice Chat on your Minecraft server.
5. Restart your server. The console should show Started Geyser on with the Geyser port and Voice chat server started at with the voice chat port.

Which UDP port does voice chat need?

A port of its own. Simple Voice Chat sends all audio over UDP on the port in its server config. The default is 24454, but on a hosted server that number isn’t yours, so always use the port from Network. Your friends don’t enter it anywhere: their mod gets it from your server.

• Not -1. That makes voice chat share your Minecraft port. The makers strongly advise against it, because UDP on that port is also used for the server query, and it can crash your server.
• Not the Geyser port. Since NetherNet, Geyser uses its port over both TCP and UDP. Two programs on one port give the error Address already in use.
• Stay on transport: nethernet. The Geyser option both, for extra compatibility with older Bedrock versions, needs yet another UDP port (webrtc-port).
• After Bedrock 26.60, planned for 27 October 2026, update Geyser once more. Your voice chat port stays the same.

Alternatives for a mixed group

Want your Bedrock friends to talk along? There are two routes. The first is a community add-on that links Bedrock players to the voice chat through something outside Minecraft. These projects aren’t made by the Simple Voice Chat team, most are still in beta, and we haven’t tested them on our servers. This is what Modrinth lists on 27 October 2026:

Read the maker’s page before you install one. Bedrock Simple Voice can send audio through a relay run by its maker, or work in a self-hosted direct mode. The maker of SimpleVoice-Geyser warns that audio from the browser isn’t encrypted unless you put it behind a secure proxy. VoiceCraft.Java needs a reachable UDP port for each voice adapter, which on our servers means another extra port.

The second route is simpler: a voice call next to the game. A Discord call or your own Mumble server works for everyone, whatever edition they play, because it runs outside Minecraft. You lose the proximity effect, but nobody needs a mod. The differences are in Mumble vs TeamSpeak vs Discord.

Voice chat not working: check these first

• A plug icon for everyone. The voice chat port is wrong or still 24454. Check that the console line Voice chat server started at shows your extra port.
• Address already in use on startup. Geyser and voice chat share a port, or the query port in server.properties is the same as the voice chat port.
• Bedrock players get kicked straight away. force_voice_chat is on. Set it back to false and restart.
• One player can’t connect. Their internet provider, mobile data or a VPN may block UDP. Ask them to test on another network.
• Version mismatch. The first two numbers of the mod version in the game must match those on the server, such as 2.6.
• Test one player. As an operator, type /voicechat test followed by the player’s name in the game.