Apps & Software

Character Counter & SMS Segment Guide: GSM-7 vs. Unicode & Social Platform Limits

Learn how character encoding impacts text message billing. Understand GSM-7 vs UCS-2 Unicode SMS segmentation, UTF-8 byte calculations, and social platform character limits.

Quick Summary & Key Takeaways

  • Objective: Learn how character encoding impacts text message billing. Understand GSM-7 vs UCS-2 Unicode SMS segmentation, UTF-8 byte calculations, and social platform character limits.
  • Estimated Time: Approximately 7 minutes following our step-by-step instructions.
  • Safety Recommendation: Ensure your device battery is above 30% and preserve any important files or passwords before modifying system settings.
Smartphone screen showing text message conversation bubbles
Calculating character counts, byte sizes, and GSM-7 vs. Unicode SMS segments.

Character counting is not merely a tool for staying under Twitter's 280-character limit. In telecommunications and enterprise marketing, understanding how characters are encoded directly affects your billing invoices.

A single hidden emoji or curly apostrophe can silently transform a 1-part SMS message into a 3-part message, tripling your carrier delivery costs.

In this guide, we demystify the difference between GSM-7 and UCS-2 Unicode encoding, explain how SMS concatenation headers work, and provide a quick reference table for social platform character limits.

πŸš€ Try the Live Utility: Calculate character breakdowns, UTF-8 bytes, and SMS segments with our free Character Counter & SMS Segments.


1. The SMS Billing Trap: GSM-7 vs. UCS-2 Unicode

When you send a text message (SMS), mobile telecommunications carriers pack the data into standard 140-byte transmission packets. The number of characters that fit into one SMS depends entirely on the character encoding:

GSM-7 Encoding (Standard English & Basic Symbols):

  • Each character requires only 7 bits of data.
  • A single standalone SMS message can hold up to 160 characters ($140 \text{ bytes} \times 8 \text{ bits} \div 7 = 160$).
  • Supports: English letters (A-Z, a-z), numbers (0-9), and basic punctuation (.,!?@$_/-).

UCS-2 / UTF-16 Unicode Encoding (Emojis, Accents & Non-Latin Scripts):

  • If your message contains even one single character outside the GSM-7 alphabet (such as an emoji πŸš€, smart curly quotes β€œ ”, or accented letters like Γ©, Γ±, Γ§), the carrier's gateway switches the entire message to UCS-2.
  • Each character now requires 16 bits (2 bytes) of data.
  • A single standalone SMS message is capped at only 70 characters ($140 \text{ bytes} \div 2 = 70$)!

2. Multi-Part Concatenated Messages & The Hidden 7-Byte Header

When a message exceeds the single-part limit, your phone does not deliver multiple disjointed texts. It stitches them together into a concatenated SMS.

However, to reassemble the pieces in the correct order on the recipient's phone, the telecom carrier must include a User Data Header (UDH) in every packet. This header consumes 7 bytes (or 6 GSM-7 characters) per message:

Concatenation Segment Limits:

| Encoding Type | 1-Part Message Limit | 2-Part Message (Per Segment) | Total Chars in 2 Segments | Total Chars in 3 Segments |

| :--- | :--- | :--- | :--- | :--- |

| GSM-7 Standard | 160 characters | 153 characters | 306 characters | 459 characters |

| Unicode (With Emoji)| 70 characters | 67 characters | 134 characters | 201 characters |

The Real-World Cost Trap:

Imagine sending a 161-character marketing text to 10,000 customers:

  • Without emoji (GSM-7): 161 characters splits into 2 segments (153 + 8). You are billed for 20,000 SMS segments.
  • With one emoji: 161 characters splits into 3 segments (67 + 67 + 27). You are billed for 30,000 SMS segmentsβ€”a 50% increase in marketing cost for a single smiley face!

3. UTF-8 Byte Length vs. Character Count

In web programming and database design (such as MySQL VARCHAR columns):

  • Basic ASCII characters (A-Z, 0-9) consume 1 byte in UTF-8.
  • Latin accented characters (Γ©, ΓΌ) consume 2 bytes.
  • Common Asian ideographs (Chinese, Japanese, Korean) consume 3 bytes.
  • Emojis (πŸŽ‰, πŸ”₯) consume 4 bytes.

Always calculate byte length when validating database inputs or optimizing low-latency network payloads.


4. Social Media & SEO Character Limits Cheat Sheet

| Platform & Field | Maximum Character Limit | Recommended Best Practice Length |

| :--- | :--- | :--- |

| Google Title Tag | ~60 characters (600 pixels) | 50 to 58 characters |

| Google Meta Description| ~160 characters (960 pixels) | 145 to 155 characters |

| Twitter / X Post | 280 characters | 120 to 220 characters |

| Instagram Caption | 2,200 characters | 150 to 300 characters |

| Instagram Bio | 150 characters | 130 to 145 characters |

| LinkedIn Post | 3,000 characters | 800 to 1,500 characters |

| Reddit Post Title | 300 characters | 60 to 120 characters |

| YouTube Video Title | 100 characters | 60 to 70 characters |

Check character counts, byte sizes, and SMS segments with our interactive Character Counter & SMS Segments.

Frequently Asked Questions

Why does adding an emoji shorten my SMS message limit to 70 characters?

Standard SMS uses 7-bit GSM-7 encoding (160 characters). Emojis require 16-bit UCS-2 Unicode encoding. The presence of even one emoji forces the telecom carrier to re-encode the entire message into 2-byte units, reducing the limit to 70 characters per segment.

What is an SMS concatenation header?

When a text message exceeds the single-part limit, carriers split it across multiple packets. A 7-byte User Data Header (UDH) is inserted into each packet so the recipient phone can stitch the segments back together in order.

What is the maximum pixel length for a Google SEO title?

Google measures title tags in pixels rather than exact characters. The desktop snippet limit is approximately 600 pixels, which translates to roughly 55 to 60 standard characters.

How many bytes does an emoji use in UTF-8?

Most modern emojis require 4 bytes of data in UTF-8 encoding, compared to standard English letters which require only 1 byte each.

Sarah Chen

About the Author: Sarah Chen

Mobile Systems Specialist

Sarah is a mobile operating system specialist focusing on Android internals, battery optimization, and iOS file management.