How to Run a Hytale Server: Complete Self-Hosting Tutorial (2026)

Running a Hytale server takes three things: Java 25, the Hytale server files, and an open UDP port 5520. Hytale ships official dedicated server software, so you can self-host a multiplayer world on Windows, Linux, or macOS from day one of Early Access. This tutorial walks through every step — from installing Java to authenticating, opening ports, configuring worlds, and adding mods — based on the official Hytale Server Manual published by Hypixel Studios for the Early Access launch on January 13, 2026.

What You Need to Run a Hytale Server

A Hytale server runs on any device with at least 4 GB of RAM and Java 25 installed, on both x64 and arm64 architectures. According to the official Hytale Server Manual, the server itself is platform-independent — it runs on Windows, Linux, and macOS — while the Hytale game client at Early Access supports Windows 10/11 (x64), Linux x64, and Apple Silicon macOS. You also need a valid Hytale game license, because every Hytale server must authenticate with the official Hytale service.

Java 25 UDP 5520 QUIC over UDP x64 & arm64 500 servers / license Windows · Linux · macOS

Hardware beyond the 4 GB minimum depends on player count and behaviour. The Hytale Server Manual identifies two drivers: CPU load grows with high player and entity counts (NPCs, mobs), while RAM grows with the size of the loaded world area. There is no single "correct" RAM number — Hypixel Studios recommends monitoring RAM and CPU during real use and setting an explicit -Xmx limit. Community hosts commonly suggest 4–8 GB for under 10 players and 16 GB or more for large public servers, but these are estimates, not an official requirement.

How to Install Java 25 for a Hytale Server

Java 25 is mandatory for a Hytale server — older Java versions will not start it. Download Java 25 from Adoptium (Eclipse Temurin), pick the 64-bit build for your operating system, and install it. Then confirm the installation by opening a terminal and running:

java --version

The expected output names Temurin 25, for example openjdk 25.0.1 2025-10-21 LTS followed by the Temurin runtime lines. If the command reports an older version or "command not found", reinstall Java 25 and make sure it is on your system PATH before launching the Hytale server.

How to Get the Hytale Server Files

There are two official ways to obtain Hytale server files. The first is fast for testing, the second is built for production servers that need easy updating.

Method 1: Copy from your Hytale launcher install

Your Hytale game install already contains the server files. Open the launcher install folder, copy the Server folder and the Assets.zip file (about 3.3 GB) into a dedicated folder such as C:\HytaleServer. The launcher install path differs by operating system:

• Windows: %appdata%\Hytale\install\release\package\game\latest
• Linux: $XDG_DATA_HOME/Hytale/install/release/package/game/latest
• macOS: ~/Library/Application Support/Hytale/install/release/package/game/latest

Method 2: Use the Hytale Downloader CLI

The Hytale Downloader CLI is the recommended method for production Hytale servers because it keeps files easy to update and sets up the folder layout needed for auto-updates. Download hytale-downloader.zip (Linux and Windows), extract it, and run ./hytale-downloader to fetch the latest release using OAuth2 authentication. Useful flags include -print-version to check the game version without downloading and -patchline pre-release to pull from the pre-release channel.

How to Launch and Authenticate a Hytale Server

Start a Hytale server with the ahead-of-time cache for faster boot times. From the server folder, run:

java -XX:AOTCache=HytaleServer.aot -jar HytaleServer.jar --assets Assets.zip

The Hytale server ships with a pre-trained AOT cache (HytaleServer.aot) that speeds up startup by skipping JIT warmup. To control memory, add -Xms and -Xmx flags — for example -Xms2G -Xmx4G. After the first launch, the Hytale server pauses and waits for authentication.

