Roblox Experience Chat for Console: What the TextChatService Announcement Means

Roblox announced Experience Chat for Xbox and PlayStation on March 10, 2025. The feature brings in-experience text chat to console players, but it is not a universal chat switch: it works only in supported experiences using TextChatService, and current Roblox rules also require age-check and communication eligibility.

That means a console player may chat with people on PC, mobile, web, or VR in the same supported experience, while seeing no chat option in another experience. For creators, TextChatService is now the required foundation for experience communication; migrating an old chat system may also require changes to custom interfaces, admin commands, moderation, logging, and controller support.

#	Preview	Product	Price
1		Retro Game Console with 30 Classic Games, HDMI TV Box with 2 Controllers	$35.99	Buy on Amazon
2		Hori 3D Surround Gaming Neckset - Wearable Speaker with Voice Chat Designed for Xbox Series X|S -...	$80.66	Buy on Amazon

What Roblox announced on March 10, 2025

The original Developer Forum announcement introduced the rollout of Experience Chat on Xbox and PlayStation. Roblox said console users would be able to communicate by text with users on other supported Roblox devices, including mobile, web, desktop, and VR, provided they were playing in the same experience.

The feature was powered by TextChatService. Roblox described a console-oriented interface with a virtual cursor and predictive text input. The rollout was initially staged, with Roblox targeting availability for all console users by the end of March 2025. That was a rollout target, not a guarantee that every experience would expose chat immediately.

#1 Best Overall

Retro Game Console with 30 Classic Games, HDMI TV Box with 2 Controllers

• 30 Preloaded Licensed Classics - Includes 30 officially authorized retro games like Top Racer 2, Power Piggs, and Bang!, delivering safe, legal, nostalgic entertainment straight out of the box.
• Online Multiplayer Support - Built-in WiFi & RJ45 Ethernet allow you to connect and challenge players worldwide via supported online platforms—bringing the arcade battle to your living room.
• Wide Display Compatibility - Connect effortlessly to TVs, projectors, and monitors using the included HDMI port. Ideal for big-screen gaming with family and friends.
• Smooth Performance Guaranteed - Powered by a 1.5GHz quad-core ARM Cortex-A7 CPU with 8GB EMMC storage, ensuring responsive gameplay, fast loading, and stable user experience.
• Simple Plug-and-Play Setup - No installation required—just plug in, power on, and play. Great for casual gamers, retro collectors, or families seeking quick entertainment.

$35.99

Buy on Amazon

The announcement was specifically about text communication inside a live Roblox experience. It did not announce Roblox-wide private messaging, Party chat, or voice chat. Those are separate communication features. Voice chat has since received its own console support for eligible users in supported experiences and regions, but it should not be confused with the 2025 Experience Chat rollout.

What Experience Chat means

Experience Chat is text communication between users who are currently in the same Roblox experience. In normal use, that conversation ends when the player leaves the experience. Roblox’s current Experience Chat support documentation describes filtered chat, mute and block controls, reporting, and directed in-experience conversations such as /w, subject to communication eligibility and privacy settings.

Does Roblox console chat work in every experience?

No. Roblox’s console support pages qualify Experience Chat as available only in supported experiences. For console chat to work, the following conditions generally need to be satisfied:

1. The experience must support the player’s console platform.
2. The experience must use TextChatService or have been migrated to it.
3. The native chat window and input bar must be enabled, unless the creator supplies a compliant custom interface.
4. The player must have completed Roblox’s required age check and be eligible to communicate.
5. Privacy, parental-control, regional, and similar-age communication rules must allow the conversation.
6. The creator must not have disabled or incorrectly replaced the relevant chat interface.

This explains a common situation: chat can work on PC, mobile, or web but be missing on console. The original announcement specifically warned that experiences still using legacy chat would not support console Experience Chat, even if those experiences continued to show chat on other devices.

Creators can intentionally hide parts of the default interface. TextChatService separates the main components into configurations such as ChatWindowConfiguration, ChatInputBarConfiguration, ChannelTabsConfiguration, and BubbleChatConfiguration. An experience can therefore have TextChatService enabled while hiding the chat window or input bar.

How to open Experience Chat on PlayStation

