Markdown Overhaul

The Foundation II Update will include a fully redesigned rich-text editor with live preview, richer Markdown-style formatting, slash commands, a new toolbar, support for tables, math (KaTeX), Mermaid diagrams, images, references, and more.

Foundation II is currently in Alpha Testing


Mermaid Diagram Example:

me_cat_ts


We’ve also introduced a new “Preview” category in the announcements section → Announcements > Preview. Going forward, we’ll be sharing all of our previews and sneak peeks here on the forum as well. We know not everyone uses Twitter (or social media in general), and this change ensures everyone can stay up to date.

If you’re interested in our dev account on Twitter, feel free to give us a follow here: @teamspeakdev


Don't miss any future Preview posts
21 Likes

As long as 99% of servers are still using BBCode because switching to Markdown in TS3 is basically impossible, you should add a translator so TS6 users can see BBCode properly rendered as Markdown instead of raw BBCode.

2 Likes

Dear TeamSpeak Team.

Sorry… But…

WTF.

I am seriously questioning the priorities and alignment regarding the tasks that actually need to be addressed. There is no real need for features like this. Even if you have free resources to work on additional functionality, please keep in mind that the community is still waiting for far more critical features and improvements. Announcing low-priority changes like this is likely to be frustrating for many users.

That is my perspective. You are free to have your own.

9 Likes

I completely agree. I expected this update to deliver a much better UI/UX experience regarding the chat. However, judging by the screenshots, the overall experience won’t improve significantly; you’ve simply added a few features that, while not bad, aren’t necessary at the moment - as @arajdon mentioned.

Since you are a small team and cannot provide 24/7 support for your IT infrastructure (chat servers, VoIP, etc.), it makes no sense for the chat to run through your servers when I am hosting my own. I simply cannot understand this logic. Furthermore, the 5 MB limit for image files has been an issue for over five years and still hasn’t been fixed. There are also numerous long-standing bugs, such as voice cracking, that remain unaddressed.

The fact is, your mobile apps are completely obsolete and need a total rework ASAP. Users have requested this many times, yet these pleas are ignored. At this pace, the project will not survive.

After more than 15 years, I shut down my server six months ago because I lost hope in this project. Try to see it from the perspective of a regular user following your socials and forums: after 3–4 months without an update, you release ‘Mermaid Diagrams.’ It’s disappointing. We are waiting for major improvements, but the development direction feels very disconnected.

I’ve heard on the forums that SFU has been in alpha testing for months but still hasn’t been released. If it’s ready for beta, why not release it? If issues arise, people can always fall back on P2P. Honestly, it feels like the project has completely lost its way.

7 Likes

Crazy, anyway

Nice feature. Excited to see more previews, especially as yall make progress on text chat.

I think the editor’s new Markdown features are great. BBCode is so '90s.

I know a lot of people want text-only channels. Now things are finally moving in the right direction, and people are still unhappy…

That said, I also think it’s a shame that beta releases are so infrequent. Maybe you could release alpha versions or snapshots for testers on a monthly basis :smiling_face_with_sunglasses:

1 Like

Based on the views expressed in the most recent replies, I can say for my part: I find both perspectives understandable.

On the one hand, some posts might seem a bit like “empty promises” when you consider the progress made over the last few years up to now.

That’s certainly not the intention—but, in my opinion, it suggests that something needs to change in terms of communication (though I’m not a community manager, so I’m not really in a position to judge).

On the other hand, I still think it’s great that we’re now getting previews of what’s to come, and I also think the changes announced here are a good step forward. Especially considering the frequently requested “chat-only channels,” I think we need a solid foundation for text-based features, and this definitely gives hope for more.

I’m definitely looking forward to the next updates :slight_smile:

4 Likes

Maybe a bit context: A good working chat with rich features is the core for (nearly) everything else. Even when screensharing, sharing ideas, diagrams or just nicely formatted messages is a core aspect of communicating next to your video/audio share. Persistent chats, forum-like thread management etc. all build up upon a solid chat experience. We now dived into the core, added a solid foundation, made huge performance improvements in the chat to ensure future features can make use of this solid foundation.

All hints in the forum still hold true, all the things you guys are mentioning are in the works, but are released in due time, when everything works as solidly as we & you expect it to be. We hopefully are not as disconnected to you guys as it might seem; we know the pain points as we also use the client daily (of course) and encounter the same issues. We will show more features, when we feel they are pretty close to release.

However, circling back again, the chat features are a core aspect of the client and you encounter rich text nearly everywhere, so having this in place now is one pain point less on our (long) list.

Screensharing and Voice calling are surely right at the top of that list and you can expect more information on that after the release of the chat overhaul.

Hope that clears some confusion on why we made the decision to why we do these things in the order we currently do.

Thanks for being a loyal community and driving the priorities that will form the client now & the future :heart: !

23 Likes

First, I want to make it completely clear that my last message, and any of my past messages, were not meant to be an attack on @SYOX , @revide , or anyone from the TeamSpeak Staff.

I just clearly stated my disappointment regarding the progress. I will try to explain my point of view, and I hope you will understand my side.


Why We Moved from TeamSpeak
First of all, I have used TeamSpeak since 2006 when I played my first FPS game, WarRock. We self-hosted a TeamSpeak 2 server because Skype took up too many resources, and my computer could only handle TeamSpeak. We got used to it. Years later, TeamSpeak 3 came out, and we all enjoyed the features it delivered over the years.

