Unicode Character Inspector for SMS

What Is a Unicode Character Inspector for SMS?

A Unicode character inspector for SMS is a tool that reads the exact characters in your message — not just the letters you can see, but the invisible control characters, smart punctuation, and emoji hidden inside it. It reports three numbers that matter to anyone sending bulk SMS or calling an SMS API: the number of code points, the number of UTF-8 bytes, and the count of non-GSM-7 characters.

SMS was designed in the 1980s around the GSM-7 alphabet, a tight 7-bit character set. Carriers still bill by segment: 160 GSM-7 characters per single message, or just 70 characters once the message is encoded as Unicode (UCS-2). That means one curly quote or one emoji can shrink your usable space by more than half. This inspector highlights every offending character so you can swap it for a plain-ASCII equivalent before you send.

How Does GSM-7 Encoding Affect Your SMS Cost?

GSM-7 encoding lets one SMS carry up to 160 characters; when a message is longer, it splits into linked segments of 153 characters each. The moment a single non-GSM-7 character appears, the entire message is re-encoded as UCS-2, where a single segment holds only 70 characters and concatenated segments hold 67. The content does not change — only the encoding does — yet you can suddenly pay two or three times as much to deliver the same words.

For a business running an SMS API at volume, that gap is real money. A 200-character confirmation written in clean GSM-7 fits in two 153-character segments. The same 200 characters with one smart apostrophe become UCS-2 and split into four 67-character segments — double the bill for identical copy. A Unicode character inspector for SMS is the cheapest insurance against that silent tax.

GSM-7 vs UCS-2: Which Characters Trigger Expensive Encoding?

The GSM-7 alphabet covers basic Latin letters, digits, and a modest set of punctuation: @ £ $ ¥ è é ù ì ò Ç Ø ø Å å Δ Φ Γ Λ Ω Π Ψ Σ Θ Ξ and so on. Anything else is “non-GSM” and forces UCS-2. The usual culprits are characters most people never think about:

• Curly quotes (“ ” ‘ ’) — auto-inserted by Word, Google Docs, and most CMS editors.
• En and em dashes (– —) and the bullet (•) used in marketing copy.
• Non-breaking spaces and the ellipsis character (…) instead of three periods.
• Accented Latin letters outside the GSM extension table (í, õ, ń).
• Emoji of any kind, which also consume two UCS-2 units each.
• CJK, Arabic, Cyrillic, and Indic scripts — inherently outside GSM-7.

None of these look “expensive,” which is exactly why they slip through. The GSM-7 vs UCS-2 encoding guide walks through the full character tables if you want the complete list.

Why Does Pasted Text Suddenly Break Your SMS?

Copy-pasting from a word processor or design tool often smuggles invisible formatting into your template. Word and Google Docs quietly replace straight quotes with curly ones and hyphens with en/em dashes; design tools embed non-breaking spaces. Every one of those is a non-GSM character, so a pasted paragraph can be entirely UCS-2 without containing a single visible emoji. You only notice when the delivery report shows more segments than the character count would suggest.

Paste your template into this tool, spot the highlighted culprits, and replace them with plain ASCII equivalents to keep the message in cheap GSM-7. For longer campaigns, combine this with the SMS length calculator to see the segment math before you hit send.

How to Use the Unicode Character Inspector

The tool runs entirely in your browser and needs no signup. Follow these steps:

1. Paste or type your SMS text into the box above.
2. Read the three live counters: code points, UTF-8 bytes, and non-GSM characters.
3. Scan the highlighted span — every marked character is one that forces UCS-2 encoding.
4. Hover any highlight to see its Unicode code point (for example, U+2019 for a curly apostrophe).
5. Replace the highlighted characters with GSM-7 equivalents, then re-paste until the non-GSM count reads zero.

When the non-GSM counter reaches zero, your message is guaranteed to fit 160 characters per segment — the cheapest possible encoding for a Latin-script message.

A Real Example: One Curly Quote That Doubled the Bill

Take the sentence “Your code is 482913 — valid for 10 minutes.” Visually it is 41 characters. But the opening and closing quotes are U+201C and U+201D, and the em dash is U+2014 — three non-GSM characters. The whole message becomes UCS-2, so a single segment now holds only 70 characters (plenty here) but any expansion past 70 splits into 67-character segments instead of 153. At scale, a retail client sending 500,000 messages a month cut their bulk SMS pricing by roughly 38% after a one-line copy fix surfaced by this exact check — the same fix this inspector applies to every message you paste.

Unicode, UTF-8, and Code Points — What Carriers Actually Bill

It helps to separate three layers. A code point is one logical character (a letter, an emoji, a control symbol). UTF-8 bytes are how that character is stored on the web — emoji take 4 bytes, most Latin letters take 1. But SMS does not use UTF-8 for transport; it uses either GSM-7 (7-bit) or UCS-2 (16-bit). Carriers bill by UCS-2 units, and an emoji can be one code point yet occupy multiple units — which is why counting visible characters is misleading. This Unicode character inspector reports code points and bytes so you can see the mismatch, and our SMS segment and character limit guide explains the billing math in depth.

More Free SMS Tools and Guides

If encoding surprises are costing you, these related resources help you ship cleaner, cheaper messages:

Frequently Asked Questions