Roblox’s current PlayStation support instructions are:

1. Press Options on the PlayStation controller.
2. Open the in-experience menu.
3. Select Chat.
4. Type with the on-screen keyboard.
5. Press R2 to send.

A USB or Bluetooth keyboard can also be used as an alternative input method. Controller-only typing is slower than using a physical keyboard, so a keyboard can be particularly useful for experiences where players need to communicate frequently.

If the Chat option is absent, do not assume that the console application is broken. The experience may not support or expose Experience Chat, the player may not have completed the required age check, account or regional settings may block communication, or the creator may have disabled the native interface.

How to open Experience Chat on Xbox

Roblox’s current Xbox support page gives these steps:

1. Press Menu on the Xbox controller.
2. Select Chat.
3. Type with the on-screen keyboard.
4. Press R2 to send.

The same support page says that a USB or Bluetooth keyboard can be connected for alternate input.

Why the Chat option may be missing

Use this checklist when chat works elsewhere or does not appear at all.

1. Check the experience

Try a known experience that clearly advertises or displays Experience Chat. A creator can disable the native chat window, input bar, or bubble chat, and an experience may have a broken custom frontend even though other experiences work normally.

2. Check whether the experience uses TextChatService

Legacy chat was the main compatibility gap in the original announcement. An experience using the old chat system could show chat on mobile, desktop, or web while offering no console chat. Roblox later retired the legacy system and began auto-migrating experiences, but older code and custom interfaces can still need testing and repair.

3. Complete the age check

Current Roblox policy requires users to complete an age check to access communication features such as Experience Chat. The global age-check requirement began rolling out on January 7, 2026, first in the United States and selected regions, followed by other regions where chat was available. See Roblox’s age-check rollout announcement and current chat eligibility guidance.

4. Check privacy, parental, and regional restrictions

Age check is necessary but does not override every other rule. Communication can also be limited by privacy settings, parental consent, regional requirements, or whether the people involved are in compatible age groups.

5. Test another input method

If the chat window opens but sending fails, try a USB or Bluetooth keyboard. Also check whether the on-screen keyboard still has focus and whether the current console interface displays a different send control from the written help article.

6. Test with another account or device only for diagnosis

If another eligible account can chat in the same experience, the problem is more likely to be account eligibility or privacy settings than the experience itself. If nobody can chat on console but PC and mobile users can, the creator should inspect migration, UI configuration, and custom gamepad support.

What changed after the 2025 announcement?

The original rollout and the later migration

The March announcement said that legacy chat was not supported on console and that creators using TextChatService could enable console communication. It also announced April 30, 2025 as the retirement or deprecation deadline for legacy chat.

That date should not be interpreted as meaning that every old place file instantly changed at midnight. Roblox later explained that it would auto-migrate experiences in batches, and on May 13, 2025 it said batch auto-migration had begun. Creators with custom chat features were strongly encouraged to migrate manually instead of waiting for an automatic change. Roblox’s legacy-chat migration update contains the timeline and follow-up details.

Roblox also stated that a migrated experience could run TextChatService at runtime even if legacy chat code remained in the place file. That distinction matters: what an older Studio file appears to contain is not always the complete picture of what the published experience uses at runtime.

The current status

As of August 10, 2026, Roblox’s Creator Hub marks the legacy Chat service as deprecated and directs creators toward TextChatService. Console chat is documented for Xbox and PlayStation in supported experiences, but account-level communication rules remain just as important as the experience’s implementation.

How creators migrate an experience

For a manual Studio migration, Roblox’s current Creator Hub instructions give this path:

1. Open the experience in Roblox Studio.
2. In Explorer, select TextChatService.
3. In Properties, find ChatVersion.
4. Select TextChatService.

That dropdown is only the starting point for a serious migration. The legacy Chat service is deprecated, and automatic migration may alter runtime behavior independently of what older scripts or place files suggest. Publish a test version and verify it on both Xbox and PlayStation before treating the work as complete.

Check the default TextChatService interface

If the experience is intended to use Roblox’s native chat UI, inspect the relevant configuration objects:

