TeamSpeak Server Hosting

Why do people still choose a TeamSpeak server?

TeamSpeak remains the voice platform of choice for esports teams, clans, simulation communities and privacy-minded groups thanks to low-latency voice, a detailed permission system and a server that is entirely under your control. Unlike centralised services such as Discord, you host the TeamSpeak server yourself: voice and chat data pass through your server, not a third party’s infrastructure.

What makes TeamSpeak stand out:

• Low latency: in competitive games even a tenth of a second matters. TeamSpeak running on a server close to players delivers callouts without delay.
• Detailed permissions: server groups and channel groups define exactly who can enter which channel, who can talk and who can upload files.
• Whisper lists: team leaders can speak to several channels at once, keeping communication organised in large organisations.
• Independence: whether the server stays up, and its rules, don’t depend on another platform’s policies.

If your community also uses Discord, you can run both: chat and announcements on Discord, in-match voice on TeamSpeak. To run bots on the Discord side, see our Discord bot hosting page.

How does TeamSpeak licensing work, and how many users can join for free?

Run without a licence file, a TeamSpeak 3 server allows one virtual server with up to 32 concurrent users for personal, non-commercial use; more slots or several virtual servers require a licence from TeamSpeak.

What to know about licensing:

• Unlicensed use: 32 slots is often enough for a group of friends, a small clan or a team, at no extra cost.
• Paid licences: for larger communities, TeamSpeak offers different licence options by slot count and term. Licence types and conditions change over time, so check the current options on TeamSpeak’s own website.
• Commercial resale: renting TeamSpeak slots to third parties requires a special licence model reserved for hosting providers authorised by TeamSpeak. That’s why the route we recommend here is running the server for your own use, with your own licence, on your own VDS.

The licence file (licensekey.dat) goes into the server folder and takes effect when the server restarts. A licence may be tied to a specific server, so check the licence terms before migrating.

Should you install TeamSpeak 3 or TeamSpeak 6?

Today the most common and mature option is the TeamSpeak 3 server; TeamSpeak 6 is the next-generation server software that comes with the redesigned client, and community tool support is still developing. Consider which client your users run and which management tools you need.

If you manage your server with ServerQuery-based bots (welcome messages, AFK moving, channel creation), TeamSpeak 3 holds fewer surprises for now. If you’re building a new community and want the new client’s features, trying TeamSpeak 6 on a test installation makes sense.

How many resources does a TeamSpeak server need?

A TeamSpeak server is very light: a 32-user server runs on a few hundred megabytes of memory and a small fraction of one CPU core. So the deciding resource is less the CPU or memory than the quality of the network connection and the disk space set aside for file sharing.

Points to consider when planning:

• Bandwidth: each speaking user’s voice stream is relayed to the others in the same channel. Traffic grows with users per channel and the codec quality chosen. For uninterrupted voice, clean upstream bandwidth and low packet loss matter more than memory.
• File transfer: if you allow file sharing in channels, uploaded files pile up on disk; per-channel quotas keep that growth in check.
• Database: the default SQLite is enough for small and medium servers; MariaDB can be preferred for very large installations.

TeamSpeak’s light footprint makes it sensible to run it on the same VDS as a game server. For example, running TeamSpeak as a separate user alongside a CS2 server or Minecraft server gives your team a voice server without renting another machine.

Don’t forget log files in disk planning: the TeamSpeak server writes connection and admin events to logs, and on a long-running server these accumulate. A scheduled task that archives or deletes old logs at intervals keeps the disk from filling up unexpectedly.

Ready-made package or VDS for TeamSpeak?

The route we recommend for TeamSpeak is to rent a VDS and install the server with your own licence, or request installation through a support ticket; the package table on this page lists the current server options suitable for TeamSpeak.

Advantages of running TeamSpeak on a VDS:

• Full control: you hold serveradmin access, ServerQuery and all configuration files, so you can set up bots, automation and custom permission structures.
• Licence flexibility: start with 32 unlicensed slots and increase capacity with a licence in your own name as the community grows.
• Co-hosting: your game server, website and Discord bot can run on the same machine alongside TeamSpeak.
• Data control: chat history, uploaded files and user identities are kept only on your server.

In return, operating system updates, the firewall and backups are your responsibility. We compare ready-made game packages and VDS on the game server package vs VDS page.

If your community is small, you don’t need a separate machine for TeamSpeak; it can be installed in a few minutes on a VDS where you already run a game server. When the community grows and the voice server needs to be restarted, updated or moved independently of the game server, moving to a separate VDS is just a matter of copying a few files. That keeps start-up costs low and lets you grow step by step.

What is the privilege key on first setup, and how do you use it?

The privilege key is a single-use code generated when the TeamSpeak server first starts; whoever uses it joins the Server Admin group. To take ownership of the server, enter this key in your client on first connection.

On first run, two important pieces of information appear in the server console and log file:

1. ServerQuery admin credentials: the serveradmin user name and password. The password is shown only once; store it somewhere safe.
2. Privilege key (token): after connecting with the TeamSpeak client, enter this key in the dialog that opens and your account is added to the Server Admin group.

On first launch the server also asks you to accept the licence terms, either with a launch parameter (license_accepted=1) or an acceptance file placed in the server folder. The server won’t run until they’re accepted.

Lost the privilege key? Don’t worry: connect to ServerQuery with the serveradmin account and create a new one. That makes the ServerQuery password the server’s “master key” — never share it.

How should you organise channels and permissions?

