TeamSpeak 6 Server Requirements
Plan a reliable self-hosted TS6 server with sensible CPU, memory, storage, network and operating-system choices.
Practical starting point
Actual resource use depends on active users, file transfers, plugins, screen sharing and other workloads on the same machine. For a small community, start modestly and monitor real usage instead of allocating resources only from a theoretical maximum.
| Resource | Practical starting point | Recommendation |
|---|---|---|
| CPU | 1 modern vCPU | Use a host with strong single-core performance and leave headroom for traffic spikes. |
| Memory | 1 GB RAM | Allocate more when the VPS also runs a panel, database, bots or several servers. |
| Storage | 5–10 GB free | Use persistent storage and keep separate backups of server data. |
| Network | Stable low-latency connection | Choose a region close to most members and use DDoS-protected infrastructure. |
| Operating system | Current 64-bit Linux or supported Windows | Docker on Linux is a convenient and maintainable option. |
Ports and firewall
Voice traffic uses UDP, while file transfer and optional query services use TCP. Only expose the services you actually need. See the current examples in our TeamSpeak 6 ports guide and confirm release-specific details against the official server documentation.
Docker requirements
For Docker, install a maintained Docker Engine release, keep server data in a persistent volume and publish the correct UDP/TCP ports. Do not store important server data only inside the writable container layer.
When to increase resources
Upgrade when CPU remains saturated, memory pressure causes swapping, storage is running low, or multiple services compete for the same resources. Monitor the VPS during real peak usage before deciding.