• ChatWindowConfiguration.Enabled controls the main chat window.
• ChatInputBarConfiguration.Enabled controls the text input bar.
• ChannelTabsConfiguration affects channel-tab presentation where applicable.
• BubbleChatConfiguration.Enabled controls whether bubble chat is enabled.

A missing console chat window can be caused by a deliberate configuration choice rather than a failed platform rollout. If the creator disables the default input bar, the replacement must provide a usable and compliant way to send messages on console.

Check a custom frontend

Roblox supports custom chat frontends. Its custom frontend example demonstrates disabling the default window and input bar, then sending messages through TextChatService.

Rank #2

Hori 3D Surround Gaming Neckset - Wearable Speaker with Voice Chat Designed for Xbox Series X|S - Xbox Series X

• Equipped with immersive virtual 3D Surround sound and two gaming sound modes
• Wearable neckset audio and voice chat solution
• Connects directly to Xbox Controller with included audio cable
• Compatible with Xbox series x|s, Xbox One, & Windows 10
• Officially Licensed by Microsoft

$80.66

Buy on Amazon

That sample should not be treated as automatically console-optimized. A custom interface must be tested with a gamepad, virtual cursor, on-screen keyboard, focus changes, cancel behavior, and the player’s ability to leave the chat UI without becoming trapped in it. A UI that works with a mouse and keyboard can fail on console if its text field cannot receive console text input or its controls have no usable gamepad navigation.

What TextChatService actually changes

TextChatService is more than a replacement chat box or a console compatibility switch. Roblox documents it as the system responsible for text-channel management, message filtering, moderation and permissions, default chat UI, custom channels, chat commands, delivery decisions, message-display callbacks, and bubble-chat customization.

The main objects and APIs include:

• TextChannel for a channel in which messages are sent and delivered.
• TextSource for a user’s source within a channel.
• TextChatMessage for a chat message and its associated properties.
• TextChatCommand for commands such as /super or /mini.
• TextChannel:SendAsync() for sending a message through a TextChannel.
• TextChannel:DisplaySystemMessage() for displaying a system message through a channel.
• TextChannel.ShouldDeliverCallback for server-side delivery decisions.
• TextChatService.OnIncomingMessage, OnChatWindowAdded, and OnBubbleAdded for client-side display customization.
• TextChatService.MessageReceived for client-side message-received behavior.
• TextChatService:CanUserChatAsync(), CanUsersChatAsync(), and CanUsersDirectChatAsync() for communication eligibility checks.

See the TextChatService API reference for the current API surface and permissions-related methods.

The server/client boundary matters

A client sends through TextChannel:SendAsync(). The chat system then applies the relevant filtering and the server evaluates whether the message should be delivered. TextChannel.ShouldDeliverCallback is server-side and controls delivery decisions.

By contrast, display callbacks such as OnIncomingMessage, OnChatWindowAdded, and OnBubbleAdded are client-side. They are appropriate for changing how an already-processed message is presented, not for treating the client as an authoritative moderation system.

This difference can affect legacy admin commands, chat logs, and moderation tools. Developers in the announcement discussion reported difficulty with the lack of a general server-side event that simply receives every raw chat message. That is a community report rather than a guarantee that every experience will encounter the same issue, but it highlights why a complex legacy chat system should be audited rather than migrated by changing one property.

Roblox has since documented specific read-only moderation capabilities for eligible creators, but creators should not promise themselves unrestricted server-side access to every raw message. Use the supported APIs and current moderation documentation instead.

Mapping common legacy features to TextChatService

For commands, Roblox’s custom TextChatService command documentation uses TextChatCommand and its Triggered event. For system notices, use the documented TextChannel system-message path rather than reproducing legacy chat’s behavior with an unrelated remote.

Current age-check and safety rules

The 2025 announcement focused on the rollout, filtering, and reporting. Current access rules are more restrictive than that original announcement alone suggests.

Roblox’s current support guidance says:

• Users must complete an age check to access communication features such as Experience Chat.
• Communication is generally limited to users in similar age groups.
• Users ages 5 through 9 require parental consent to enable Experience Chat.
• Users under 16 require parental consent for Direct chat.
• Additional regional restrictions may apply.

