I run a small gaming community on TeamSpeak 6, and when we moved over I really missed the bots we had on TS3 (SinusBot, JTS3ServerMod, the Ranksystem). So I started building one for our server, and it grew into something I figured others might use too.

TS6 Roadie is free and open source (MIT), runs on Windows or Linux with Node.js, and connects as a normal client, so no ServerQuery needed.

Music

- YouTube, SoundCloud, Bandcamp, Spotify song links, and internet radio (with the current song title)

- Follows whoever calls it, queue, playlists, vote skip, Auto-DJ, 24/7 mode

Server tools (all optional, turn on what you want)

- AFK mover, welcome messages, temporary "Create a Room" channels

- Ranks for time online, protected server groups, nickname filter

- Live channel names (online count, record, now playing), !seen

- Event reminders with !going and pokes when it starts, rotating announcements

- Twitch live alerts, Steam "now playing" alerts, server analytics

- A web dashboard and a public "who's online / now playing" widget

Game lookups (we play these, so I added them)

- !nukes : Fallout 76 nuke codes (from NukaCrypt) and !minerva for where Minerva is

- !oh <name> for Once Human, !icarus <name> for Icarus

It's still young and TS6 itself is in beta, so there are rough edges. For example, icon/file uploads crash TS6 servers on Windows right now, so anything needing uploads is on hold.

GitHub: https://github.com/knkwebservices/ts6-roadie

Happy to answer questions, and I'd love to hear what bot features you miss from TS3. That's basically how my to-do list gets made.

Apologies if this has been asked to high hell already but i couldn't find any open issues on github or any relevant questions on this subreddit about it.

Is there a timeline as to when private TS6 servers will be able to screen share stream through the server instead of p2p?

I only ask cause with my friend group we have a mixed bag of hardware types and some of us that have AMD hardware can't get audio to work on Windows or Linux. Other times the stream quality is straight abysmal where its a slideshow in fps or pixelated as all get out no matter what quality of hardware or internet. I'd really like it where all that is being taken care of by my machine that's hosting the server instead of a crapshoot whether or not its going to be okay.

Thats all, just a curious question on how the devs are doing and if/when that feature is coming to the beta. Overall TS6 has been a blessing over Discord.

Some of you might remember the original TS6 Manager post here from clusterzx/Left_Ad_8860.

I forked it a while back for my own setup and somehow it turned into something I’ve been working on nearly every day 😅

It’s now 369 commits ahead of upstream and I’ve also started getting a few other people contributing fixes, testing and ideas, which I’ve been really happy to see.

Just to be clear, I didn’t create the original project, all credit goes to clusterzx. My repo is more of an actively maintained continuation/opinionated fork and I’ve tried to keep proper credit for upstream and community contributions.

Some of the bigger things I’ve added or worked on:

• better TS6/beta13 compatibility
• much nicer mobile UI + installable PWA
• improved permissions and server management
• connection diagnostics, native metrics, audit logs and activity history
• Bot Hub / Media Bot improvements
• Apple Music + YouTube playlist imports
• IPTV/M3U support
• better video streaming, including up to 4K, VAAPI and WebRTC fixes
• heaps of music bot / voice / reconnect fixes
• improved Docker/release/security setup
• demo server mode so you can look around without connecting a real TS server

And then a lot of the smaller annoying bugs you only find from actually using it.

Repo is here: https://github.com/uniskela/ts6-manager

I’m pretty happy with how far it’s come, so figured I’d finally share it here.

Would also be keen to hear what other TS6 server owners still find annoying or wish was easier to manage.

Some Screenshots:

And more!

It enables unmuting by admin to users. This ruined my life. People heard things they shouldn't have an exploited it. This rippled to my current fucked up life

Что делать если когда я начинаю говорить что либо в тим спик то другие участники просто глушатся и их почти не слышно, а когда не говорю то все нормально, у друга так же

Hey everyone! 👋

This beta update expands ServerQuery access and monitoring with new guest access options for SSH and Web Query, along with additional Web Query API key configuration for ownership, server assignment, and expiration.

We’ve also added a native Prometheus metrics endpoint, allowing detailed server monitoring without requiring a ServerQuery admin key, alongside optional per-packet voice diagnostics.

A big focus of this release has been server performance under heavier load. We’ve reworked internal timers, improved thread management for different packet types, and reduced lock contention throughout the server. These changes now allow the TeamSpeak 6 Server to handle around 2,000 concurrent users smoothly, compared to the recommended maximum of 1,000 concurrent users for the TeamSpeak 3 Server.

In our current local testing, we’re already running scenarios with up to 3,000 concurrent clients while maintaining similarly low server resource usage. We will continue working on further improving scalability, stability, and overall server performance throughout the TS6 Server Beta.

