Major UX Flaw on Download Page: Users are missing TS3 due to confusing layout

[canacan]

Hi TeamSpeak Team,

I’ve noticed a significant inconsistency in your web design that is causing confusion for our community members.

On your Support Page (https://support.teamspeak.com/), you provide a very clear choice: “TeamSpeak” (TS6) or “TeamSpeak 3”. This makes it easy for users to find what they need.

However, on the Downloads Page (https://www.teamspeak.com/en/downloads/), this clear distinction is missing. The TS6 Beta is set as the default view, and the “Download” button at the top leads directly to the Beta version.

When we tell new users to “Go to the site and download TeamSpeak,” they don’t see the version tabs. They simply click the first button and end up with the Beta, which isn’t compatible with our TS3 servers. This results in us having to explain the UI layout to every single new person.

My Suggestion:
Please bring the same clear selection logic from your Support Page to your Downloads Page. If users were presented with two clear boxes (TS3 vs TS6) upon entering the download section, it would eliminate all this confusion.

Consistency between your support and download pages would greatly improve the user experience.

Best regards,
[Caner Can]

[SYOX]

Hey, thank you for the feedback.

To be honest, I don’t think I fully understand your request. I should also mention that we’re currently working on a complete redesign of our website, which we hope to launch soon.

If I understand correctly, you’re complaining that users have to switch to the second tab to download TeamSpeak 3, rather than that tab being displayed by default when you open the Downloads Page? If that’s the case, I have to say that nothing will change in that regard.

Having TeamSpeak 6 as the default download view is intentional, as it is the newer product and we are focusing all our time and resources on it.

TeamSpeak 3 is still available for download, but it is no longer the focus of product development. Users simply need to switch to the second tab to download the TeamSpeak 3 Client.

Here’s the direct link to the TS3 Client Download Tab: https://teamspeak.com/en/downloads/#ts3client

Also, the TeamSpeak 6 Client is backward compatible, so you can use TeamSpeak 6 to connect to a TeamSpeak 3 Server, UNLESS you are running an outdated version of the TeamSpeak 3 Server.

---

In summary, we are currently working on a complete redesign of the website. The new website will still feature tabs for the download section, but the client version will be spelled out in full rather than simply appearing as “TS6 Client” or “TS3 Client.”

If I’ve misunderstood anything, please feel free to clarify.

Thank you!

[canacan]

Thank you for the reply, but I think there is a significant misunderstanding regarding the “real-world” user perspective.

I have been a TeamSpeak member for years and I run a public server. I am not talking about my own ability to find a link; I know where the tabs are. I am talking about the new users we invite to our communities every day.

1. The “First Impression” Problem: When a person hears about TeamSpeak and wants to try it, they click ‘Download’ and get TS6 Beta by default. They don’t even know TS3 exists because it is hidden behind a tab. They aren’t “choosing” TS6; they are being forced into a Beta experience without knowing there is a stable alternative.

2. The Burden on Community Leaders: As server owners, we act as your “support team” on the ground. We have to guide every single new user on how to set up ‘Push-to-Talk’ or basic settings. TS6’s interface is completely different and, frankly, far too complex for someone who just wants to join a server and talk. When I show these users the TS3 interface, they literally say: “Yes, this is what we want, the other one was too confusing/bloated.”

3. Request for Clarity (Not just Tabs): Why not offer a clear, side-by-side choice on the main page?

• TeamSpeak 3: (Classic / Stable / Resource Friendly)

• TeamSpeak 6: (Next-Gen / Beta / New Features)

Listing them with their intended use-cases would be much better than hiding the most-used version. Forcing a Beta product as the “default” creates a barrier for entry and adds extra work for us (the community leaders) who actually bring users to your platform.

I hope the redesign focuses on this “Freedom of Choice” and transparency, rather than making the most stable version harder to find.

[SYOX]

Thanks for clarifying.

I understand that your main concern is not which tab is shown by default, but that first-time visitors might not even realize there are two separate clients, each serving a different purpose. That’s a fair point, and I can see how the downloads page might leave people a bit confused on that.

To be upfront about our side of things tho: TeamSpeak 6 is intentionally the default and primary client showcased on the website. It’s the client we’re actively building, investing in, and betting on as the future of TeamSpeak (as mentioned earlier), so from a product and branding standpoint, we want new users landing there first, not on TS3.

Part of that comes down to perception, too. A huge challenge for us has been that a lot of people who don’t know TeamSpeak well tend to associate it with TeamSpeak 3, which is simply outdated. So leading with TS6 just makes more sense for us when it comes to attracting new users and shaping how the product is seen.

And I think calling TeamSpeak 6 unstable or bloated is a bit unfair. It’s still in beta, yes, but that’s not really the experience people are having with it. The UX can definitely improve though, which I agree on (so it’s not as confusing).

That said, I can see that the distinction between TeamSpeak 6 and TeamSpeak 3 could be communicated more clearly. Even if TeamSpeak 6 remains the primary/default option.

I cannot promise that we will change the downloads page in the exact way you suggested, but your point about clarity for new users and community onboarding is reasonable.

I’ll take this to the team for internal discussion.

Thanks again!

[djchap]

“They simply click the first button and end up with the Beta, which isn’t compatible with our TS3 servers.”

TS6 Client is compatible to TS3 Server !!!

And I believe there is no development for TS3 Server / client anymore (last server update in 2022, last client update in 2023)

So from my point of view you should update to ts6 server and client.

[canacan]

Let’s be clear: TS3 is the gold standard for performance. There’s a reason why the world’s top e-sports pros and competitive teams still stick with TS3 during major tournaments; when every millisecond and every FPS counts, you don’t trade stability for fancy UI. Starting someone on TS6 without them experiencing the core efficiency of TS3 is like trying to drive a luxury car without knowing how an engine works.

Of course, when users need modern tools like screen sharing or camera support, TS6 is the obvious choice and my system fully supports that. But I will always prioritize the TS3 link because ‘Pure Performance’ is what a real gamer needs. I’m offering the foundation of TS3 with the flexibility of TS6. Experience over hype, always.

[KorppuJauho]

If you want your community to use TS3 client, maybe you should say to them “download TS3 client” instead of “download Teamspeak”.

And if clicking TS3 client tab is overwhelmingly complicated to the user, I don’t think few milliseconds will matter at that point.

[OyuncuDedeler]

@canacan

TS6’s interface is completely different and, frankly, far too complex for someone who just wants to join a server and talk. When I show these users the TS3 interface, they literally say: “Yes, this is what we want, the other one was too confusing/bloated.”

Oh man, my friends wanted to switch to teamspeak from steam chat, at first they were quite confused as to how “anything” is possible. Untill trying to get them to use TS, I have never tried ts6 myself, and while its been a year, I still cant use ts6. I just had them switch to ts3, and almost all of them use TS3 still, only opening TS6 for screen sharing purposes.

TS6 complexity almost drove away my friends from TS all together.

[RexiikCZ]

Yeah, TS3 is for sure a way to go for many people, the chromium base is really HW heavy as we can see. It’s taking for me more than 700mb of ram in the idle and we don’t know how many garbage was left from the chromium base in it. TS3 is just so lightweight u don’t even need to care about it.

[canacan]

My intention isn’t to criticize TS3 and TS6, it’s just that when I tell someone to download an app, they download a sample app, I give instructions like using voice commands or push-to-talk, but they say it’s too complicated. I can’t explain the settings, push-to-talk, etc. either. I suggest people look at TS3 first, then TS6. TS6 shouldn’t be prominently displayed on the download screen. I would understand if there was a separate option like “Download this for screen sharing,” but…

[mbrouil3]

@canacan

My intention isn’t to criticize TS3 and TS6, it’s just that when I tell someone to download an app, they download a sample app

As a former TS3 server owner and now a proud TS6 server owner, I provide the TS6 download link for my users to utilize. They are not told to simply “just go download teamspeak”. Leaving the users to figure it out on their own is a disaster, therefore I give them the direct URL for TS6.

As a side benefit, this methodology also helps them stay away from shady sites that are NOT hosted, run, or moderated by Teamspeak.

[canacan]

As the author of this thread, I want to clarify our stance so TeamSpeak staff can see this purely as constructive UX feedback rather than ‘bashing the new client’. We fully respect that TS6 is the future and your primary focus.

However, from a Product Management and User Acquisition perspective, the current download page creates unnecessary friction for new users. Below is a production-ready Side-by-Side UX Layout that I designed. This structure completely solves the confusion without overshadowing TS6’s marketing goals. It simply lets users make an educated choice based on what they need (the specific features listed below are just placeholders/examples):

CHOOSE YOUR TEAMSPEAK VERSION

To give you the best experience, please select the version that fits your needs:

TEAMSPEAK 3 (Classic Edition) [STABLE]	TEAMSPEAK 6 (Next Generation) [BETA]
The legendary, lightweight voice client	Modern UI tailored for new communities
Preferred by Esports Pros	Screen & Camera Sharing
XX Feature	XX Feature
XX Feature	XX Feature
XX Feature	XX Feature
XX Feature	XX Feature
[DOWNLOAD TS3 FOR WINDOWS]	[DOWNLOAD TS6 FOR WINDOWS]
Other OS / Mobile available below	Other OS / Mobile available below

This layout doesn’t split the user base—it manages it efficiently. I highly recommend the web design team to run an A/B test with a split layout like this. It will drastically lower user friction and prevent newly invited users from dropping off during their first 5 minutes on TeamSpeak.

[ImScheinox]

I think you’re worrying too much about a „Change“ that, in the end, wouldn’t be worth tying up valuable resources (staff) for. TeamSpeak 3 won’t be getting any new feature, just security patches.
People who use TeamSpeak or are thinking about switching to TeamSpeak probably want features similar to those in their previous program, so it only makes sense that TeamSpeak 6 is the first choice. TeamSpeak 3 is really only chosen by people who already know the program and/or don’t need or want all the new features.

And I don’t mean to be rude, but anyone who goes to the download page can see that there are different options.
I don’t know anyone in my circle who’s had trouble figuring it out so far.

[canacan]

@LeonMarcelHD “I saw that you liked the comment above instead of addressing the core issues yourself. Since you seem to agree with that perspective, let’s put the corporate arrogance aside for a moment and look at the reality of what you are forcing upon your user base…
Let’s put the corporate arrogance aside for a moment and look at the reality of what you are forcing upon your user base. You get 2 likes on a forum comment and think you are doing a great job, while completely ignoring the people who have kept TeamSpeak alive for over a decade.

As a TS3 user for many years, I downloaded TS6 and felt completely alienated. We were so hyped and excited for a brand new client, but you made the interface so convoluted that when we finally figured out how the voice was transmitting and where the private message button was hidden, we literally started dancing at home celebrating it like a miracle. You are treating your loyal community like forced, unpaid beta testers for an application that is fundamentally broken and missing core features.

Here is the reality of the ‘TS6 experience’ you are so proud of:

• Complete Lack of Localization: Not everyone speaks English fluently. You don’t support major languages, yet you rush to force this app on everyone.

• Broken UI & Missing Features: Where is the basic ‘Back’ button? Navigating the UI is a nightmare. Channel settings are stripped down to just a name and password when creating them. The private messaging button is so microscopically small it’s barely clickable. Why is Channel Commander looking like a permission/rank instead of its classic distinct color indicator?

• Broken Legacy Systems: BBCode is completely broken; raw code is visible in channels and descriptions. The classic profile/avatar system is ruined—why is a user’s avatar suddenly their global profile picture? Why doesn’t tagging someone via [URL=client://UID] work anymore? Have you completely rewritten the tagging system without documenting it?

• Hidden Permissions: I couldn’t even find where to manage server permissions easily. You hid the backbone of TeamSpeak.

• Forced Accounts & Data Privacy: Why am I forced to log in with a myTeamSpeak account just to use a VoIP client?

• The ‘Spectator’ Issue: Why can we see server query logins and logouts instantly without even using a query tool/binoculars? This ruins privacy and server management.

But what infuriates me and the community the most is your marketing hypocrisy.

Whenever a country bans Discord, you run to X (Twitter) to post cringey tweets saying ‘Welcome to TeamSpeak!’ trying to flex. You rejoice over other platforms being banned, yet you don’t care enough about those banned countries to even provide them with basic language support in your new app.

Instead of obsessing over Discord on social media and celebrating their bans, you should focus on your own dying platform. At this rate, Discord doesn’t even need to try to beat you; you are defeating yourselves.

If you are building a brand new client from scratch (first calling it TS5, now TS6), why are we still connecting via highly vulnerable, open IP and port addresses? Why haven’t you implemented a modern, masked, and secure connection layer to protect communities from DDoS attacks?

If your response to genuine UX and community feedback is always ‘This is how we wanted it’, then why does this forum even exist? We are not your forced test subjects, and we are not obligated to report bugs for a tool that breaks everything we’ve built over the last 15 years just because your team wants to feel modern.”

---

[LeonMarcelHD]

I don’t need to repeat the same words that we’re already mentioned multiple times here in this thread?

I personally have not seen a reason to rewrite the same arguments that we’re posted before.

We (the company) want new users to land on TS6, the product that is currently being focused by our devs and is actively maintained, and not on TS3.

Your previous mentioned critique points are to some/most degree invalid or intended features/changes.

---

By that, I mean you don’t have to agree with or like every decision we make. We welcome constructive feedback, take community concerns into account, and are always open to discussion.

However, if you’ve already been given a detailed explanation of our position and the reasoning behind an intended decision, there’s no need to ask every staff member individually in hopes of receiving a different answer.

---

We appreciate your feedback and discussion points. However, as the topic has already been fully addressed from our side of view and is now driving off-topic, I will be closing this thread.