RCS (Rich Communication Services) is a messaging protocol that replaces SMS and MMS. It runs over your data connection instead of legacy cellular signaling, which means richer messages: high-resolution images, video, read receipts, typing indicators, interactive buttons, and branded business conversations. This happens in the phone's built-in messaging app, with no extra download required.
If a recipient's device or carrier doesn't support RCS, the message falls back to SMS or MMS automatically.
How RCS differs from SMS and MMS
| SMS | MMS | RCS | |
|---|---|---|---|
| Character limit | 160 per segment | 1,600 (varies) | Up to 8,000+ (carrier-dependent) |
| Media | None | Images/video up to ~300 KB | High-res images, video, files |
| Read receipts | No | No | Yes |
| Typing indicators | No | No | Yes |
| Interactive elements | None | None | Suggested replies, buttons, cards, carousels |
| Branding | Shortcode only | Shortcode only | Sender name, logo, colors, verification badge |
| Connection | Cellular signal | Cellular signal | Data or Wi-Fi (falls back to SMS if unavailable) |
| Encryption | None | None | E2EE rolling out (Universal Profile 3.0) |
A brief history
- 2008: The GSMA publishes the first RCS specification.
- 2016: The GSMA releases the Universal Profile, a single standard so RCS works the same across carriers and devices.
- 2019-2023: Google drives adoption by building RCS into Google Messages and running the Jibe cloud platform for carriers.
- September 2024: Apple adds RCS to iOS 18, bringing cross-platform RCS to iPhone for the first time.
- March 2025: Universal Profile 3.0 adds end-to-end encryption using the MLS (Messaging Layer Security) protocol.
- May 2026: Cross-platform E2EE between iPhone and Android begins rolling out in beta with iOS 26.5 and the latest Google Messages.
Key features
For consumers
- Read receipts and typing indicators. You see when someone has read your message and when they're typing back.
- High-resolution media. Share photos and videos without the compression and size limits of MMS.
- Group chat management. Name groups, add or remove members, and leave conversations.
- End-to-end encryption. E2EE is rolling out across carriers using the MLS protocol. A lock icon appears in encrypted conversations.
For businesses (RCS Business Messaging)
- Branded sender identity. Your company name, logo, brand colors, and a verification badge appear in the recipient's messaging app.
- Rich cards and carousels. Showcase products, services, or options with images, descriptions, and action buttons.
- Suggested actions. Tap-to-call, open a map, visit a URL, or add a calendar event, all without leaving the conversation.
- Suggested replies. One-tap response buttons that guide the conversation.
- Conversational. Recipients reply in the same thread. Responses can route to automated flows or human agents.
- No app install. Unlike WhatsApp or other OTT apps, RCS works in the native messaging app already on the phone.
Device and carrier support
Android
Google Messages supports RCS on virtually all modern Android devices. Most major carriers worldwide have deployed RCS Universal Profile support.
iPhone
Apple added RCS in iOS 18 (September 2024). RCS works on iPhone XS and newer with a carrier that supports RCS on iPhone. The major US carriers (Verizon, AT&T, T-Mobile) all support it.
Global reach
Over 80 carriers worldwide have deployed RCS, and device coverage has reached approximately 96%. Smaller MVNOs and prepaid carriers sometimes lag behind major networks.
How it works (simplified)
- Your phone connects to the carrier's RCS platform over data (cellular or Wi-Fi).
- The platform checks whether the recipient supports RCS.
- If yes, the message delivers as RCS with all the rich features.
- If no (the recipient's device or carrier doesn't support RCS, or there's no data connection), the message automatically falls back to SMS or MMS.
The protocol handles this fallback automatically. Senders don't need to do anything extra.
RCS Universal Profile
The Universal Profile is the GSMA's industry standard that defines which features RCS supports and how they work across carriers and devices. It's what makes RCS interoperable: a message composed on one carrier's network delivers correctly on another.
Version 3.0 (released March 2025) added end-to-end encryption via the MLS protocol, which is the same encryption framework that other major messaging platforms use.
How RCS compares to other messaging platforms
| RCS | iMessage | ||
|---|---|---|---|
| Platform | Android + iPhone | Apple only | Cross-platform |
| App required | No (native messaging app) | No (built into iPhone) | Yes (separate download) |
| E2EE | Rolling out (Universal Profile 3.0) | Yes (default) | Yes (default) |
| Business messaging | Branded agents, rich cards, carousels | Apple Business Chat | WhatsApp Business API |
| Global users | 96% device reach | ~1.8B Apple devices | 2B+ users |
| US strength | Growing, cross-platform | Dominant on iPhone | Secondary to native apps |
| Requires data | Yes (falls back to SMS) | Yes (falls back to SMS) | Yes (no fallback) |
RCS fills a unique gap: it's the only rich messaging protocol that works cross-platform in the native messaging app without requiring a download. For businesses, that means reaching subscribers on both Android and iPhone through a single channel.
Current limitations
- Data connection required. No Wi-Fi or cellular data means the message falls back to SMS.
- E2EE is still rolling out. Cross-platform encryption is in beta and depends on carrier support. Business (A2P) messages don't yet support E2EE.
- Carrier dependency. Some smaller carriers and MVNOs haven't fully deployed RCS, especially for iPhone.
- Green bubbles remain. On iPhone, RCS conversations still appear as green bubbles, not blue (Apple reserves blue for iMessage).
- Feature gaps across platforms. Some features (like message editing and unsend) don't yet work consistently between iPhone and Android.