iMessage vs. SMS: Why "No Character Limit" Isn't Quite the Whole Story

"SMS is limited to 160 characters, but iMessage has no limit" is close to true, and also skips over the more interesting part of the story. SMS's number is precise, standardized by a technical body, and explainable down to the byte. iMessage's number doesn't exist in any Apple documentation at all — not because Apple forgot to publish it, but because the protocol was built without the same hard technical ceiling SMS has always had.

Curious which encoding your own message would trigger? Clear Count shows character and byte counts instantly.

SMS's Numbers Are Precise Because the Technology Forces Them to Be

SMS was standardized in the late 1980s within a 140-byte payload per message. Using GSM-7, a 7-bit character encoding covering basic Latin text, that works out to exactly 160 characters. The moment a single character falls outside GSM-7's limited set — an emoji, an accented letter, most non-Latin scripts — the entire message switches to UCS-2, a 16-bit encoding, cutting the same 140-byte payload down to 70 characters. This isn't a rounding error or a marketing simplification; it's a direct consequence of how many bits each encoding needs per character, covered in more detail in the earlier SMS character limit post.

Why the Number Drops Again for Longer Messages

A message that exceeds a single segment doesn't just get a bigger overall limit — each subsequent segment loses a few more characters to a User Data Header, the metadata that tells the receiving phone how to reassemble multiple segments back into one message. That knocks GSM-7 segments down to 153 characters each beyond the first, and UCS-2 segments down to 67. A long text message is being silently split, numbered, and billed as multiple separate messages by the carrier — mechanics that are fully documented in the GSM standard, down to the exact byte.

iMessage Has No Official Limit — Not Even From Apple

This is where the comparison becomes genuinely different rather than just a bigger number. Apple has never published an official character limit for iMessage text. Users on Apple's own community support forums describe the situation as "nebulous," and the most commonly cited empirical data point — some users reporting errors when approaching roughly 20,000 characters — comes from real-world testing, not from any Apple specification. There's no equivalent of the GSM-7 versus UCS-2 math here, because iMessage doesn't work the way SMS does: it's an internet-based, Apple-proprietary protocol, not a text payload squeezed into a fixed-size cellular data packet.

"No official limit" and "no limit" are different claims. SMS's 160 characters is a hard technical ceiling anyone can derive from the encoding math. iMessage's lack of a published number just means nobody outside Apple has a confirmed, documented answer — which is a gap in public information, not proof the ceiling doesn't exist somewhere in Apple's own infrastructure.

The Apple-Documented Number That Gets Confused With It

Apple has published one specific, exact number adjacent to this topic, and it's worth being careful not to conflate the two: the MSMessage URL property, used by iMessage app extensions to attach structured data to a message, is documented at a hard 5,000-character maximum. That's a real, confirmed Apple limit — added to the developer documentation after a bug report asked for exactly this to be clarified — but it governs a metadata field inside an iMessage app extension, not the plain text a person types into the Messages app. Seeing "5,000" attached to iMessage in some contexts and assuming it's the message-text limit is an easy, understandable mistake.

What Happens When iMessage Falls Back to SMS

None of iMessage's generous, undocumented ceiling survives contact with a non-Apple recipient. When the person on the other end doesn't have iMessage active — an Android phone, or an iPhone with no data connection — the message reverts to standard SMS, and the same 160/70-character encoding rules apply exactly as they would for any other text message. A long iMessage composed with no length concerns can silently split into several billed SMS segments the moment it's sent to the "wrong" kind of phone, with no confirmation dialog warning that the fallback happened.

RCS Doesn't Have One Consistent Number Either

RCS, the modern successor protocol Google has pushed as SMS's replacement and that Apple adopted starting with iOS 18, is frequently described as having "no character limit" in marketing material — but published technical figures for it vary more than the marketing suggests. Different sources describing RCS's actual ceiling cite figures from roughly 1,000 characters up to 3,072 characters, without a single authoritative number appearing consistently across them. Unlike SMS, where the 160/70 figures trace back to one widely cited encoding standard, RCS's exact text ceiling doesn't have an equally prominent, single source everyone points to — making it the second major messaging protocol in this comparison, alongside iMessage, where "the limit" is genuinely harder to pin down than SMS's textbook-precise numbers.

What This Means in Practice

For anyone actually composing a message, the practical guidance is simpler than the technical picture suggests: SMS's numbers are worth knowing precisely, since a single emoji genuinely does cut capacity by more than half and can turn one message into several billed segments. iMessage and RCS, by contrast, are both generous enough in practice that hitting either one's real ceiling in ordinary conversation is unlikely — the more relevant risk with either is the silent SMS fallback, not an actual length limit. Signal takes a related but distinct approach worth comparing, covered in the earlier post on the Signal character limit — another messaging platform that, like iMessage, has never published an official number at all.

---

The honest summary: SMS's character limits are some of the most precisely documented in any messaging technology, derived directly from encoding math that hasn't changed since the standard was written. iMessage has no equivalent — Apple has never published a text character limit, only an unrelated 5,000-character cap on a different, structured data field inside app extensions. RCS sits in between, marketed as limitless but reported with wildly different actual figures depending on the source. "No character limit" turns out to mean three different things depending on which of these three protocols is actually carrying the message.