Roblox later expanded in-experience text and voice communication for eligible age-checked users who are designated Trusted Connections or Trusted Friends. This can allow some communication across ordinary age-group boundaries, but it is a Roblox platform-level exception, not a creator-controlled way to bypass safety settings. The Trusted Connections/Friends announcement describes that change.

Consequently, enabling TextChatService does not guarantee that every player in the server can send messages to every other player. A correctly migrated experience can still show no usable chat for an account that has not completed age check or is restricted by privacy, parental, regional, or age-group rules.

Filtering, reporting, muting, and blocking

Experience Chat is filtered to help prevent inappropriate content and personally identifiable information from being displayed. Players can mute or block other users and report messages or use Report Abuse from the Roblox menu. A filtered, hidden, or undelivered message is therefore not automatically evidence of a console defect.

For developers, Roblox’s in-game chat guidelines require user-to-user in-game text chat to use TextChatService. User-generated text displayed to other users must be filtered, direct-chat channels must respect privacy settings, and in-game communication must remain reportable. A custom communication system must not bypass Roblox’s safety or age-based controls.

Preset communication systems are not an unrestricted workaround

A creator may use a preset-message or communication-wheel system to help players coordinate without typing. That can improve accessibility and console usability, but it cannot be used to simulate unrestricted conversation or evade Roblox’s age-based communication requirements.

Roblox’s preset system guidelines should be checked before shipping such a feature. In particular, do not use a custom RemoteEvent to transmit arbitrary player-to-player text around TextChatService. Custom frontends are supported, but the underlying communication must still use the supported TextChannel/TextChatService flow and obey filtering, privacy, reporting, and age restrictions.

Console-specific design and QA checklist

Console support should be treated as a user-interface project as well as an API migration. Controller-based text entry is slower, chat can cover gameplay, and a desktop-first custom interface may not be navigable with a gamepad.

Test both console families

• Run a published test build on Xbox.
• Run a published test build on PlayStation.
• Test with controller only.
• Test with the on-screen keyboard.
• Test with USB and Bluetooth keyboards if the experience expects frequent chat.
• Test players on PC and mobile in the same server to verify cross-device communication.

Test the complete input path

• Can the player open Chat from the console menu?
• Does the virtual cursor reach the chat window and input bar?
• Does the on-screen keyboard open reliably?
• Does the input field retain focus while typing?
• Does the current on-screen prompt send the message?
• Can the player cancel, close, or minimize chat without losing gameplay control?
• Can the player navigate out of the chat interface with a controller?

Test how chat interacts with the game

• Does the window cover important HUD elements?
• Does it fit inside television safe areas and account for overscan?
• Does large-font or accessibility scaling obscure controls?
• Can players still reach custom menus while the chat field is focused?
• Are bubble chat and the main chat window visually distinguishable?
• Do channel tabs, custom commands, and system messages remain usable without a mouse?

Test permissions and safety branches

• An age-checked player who is eligible to communicate.
• A player who has not completed age check.
• Players in different age groups.
• Direct chat with privacy restrictions.
• Messages that are filtered or rejected.
• Muted and blocked users.
• Report Abuse and message-reporting flows.
• Region-specific communication restrictions where applicable.

What creators gain—and what migration can break

Benefits of TextChatService

• Console support for Xbox and PlayStation.
• Roblox-maintained filtering and privacy integration.
• Default UI components that can be configured independently.
• Custom channels and chat commands.
• Server-side delivery decisions through supported callbacks.
• Eligibility APIs for chat and direct chat.
• A foundation for newer features such as cross-server chat and age-aware communication.
• Platform-level improvements to moderation and communication behavior.

Costs and risks

• Legacy chat modules and assumptions may no longer work.
• Custom admin commands may need to move to TextChatCommand.
• Custom logs and moderation tools may not have the same server-side hooks as before.
• Custom tabs and chat frontends may need to be rebuilt.
• A custom input field may not accept console keyboard input.
• Gamepad focus, safe-area layout, and chat obstruction require separate QA.
• Some players may be unable to communicate even after a technically correct migration because of current platform eligibility rules.

Performance context