A tidy TeamSpeak channel and permission structure comes from grouping permanent channels by purpose, clearly defining server groups (ranks) and channel groups (channel admin, operator) and giving guest users only the rights they need.

An example structure for community servers:

• Welcome and AFK channels: a lobby where newcomers land and an AFK channel where long-silent users are moved.
• Game and team channels: a main channel per game or team with sub-channels used during matches; entry to team channels by password or permission.
• Admin channels: channels visible only to staff.
• Temporary channels: channels users can open for themselves, deleted when empty.

The most common permission mistake is giving the Guest group too many rights. Turn off guests’ rights to create channels, upload files and move other users, and put trusted members in a separate server group. After setting up server and channel groups, exporting them as a template saves time when you build a similar server later. Using game and team names in channel names helps newcomers find their way without asking.

How should you set voice quality and codecs?

Voice quality in TeamSpeak is set per channel through the codec and quality level. Using Opus Voice for talk channels and Opus Music for music or broadcast channels, with the quality level matched to your bandwidth, gives the most balanced result.

What to consider when choosing codec and quality:

• Opus Voice: tuned for the human voice; keeps speech intelligible even at low bandwidth. It should be the default for in-game communication channels.
• Opus Music: preserves a wider frequency range; suitable for music bots or live broadcast channels, but generates more traffic.
• Quality level: the higher the quality, the more data sent per user. Very high quality in crowded channels strains both the server and users on weak connections.

A large share of voice problems come not from the server but from user-side settings: wrong microphone sensitivity, voice activation threshold or background noise. Recommending push-to-talk and the client’s noise suppression to your users noticeably improves communication in crowded channels. On the server side, a location close to players and a clean network path minimise delay and drop-outs.

How do you keep a TeamSpeak server secure?

Securing a TeamSpeak server takes network-level DDoS filtering, ServerQuery access limited to trusted IP addresses, an up-to-date server version and narrowly scoped guest permissions, applied together.

• DDoS: voice servers can be targeted by rival teams or banned users, and voice cuts out during an attack. The RouteFence firewall in our data center filters attack traffic at network level.
• ServerQuery: ports 10011 and 10022 are the server’s management gateway. Open them only to your own IP address and the machine running your bots, and add only trusted addresses to the server’s allowlist file. Keep the WebQuery port closed if you don’t use it.
• Updates: older server versions may have known vulnerabilities; apply TeamSpeak’s updates regularly.
• Flood protection: the server’s built-in flood settings limit fake connection and message flood attempts.
• Admin accounts: keep the Server Admin group to a few trusted people; define a separate moderator group with channel move and kick rights for daily moderation.
• Operating system: run TeamSpeak as a separate user rather than root and allow only the necessary ports in your firewall rules.

How do you back up and migrate a TeamSpeak server?

A TeamSpeak backup consists of the database file holding channels, groups and permissions (ts3server.sqlitedb in a default install), the files folder with files uploaded to channels, the licence file if any, and the configuration files.

Because the SQLite database is updated constantly while the server runs, the safest backup is to stop the server briefly and copy the files. This usually takes a few seconds and can be automated with a scheduled task at night.

When moving to another server:

1. Stop the old server; archive the database file, the files folder and the configuration files.
2. Install the same or a newer TeamSpeak server version on the new server.
3. Extract the archive, put the files in place and start the server; channels, groups and user permissions come across unchanged.
4. Announce the new address to users, or point your domain’s DNS record to the new IP.

Giving users a domain or subdomain (for example ts.yourcommunity.com) instead of an IP means you only need to update the DNS record after a migration.

What are the most common TeamSpeak server problems?

The most common TeamSpeak server problems are unaccepted licence terms, a closed UDP port, a lost privilege key, file transfer not working and blocked ServerQuery access.

• Server starts and shuts down immediately: the licence terms haven’t been accepted. Add license_accepted=1 to the launch parameters or create the acceptance file.
• Client can’t connect: port 9987/UDP is closed in the firewall. Opening only TCP isn’t enough; voice travels over UDP.
• File upload and download don’t work: port 30033/TCP is closed or the channel’s file quota is full.
• Privilege key lost: connect to ServerQuery with the serveradmin account and create a new key.
• Bot can’t connect or gets kicked from ServerQuery: the bot’s IP address isn’t on the allowlist and flood protection has temporarily blocked the connection.
• User count stuck at 32: the licence file hasn’t been installed or the server hasn’t been restarted.

When diagnosing, the logs directory in the server folder is the first place to look; connection refusals, licence status and ServerQuery blocks are clearly recorded there. Including the relevant log lines in a support ticket speeds up the fix.

How does renting a TeamSpeak server work?

Choose a suitable VDS from the package table and complete your order; the server is provisioned automatically, and you then install the TeamSpeak server software yourself or request installation through a support ticket.

If you install it yourself, the basic steps are: connect to the server over SSH, create a separate user for TeamSpeak, download the server files from TeamSpeak’s official website and extract them into that user’s folder, accept the licence terms and start the server as a system service. Save the serveradmin password and privilege key shown on first launch. Then open ports 9987/UDP and 30033/TCP, and configure the ServerQuery ports to allow only your own IP address. If you prefer Docker, TeamSpeak’s official Docker image simplifies setup too.

Once the server is ready, connect with your client and enter the privilege key, create the channel structure and groups, take a first backup and share the address with your team. LIONFIN’s 24/7 NOC and SOC monitoring and 99.99% availability target are aimed at keeping voice running during match hours. Prices are shown in Turkish lira excluding VAT and the checkout is in Turkish; contact us by email if you need help ordering.