Around 2017, Discord came along. It initially had many issues, none of my friends used it, and many of us hated it. I’m still not a big fan of it, but it does have many more features that make the experience with friends better—I cannot lie about that.

A year ago, some of us were still using TeamSpeak 3 and TeamSpeak 5. A few friends tried to convince us to move to Discord, so we would talk on TS and use Discord only for screen sharing. Over the years, Discord improved, and my friends started to like it more and more. Because of nostalgia, a few of us still forced 80% of our friends to stay on TeamSpeak. But at a certain point, we couldn’t force them to keep using a platform that couldn’t deliver what the other one had.

For example, most of our friends are over 30, have families, and spend a lot of time in their cars or outside; we can’t always sit behind a PC to talk. The biggest disadvantage is the mobile app. The mobile apps are obsolete, as I wrote above, and don’t work well with car Bluetooth (especially the Android one). The chat is not as rich as on Discord, and the biggest dealbreaker is that you can’t share video or turn on your IRL camera.

At that point, I couldn’t keep pushing TeamSpeak because people couldn’t use it properly with their Samsung Earbuds and other devices. Eventually, only a few of us stayed on TeamSpeak while the rest moved to Discord, so we all had to make the switch. Screenshare on TeamSpeak didn’t deliver what we expected and nobody wanted to used it, that’s I abandon long history of my TeamSpeak server.

I’m still a fan of self-hosted solutions. I would be the first one to pay for a server license, no matter the cost, if it could deliver good features and performance. I was talking with @revide privately and explained that my TeamSpeak 6 screen sharing still doesn’t work as it should; after a certain time, voices become robotic and the stream freezes. That’s why I was looking forward to P2S so much.


What Do I Miss the Most?
As I have written many times before, P2S was highly requested. I read on the forums that it was released in alpha in December 2025, and I was optimistic that we could expect a full release within two months. However, four months have passed, and as far as I can see, we are still not close. Try to understand my last message, after chat being upgraded it made me a lil disappointed because there are core most wanted features which don’t work 100% as it should and I expected in next patches to be significantly improved.

I understand that the team is small, but communication is something I really miss from TeamSpeak. It would be great if you could release any info regarding the mobile apps, self-hosted chat, or when you expect P2S to be released. I understand that if development isn’t going smoothly, you don’t like to give specific dates, but we are all adults and we would understand. The biggest problem is that we get a TeamSpeak update, followed by three months of absolute silence. We really don’t know what’s coming next—whether we’re going to see a message saying the project is abandoned, or if the team is working hard behind the scenes…

Please try to understand me and others who write messages like this. We really don’t want to create a bad mood, but we are just feeling disappointed.

I want to repeat once again that I know this is not @revide’s fault, nor @SYOX . The team is small, and the slow development is a management issue. I might be wrong, but it looks like @revide is working alone on the client for Mac and Windows, which is crazy.

Considering all the pressure on the TeamSpeak brand, the number of pro players who have used this program, and its amazing history—it’s all resting on the shoulders of just a few people. Huge respect to all the guys who work on this. I support and respect you all.

That’s all from me. All the best.

11 Likes

I couldnt agree more with 90% of your statements. I Love Teamspeak i never really liked Discord but progress since first TS5 public Beta has been so slow its really weird to me. Maybe the Teamspeak team needs to find better ways to make money to hire more devs idk but if the prpgress keeps being this slow Teamspeak will completely die i feel like.

And a lot of people in the Counter Strike community still use Teamspeak but also want to use screenshare and similar features that only really work good in discord.

I know the Teamspeak team probably also want to succeed obviously but maybe you could make some statements and have even better connection and talk more to the community which difficulties you face.

Thanks for your work you are already doing.

1 Like

I see a really good opportunity for teamspeak to actually overcome the competition with discords new crap, and instead of adding actual functionality and stable versions for Linux, windows and Mac. This is what you are working on? I know yall just ran out of regions for server hosting, so I know the money is coming in. It isn’t lack of funding it’s lack of common sense. Get the app running for everyone and add features people want and you guys would take over..

Not a hatepost, but: you don’t need formatted messages next to screensharing until screensharing actually works. I’m really trying to bring my friends to TS6 but screensharing and mobile apps are game-changers here unfortunately

Screen sharing works very well in most cases. Where exactly are you having problems?

In networks with symmetric NAT p2p doesn’t work without TURN. This may happen when user router doesn’t support full-cone (which is not very much secure also) and sometimes ISP is an issue when double-NAT or 1:1 NAT happens (it depends). We also had an issue when a third client joins, “second one” who was already joined gets knocked. In a group of only four we could never reliably “mesh” screensharing. One guy has never became lucky to stream his screen, others are “I can stream and one can watch but the others cannot” etc. We tried a lot but this is not even close to be “user-friendly”.

1 Like

In games when the teamspeak client is not in focus. Only game I have good capture time in is league of legends. Otherwise the stream gets around 8 fps, but as soon as you click on teamspeak you get 60 fps again.

The fans of TeamSpeak… And here I was collecting every single piece of hardware supported since TeamSpeak 3 was popular back in the golden days… :grinning_face_with_smiling_eyes: