SMS Character Counter

Every text message you send is billed by the segment, not by the character alone. A standard text uses GSM‑7 encoding and fits 160 characters into one segment. If your message contains even one special symbol or emoji, the entire text switches to UCS‑2 (Unicode), shrinking the single‑segment limit to 70 characters. Exceed that threshold and your message splits into multiple segments, each charged separately.

Knowing your exact character count total before you hit send helps you avoid those surprise overages. Our tool calculates the real segment count, accounting for concatenation headers, so you see what you’ll actually pay for.

A message segment is one billable unit of an SMS. When your text is too long to fit in a single segment, the sending platform chops it into parts and adds a small header to each part so they can be reassembled on the recipient’s phone. That’s why a “160‑character limit” drops to 153 characters per segment in a long message. Understanding SMS message character limits means understanding where those segment breaks happen — and how to avoid them.

If you’re using Twilio, the platform follows the same rules — but the financial impact is immediate. Twilio charges per segment, not per API request. A text that spans 3 segments costs you 3 message units, even if it was sent as a single API call.

Our SMS character counter gives you the segment breakdown directly. Combine that with your Twilio per‑segment rate, and you can estimate costs before launching a campaign. This is particularly valuable for marketing messages, two‑factor authentication texts, and bulk notifications.

Not all characters are created equal. Even within GSM‑7, some symbols eat up two character slots. And in Unicode, many emojis use multiple code units. This is the number‑one reason users see unexpected segment jumps.

The following characters are part of GSM‑7’s extended set: **€ { } [ ] ~ ^ | \ **Each of these requires an invisible escape code, effectively consuming two character positions from your 160‑character budget. For example, a message of 159 normal letters plus a single € will be treated as 161 characters and split into two segments.

In UCS‑2, some emojis and rare symbols are encoded with two 16‑bit code units (a surrogate pair). A single emoji, such as 💡 or 🚀, can count as two characters toward the 70‑character limit. If your text contains multiple such emojis, the segment count can escalate faster than you’d expect.

Our tool accurately counts every character, including extended GSM‑7 and surrogate pairs, so you always see the real segment count.

1. Paste your draft into the calculator.
2. Check the segment count. If it’s more than one, every additional segment adds cost.
3. Eliminate Unicode triggers. Swap emojis for emoticons like :-).
4. Replace costly accented letters with free ones.
5. Shorten URLs with a link shortener to reclaim dozens of characters.
6. Rewrite to trim below the threshold. Removing just a few words can bring a 2‑segment message back to a single segment — instantly halving your cost.

Small edits make a big difference. A message at 162 characters costs twice as much as one at 159. Use the tool iteratively until you land safely inside a single segment.