SMS Segments Explained: GSM-7, UCS-2 and Limits

Updated

Short answer: A segment is the unit a text message is sent and billed in. A message written only in the GSM-7 alphabet fits 160 characters in one segment, and a longer one splits into parts of 153. One character outside GSM-7 switches the whole message to UCS-2, where the limits drop to 70 and 67.

What a segment is

Twilio explains that "SMS splits messages longer than 160 characters into parts called segments". The recipient's phone joins the parts back together, so they usually see one message. You pay for every part.

Segments are the unit the whole industry counts in. Twilio says that "Message segments are how Twilio (and the SMS industry as a whole) counts messages" and that it "bills SMS per message segment sent." Sending speed is measured the same way: throughput is counted "in terms of Message Segments per Second rather than total messages."

Why the limits are 160, 153, 70 and 67

An SMS carries 140 bytes at a time. How many characters fit depends on the encoding:

  • GSM-7 uses 7 bits per character. The 3GPP standard that defines the alphabet does the sum: "in 140 octets, it is possible to pack (140x8)/7=160 characters."
  • UCS-2 uses two bytes per character, so the same 140 bytes hold 70 characters. Twilio puts it as "140 bytes divided by two-bytes per character."
  • Split messages need room for a header. Twilio "prepends a User Data Header of 6 Bytes (this instructs the receiving device on how to assemble messages), leaving 153 GSM-7 characters or 67 UCS-2 characters for your message."
EncodingOne segmentEach part of a longer messageTwo segments holdThree segments hold
GSM-7160 characters153 characters306 characters459 characters
UCS-270 characters67 characters134 characters201 characters

Every phone and network has to support GSM-7. The standard says "Implementation of the GSM 7 bit default alphabet is mandatory. Support of other character sets is optional."

What switches a message to UCS-2

The encoding applies to the whole message, not to one character. Twilio: "If your message includes a UCS-2 character like an emoji or a Chinese hanzi, SMS switches to the UCS-2 encoding."

A less obvious cause is punctuation your writing app inserted for you. Twilio warns that text editors "might automatically add angled smart quotes, non-standard spaces, or punctuation which looks similar to GSM-7 but is a different Unicode character." Characters That Turn a Text Into Unicode lists the ones to look for.

A few symbols, such as { and ], are part of GSM-7 but need an escape character. Twilio notes that these "count as two characters in a GSM-7-encoded message."

Worked examples

MessageEncodingCharactersSegments
Plain textGSM-71601
Plain textGSM-71612 (153 + 8)
Plain textGSM-73062
Plain textGSM-73073
Text with one curly apostropheUCS-2701
Text with one curly apostropheUCS-2712
Text with one curly apostropheUCS-21353
152 GSM-7 characters plus one Unicode characterUCS-21533

The 161-character row is Twilio's own example: "one with 153 characters and a second with eight characters." The last row is too: Twilio says such a message "will be split into 3 messages when encoded in UCS-2."

Now take this 142-character appointment reminder:

Hi Maria, it’s Dan from Acme Roofing. Your free inspection is booked for Tue 3pm. Reply YES to confirm or call 555-0100. Reply STOP to opt out

With a straight apostrophe (') in "it's", the message is GSM-7 and fits in 1 segment. With the curly apostrophe shown above (’), it becomes UCS-2, and 142 characters at 67 per part make 3 segments. One character triples the cost of every send. How SMS Is Billed works through what that means for a campaign.

Exceptions to the standard limits

  • US and Canadian toll-free numbers on Twilio. "As an exception, toll-free multi-segment SMS messages sent to the US or Canada support 152 characters per segment for GSM-7 messages and 66 for UCS-2 messages." A 305-character GSM-7 text is 2 segments at 153 per part but 3 at 152.
  • US Cellular. Twilio says US Cellular does not support concatenated SMS and "limits the length of a single message to 150 characters in GSM encoding, instead of 160." Longer messages carry labels such as "1/3" and "2/3" and are "limited to 142 characters for GSM-encoded messages and 64 characters for Unicode-encoded messages."
  • Very long texts. Twilio accepts up to 1,600 characters per message, but it recommends "keeping SMS messages to a length of 320 characters or less" and warns that "Regularly sending very long SMS messages may reduce your overall delivery rate." It also says some carriers "may have trouble handling" messages longer than 10 segments with Unicode characters.

How to check a message before you send it

  1. Count the final text, with names, links and other inserted values filled in at realistic lengths.
  2. Check the encoding. If it says UCS-2 and you didn't mean to use an emoji or another script, find the character responsible.
  3. Replace look-alikes: curly quotes with straight ones, long dashes with hyphens and a one-character ellipsis with three periods.
  4. Trim to a segment boundary: 160 characters for one GSM-7 segment and 306 for two, or 152 per part on a US or Canadian toll-free number.
  5. Keep long messages within Twilio's recommended 320 characters.

If you send through Twilio, its Smart Encoding setting can swap many look-alike characters for you. Twilio Smart Encoding explains what it covers and what it misses.

Common mistakes

  • Counting 320 characters as two segments. HighLevel's cost article says "having between 161 to 320 characters will automatically result in 2 segments". Twilio puts 153 characters in each part, so two GSM-7 segments hold at most 306 characters, and a text of 307 to 320 characters is billed as 3.
  • Trusting how the text looks. A curly apostrophe looks almost like a straight one, and some characters don't show at all. HighLevel describes "Hey there" copied from a web page that came to 4 segments because it "contains many hidden (empty) characters".
  • Forgetting the double-count symbols. Each { or ] takes two places, whether the limit is 160 or 153.
  • Using standard limits for a toll-free number. Long toll-free texts to the US and Canada get 152 or 66 characters per part.

Precheckly's free SMS segment calculator shows the encoding, the segment count and an estimated cost at a per-segment rate you choose. It highlights each character outside GSM-7 and runs entirely in your browser, so your text is never sent anywhere.

Sources

Not legal advice. Carrier rules and provider documentation change, so check the linked sources before you rely on them.