Authenticate the Hytale server by typing /auth login device in the server console. The console prints a link (https://accounts.hytale.com/device) and a code such as ABCD-1234. Open the link in a browser, sign in with your Hytale account, and enter the code. The code expires in 900 seconds (15 minutes). On success the console shows "Authentication successful!". Authentication lets the Hytale server talk to official service APIs and counters abuse — there is a limit of 500 servers per Hytale game license.

How to Configure Ports and Firewall for a Hytale Server

A Hytale server uses the QUIC protocol over UDP, on default port 5520 — so you must forward UDP, not TCP. This is the single most common cause of connection failures: forwarding only TCP leaves players unable to join. To host behind a router, forward UDP port 5520 to your server machine's local IP, then allow the port through the operating system firewall.

QUIC handles NAT traversal well in most cases. If players still cannot connect, confirm the forward is UDP, check that the bind address is 0.0.0.0 rather than 127.0.0.1, and note that symmetric NAT setups may require a VPS or dedicated server.

How to Connect to Your Hytale Server

Players join a Hytale server through Multiplayer → Direct Connect in the Hytale client. The address format is the server IP followed by the port: use localhost:5520 on the same machine, the local IP such as 192.168.1.100:5520 on a home network, or your public IP or domain with UDP 5520 forwarded for internet play. The Hytale server runs independently of the client, so the world stays online after you close the game. Shut it down cleanly with the /stop command.

How to Configure a Hytale Server World

A Hytale server uses two layers of configuration. The root folder holds config.json (server-wide settings, including the auto-update block), plus permissions.json, whitelist.json, and bans.json. Each world has its own config.json inside universe/worlds/. Per-world settings include the world seed, world generation type, and gameplay toggles such as PvP and fall damage.

{
  "Seed": 1767292261384,
  "WorldGen": { "Type": "Hytale", "Name": "Default" },
  "IsPvpEnabled": false,
  "IsFallDamageEnabled": true,
  "IsSpawningNPC": true,
  "GameplayConfig": "Default"
}

Edit Hytale server configuration files only while the server is stopped. The Hytale Server Manual warns that config files are read on startup and rewritten when in-game actions occur, so manual changes made while the server is running are likely to be overwritten.

Hytale Server Commands and Permissions

The most reliable way to discover Hytale server commands is the /help command, which lists every command supported by your specific build; add --help to any command for its syntax. The official Hytale Server API confirms commands exist for bans, the whitelist (add, remove, list, enable, disable, clear, status), and permissions, alongside core commands like /auth login device, /stop, and /update. In the server console you type commands without the leading slash.

Because exact command syntax still shifts between Early Access builds, the safest way to grant admin access on a Hytale server is to edit permissions.json directly while the server is stopped. The file has two sections: groups (each defining a set of permissions) and users (mapping a player's UUID to one or more groups). A group with ["*"] has full admin rights, while an empty list is a basic player. Operators always bypass the whitelist.

How to Install Mods on a Hytale Server

Hytale uses a server-first modding model: all mods live on the Hytale server and are delivered to players automatically when they connect. Players never download client mods or juggle mod loaders — this is a defining difference from games like Minecraft. To add mods, drop .zip or .jar files (for example from CurseForge) into the server's mods/ folder; the server loads them on startup and serves them to everyone who joins.

Hytale modding spans four content types. Server Plugins are compiled Java .jar files that use the Hytale Server API to add mechanics, economies, commands, and minigames. Data Assets are JSON files that define blocks, items, NPCs, world generation, and loot tables without code. Art Assets are sounds, models, and textures, with Blockbench integration for models. Save Files are worlds and prefabs you can share. The Hytale client is a closed-source renderer that runs no game logic, so client-side-only mods are not supported by design.

Hytale Server Performance and View Distance

View distance is the main driver of RAM usage on a Hytale server. The Hytale default is 384 blocks — that equals 12 Hytale chunks (a Hytale chunk is 32 blocks) and is roughly 24 Minecraft chunks (a Minecraft chunk is 16 blocks), far larger than Minecraft's default 10-chunk view. Because of this, Hypixel Studios recommends capping maximum view distance around 12 chunks (384 blocks) and tuning it down for higher player counts. Start conservative and raise the value only if your hardware stays stable.

Hypixel Studios' hosting partners Nitrado and Apex Hosting maintain plugins for common Hytale server needs:

Hytale Server Backups and Auto-Updates

A Hytale server has a built-in backup and auto-update system. Enable periodic backups with --backup --backup-dir backups --backup-frequency 30 (the default wrapper scripts already include these). Always test restoring a backup before you actually need it. For auto-updates, the Hytale server checks for new versions, downloads them to updater/staging/, and shuts down with exit code 8; the included wrapper script (start.sh or start.bat) detects exit code 8, swaps in the new files while preserving your config, saves, and mods, then restarts.

Control updates with the /update commands: /update check, /update download, /update apply --confirm, /update status, and /update cancel. Auto-apply behaviour is set in the Update block of the root config.json via AutoApplyMode (Disabled, WhenEmpty, or Scheduled). You can disable updates entirely with the HYTALE_DISABLE_UPDATES environment variable.

Hytale Server Troubleshooting

Most Hytale server problems come from networking, memory, or version mismatches. The fixes below cover the issues operators hit most often during Early Access.

• Server window closes instantly: HytaleServer.jar or Assets.zip is missing from the folder — verify both are present and run with --help.
• Players cannot connect: only TCP was forwarded instead of UDP 5520, the bind address is 127.0.0.1 instead of 0.0.0.0, or the firewall is blocking — also check for symmetric NAT.
• Crashes from memory pressure: raise -Xmx. Rising CPU usage is a symptom of garbage-collection pressure.
• Cannot connect after a game update: client and server protocol versions must match — update the Hytale server.
• Config edits are not saved: edit configuration files while the server is stopped; changes on a running server get overwritten.
• Authentication expired: re-run /auth login device — the code is valid for 900 seconds.

Running a Hytale Server Network: Multiserver Architecture

Hytale supports multiserver networks natively, so no external reverse proxy such as BungeeCord is required. A Hytale server can transfer a connected player to another server with a referral packet (PlayerRef.referToServer(host, port, data)), redirect a player during the connection handshake, or send disconnected players to a pre-configured fallback server. Because referral payloads pass through the client and can be tampered with, Hypixel Studios advises signing them cryptographically (for example with HMAC). Custom proxies can be built on Netty QUIC, since Hytale uses QUIC exclusively for client-server communication.

What's Coming to Hytale Servers

Several Hytale server features are confirmed as planned but not yet available, as of the Early Access launch in 2026. Hypixel Studios has announced an in-client server and minigame discovery catalogue with verified player counts, a party system for groups moving between servers together, an integrated payment gateway for server operators, first-party API endpoints (UUID-to-name lookups, game version, player profiles, server telemetry), and protocol version tolerance of ±2. SRV record support is under evaluation but not yet available. Treat these as roadmap items, not current features.

How to Run a Hytale Server — Frequently Asked Questions

Can you run a Hytale server for free?

Yes, you can run a Hytale server for free by self-hosting on your own computer — you only need Java 25, the server files, and a forwarded UDP port 5520. You do need a valid Hytale game license to authenticate the server. Renting a managed Hytale server from a hosting provider costs money but adds 24/7 uptime and one-click setup.

How much RAM does a Hytale server need?

A Hytale server needs at least 4 GB of RAM according to the official minimum. Actual usage is driven mainly by view distance and the loaded world area, so larger or busier servers need more. Hypixel Studios recommends monitoring RAM in real use and setting an explicit -Xmx limit rather than relying on a fixed number.

What port does a Hytale server use?

A Hytale server uses UDP port 5520 by default, over the QUIC protocol. You must forward UDP, not TCP. The port can be changed with the --bind argument, for example --bind 3500.

Do players need to install mods to join a modded Hytale server?

No. Hytale uses server-first modding, so all mods live on the Hytale server and are delivered to players automatically on connect. Players do not download client mods or install mod loaders to join a modded Hytale server.

Can a Hytale server run on Linux?

Yes. The Hytale server is platform-independent and runs on Windows, Linux, and macOS, on both x64 and arm64 architectures, as long as Java 25 is installed. The Hytale Server Manual provides Linux firewall commands and a Linux launcher script.

How many Hytale servers can one license authenticate?

One Hytale game license can authenticate up to 500 servers. Hypixel Studios set this limit to prevent early abuse; operators who need more capacity can contact Hytale support.