THE PRACTICAL GUIDE · NORMANDIN SYSTEMS
Get more from Unicode to GSM-7
Unicode to GSM-7: Encode unicode text to SMS GSM-7 encoding and display related SMS send info. SMS length depends on the encoding and character repertoire; some characters consume extension positions or require a different encoding. An encoding changes how information is represented so that another program, protocol, or document can handle it. Correct interpretation depends on the precise format and any relevant character set, byte order, or variant. Encoding does not necessarily compress data and does not make it secret. When possible, use a small known value to verify the direction of conversion, then perform a round trip back to the original representation. Preserve leading zeros and other structural characters because a visually minor change can alter the underlying bytes.
Guide updated October 13, 2026
How to use this tool
- Begin with a representative input. For a practical test, use: A sample SMS message containing only supported GSM-7 characters. Replace demonstration values only after you understand the output.
- Choose the appropriate conversion direction and format options, then provide a short known value before processing your full input.
- Check the returned representation, especially leading zeros, separators, character encoding, and any format-specific prefix or checksum.
- Where a reverse operation is available, convert the result back and compare the recovered content with the original.
SEE IT IN PRACTICE
A worked example
Hello
5 GSM-7 septets for the five basic-alphabet letters
This short ASCII example fits the basic GSM-7 repertoire. Extension characters and unsupported Unicode can change the count or encoding, so inspect the full real message.
Follow the representation layers
A character is interpreted through an encoding when stored as bytes. Unicode also allows visually similar text to have different code-point sequences, such as a precomposed accent versus a combining mark. GSM-7 has its own repertoire and extension rules. Inspect the representation used by the destination rather than assuming every visible symbol consumes one storage or transmission unit.
Use representative multilingual samples
ASCII-only text can conceal encoding problems because many encodings agree on those characters. Include accents, punctuation, and any scripts or emoji your real content uses. Charset detection offers candidates rather than certainty, while code-point inspection identifies the actual sequence. For SMS, inspect the entire draft after edits because one unsupported character can change the encoding or segmentation behavior.
When this tool is useful
- Inspect an SMS draft
- Find encoding-sensitive characters
- Compare message lengths
Tips for a better result
- A single unsupported character can change message segmentation, and provider billing behavior should be checked separately.
- Treat bytes and displayed characters as different layers; the same visible text can have more than one byte representation.
- Keep the format name and selected variant with the converted value so another person can decode it consistently.
Frequently asked questions
Why can visible character count differ from byte or SMS length?
Characters can require multiple bytes, multiple code points, or encoding escape positions. The relevant unit depends on whether the destination counts encoded bytes, Unicode sequences, or SMS septets.
Why might another decoder reject my result?
It may expect a different variant, alphabet, padding rule, character set, or byte layout. Compare the exact format settings and inspect the copied input for added spaces, omitted prefixes, or truncated content.
What is a useful verification method?
Use a published or otherwise known test value, then try a round trip if the format supports it. Matching the original bytes provides stronger evidence than simply seeing readable-looking output.
What happens to the information I enter?
The utility processes your input in this browser. Some tools retain field values in browser storage or the URL; avoid entering secrets in shareable fields. Page and asset requests still go to the hosting provider. Read the privacy and offline-use notes for details.