---
title: "UCS-2 vs UTF-8 in SMS"
---

UCS-2 vs UTF-8 in SMS: Why Emojis and Special Characters Cut Max Length to 70 Chars: SMSRiver

- [Skip to main content](#main-content) [sms river .com](/) [Public Inboxes](/#numbers-section) [Country Codes](/country-codes/) [Workbench](/workbench/) [Tools](/tools/) [Developer API](/developer/) [Pricing](/pricing/) [Log In](/accounts/login/) [Log In](/accounts/login/) [Get API Key](/pricing/) [Home](/)

- [Articles](/articles/)

- Character Encoding & Economics

Character Encoding & Economics

Published 2026-08-17

•

7 min read

# UCS-2 vs UTF-8 in SMS: Why Emojis and Special Characters Cut Max Length to 70 Chars

Learn why including a single emoji or accented character slashes your SMS segment limit from 160 to 70 characters. Understand UCS-2 16-bit encoding mechanics.

Key Takeaway & Executive Summary

A single non-GSM character switches the entire SMS payload to 16-bit UCS-2 encoding, reducing single segment capacity from 160 to 70 characters (56% drop).

Modern software developers take UTF-8 for granted. However, the telecom signaling protocol (SMPP/SS7) does not support variable-length UTF-8. When an SMS contains any character outside the GSM-7 alphabet (such as an emoji, smart quote, or Cyrillic/Arabic/Chinese character), carriers switch the entire message to UCS-2 encoding.

## Table of Contents

- [The Mathematical Reality of UCS-2](#section-1)

- [Frequently Asked Questions](#frequently-asked-questions)

## 1 The Mathematical Reality of UCS-2

In UCS-2, every character consumes 16 bits (2 bytes). Because standard SMS signaling packets are strictly capped at 140 bytes (1,120 bits):

- GSM-7: 1,120 bits / 7 bits per char = 160 characters per segment.
- UCS-2: 140 bytes / 2 bytes per char = 70 characters per segment.

Adding a single emoji to a 150-character message splits it from 1 segment into 3 billable segments!

## Frequently Asked Questions • Character Encoding & Economics

Why does a 150-character UCS-2 message take 3 segments instead of 2?

When messages span multiple segments, carriers require a 6-byte User Data Header (UDH) in each segment, reducing multi-segment UCS-2 capacity to only 67 characters per segment (150 / 67 = 3 segments).

## Related Technical Articles & Deep Dives

[Character Encoding & Economics
8 min read

The Complete GSM 03.38 Character Set: Standard Chars, Extension Table, and Traps](/articles/gsm-7-character-set-and-escape-table/)

[Character Encoding & Economics
8 min read

User Data Headers (UDH) Deep Dive: How Carriers Reassemble Multi-Part SMS](/articles/udh-user-data-headers-and-multi-segment-sms/)

[Character Encoding & Economics
8 min read

Calculating Billable SMS Segments: Financial Analysis of Hidden Telco Costs](/articles/calculating-sms-segment-costs-at-scale/)

Developer Sandbox

### Automate Inbound SMS & OTP Testing

Eliminate flaky 2FA in CI/CD. Access dedicated virtual lines, programmable synthetic SMS webhooks, and Model Context Protocol (MCP) integrations.

[Explore Developer Tiers →](/pricing/)
[View MCP Setup Guide](/developer/mcp-setup/)

### Developer Utilities

- [SMS Segment Calculator Calculate segment counts and carrier costs in real time.](/tools/sms-segment-calculator/)

- [Webhook Payload Validator Verify JSON webhook payloads against provider schemas.](/tools/webhook-payload-validator/)

- [SMS Delivery Troubleshooter Diagnose carrier filtering and OTP delivery failure.](/tools/sms-delivery-troubleshooter/)

- [E.164 Phone Number Formatter Format phone numbers into international E.164 standard.](/tools/phone-number-formatter/)

### Public Verification Numbers

- [United States (+1) View Line →](/receive-sms/us/)

- [United Kingdom (+44) View Line →](/receive-sms/gb/)

- [Canada (+1) View Line →](/receive-sms/ca/)

- [Germany (+49) View Line →](/receive-sms/de/)

Copied to clipboard

FULL PACKET INSPECTION
SMS

### Line: DE +49 ...

Timestamp: Just now

Extracted code

Copy Code

Message Body:

Copy Full Message

[Open Live Inbox](#)

smsriver.com

Central Office carrier inventory platform & developer SMS verification sandbox. Receive OTP codes instantly with zero SIM card requirement.

Public numbers·Live inboxes·Developer tools

Public Inboxes

- [United States (+1)](/receive-sms/us/)

- [United Kingdom (+44)](/receive-sms/gb/)

- [Canada (+1)](/receive-sms/ca/)

- [Philippines (+63)](/receive-sms/ph/)

- [Germany (+49)](/receive-sms/de/)

Developer & Tools

- [SMS Debugging Workbench](/workbench/)

- [Phone Number Inspector](/tools/phone-number-inspector/)

- [Bulk Phone Validator](/tools/bulk-phone-validator/)

- [Phone Lookup API](/developer/phone-lookup-api/)

- [E.164 Phone Formatter](/tools/phone-number-formatter/)

- [SMS Segment Calculator](/tools/sms-segment-calculator/)

- [Webhook Validator](/tools/webhook-payload-validator/)

Guides & Trust

- [Country Calling Codes](/country-codes/)

- [Troubleshooting Hub](/troubleshooting/)

- [Carrier Comparisons](/compare/)

- [Developer Reference](/developer/)

- [OpenAPI Specification](/openapi.json)

- [MCP Tools Manifest](/.well-known/mcp.json)

- [Privacy & Security Guides](/guides/)

- [Engineering Articles](/articles/)

© 2026 SMSRiver. Operating on Cloudflare Workers & D1. Adheres to CTIA Messaging Principles and 10DLC compliance standards.

[About](/about/)
[Contact](/contact/)
[Privacy Policy](/privacy/)
[Terms of Service](/guides/terms-of-service/)
Cookie Preferences