Setup

Overview

Bedrock clients will join through Geyser, and it will handle all the packet translations. There are six different versions of Geyser:

Geyser for Spigot (works on derivatives such as Paper),
Geyser for BungeeCord (also works on Waterfall),
Geyser for Velocity,
Geyser for Sponge,
Geyser for Fabric (for setups that support vanilla Java clients; requires Fabric API),
Geyser Standalone (Standalone Setup instructions are here).

The first five versions run as plugins/mods and can be installed directly onto the server. The standalone version can be used in a similar way, except you run it separately.

If you are running a server, it is highly recommended you use one of the plugin versions, and if you want to join a server that does not have Geyser installed, you can run the standalone version. If you use Pterodactyl Panel we have an egg for the standalone version, please see here for more information.

Prerequisites

The server you are connecting to has to support the latest version of Minecraft Java Edition (at this time this is Minecraft 1.19.4) The server itself does not have to be the latest version but does have to allow connections. If you’re running the server on an older version, you can use the plugin ViaVersion, but do note that only 1.13.2 and any version above is officially supported. For older versions, use Geyser Standalone, or Geyser on a proxy like Velocity or BungeeCord.
The device running Geyser must support Java 16 or later. If you need help installing or updating, please see PaperMC’s Java update page. If you’re running a version of Paper that does not support Java 16 or later, you can add the flag -DPaper.IgnoreJavaVersion=true to your startup Java arguments to allow Paper to run on Java 16. You can run Geyser standalone on another device if a server software cannot be updated to use Java 16.
If you are connecting to an online mode Java server, a paid Java account is required. If you are running the server, you can bypass this requirement for your server with Floodgate.
Your Bedrock client has to be a supported version - at this time that is Bedrock version(s) 1.19.40 - 1.19.80.
If you are running the server, you need to have a UDP port opened. See below for more instructions.
In order for Bedrock players to chat (1.19.3+) or join (1.19.1/1.19.2), you need to disable chat signing. More information about that can be read on the chat signing page.

Plugin Setup

Read the Prerequisites above, especially if you are setting up Geyser for an older Minecraft Java Edition version!
To make sure you are using the easiest way to set up Geyser, please check whether your hosting provider features built-in Geyser. If you are not using a hosting provider, or your hosting provider is not featured on said list, continue with the steps below.
If 2. does not apply: download Geyser here for the platform your server runs on. See the FAQ if you’re confused about which build to download.
Put the Geyser jar file in your plugins folder and start up the server.
Port-forwarding:
- If you are using a hosting provider, you will likely need to change your Bedrock port in config.yml. Information on your hosting provider might be available on the Supported Hosting Providers page. If there is no information on your hosting provider and you are unable to assign/open ports yourself, try enabling clone-remote-port in Geyser’s config.ymlfile and connecting with the same IP/port as you would with Java Edition.
- If not using a hosting provider, you will need to use port forwarding to allow people outside your LAN to connect. You want to port forward 19132 UDP, instructions to do that for most routers can be found here. If you are trying to join from the same LAN, the server should show up in the friends tab.
- To check whether it is working correctly, you can use the geyser connectiontest [yourIP]:[yourPort] command in your server console to check if the server is reachable from the outside.
- Restart your server if you edited your config! Simply reloading will not work.
Besides the port entry in the Bedrock Section of Geyser’s config.yml, you rarely need to change anything. A few examples:
- address: 0.0.0.0 The IP address that will listen for connections. There is no reason to change this unless you want to limit what IPs can connect to your server or if your hosting provider instructs you to do so.
- port: 19132 The port Bedrock players will use to connect. If the option clone-remote-port is set to true, this port is ignored, and you’ll have to use the same port on bedrock as you would on Java to connect.
The remote section in the config.yml determines, which Java server the Bedrock players join.
- address: auto This means, that Geyser configures the server’s IP, port and auth-type of the java server by itself, leave this at auto.
- port: 25565 This should be the port of the Java server. By default, it is set to 25565 - your hosting provider may have assigned a different port to your Java server, set that here.
If you wish to remove the Java account requirement, set up the Floodgate plugin. This will allow Bedrock players to play on your server, without you having to use offline mode.
For further Geyser config changes, like allowing Bedrock players to build on the nether roof, refer to the config help article.