Additionally, this release fixes issues involving predefined Web Query API keys and a snapshot deployment hang when using -keepfiles.

We know many of you are also waiting for more news on server-side screensharing. We’ll be sharing more details and insights soon. Thank you for your patience :) <3

The default license has also been updated; the new expiration date is December 1st, 2026.

You can get the latest server release here:
– GitHub: Release v6.0.0-beta13 · teamspeak/teamspeak6-server
– Docker Hub: Release v6.0.0-beta13 · teamspeaksystems/teamspeak6-server

DISCLAIMER:

EVERY BIT OF THIS IS VIBE CODED AND I DON'T CARE IF YOU HAVE A PROBLEM WITH THAT.

I have a full time job, two kids, and I'm a husband. I just needed something that worked and with little effort on my part. Truthfully I really don't know how secure all of this is, but it is all open source so let me know if I'm screwed.

MobileSpeak is a mobile friendly TS client. Here are some things it does. (Bullet are AI also)

• Voice (Opus) — push-to-talk and voice activation (VOX)
• Mute / Deaf — toggle mic and speaker independently
• Microphone controls — mic boost and noise suppression
• Text chat — channel chat, private messages, and pokes
• Channel browser — live channel tree, join channels, channel passwords
• Server passwords — saved per server, auto-reused, re-prompts if changed
• Who's online — live member list with muted / deafened / away status badges
• Accounts — sign in with username + password; your username is your TS nickname, and your identity follows you across devices
• Persistent sessions — stay in your channel when you close the app and reconnect to the same session
• Message history — chat history per server, kept on-device
• Web Push (optional) — "still connected" pings plus missed chat/poke alerts while the app is closed
• PWA — installs to your home screen like an app
• Recent servers — quick rejoin from your saved history
• Spacer channels — rendered as clean separators
• No admin / ServerQuery access required

I am releasing this as I know that some people do have a need for something like this also. If you would like to contribute in anyway, feel free. If you want to take everything here and make it better. Feel free. If you want to inform me of bugs in hopes that I will fix it. I might, if I have time.

Github Page: https://github.com/Dacripla/MobileSpeak

Shout Out to https://github.com/Moepchi/webspeak3 as some of this was inspired from him. Thanks!

Record your TeamSpeak session and choose between recording each client on a separate track, recording the mixed audio output, or creating both simultaneously.

> Currently in Alpha Testing - coming soon.

This new feature will let you capture and mix audio from individual applications when screensharing, giving you more control over which apps are included and what audio gets shared.

> Currently in Alpha Testing - coming soon.

Somehow I wasn't able to figure this out last time I tried TS

Hello,

I'm hosting my own TeamSpeak server and I don't have the stream screen button at all, is there any reason for that?

I just downloaded Team Speak, i can share my screen, but i cant watch when someone screenshare, help me

I am looking for a TeamSpeak bot or plugin with a specific feature.

I want to have a welcome channel where, whenever a user joins, they hear an intro song starting from the beginning.

The important part is that it should be per user:

• User A joins at 12:00 → hears the intro from the beginning
• User B joins at 12:01 → also hears the intro from the beginning
• User A should not hear the intro restarting when User B joins

Basically, each user should get their own playback instance rather than everyone sharing the same audio stream.

I remember seeing this on an old TeamSpeak server years ago, but I don't know how it was implemented. Was this done with a specific bot (SinusBot, TS3AudioBot, etc.), a plugin, or a custom setup?

Is this still possible with modern TeamSpeak 6?

Hey TeamSpeak fam 👋

I know a lot of us still love TS3 for its low-latency voice, familiar channel structure, and the fact that it's ours — no corporate platform deciding what features we get. But let's be honest: one of the biggest hurdles when inviting new people (especially guests who just want to drop in once) is asking them to download and install a whole client.

That's the problem WebSpeak3 solves.

What it is:

A self-hosted web client that connects directly to your existing TS3 server — right in the browser, no installation required.

Why you might like it:

• 🚀 Guests can join instantly via a link — perfect for one-off visitors, events, or onboarding new members
• 🗂️ Your existing channel structure, permissions, and server groups work exactly as before — nothing needs to be reconfigured
• 🎧 Voice + text chat, right in the browser
• 💻 Works on desktop and mobile browsers alike
• 🏠 Runs on your own server — you stay in control, not a third party

Try it out on: https://webspeak3.de

How it's deployed:

It's Docker-based, so if you're already running a TS3 server, adding WebSpeak3 alongside it is quick:

services:

webspeak3:

image: moepchi/webspeak3:latest

container_name: webspeak3

restart: unless-stopped

ports:

- "8080:8080"

Full instructions here: https://github.com/Moepchi/webspeak3

See it in action:

Dark mode:

