The SMS character limit is 160 characters per message when you use the standard GSM-7 character set. Go past 160 and your message is split into segments of 153 characters each, and every segment is billed as a separate message. Include even one emoji or curly quote and the encoding switches to UCS-2, dropping the limit to 70 characters (67 per segment when concatenated). Understanding these mechanics is the difference between predictable messaging costs and a bill that quietly doubles.
Key takeaways:
- A single SMS holds 160 characters in GSM-7 encoding; longer messages split into 153-character segments that are billed individually.
- Any character outside the GSM-7 set, including emoji, curly quotes, and many accented letters, forces UCS-2 encoding and cuts the limit to 70 characters (67 concatenated).
- One stray emoji in a 300-character message can turn two segments into five, multiplying the cost of an entire campaign.
- Personalization tokens and long URLs are the most common hidden causes of unexpected extra segments.
- Writing tight, single-segment messages improves cost, readability, and often deliverability at the same time.
The 160-character rule and where it comes from
SMS was designed decades ago with a hard technical constraint: each message travels in a packet with room for 140 bytes of content. Using the GSM-7 encoding scheme, which packs each character into 7 bits, those 140 bytes hold exactly 160 characters. That is the origin of the famous limit. It is not a marketing convention or a platform choice; it is the physics of the protocol every carrier still honors.
The GSM-7 character set covers the unaccented Latin alphabet, digits, and common punctuation: enough for ordinary English sentences. As long as every character in your message belongs to that set, you get the full 160 characters in a single message.
Two wrinkles complicate the simple story. First, a handful of GSM-7 characters are "extended" and consume two character slots instead of one, including the caret, curly braces, square brackets, backslash, pipe, tilde, and the Euro symbol. A message full of brackets runs out of room faster than its visible length suggests. Second, and far more consequential, anything outside the GSM-7 set changes the encoding of the entire message, which is the subject of the next section.
What happens after 160 characters: concatenation and segments
Modern phones and platforms let you type far past 160 characters, so what actually happens when you do? The message is split into multiple SMS segments, each carrying a small header called a UDH (User Data Header) that tells the receiving phone how to stitch the pieces back together in order. That header consumes space, which is why concatenated segments hold 153 characters each rather than 160.
The arithmetic matters for budgeting:
- 1 to 160 characters: 1 segment
- 161 to 306 characters: 2 segments
- 307 to 459 characters: 3 segments
- 460 to 612 characters: 4 segments
Notice the trap between 160 and 161: one extra character doubles the cost of the message. The recipient sees a single continuous text, so nothing looks different on their screen, but your invoice counts every segment. Carriers and platforms bill per segment because each segment traverses the network as its own message.
For a deeper look at how message construction interacts with carrier filtering and delivery, see our guide to SMS deliverability and why texts sometimes fail to land.
The Unicode trap: how one emoji triples your cost
Here is the mechanic that surprises almost everyone. SMS encoding is all or nothing for a given message. If every character fits GSM-7, the whole message is GSM-7 and you get 160 characters. If even one character falls outside that set, the entire message must be encoded as UCS-2, which uses 16 bits per character. Your 140-byte packet now holds only 70 characters, or 67 per segment when concatenated.
Characters that silently trigger UCS-2 include:
- Emoji. Every one of them.
- Curly (smart) quotes and apostrophes. Word processors and some CMS tools insert these automatically when you type straight quotes.
- Long dashes and ellipsis characters pasted from documents.
- Accented and non-Latin characters outside the small set GSM-7 supports.
- Trademark, copyright, and degree symbols and similar typographic marks.
The cost math is brutal. A 300-character message in GSM-7 is 2 segments. Add one emoji and the same message becomes UCS-2: at 67 characters per segment, it now takes 5 segments. One character, two and a half times the cost, multiplied across every recipient on the campaign. On a list of 10,000 contacts, that single emoji generated 30,000 extra segments.
The fix is procedural: paste campaign copy through a plain-text step, use straight quotes, and use a platform that shows a live segment counter as you type. FRANSiS displays encoding and segment counts before you send, so a smart quote pasted from a Word doc gets caught in the composer rather than on the invoice.
Why segments drive your bill
Nearly every SMS platform and carrier prices messaging per segment, not per message as recipients perceive it. Whether you pay per message or a flat platform rate with volume limits, segments are the underlying unit of consumption. That has three budgeting implications:
- Estimate campaigns in segments, not messages. A 320-character appeal to 5,000 supporters is 15,000 segments in GSM-7, not 5,000 messages.
- Small copy edits have outsized cost effects. Trimming a message from 170 to 158 characters halves its cost. No other edit in your marketing stack has that kind of leverage.
- Encoding audits pay for themselves. A quarterly review of your templates for stray Unicode characters is one of the fastest cost reductions available.
Segment economics also interact with how your platform charges overall. Some platforms bill strictly per segment, others bundle volume into flat plans; understanding which model you are on determines whether long messages hit your invoice directly or your plan allowance. You can review how FRANSiS approaches this on our pricing page.
Practical tips to stay inside one segment
Single-segment messages are cheaper, cleaner, and force better writing. Techniques that help:
- Front-load the point. Lead with the action or information; supporting detail comes second or not at all.
- Use a link for the details. The text earns the click; the landing page carries the depth.
- Shorten URLs deliberately. A full-length URL can consume half a segment by itself. Use a short branded domain rather than raw links. Note that link shorteners help length but generic public shorteners can hurt deliverability, so prefer branded short domains.
- Budget for personalization tokens. A merge field like a first name varies per recipient. "Hi Alexandra" costs more characters than "Hi Al". Leave headroom of 15 to 20 characters so your longest names do not push individual messages into a second segment.
- Watch opt-out language. Required footer text like "Reply STOP to opt out" consumes real estate; include it in your character budget from the start, not as an afterthought.
- Kill typographic characters. Straight quotes, plain hyphens, three periods instead of an ellipsis character. Your composer's segment counter should read GSM-7 before you press send.
How carriers handle long and concatenated messages
Concatenated SMS is well supported across US carriers, and modern handsets reassemble segments reliably. Still, a few operational realities are worth knowing. Segments of a long message can occasionally arrive out of order or with slight delays before reassembly, especially under network congestion. Very long messages, beyond eight to ten segments, are more likely to encounter handling problems and are usually a sign the content belongs in an email or a linked page instead. Some platforms cap maximum message length for exactly this reason.
Concatenation also interacts with throughput: every segment counts against your sending rate limits, so long messages slow down large campaigns in addition to costing more. When timing matters, such as event-day reminders, short messages are also fast messages.
Frequently asked questions
What is the SMS character limit?
A single SMS holds 160 characters using GSM-7 encoding, the standard character set for English-language texting. If any character in the message requires Unicode (UCS-2) encoding, such as an emoji, the limit for a single message drops to 70 characters.
What happens if I go over 160 characters?
The message is split into segments of 153 characters each (the missing 7 characters hold the header that lets the phone reassemble the pieces). Recipients see one continuous message, but each segment is billed separately by your platform or carrier.
Do emoji really change the cost of a text?
Yes. One emoji anywhere in the message switches the entire message from GSM-7 to UCS-2 encoding, cutting capacity from 160 characters to 70 (67 per segment when concatenated). A message that was 2 segments can become 5 with a single emoji added.
Do spaces and punctuation count as characters?
Yes. Every space, comma, and period counts toward the limit. A few GSM-7 extended characters, including square brackets, curly braces, the caret, backslash, pipe, tilde, and the Euro sign, count as two characters each.
How do I know how many segments my message will use?
Use a platform with a live segment counter in the message composer, which should show both the character count and the detected encoding. If the counter says UCS-2 and you did not intend to use emoji, hunt for a pasted curly quote or long dash and replace it with the plain ASCII equivalent.
Conclusion
The SMS character limit is not trivia; it is the pricing model of the entire channel. The rules are fixed and knowable: 160 characters in GSM-7, 153 per concatenated segment, 70 in UCS-2, 67 concatenated. Teams that internalize them write tighter messages, catch encoding accidents before sending, and budget campaigns accurately. Teams that do not, pay for the difference every month without noticing. A segment counter in the composer, plain-text discipline in your copy workflow, and a habit of front-loading your message are all it takes to stay on the right side of the math.
Ready to see exactly what every message costs before you send it? Contact the FRANSiS team for a walkthrough of segment-aware composing, encoding detection, and campaign tools built for mission-driven organizations.


