Where Does the TeamSpeak Server Store Data and Config?
TeamSpeak servers keep identity in ts3server.sqlitedb with settings in an INI. Working-dir, package and Docker layouts.
Last updated
TeamSpeak 3 servers keep everything beside the binary: ts3server.sqlitedb with channels, groups, bans and identities, ts3server.ini with ports and options, logs alongside. Manual installs live wherever you extracted them, commonly /opt. There is no registry or AppData involvement.
Package installs reorganize into system paths: Arch uses /etc/teamspeak3-server.ini with state in /var/lib and logs in /var/log. Docker uses /var/ts3server for persistence. The admin token prints once at first boot and never again, so capture it from logs immediately. MariaDB replaces SQLite for multi-instance setups only. This covers the server; the TeamSpeak client post covers the other end.
Where TeamSpeak 3 server stores this, by platform
/opt/teamspeak3-server/ts3server.sqlitedb
Manual installs keep ts3server.sqlitedb, ts3server.ini and logs in the working directory (commonly /opt/teamspeak3-server). Arch packages use /etc/teamspeak3-server.ini with state in /var/lib/teamspeak3-server. Docker persists /var/ts3server. Back up the database file, not the binaries. Admin token prints once at first boot.
Frequently asked questions
how do i move teamspeak server to a new machine
Copy ts3server.sqlitedb plus ts3server.ini and any licensekey.dat to the new machine, keeping paths consistent. Channels, groups, bans and identities travel in the database. Never run two instances against one SQLite file; MariaDB exists for that. Grab the fresh admin token from first-start logs.
where is the teamspeak admin token
The token prints once into the server log on first boot with a fresh database. Check the log file or docker logs output for the privilege key lines. If lost, generate a new one via ServerQuery with tokenadd rather than wiping the database. Store it somewhere safe immediately.
how do i persist teamspeak docker data
Mount a host directory at /var/ts3server so the database and INI persist outside the container. The official image documents this mount plus license and MariaDB variables. Without the mount, recreating the container wipes the server. Logs go to docker logs in this setup.
Notice an outdated path? Let us know.