If you’re still having problems with Geyser not working or giving you an “Unable to connect to world” error, see the Common Issues page.
For more information, take a look at the Understanding the Config page, and the FAQ page.
And if you still have questions, feel free to join the Discord if you haven’t already.

BungeeCord/Velocity Setup

If you are using a BungeeCord, Waterfall, or Velocity proxy, then you only need to install Geyser (and Floodgate, if you desire) on the proxy.

You can install Floodgate (but not Geyser) on the back-end servers to improve skin functionality and to let other plugins access the Floodgate API. If you do this, then you must make sure that the same key.pem file is used between all instances of Floodgate; otherwise, Bedrock clients will not be able to join. Full instructions can be found on the Floodgate Wiki.

The Bedrock clients, like Java clients, should connect to the proxy server, and should never directly connect to a back-end server. You don’t need to (and shouldn’t) port-forward anything for the back-end servers!

Setup:

Make sure Velocity/BungeeCord is up-to-date. The proxy can be newer than the servers behind it (also called backend servers). If you’re running the backend servers on an older version then the current 1.19.4, you can use the plugin ViaVersion. It is recommended to have the plugin on all backend servers where necessary, instead to having it on the proxy.
Download Geyser here for the platform your server runs on. See the FAQ if you’re confused about which build to download.
Put the Geyser jar file in your plugins folder and start up the server.
Port-forwarding:
- If you are using a hosting provider, you will likely need to change your Bedrock port in the config.yml file. Information on your hosting provider might be available on the Supported Hosting Providers page. If your hosting provider is not listed there, and you are unable to port forward the default 19132 port on UDP, try setting clone-remote-port to true and connecting with the Java IP and port. Any port will work, as long as the UDP protocol is not blocked or already in use by the query feature (see server.properties) or another mod.
- If you are not using a hosting provider, you will need to use port forwarding to allow people out of your LAN to connect. You want to port forward 19132 UDP, instructions to do that for most routers can be found here. Note: Any port will work, as long as UDP traffic is not blocked. Java uses the TCP protocol, so you will need to open both UDP and TCP if you wish to use the same port.
- To check whether it is working correctly, you can use the geyser connectiontest [yourIP]:[yourPort] command in your server console to check if the server is reachable from the outside.
- Restart your server if you edited your config! Simply reloading will not work.
Besides the port entry in the Bedrock Section of Geyser’s config.yml, you rarely need to change anything. A few examples:
- address: 0.0.0.0 The IP address that will listen for connections. There is no reason to change this unless you want to limit what IPs can connect to your server or if your hosting provider instructs you to do so.
- port: 19132 The port bedrock players will use to connect. If the option clone-remote-port is set to true, this port is ignored, and you’ll have to use the same port on Bedrock as you would on Java to connect.
The remote section in the config.yml determines which Java proxy the Bedrock players join. The proxy then configures which server the players are sent to.
- address: auto Leaving this at auto is recommended, because it means that Geyser configures the proxy’s IP, port and auth-type itself.
- port: 25565 This should be the port of the Java server. By default, it is set to 25565 - your hosting provider may have assigned a different port to your proxy, set that here.
For further Geyser config changes, like allowing Bedrock players to build on the nether roof, refer to the config help article.

Standalone Setup

Please read Standalone Setup to set up Geyser Standalone.

Port Forwarding

Unlike Minecraft Java Edition, Bedrock Edition runs on port 19132 on the UDP protocol. When port forwarding, make sure to allocate to 19132 UDP or another UDP port. For many server hosting providers, you will simply need to change your Bedrock listening port (see here for a list of supported providers).