Think of Universal Profile as the contract that keeps RCS from fragmenting: it specifies the feature set and technical enablers every compliant implementation must support. Newer versions add capabilities (E2EE in 3.0) and refinements (4.0), though carrier and device rollout of each version takes time.
The version history matters more than it looks, because a feature is only usable when the spec, the backend, the carrier and the handset have all caught up.
| Version | Released | What it added |
|---|---|---|
| UP 1.0 | 2016 | The first common baseline: chat, group chat, file transfer, read receipts |
| UP 2.0 to 2.3 | 2017 to 2019 | Rich cards, carousels, suggested replies and actions, the foundation of RCS Business Messaging |
| UP 2.4 | 2019 | Refinements to business messaging and verified sender handling |
| UP 3.0 | March 2025 | End-to-end encryption for person-to-person chat via Messaging Layer Security |
| UP 4.0 | March 2026 | Further interoperability and business messaging refinements |
The gap between finalized and available is the part that catches teams out. Universal Profile 3.0 was published in March 2025, but default end-to-end encryption for cross-platform chats only began rolling out with iOS 26.5 in May 2026, more than a year later. Planning a campaign around a newly ratified capability is therefore a mistake: the safe assumption is that a spec version becomes reliably available a year or more after it is finalized, and that a capability check, not the spec sheet, tells you what a given recipient can actually receive.
It is also worth being precise about what the encryption in 3.0 covers. It applies to person-to-person conversations. Business messaging is transport-secured and processed by the sending platform, exactly as a marketing email is, because your platform has to be able to render, log and report on the message. Is RCS encrypted? sets out that distinction in full, and it is the single most commonly misread point about the standard.
How RCS works technically shows the profile in use, who owns RCS places the GSMA among Google, Apple and the carriers, and does Apple support RCS covers the iPhone implementation.
- Universal Profile = GSMA spec ensuring RCS interoperability across carriers/devices.
- UP 3.0 (March 2025) introduced end-to-end encryption via Messaging Layer Security (MLS).
- UP 4.0 finalized March 2026; carrier/device support of new versions rolls out gradually.
- Business messaging features arrived in the 2.x line; encryption arrived in 3.0 and applies to person-to-person chat.
- Expect a year or more between a Universal Profile version being finalized and being widely usable.
- Target features by capability check, never by assuming a recipient is on the newest profile version.