Roblox reported post-launch Experience Chat performance work in July 2025. In its own production measurements, Roblox said measured P95 React frame time fell between March and July 2025 by 22% on console, 72% on Windows, 68% on macOS, 69% on Android, and 56% on iOS. These are Roblox’s reported measurements and experiments, not independent benchmarks or a guarantee that every experience received the same improvement. The figures are documented in Roblox’s Experience Chat performance update.

Timeline: from console launch to current rules

Player troubleshooting decision tree

The Chat option is missing entirely

1. Try another known supported experience.
2. Confirm that the account has completed age check.
3. Review communication, privacy, and parental-control settings.
4. Consider regional restrictions and similar-age requirements.
5. Ask the creator whether the experience uses TextChatService and whether its native chat UI is enabled.
6. If chat works on PC but not console, report the platform-specific failure to the experience creator.

The chat window appears but messages will not send

1. Check whether the account and intended recipient are allowed to communicate.
2. Try a simple message that does not contain potentially restricted content or personal information.
3. Confirm that the on-screen keyboard still has focus.
4. Use a USB or Bluetooth keyboard if available.
5. Follow the current on-screen send prompt rather than relying on conflicting third-party button guides.
6. Test whether the problem occurs for multiple eligible players in the same experience.

Chat works on PC but not on Xbox or PlayStation

The most likely explanations are legacy or incomplete migration, an incorrectly configured native UI, a custom frontend without gamepad support, or different communication restrictions on the console account. The original announcement explicitly identified the legacy-chat mismatch as a reason chat could work on mobile, desktop, and web while remaining unavailable on console.

Do not confuse the announcement with newer features

The title of the March 10, 2025 forum post is now historical. It remains the source for the original console rollout, but it is not a complete description of Roblox communication in 2026.

• Console Experience Chat means in-experience text chat on Xbox and PlayStation.
• Voice Chat is a separate feature with separate eligibility and region requirements.
• Party or cross-experience chat is separate from messages handled by an experience’s TextChatService.
• Cross-server chat is a later feature that connects servers within a universe and should not be presented as part of the original console launch.
• Direct chat is still in-experience communication and remains subject to privacy, age, and platform restrictions.

Roblox’s current Xbox and PlayStation support pages are the best references for player-facing console behavior, while the Creator Hub’s TextChatService documentation and chat guidelines are the relevant references for developers.

Frequently Asked Questions

Can every Xbox or PlayStation player use Roblox Experience Chat?

No. The player must be in a supported experience, the experience must expose TextChatService chat, and the account must satisfy Roblox’s current age-check, privacy, parental, regional, and age-group communication rules.

Why can I chat on PC but not on console?

The experience may still use legacy chat, its native console chat UI may be disabled, or its custom frontend may not support gamepad input. Your console account may also have different communication restrictions.

Is Roblox console Experience Chat the same as voice chat?

No. Experience Chat is text communication inside an experience. Voice Chat is a separate Roblox feature with its own eligibility, region, and experience requirements.

Can a developer create a custom console chat box?

Yes, but the custom frontend must use the supported TextChatService and TextChannel flow. It must also preserve filtering, privacy, age-based controls, reporting, and usable controller navigation. Sending unrestricted user text through a custom RemoteEvent is not a compliant replacement.

Can Roblox creators automatically receive every chat message on the server?

Creators should not assume they receive an unrestricted raw-message stream. TextChatService separates server-side delivery decisions from client-side display callbacks. Custom logging, moderation, and admin systems should be designed around the supported APIs and current Roblox documentation.

The Bottom Line

The March 10, 2025 announcement made Xbox and PlayStation console text chat possible through TextChatService; it did not make chat universal across Roblox. Players need a supported, correctly configured experience and an account that passes current communication rules. Creators should treat TextChatService as the required chat architecture, then test native or custom UI separately on Xbox and PlayStation—including controller focus, keyboard input, filtering, reporting, and age-based restrictions.

Quick Recap

Bestseller No. 1

Retro Game Console with 30 Classic Games, HDMI TV Box with 2 Controllers

$35.99

Bestseller No. 2

Hori 3D Surround Gaming Neckset - Wearable Speaker with Voice Chat Designed for Xbox Series X|S - Xbox Series X

Equipped with immersive virtual 3D Surround sound and two gaming sound modes; Wearable neckset audio and voice chat solution

$80.66

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.