Evolution Host Logo

Evolution Host
Invent the Future

Hytale Server Requirements

Official baseline requirements, recommended specs by player count, bandwidth expectations, dependencies, storage planning, setup steps, tuning tips, and FAQs - all in one place.

Official baseline requirements Server Dependencies Sizing by player count

Tip: If you expect public traffic, prioritize consistent CPU performance, enough RAM headroom, and NVMe storage.

Official Dedicated Server Requirements

Ensure your Hytale Hosting provider meets these specs at a bare minimum.

Baseline (minimum)

  • RAM: 4 GB+ available
  • CPU: modern x64 / arm64 recommended
  • Storage: SSD (NVMe preferred)

Best practice: set a clear memory limit (example: -Xmx8G) to avoid runaway RAM usage.

What matters most

  • CPU: entity counts + busy hubs hit CPU
  • RAM: view distance + scattered players raise memory
  • IO: autosaves + backups benefit from NVMe

Rule of thumb: most lag is CPU/RAM before bandwidth.

Recommended Specs by Player Count

Practical guidance for smoother gameplay and headroom.

Server size Players CPU RAM Storage Notes
Small 1–10 2 vCPU (high clock) 4–6 GB 30+ GB NVMe Friends, testing, vanilla-style play.
Medium 10–30 3–4 vCPU 8–12 GB 60+ GB NVMe Best baseline for public/community servers.
Large 30–80 6–8 vCPU 16–24 GB 120+ GB NVMe Events, multiple worlds, heavier mods.
Enterprise 80+ Dedicated cores 32 GB+ NVMe + scheduled backups Consider multi-server architecture + dedicated hardware.

CPU matters most

Clustering players and entity-heavy areas usually become the first bottleneck.

RAM scales with activity

Exploration, view radius, and mods typically increase memory usage.

NVMe helps saves

Autosaves and backups benefit from fast IO, especially at higher player counts.

Bandwidth Expectations

Bandwidth varies by player activity, view distance, and how often players travel between areas. Use these ranges as planning guidance, then measure peak usage.

Rule of thumb (planning ranges)

Players Typical outbound Peak bursts
1–10 5–20 Mbps 30+ Mbps
10–30 20–60 Mbps 100+ Mbps
30–80 60–150 Mbps 250+ Mbps
80+ 150+ Mbps 500+ Mbps

Outbound is usually the limiter. Expect bursts during events or when many players move/teleport at once.

What increases bandwidth

  • Higher view distance / streaming radius
  • Frequent movement between distant areas
  • Large hubs with many players in one space
  • Mods that increase sync/update frequency

For public servers, stable routing + DDoS protection matters as much as raw Mbps.

Dependencies

Common software components for stable, secure operation. Keep updates scheduled and test changes in staging.

Runtime

  • JavaRequired (set -Xmx)
  • Service managersystemd recommended

Leave OS headroom (don’t allocate 100% RAM to Java).

Networking & Access

  • FirewallAllow game port (default 5520) & Optionally allow query port (default 5533)
  • SSHKey-based login
  • SFTPOptional for files

Avoid exposing extra ports and rotate credentials regularly.

Operations

  • BackupsSnapshots + offsite
  • MonitoringCPU/RAM/IO alerts
  • Log rotationPrevent disk fill

Monitoring prevents surprise outages during peak hours.

Example: sane Java memory sizing

Adjust values to your plan - keep some RAM free for OS and caching.

# Example startup (adjust jar + paths)
java -Xms4G -Xmx8G -jar HytaleServer.jar --assets PathToAssets.zip

Storage Planning

Plan for more than your world folder: backups, logs, caches, and growth over time. Headroom prevents backup failures.

How much storage do I need?

Server type Suggested NVMe
Small 30–60 GB
Medium 60–120 GB
Large 120–250 GB
Enterprise 250 GB+

NVMe helps most during autosaves and backup creation/restores.

Backup headroom rule

  • Keep 2–3× current world size free for local backups
  • Use daily offsite snapshots for disaster recovery
  • Rotate logs so they don’t silently fill disk
  • Test restores monthly (the only reliable check)

Mods and multiple worlds increase storage faster than most people expect.

World growth factors

Scattered exploration and chunk generation are the biggest drivers of world size.

Retention strategy

Hourly (short), daily (medium), weekly (long) is a common and effective approach.

Restore speed

NVMe + snapshots can reduce downtime significantly on large servers.

Setup Quickstart

A clean checklist you can skim and follow.

  1. Prepare your runtime Install required runtime and verify it works.
  2. Upload server files Place server files + assets in a dedicated directory.
  3. First launch Start once to generate configs and verify permissions.
  4. Open ports Allow inbound traffic for your game port.
  5. Optimize Server Fine-tune and optimize your server resources.
  6. Go live Invite players and monitor CPU/RAM during peak.
View our extensive Hytale server setup guide

Performance Tuning

Simple changes that usually improve stability quickly.

Reduce RAM spikes

  • Lower view distance / view radius for public servers
  • Keep autosave cadence reasonable
  • Set a memory cap and leave OS headroom

Improve CPU performance

  • Limit heavy entity/AI density in hubs
  • Profile mods/plugins before production
  • Split worlds/features into separate servers if needed

Mods & Plugins

Mods increase features - and resource usage. Plan accordingly.

Best practices

  • Use a staging server for updates
  • Update on a schedule (not during peak)
  • Remove heavy mods you don’t need 24/7

Sizing with mods

  • Add +2–4GB RAM for heavier modpacks on medium servers
  • Expect CPU limits first when many players cluster
  • For large modded servers, consider dedicated cores

Backups & Safety

A reliable routine that prevents painful data loss.

Recommended routine

  • Backups every 30–60 minutes
  • Daily offsite snapshots
  • Retention: 7–14 days (longer for big communities)

Restore testing

  • Test restores at least monthly
  • Verify world + player data integrity
  • Document restore steps for staff

FAQ

Quick answers to common questions.

Ready to Host a Hytale Server?

Get fast CPU performance, plenty of RAM, NVMe storage, and DDoS protection - then scale as your community grows.