Short answer. Download the free TeamSpeak server (TeamSpeak 3 server 3.13.8 from teamspeak.com, or the TeamSpeak 6 server beta from TeamSpeak's GitHub), accept the licence, open UDP port 9987 and TCP port 30033, and start it. The first start prints a ServerAdmin privilege key: paste it into your TeamSpeak client to become admin. Without a licence file the server runs one virtual server with 32 slots, and TeamSpeak 3's licence text says this free model is only for non-commercial groups and consumers. PlayNHost does not rent TeamSpeak servers; if your group mainly needs voice chat, rent a Mumble server instead, which is open-source software with no slot licence to buy. Checked on 6 November 2026 against TeamSpeak 3 server 3.13.8 and TeamSpeak 6 server v6.0.0-beta13.1. The TeamSpeak 6 licence dates were re-checked on 19 November 2026 against v6.0.0-beta14, released 17 November 2026.
TeamSpeak 3 or TeamSpeak 6 server?
TeamSpeak 3 server is the long-standing release. The downloads page on teamspeak.com lists version 3.13.8 for Linux, Windows, macOS and FreeBSD.
TeamSpeak 6 server is a beta. TeamSpeak publishes it on GitHub (teamspeak/teamspeak6-server) as Linux and Windows downloads and as a Docker image. Its own README says it is not yet fully feature-complete.
The two do not mix: TeamSpeak's README says TeamSpeak 3 licences are not compatible with TeamSpeak 6 servers and that there is currently no migration path between the two versions.
What the free licence allows
TeamSpeak 3: with no licence file the server runs one virtual server with up to 32 slots. The licence text in the download calls this model "Unlicensed" and says it is "exclusively available to non-commercial groupings and consumers". TeamSpeak's quickstart guide says more than one virtual server or more than 32 slots needs a licence file.
TeamSpeak 6: the beta includes a 32-slot licence that TeamSpeak says is renewed every two months during the beta, and its README says a larger licence cannot be obtained yet. In our test of v6.0.0-beta14 (released 17 November 2026), the server printed a licence with a starting date of 1 November 2026 and an ending date of 1 February 2027, for 1 virtual server and 32 slots; the beta13.1 build we tested earlier printed 1 September to 1 December 2026. Your server log shows the dates for your copy.
Hosting for other people is a separate licence. The licence text shipped with TeamSpeak 3 server 3.13.8 describes an "Authorized TeamSpeak Hosting Provider" model with a one-off basic fee of 50 US dollars plus fees based on the number of slots used per calendar day. The terms shipped with the TeamSpeak 6 beta say sublicensing slots or virtual servers to third parties is not permitted. TeamSpeak's licensing page, checked on 19 November 2026, lists TeamSpeak 6 licences as coming soon and does not list TeamSpeak 3 licences, so ask TeamSpeak before you plan around either.
What you need
A Linux machine or VPS that stays on, with a public IP address. TeamSpeak 3 also has Windows, macOS and FreeBSD builds; TeamSpeak 6 also has a Windows build.
UDP port 9987 (voice) and TCP port 30033 (file transfer) open to the internet. ServerQuery uses TCP 10011 (raw, TeamSpeak 3 only), 10022 (SSH) and 10080 (HTTP); keep those closed to the internet unless you need them.
Little memory and disk. We measured both servers on our own hardware: see the numbers below.
The TeamSpeak client on every person's computer or phone.
Option 1: TeamSpeak 6 server with Docker
This is the route TeamSpeak's README recommends. With Docker installed:
Setting TSSERVER_LICENSE_ACCEPTED=accept means you accept TeamSpeak's licence, so read it first (the LICENSE file inside the server download on TeamSpeak's GitHub releases page). Then read the log, which holds your privilege key:
docker logs teamspeak-server
Look for these lines and copy the value after token=:
ServerAdmin privilege key created, please use the line below
token=...
The data lives in the teamspeak-data volume, so docker rm and a new docker run keep your channels and permissions. docker volume rm teamspeak-data deletes them for good.
Option 2: TeamSpeak 3 server on Linux
Install bzip2 first. The download is a .tar.bz2 file, and on a system without bzip2, tar stops with bzip2: Cannot exec: No such file or directory (it happened on our own Linux machine while writing this guide):
sudo apt install bzip2
Download and unpack the server:
curl -LO https://files.teamspeak-services.com/releases/server/3.13.8/teamspeak3-server_linux_amd64-3.13.8.tar.bz2
tar xjf teamspeak3-server_linux_amd64-3.13.8.tar.bz2
cd teamspeak3-server_linux_amd64
Read the LICENSE file. If you accept it, create the file the server checks for:
touch .ts3server_license_accepted
Start the server as a normal user, not root (the start script itself warns against running as root):
./ts3server_startscript.sh start
Copy the privilege key. It is written to the log of virtual server 1, the file in logs/ whose name ends in _1.log:
grep token= logs/*_1.log
Open the ports in your firewall. On Ubuntu with ufw:
sudo ufw allow 9987/udp
sudo ufw allow 30033/tcp
The first start also prints a ServerQuery login to the console (loginname= "serveradmin", password= "..."). Save it: TeamSpeak's quickstart guide says it is shown only once, and you use it to make a new privilege key later.
If the server stops at start with instance check error, TeamSpeak's quickstart guide says /dev/shm is not mounted as tmpfs. The fix as root is mount -t tmpfs tmpfs /dev/shm, plus the line tmpfs /dev/shm tmpfs defaults 0 0 in /etc/fstab so it survives a reboot.
Connect and become admin
Open the TeamSpeak client and connect to your server's public IP address. Add :port only if you changed the voice port from 9987.
Paste the privilege key into the client's privilege key dialog. The key works once and moves you into the Server Admin group of that virtual server.
We ran both servers in containers on one of our own servers, limited to 1 CPU core and 1 GB of memory, with TeamSpeak's own server files and no one connected. "Ready" is the time from starting the container until the server logged that it was listening for connections:
TeamSpeak 3 server 3.13.8: 22 MB on disk, ready in 1.55 to 1.67 seconds over three starts, about 26 MB of memory (resident) at rest after 5 minutes.
TeamSpeak 6 server v6.0.0-beta13.1: 54 MB on disk, ready in 3.01 to 3.27 seconds over three starts, about 51 MB of memory (resident) at rest after 5 minutes. Measured on beta13.1, not repeated on beta14.
Most of that start time is one step the server logs as Puzzle precompute time: about 1.1 seconds on TeamSpeak 3 and 2.4 to 2.8 seconds on TeamSpeak 6. We did not measure with people connected.
On our server the TeamSpeak 6 server also logged Socket buffers limited by the kernel and named the fix itself: set net.core.rmem_max and net.core.wmem_max accordingly.
Renting instead of self-hosting
PlayNHost does not rent TeamSpeak servers. TeamSpeak itself rents TeamSpeak 6 servers through TeamSpeak Communities, and its README points there if you do not want to host one.
Self-hosted TeamSpeak costs no licence fee on one virtual server with 32 slots (TeamSpeak 3 for non-commercial groups and consumers; TeamSpeak 6 under its beta licence), and it is yours to run: updates, backups of the database (ts3server.sqlitedb on TeamSpeak 3; tsserver.sqlitedb on TeamSpeak 6, which keeps -wal and -shm files next to it while it runs), the firewall and a machine that never switches off.
A rented TeamSpeak server comes from a host licensed by TeamSpeak, or from TeamSpeak itself through TeamSpeak Communities.
A rented Mumble server skips the licence question: the software is open source, and the price is only the server.
We use cookies to keep the site working, to understand how it is used, and to measure our marketing. You can accept all, accept essential cookies only, or choose per category.We use cookies to keep the site working, to understand how it is used, and to measure our marketing. They are on by default here. You can switch off anything you do not want.Read our privacy policy