/
AaSMS encoding & segments
← All symbols & tools

Copy2Paste / Text tools

SMS Encoding & Segment Checker

Check GSM-7 and Unicode SMS encoding, explain segment counts, locate special characters and preview punctuation replacements. Text stays on your device.

Interactive example: 139 A characters and one curly apostrophe. Apply the suggested replacement to compare encoding and segments. No SMS is sent.

AGSM-7’U+2019→ 'U+0027

140 / 4,000 UTF-16 units; no silent truncation

Estimates SMS only. Not a universal rule for RCS, MMS, WhatsApp or all providers. Signatures, opt-out text and provider processing may change the final content.

3Estimated SMS segments
140UTF-16 units
61Units remaining in last segment

Encoding: UCS-2 / UTF-16 · 140 code points

At least one character is outside GSM-7, so the entire text uses Unicode units. An emoji may use two or more UTF-16 units; one visible glyph is not necessarily one unit.

Single-segment capacity: 70 · Current per-segment capacity: 67. Multipart SMS reserves space for headers. This estimator keeps GSM escape pairs and complete grapheme clusters (such as compound emoji) together.

Which characters trigger Unicode encoding?

Character and positionReason
’U+2019UTF-16 position 140Outside GSM-7; switches the whole message to Unicode.
1/1 · 1 occurrences

Common punctuation and space replacement preview

A small set of common replacements, not the complete Twilio Smart Encoding feature. Chinese text, emoji and unlisted characters are preserved. Applying changes your wording; review first.

After applying: GSM-7 · 3 → 1 segments · 1 replacements

U+2019 → U+27

Segment capacity

1
67/67
2
67/67
3
6/67

Segmentation estimate only. It does not simulate handset display or guarantee delivery or a bill amount.

All text analysis and replacements run locally. No automatic saving, uploading or SMS sending. Rules checked: 2026-11-18.

Frequently asked questions

Why can a quote or emoji add segments?

Curly quotes, Chinese text and emoji may fall outside GSM-7 and switch the entire SMS to Unicode encoding. An emoji may also contain multiple UTF-16 units. The tool lists characters which trigger the encoding change.

What are the single and multipart capacities?

Common GSM-7 capacities are 160 septets for one segment and 153 per multipart segment; Unicode uses 70 UTF-16 units for one and 67 per multipart segment. GSM extensions use two units. Complete grapheme clusters move together to the next segment and may leave unused space. The US/Canada toll-free profile uses multipart capacities of 152/66.

Is replacement preview the complete Twilio Smart Encoding feature?

No. It suggests only a listed subset of common punctuation and space substitutions. Applying is explicit and can be undone. Chinese text, emoji and unlisted characters are not deleted.

Does the estimate guarantee billing or delivery?

No. This is an encoding estimate for the selected SMS rules, not a universal result for RCS, MMS or every provider. Signatures, opt-out text, routing and sending limits may change actual behavior. No SMS account is connected and no message is sent.

What is the input limit, and is text saved?

Up to 4,000 UTF-16 units. Oversized input produces an error and clears previous results without truncation. Text is neither uploaded nor automatically saved. The tool input limit is not a provider sending limit.

Twilio SMS rules ↗ · Smart Encoding reference ↗