Players and world state
The catalog does not assign a fixed player capacity. Active players, simulation range, entities, automation, maps, and save growth can all change CPU and memory demand.
Hardware report
Allow at least 1 CPU core and 512 MiB of available memory. Larger worlds and mods need extra headroom.
Check my computer →
NewGRF and scenario files are manually uploaded. Provider lookup, compatibility resolution, and automatic updates are unavailable.
Explore OpenTTD →Plan for your setup
A dedicated-server workload changes over time. Keep headroom for growth and test with the world, players, and content you actually plan to use.
The catalog does not assign a fixed player capacity. Active players, simulation range, entities, automation, maps, and save growth can all change CPU and memory demand.
Storage needs grow with your world. Leave room for the game, saves, logs, updates, and backups, and check the complete game guide for recommendations.
Players connect over TCP and UDP. The upload speed and latency you need depend on the game and number of players. Connection stability, route quality, and simultaneous household traffic matter.
Core count alone does not describe single-core speed, CPU generation, thermals, or contention from other programs. Test performance with your intended world and players.
Content and operations
Review the available content, backup, and server tools before choosing your setup.
NewGRF and scenario files are manually uploaded. Provider lookup, compatibility resolution, and automatic updates are unavailable.
Check the game guide for the files included in backups and allow room for several restore points.
Start, stop, and monitor your server from the browser. Check the game guide for game-specific tools and any setup they require.