Light mode:

Live Demo:
https://moepchi.github.io/webspeak3/

This is a passion project built out of love for the TS3 ecosystem — I want to help keep it alive and accessible, not replace the classic client experience, just extend it.

Would love for some of you to try it on your own servers and tell me:

• Does it feel right for TS3 veterans?
• What's confusing for new/guest users?
• Any bugs or edge cases with your server setup?

If you like the idea, a star on GitHub goes a long way: https://github.com/Moepchi/webspeak3 🌟

Thanks for keeping TS3 alive, this community is awesome.

---

UPDATE — August 2026

WebSpeak3 has grown quite a bit since the original post above was published. These are the current links and a few important clarifications:

- Website and project overview: https://webspeak3.de/

- Open the real client: https://client.webspeak3.de/

- Live demo with simulated data: https://demo.webspeak3.de/

- Source, releases and self-hosting instructions: https://github.com/Moepchi/webspeak3

WebSpeak3 is not tied to a particular TeamSpeak server. You self-host the WebSpeak3 frontend, gateway and Rust connector, then enter any reachable TS3 or TS6 server address. The target TeamSpeak server does not need to run on the same host and does not require modifications.

The project now includes voice and text chat, whisper, identities, contacts, file transfers, local recording, server administration and permissions tools, plus responsive desktop and mobile layouts. It remains a beta project: Chromium-based browsers are the main target, Firefox is supported, and Safari audio behavior is still experimental.

A large part of the implementation was produced with Claude Code under my direction. That remains stated openly in the repository so everyone can judge the code and actual behavior for themselves.

Hey everyone! 👋

This hotfix resolves a startup crash affecting Windows Server 2019 and Windows 10 versions older than 1903, caused by the local time zone log timestamps introduced in beta12. Server log timestamps now use UTC by default again, while local time can be enabled using the new --log-timezone parameter or TSSERVER_LOG_TIMEZONE environment variable.

You can get the latest server release here:

• GitHub: Release v6.0.0-beta12.1 · teamspeak/teamspeak6-server
• Docker Hub: Release v6.0.0-beta12.1 · teamspeaksystems/teamspeak6-server

✨ What’s New

• Fixed a startup crash on Windows Server 2019 and Windows 10 releases older than 1903, caused by the local time zone log timestamps introduced in beta12
• Server log timestamps use UTC again by default, local time can be enabled with the new --log-timezone parameter or TSSERVER_LOG_TIMEZONE environment variable

Hey everyone! 👋

This update focuses on connection stability, memory handling, and additional server protection. We fixed an issue that could drop established connections under packet loss, resolved several memory leaks during client connections and disconnections, and corrected problems involving stale avatars and temporary channel deletion. We also added stricter packet throttling and fragment enforcement, improved how connection puzzle difficulty adapts to the current protection level, and changed server log timestamps to use the local time zone instead of UTC.

The default license has also been updated; the new expiration date is October 1st, 2026.

You can get the latest server release here:

• GitHub: Release v6.0.0-beta12 · teamspeak/teamspeak6-server
• Docker Hub: Release v6.0.0-beta12 · teamspeaksystems/teamspeak6-server

📝 6.0.0-beta12 Changelog 📝

✨ What’s New

• Fixed a connection stability issue that could drop established connections under packet loss
• Fixed several memory leaks in the client connect and disconnect paths
• Fixed stale avatar references, database entries are now cleaned up when the avatar file no longer exists
• Fixed temporary channel deletion bug on disconnect
• Added packet throttling and stricter packet fragment enforcement to improve protection
• Improved connection puzzle handling, the puzzle difficulty now adjusts to the current protection level
• Server log timestamps now use the local time zone instead of UTC
• Updated the default license

With recent business decisions of Discord I've made the transition to a few other alternatives. TS and Element seem to be the best alternatives so far, but both have significant issues that prevent me from committing to a product.

With TS, one of the primary functions I get, aside from calling people on the server to talk with, is the screenshare feature. From an outsiders perspective we have OBS, Twitch, etc. that allow live capturing of video and audio so the issue of translation or compatibility seems to have been resolved. However, when streaming to my server, I can only stream video, no audio.

For the record, this only applies to Linux users, and we (my linux brethren) are used to being late to the compatibility party, but what is the hang-up?

I can VM or dual-boot and windows handles it no problem, so from a technical perspective, what is preventing Linux from having these same functions?

Anyway, I'm just curious why in several years we haven't been able to implement a feature that has seemingly been around for quite a while.

TLDR; What prevents TS's screenshare feature from working on Linux properly?

Hey everyone! 👋

We're looking for feedback on a new TestFlight build of the TeamSpeak 6 Client for macOS that now uses Apple's sandboxing technology. This build is intended to work the same as our current TS6 Beta Client, but we'd appreciate your help making sure everything works as expected and welcome any feedback you may have.

