[Update] October 28, 2026
[Update] October 22, 2026
Hi Creators,
Today we’re sharing reminders that chat between users must go through TextChatService (TCS) and introducing a foundational update that makes text chat more native to Roblox, like how voice chat already works.
Phase 0 [Now]:
- Ensure you’re using TextChatService (TCS) for any chat between users.
As a reminder; enabling chat outside of TCS is against Roblox’s Chat System Guidelines. If you have features built for chat, they must use TCS so that users have the right safety guardrails built in.
What to look for: If players can hold a real-time conversation in your game outside TextChatService, they will find it. Common culprits are Signs, Bulletin Boards, Pet names, License plates, Trading systems, Announcement systems, Admin Tools, Comment Systems, and other free-text inputs. Some admin modules include messaging features that may bypass chat rules. Such features must be changed, removed, or rate limited to 1 update per minute.
How to fix it:
- Route all communication between users through a
TextChannel. This applies filtering and user settings automatically. - If you have UGC text inputs that aren’t chat, such as signs or bulletin boards, add a rate limit of at least 1 minute between submissions so they can’t be used for conversation.
- Turn off or restrict admin-module commands that let players message each other. Alternatively update to the latest versions, which should be compliant.
If your game isn’t compliant, expect to hear from us in the upcoming weeks. If you get a notice, please act on it right away. Continued violations may result in suspension or removal of your game from Roblox.
Phase 1 [Now - Feb 2027]:
- You can start testing the new updates to TextChatService (TCS) and give us feedback on any gaps. We’ll be adding several new features to provide customizations so chat can still feel unique to your game. The full list of features is below and we’ll consider additions based on your feedback.
Phase 2 [Feb 2027]:
- All new and existing games will be opted in automatically, with an option to opt out. We will share further details and opt-out instructions as this date approaches.
Phase 3 [May 2027]:
- The updated TextChatService will be the only way to have custom chat in new and existing games.
5 Key Changes for Creators
Here are some common custom implementations and workflows you will need to migrate by May 2027, and what to use instead. More information is in the Unsupported APIs section of this post.
- Custom chat UIs: migrate to
TextChannelWindow, a native window interface with customizations. - Custom moderation: migrate to read-only moderation.
- Custom commands: migrate to
TextChannelCommands. - Custom presets: migrate to Customizable Quick Words, our recently launched native preset system. Upload game-relevant phrases in Creator Hub and publish them to players.
- Custom prefixes: new native solution is coming soon in early 2027.
Why We’re Making This Change
We want every creator to have a customizable chat system, while keeping player’s privacy protected and providing safety tools like reporting and muting. With the updated TextChatService, you get the newest chat features in your game automatically, and they work consistently and safely for players of all ages across all chat windows.
Features We’re Building
For the rest of the year, we’re investing in new features to bring the TextChannelWindow to parity with the custom in-game chat UIs we’ve seen, like phone apps and social-style in-game chat experiences.
Our current roadmap includes:
Phase 1
| Timing | Feature | Description | What component? |
|---|---|---|---|
| Launched today | Enables creators to filter TextChannel messages from the default window. |
Use ChatWindowConfiguration.TextChannelDisplayMode to filter out custom TextChannels from the default window. |
Default Window |
| Launched today | TextChannelWindow |
Enables creators to render TextChannel conversations within a standalone window. |
TextChannelWindow |
| November | Emojis | Lets players send emojis into chat with one click. | Coming soon to the Default Window and eventually the TextChannelWindow |
| November | Voice Typing | Lets players use Voice Typing in the TextChannelWindow input bar. |
Already in the Default Window. Coming soon to the TextChannelWindow |
| November | Translations and AI-Rephrases | Lets players see translations and AI-Rephrases in the TextChannelWindow. |
Already in the Default Window. Coming soon to the TextChannelWindow |
| Later this year | Avatars | Enables creators to turn on avatars in chat. | TextChannelWindow and eventually the Default Window |
| Later this year | Display Name Color | Enables creators to update the display name color of players in chat. | Coming soon to the Default Window and TextChannelWindow |
| Later this year | Bubbles | Enables creators to turn on bubbles for chat messages. | Coming soon to the TextChannelWindow |
| Later this year | Quick Words | Lets players use Quick Words in the TextChannelWindow. |
Already in the Default Window. Coming soon to the TextChannelWindow |
| Early Feb 2027 | Native solution for prefixes | Enables creators to attach approved roles to players at runtime that render consistently alongside display names in chat. | TextChannelWindow and the Default Window |
Phase 2
| Timing | Feature | Description | What component? |
|---|---|---|---|
| 2027 | Quick Action Menu | Lets players tap a player’s avatar thumbnail or display name in chat to open a quick-action menu, where they can view profiles, report, block, and eventually teleport. | TextChannelWindow and the Default Window |
| 2027 | Typing Indicators | Lets players see who is typing in chat before messages are sent. | TextChannelWindow and the Default Window |
These are examples of the customization we’ll be offering for TextChannelWindow, like bubbles, prefixes, and avatars.
What This Changes For Your Game
Roblox now controls how every chat message is delivered and rendered, so message text is no longer accessible to your code. If you’ve built a custom in-game chat experience, you can still place chat inside your UI with a TextChannelWindow, choose which TextChannel a window displays, and control the window’s size, color, and position.
Channel membership, sender identity, delivery status, timestamps, and message IDs work the same.
API Changes
If you set [TextChatService.PlatformIntegratedChat](https://create.roblox.com/docs/chat/platform-integrated-chat) to Enabled today, these APIs will return ””(empty string, not nil) so that your scripts won’t crash. They’ll get an empty value back and a warning in the output. Opting in will turn on the TextChatService update for that game. You can opt out of the update at any time and continue to use your previous build.
Unsupported APIs
| Feature | Unsupported APIs | What you can do instead |
|---|---|---|
| Chat messages and display | TextChatMessage.Text, .Translation |
Migrate custom chat GUI to TextChannelWindow in your game. Target a TextChannel to it. Users can send and receive messages automatically. All chats must go through TextChatService and any UGC text surface can only be edited once per minute. |
| Chat prefixes | TextChatMessage.PrefixText |
Roblox will provide official support for attaching and rendering prefixes within chat via the upcoming user prefix service. |
| Presets / Chat Wheels | TextChannel:SendAsync |
Use Quick Words for all creator-based presets. Custom presets can no longer render in chat, and the preset policy will update by February 2027 to reflect this. |
| Moderation / Admin commands | OnIncomingMessage and Player.Chatted |
Use TextChatCommands to trigger actions based on commands in chat. For moderation flows we recommend using read-only chat permission so members with appropriate permissions can view all in-game messages and take action. |
New APIs
| New APIs | What it is | What you can do |
|---|---|---|
TextChatService.PlatformIntegratedChat |
Opt-in control (default / enabled / disabled) for the TCS update. | Set to Enabled in Studio to begin testing. Can be set to Disabled to opt out anytime before March 2027. |
TextChannelWindow |
A chat window you can place anywhere in your game. | Add a custom chat window to your game and resize or reposition it as needed. Roblox handles message delivery, message filtering/rendering plus automatically complies with user settings. Note: Channels targeted to the TextChatWindow will automatically render as a new tab in the default chat window. An update expected to land in October to change this functionality. |
TextChannelWindow.Target |
Controls which chat channel appears in your custom window. | Point each window at a specific TextChannel. |
ChatWindowConfiguration.TextChannelDisplayMode |
Property that controls which TextChannels the default chat window renders. Values are AllTextChannels (default) and DefaultTextChannels. Scripts can read it but not change it. | Set to DefaultTextChannels in Studio so custom channels appear only in their own TextChannelWindow and not also in the default window. |
TextChannel.AddPlayersOnJoin |
Boolean property on TextChannel. When true, every player who joins the experience is automatically added as a member of that channel, so no manual join-time handling is required. | Set to true on a custom TextChannel (for example, one you create at runtime for a guild or team) so new players are added automatically. Without it, a TextChannelWindow targeting that channel won’t receive messages for players who haven’t been explicitly added. |
Give Us Your Feedback
We want to make this transition as smooth as possible. Before migrating, please test the update in a test place and share feedback on what breaks, what is missing, and how we can better support the chat patterns you depend on today. We will be actively updating our roadmap and sharing back updates with you here.
Thank you,
Roblox Team

