How to Install TeamSpeak 3 and Join a Server

You join a community's game server, play for an hour, and somebody types "get on TS" followed by an address that looks like a website but is not one. Nobody explains it. Everybody else clearly knows what to do with it.

That address is a TeamSpeak server, and this guide exists because nothing about the first five minutes of TeamSpeak is self-explanatory to anyone who learned voice chat on Discord. Listings collect on the software's hub.

The short version: download the client, paste the address in, pick a nickname, then move yourself into whichever room the people you know are sitting in. The longer version explains why it works that way, and why a large number of communities have declined to move off it.

It is a building, not a phone call

The mental model that makes TeamSpeak make sense is architecture.

A TeamSpeak server is not a call you join. It is a set of rooms arranged in a tree, displayed down the left-hand side of the window, and you are always standing in exactly one of them. The people in your room hear you. The people in the next room do not.

That structure is the whole design. A community running one will have a lobby, several rooms for different games, a couple of rooms for whichever squads are playing tonight, a room where the admins talk. There will also be a room named something rude that nobody has cleaned up since 2014.

You move by double-clicking a room. There is no invitation, no queue, no ringing. You walk in, and if people are talking, you are now in the conversation.

This is the thing Discord users find disorientating and the thing long-time users refuse to give up. Being able to see at a glance who is where, and to move to them without asking, is a genuinely different social experience from a list of channels you have to guess about.

Installing the client

The client is free and there is nothing to buy. Download it from TeamSpeak's own site and install it in the ordinary way.

Two things to do before you connect anywhere.

Set up push-to-talk. Open the settings, find the capture options, and bind a key. Open microphone transmission is the default in most modern voice software and it is not the convention here — a room of twelve people with open microphones is a room of twelve keyboards and twelve background televisions. Choose a key you will not press by accident and that is not already doing something in the game you are playing.

Test your microphone properly. The client has a test facility. Use it before you are in a room with people rather than after somebody tells you that you sound like a drive-through speaker.

Set your nickname while you are in there. It is a client-side setting rather than something you register, which means you can be a different name on different servers and nobody will stop you.

Your identity is the important part

This is the concept nobody explains and the one that causes the most grief.

TeamSpeak does not identify you by a username and password. It identifies you by an identity, which is a key your client generates and stores locally. When a server administrator gives you a rank, they are granting it to that identity. Not to your nickname, which anybody can copy, and not to an account, because there is not one.

The consequences are immediate. Reinstall your operating system without exporting your identity and you arrive back on every server you use as a stranger with no permissions. Move to a new computer and the same thing happens. Every long-term TeamSpeak user has done this once.

Export your identity and keep the file somewhere safe. The option is in the client, under identities, and it takes about ten seconds. Then, when you move machines, import it and everything you had comes back.

Connecting to a server

Open the connect dialogue, paste in the address you were given, and go.

Most addresses are a hostname on its own, and the client fills in the rest. Where a server runs somewhere other than the standard place, the address will have a port appended after a colon — copy the whole thing, because a host running several voice servers on one machine cannot give them all the same one.

Some servers want a password, and there is a field for it. Some are open to anyone and put newcomers in a lobby channel with no rights until somebody notices them.

Bookmark anything you use more than once. The bookmark stores the address and your nickname for that server, along with any password, so joining becomes one click rather than a search through your old messages for something posted in 2019.

The etiquette nobody writes down

Every established TeamSpeak server runs on conventions its regulars absorbed years ago and will not think to explain.

Use push-to-talk. This is the big one, and it is the difference between being welcome and being the person everybody mutes.

Move to the room that matches what you are doing. Sitting in a game's channel while playing something else is how people end up in the wrong conversation, and the tree only works if everybody keeps it honest.

Do not sit in the admin channel because it was empty. Do not play music into a room unless somebody asked. Do not follow a person from room to room, which reads very differently from the other side than it feels from yours.

And when you join somewhere new, say who you are. A silent stranger with no permissions in the lobby will be ignored for a very long time. Thirty seconds of introducing yourself skips all of it.

Permissions, and why you cannot do things

The first hour on a new TeamSpeak server frequently involves discovering that you are not allowed to do something, with an error message that explains itself in the language of a database.

The system underneath is genuinely powerful and genuinely opaque. Server administrators define groups, assign them to identities, and control what each group may do — which channels it can see, which it can enter, whether it can speak in them, whether it can move other people, whether it can create rooms of its own.

For a newcomer this shows up in three ways. You cannot talk in a channel, because speaking there requires a group you do not have. You cannot see a channel that other people are clearly in. Or you are stuck in a lobby waiting for somebody to promote you.

None of that is a fault. Ask in whatever channel you can reach, or in the community's game server, and somebody will fix it in a few seconds.

Administrators hand out rights using tokens — a string of characters that grants a group when you use it. If someone sends you one, there is a menu option for entering it, and it applies to your identity permanently. Which is the other reason to back that identity up.

Two features worth knowing about

Whisper. You can bind a key that sends your voice to a specific person or a specific group rather than to the room you are in. Squad leaders in large games use this constantly, and it is the feature that makes TeamSpeak workable for organised play in a way that a flat list of channels is not.

Poke. A short message that appears in a box on somebody's screen and demands attention. It is deliberately annoying. Used properly it is how you get one person out of a game without shouting at everybody.

There is also per-channel file storage, which communities use for map packs, configs, rules documents. It is quietly one of the more useful things the software does and almost nobody mentions it.

Why communities have not all moved to Discord

They have, mostly. That is the honest answer, and any guide that pretends otherwise is selling something.

What is worth understanding is why a substantial minority stayed. Every reason is about control.

A TeamSpeak server belongs to whoever runs it. The permissions are theirs to define in detail that no hosted platform offers. The channel structure is theirs. Nothing changes underneath them because a company redesigned an interface, and no account policy at a company they have never dealt with can remove twelve years of a community overnight.

There is a latency argument too, and for organised competitive play it is not nothing. Voice quality and delay depend on the machine and where it is, both of which a self-hosted server controls and a hosted platform does not. Where you put it matters, and our notes on choosing a hosting region apply to a voice server exactly as they do to a game server.

The honest counter-argument is substantial. TeamSpeak has no meaningful text history; it is awkward on a phone; it requires somebody to run and maintain a server; it asks every newcomer to install a separate program before they can say hello. Those are real costs and they are why the shift happened. We wrote about how Discord changed the way gaming communities organise, and voice hosting is the clearest single example of what moved and what did not.

Plenty of communities now run both — Discord for text, announcements, the people on phones; TeamSpeak for the evenings when thirty people are playing something that needs proper channel discipline.

Running one

Server software is available from TeamSpeak and is free for non-commercial use within limits that a community-sized server will not usually trouble.

Two pieces of practical advice for anyone standing one up.

The first token the server gives you on creation is what makes you the administrator. Save it somewhere that is not a chat window. Losing it before you have used it is an irritating way to start.

And put the machine where your people are. A voice server is a light load and a latency-sensitive one, which is an unusual combination — the cheapest box in the wrong country will be worse than a modest one nearby. Our piece on game server hosting costs covers the money side, and voice sits at the cheap end of everything discussed there.

Voice servers also attract the same nuisance traffic that game servers do, particularly if your community is competitive. Dealing with that on a small server is worth reading before it happens rather than during.

The alternatives

Mumble is the other survivor, and it is the one to look at if the control argument appeals but you would rather run something open. Its positional audio, where voices come from the direction the speaker is standing in, is genuinely better than anything else in this category.

Ventrilo is older still and persists in a handful of long-established communities that never saw a reason to move.

And the TeamSpeak hub covers the software's newer generation, which most communities have not yet moved to — which is why the address a stranger hands you is still, more often than not, a TeamSpeak 3 one.

<!-- joingg-footer -->

---

JoinGG is a live directory of community game servers. Every listing is queried directly every fifteen minutes, so the player count you see was measured rather than reported by its owner, and each one carries a copyable connect address. TeamSpeak 3 servers are listed here, and every game on the site has its own hub. Player counts across every game are on the statistics page.