Geyser Standalone vs Plugin Mode, Which to Choose

What Geyser Does

Geyser is a proxy that translates the Bedrock Edition protocol into Java Edition protocol, letting Bedrock players connect to Java servers. It does not modify the Java server itself. When deciding between geyser standalone vs plugin deployment, the core functionality is identical. The difference is where Geyser runs and how it connects to your backend.

If you have not set up crossplay yet, start with our full crossplay guide for a broader picture before choosing a deployment mode.

Plugin Mode

In plugin mode, Geyser runs inside your existing server software as a plugin or mod. Supported platforms include Spigot, Paper, Purpur, Velocity, BungeeCord, Fabric and NeoForge. You drop the Geyser jar into your plugins/ or mods/ folder, restart, and Geyser opens a UDP listener (default port 19132) alongside the server's existing TCP listener.

Advantages

• Single process to manage. No separate service to start, stop or monitor.
• Lower latency between Geyser and the Java server since they share the same JVM.
• Simpler configuration, Geyser auto-detects the Java server address as 127.0.0.1.
• Easier for panel-based hosts (Pterodactyl, AMP) where running a second process is awkward.

Disadvantages

• Geyser's protocol translation adds CPU load to the same process handling your Java players.
• If the Java server crashes, Bedrock players lose connection too, no graceful fallback.
• On a multi-server network, you would need Geyser installed on the proxy (Velocity/BungeeCord), not on individual backend servers. Installing it on a backend causes routing issues.

Host any Bedrock or crossplay server with zero config headaches. Astroworld Hosting supports Geyser, BDS, and every server type on every plan.

Standalone Mode

In standalone mode, Geyser runs as its own Java application in a separate process. It listens for Bedrock connections on UDP 19132 and forwards them to a Java server address you configure (e.g., 127.0.0.1:25565 or a remote IP). The Java server sees incoming connections as regular Java clients.

Advantages

• Complete isolation. Geyser crashing does not take down the Java server.
• Can sit on a separate machine or VPS, useful if your Java host does not allow extra UDP ports.
• Works with any Java server, including vanilla, modded servers and hosts you do not control.
• Easier to update independently without restarting the Java server.

Disadvantages

• Requires managing a second process (or a second systemd service, Docker container, etc.).
• Adds network hop latency if Geyser and the Java server are on different machines.
• Floodgate integration requires the Floodgate plugin on the Java server plus config alignment with the standalone Geyser instance.

When to Pick Plugin Mode

Choose plugin mode when you run a single Java server (not a network) and want the simplest setup. This covers most small to mid-size community servers. If you use a hosting panel that makes it easy to install plugins but hard to run extra processes, plugin mode is the practical choice. In the geyser standalone vs plugin debate, plugin wins on convenience for single-server setups.

When to Pick Standalone Mode

Choose standalone when any of these apply:

• You run a multi-server network and want one Geyser instance in front of your proxy.
• Your Java host does not allow UDP ports or extra plugins.
• You want to run Geyser on a separate, cheaper VPS to offload translation work.
• You want to update Geyser without restarting the main server.
• You connect to a Java server you do not own or admin (e.g., a friend's server).

Floodgate Considerations

Floodgate lets Bedrock players join without a Java account by prefixing their Xbox gamertag (e.g., .Steve). In plugin mode, Floodgate installs alongside Geyser and shares the same key file automatically. In standalone mode, you must copy the key.pem from the standalone Geyser's data folder to the Floodgate plugin on your Java server. Mismatched keys cause authentication failures. For skin-related issues with Floodgate, check our Floodgate troubleshooting guide.

See crossplay in action: Astroworld MC, IP play.astroworldmc.com, Java + Bedrock.

Performance Comparison

The translation work is the same in both modes. The difference is resource allocation. In plugin mode, Geyser shares heap memory and CPU threads with your Java server. In standalone mode, you can allocate separate RAM (512 MB to 1 GB is usually enough for Geyser alone) and pin it to different CPU cores if needed. For servers with more than 30 Bedrock players, standalone mode gives you finer control over resource distribution.

Quick Decision Table

Scenario	Recommended Mode
Single Paper/Spigot server, under 30 players	Plugin
Velocity or BungeeCord network	Plugin on the proxy
Cannot install plugins on Java host	Standalone (separate machine)
Want isolated updates and restarts	Standalone
Connecting to someone else's server	Standalone

Whichever mode you choose, the player experience is the same. Bedrock clients connect, Geyser translates, and they play alongside Java users. The geyser standalone vs plugin decision is purely about your infrastructure preferences.