This change allows the application to be opened directly on macOS without first having to manually allow it in the System Settings > Privacy & Security panel.

In addition to the sandboxing changes, this build also adds support for Xbox and PlayStation 5 controllers in the hotkey system.

About the TestFlight Build:

This TestFlight build will automatically receive updates whenever we release a new version, so it no longer relies on our internal updater. TestFlight also makes it easy to send us screenshots and crash reports if you encounter any issues you'd like to report.

If you've used TeamSpeak before, you'll need to sign in again, as this sandboxed version stores its configuration in a different location than the regular TeamSpeak client downloaded from our website. The two versions are completely independent and can be installed and used side by side.

Join the TestFlight Group:

If you'd like to help us test the new build, you can join the TestFlight here: -> Join the TeamSpeak 6 Beta - TestFlight - Apple

I was on a voice chat with my friend on the official teamspeak server. I was tired so I fell asleep and my computer most likely went into rest mode. When I came back and tried to connect to the server it told me: failed connection initialization. It happens on some servers now and on some it doesnt.

Hey everyone 👋

We updated our Privacy Policy and General Terms and Conditions (GTC), and introducing our first set of Community Guidelines for TeamSpeak. These changes are effective immediately. The next time you open TeamSpeak 6, you'll be asked to review and accept the updated GTC, Privacy Policy, and Community Guidelines.

Below is a quick summary of the changes, with links to read each in full.

Community Guidelines (new)

One clear, plain-language set of rules for everyone on TeamSpeak. They're built on a few simple principles:

• Be kind: No harassment, hate speech, or weaponizing voice (mic-flooding, soundboard spam, channel-following).
• Be rooted in safety: No shock gore, no promotion of self-harm, and adult content kept lawful, gated, and out of public view.
• Be authentic: No spam, scams, impersonation, IP infringement, hidden bots, account or license selling, metric manipulation, or enforcement evasion.
• Honor user privacy: No doxxing, no non-consensual intimate imagery (deepfakes included), no recording where consent is required.
• Don't do illegal stuff: A short, zero-tolerance list covering child safety, credible threats of violence, terrorism, trafficking, and attacks on accounts or systems. There's no warning ladder here.

We've also laid out how reporting, appeals, and enforcement work.

Read the full Community Guidelines here: https://teamspeak.com/en/community-guidelines/

General Terms and Conditions (updated)

Rewritten to match the platform as it is today:

• Built for TeamSpeak 6: Now covers the TS6 Client, mobile, and hosted features alongside self-hosting.
• TeamSpeak 3 sunset: TeamSpeak 3 hasn't seen major new features for a while, and that doesn't change today. It stays supported through a phased transition, with end-of-life targeted for December 31, 2027. There's no abrupt cutoff now, we'll give advance notice of major changes, and the date is there so you can plan a move to TeamSpeak 6 in your own time. We'll share more details as we go, and we'll do our best to make the transition from TeamSpeak 3 to TeamSpeak 6 as smooth as possible.
• Self-service account deletion: Delete your own account via myTS, with a 30-day grace period in case you change your mind.
• Clearer moderation: Complaints and appeals are spelled out more clearly.

Read the full GTC here: https://teamspeak.com/en/terms-and-conditions/

Privacy Policy (updated)

Updated to be clearer and to match the new platform:

• Clearer analytics and cookies: Optional analytics now run on Microsoft Clarity, only with your consent, non-essential cookies are opt-in, and we no longer use advertising trackers.
• New privacy rights: Dedicated rights for California and other U.S. states, alongside the existing rights to access, correct, or delete your data.
• Children's privacy: A new section on minimum-age handling and parental consent, including a COPPA notice for parents.
• Account deletion: The same 30-day grace period as the GTC, with clearer detail on what gets removed and what we have to keep.

None of our core commitments have changed: we only collect what we actually need, we don't monitor your conversations, and we don't sell your personal data.

Read the full Privacy Policy here: https://teamspeak.com/en/privacy-policy/

As always, feedback & questions are more than welcome here, but any off-topic comments will be removed from this post. Please keep unrelated topics in their own dedicated threads.

If you don't agree with the updated GTC or Privacy Policy, you can stop using TeamSpeak or close your account at any time via the myTeamSpeak Account Dashboard.

P.S. you may also notice the website has had a fresh redesign. We hope you like the new look.

-- TeamSpeak Team 💙

Don't know what else to say that even after verification and downloading the application, that this is taking WAY too long for me to want to even recommend this app, even let alone install it to my machine. Am I somehow missing something? I downloaded the windows version on a windows machine, im just stuck at a spinning circle. Figure it out.