How to Create a TeamSpeak Server: Guide to TS3 and TS6

To host a TeamSpeak server, version 3 remains the stable choice: it is free to download, supports up to 32 slots for non-commercial use, and displays your privilege token upon first launch—the key that gives you administrator powers. Version 6 is already available for installation, but the server is still in beta.

Hosting the server yourself has two advantages over renting one: you don’t pay a monthly fee and you have full control over the configuration. The downside is that the host computer must remain turned on and reachable. Let’s look at installation on Windows and Linux, how to become an administrator, and how to let your friends join from the internet.

Version 3 or version 6? #

	TeamSpeak 3	TeamSpeak 6
Server Status	Stable, mature	Beta
Distribution	Package from the official website	Public repository and container image
Client	Dated but functional	Modern, free
Recommended for	A group that uses it every day	Testing, and those who want the latest features

If you just want a server that works, choose version 3 today. Version 6 is good for testing, keeping in mind that something might change or break between updates. The most recent clients connect to a TeamSpeak 3 server without any issues.

What you need #

A computer or a small server that stays on all the time. For about ten people, very little is required: 1 GB of RAM and any processor from the last few years.
A stable connection, preferably via Ethernet.
The correct ports open:

Port	Protocol	Purpose
9987	UDP	Voice: this is the only indispensable one
30033	TCP	File transfer between users
10011	TCP	ServerQuery, for remote management

Installing TeamSpeak 3 server #

Download the server package from the official TeamSpeak download page by selecting your operating system. Make sure you don’t download the client instead of the server: they are two different files.
Extract the archive into a dedicated folder.
Start the server:
- on Windows, by running ts3server.exe;
- on Linux, using ./ts3server_minimal_runscript.sh license_accepted=1 for testing, or by configuring it as a service (explained below).
Accept the license upon first launch. On Linux, you can also create an empty file named .ts3server_license_accepted in the server folder so you don’t have to repeat this step.

At first launch, immediately copy three things: the administrator username and password for remote management, and most importantly, the privilege token. You only need that string once to become an administrator, and if you lose it, recovering it is a hassle. On Linux, if it has already passed by, you can find it in the log file inside the logs folder.

TeamSpeak server console at first launch with the privilege token highlighted — The token appears only once: make sure to copy it before closing the window

On Linux, as a service #

Do not run the server as root. Create a dedicated user, move the server folder there, and start the service using systemd:

sudo adduser --disabled-login teamspeak

Then create the /etc/systemd/system/teamspeak.servicefile:

[Unit]
Description=TeamSpeak 3 Server
After=network.target

[Service]
User=teamspeak
WorkingDirectory=/home/teamspeak/teamspeak3-server_linux_amd64
ExecStart=/home/teamspeak/teamspeak3-server_linux_amd64/ts3server license_accepted=1
Restart=on-failure

[Install]
WantedBy=multi-user.target

And enable it with sudo systemctl enable --now teamspeak. From that moment on, the server will start automatically upon every reboot, and you can find the token using sudo journalctl -u teamspeak.

Using the privilege token #

The token turns a normal user into a Server Admin. Without it, the server works, but no one can create channels or manage permissions.

Open your TeamSpeak client and connect to the server: use localhost if you are on the same computer, or the IP address if you are on another.
When connecting to a new server for the first time, the client will ask you directly for the key. If it doesn’t, select Permissions → Use Privilege Key from the menu.
Paste the string copied during the first launch and confirm.

At this point, you have all the powers: you can create channels, assign groups, and generate other tokens to appoint moderators.

TeamSpeak client asking for the privilege key to obtain server administrator permissions — The privilege key is pasted only once, during the first connection

You can create subsequent tokens via Permissions → Privilege Keys, choosing the group they will assign. This is the correct way to grant permissions to someone without giving them your admin credentials.

Letting friends join from the internet #

On a local network, you don’t need anything else: other computers in the house connect using the server’s internal IP address.

From the internet, you have three options:

Port forwarding on your router, forwarding port 9987 UDP (and 30033 TCP if you want file transfers) to the computer hosting the server. You need a reachable public IP address, which not all home connections have: many FWA or mobile connections do not support port forwarding.
A private network between friends, for example using Tailscale: no ports to open, everyone simply installs the app and connects via the internal address.
A small rented server, which also solves the problem of having to keep your computer turned on.

On Windows, you should also create a rule in the Firewall to allow incoming connections to ts3server.exe, otherwise the port will appear closed even after opening it on the router. Usually, Windows will ask you this during the first launch: select “Yes” for private networks.

A router panel showing the port forwarding rule for UDP 9987 to the computer — Without forwarding UDP 9987, no one from the outside can join the server

The TeamSpeak 6 server #

The next-generation server is already available for installation: there is a package for Linux and Windows as well as a Docker image; configuration is handled via files, environment variables, or command-line parameters.

However, it is still officially in beta: some features are still under development and behavior may change. For a group that just wants to talk while gaming, option 3 remains the most hassle-free choice. Version 6 makes sense if you want to follow its development. The TeamSpeak 6 client, on the other hand, is already stable and free.

Alternatives to hosting it yourself #

Renting a server from a specialized provider costs only a few euros per month and removes all concerns regarding ports and keeping your computer running.

Mumble is the open-source alternative: lighter, featuring positional audio, and just as easy to install.

Discord is free and requires no server of your own, but the audio quality is lower and everything runs through the company’s servers.

FAQ #

How many users can I host for free? #

The free license for non-commercial use covers a virtual server with a maximum of 32 slots. This is more than enough for a group of friends. For commercial use or more slots, paid licenses are required.

I lost my privilege token: what should I do? #

If you have just installed the server, the fastest way is to start over: delete the database file (ts3server.sqlitedb) and restart, and a new one will be generated. On an already configured server, you can create a new token via ServerQuery using the administrator credentials you saved during the first launch.

Do I need a powerful computer? #

No, a voice server uses very little resources: the main load is audio traffic, which is minimal for about ten people. A stable connection and ensuring the machine stays on are much more important.

Can I host it on a Raspberry Pi? #

The official TeamSpeak 3 server only exists for x86 processors, so it won’t run directly on a Raspberry Pi. For a voice server on that type of board, Mumble is the natural choice, and it works great.

Can I host it on a Mac? #

Yes, the official website also provides a server package for macOS. It starts up just like on Linux, requiring you to accept the license upon first launch. However, for a server that needs to stay online 24/7, a Mac that goes into sleep mode is not ideal.

What is the difference between a client and a server? #

The client is the program you use to connect and talk; the server is what hosts the channels and users. A group only needs one server, while everyone installs the client on their own computer.

My friends can’t connect: what should I check? #

If you can connect via localhost or using the internal IP but no one from the outside can join, the problem is almost always the UDP 9987 port forwarding on your router or the Windows Firewall. Also, make sure you have given your friends your public IP address, which you can find by searching “what is my IP” from the server computer.