If you have ever added a 😊 to a text message and suddenly seen your SMS counter jump, you may have wondered what happened. An emoji can take more than one character in an SMS, and using an emoji can also change the way your entire message is encoded.
The important part is this: there is no single character count that applies to every emoji or every SMS. A normal SMS using GSM-7 encoding can contain up to 160 characters in one message, while a Unicode SMS is generally limited to 70 characters per single message. Many emojis require Unicode encoding, so adding one can reduce the available character space dramatically.
I have run into this issue most often when checking short messages that look comfortably under 160 characters but are unexpectedly split into multiple SMS messages. The emoji itself is only part of the story; the encoding used by the phone and carrier matters just as much.
What does “one emoji” mean in an SMS?
An emoji is a visual symbol such as 😀, ❤️, 👍, or 😂, but phones do not necessarily store or transmit it as one character.
For SMS purposes, an emoji may require multiple Unicode code points or UTF-16 code units, and its presence usually causes the message to use Unicode encoding rather than GSM-7.
That distinction explains why an emoji can have a much bigger effect on SMS length than its appearance suggests.
For example, these may look like individual symbols:
- 😀 Grinning face
- 👍 Thumbs up
- ❤️ Red heart
- 👨👩👧👦 Family
- 🏳️🌈 Rainbow flag
But internally they are not all represented in the same way. Some emojis consist of multiple Unicode components joined together to create a single visible emoji.
So there are really two different questions:
- How many characters or code units does the emoji occupy internally?
- How many SMS characters remain after the message switches to Unicode encoding?
For sending an actual SMS, the second question is usually the one that matters most.
Why does one emoji reduce an SMS from 160 to 70 characters?
The biggest issue is encoding.
Traditional SMS text can use GSM-7, an encoding designed around a relatively small character set. When a message contains a character that GSM-7 cannot represent, many phones switch to Unicode/UCS-2-style SMS encoding.
GSM-7 allows:
- 160 characters in a single unsegmented SMS
- 153 characters per segment when a longer message is split into multiple SMS segments
Unicode SMS generally allows:
- 70 characters in one segment
- 67 characters per segment when the message is split into multiple segments
Most modern emojis are not part of the basic GSM-7 character set. As a result, inserting an emoji can cause the whole SMS to use Unicode.
That means a message such as:
Your order is ready. Please collect it today.
might fit comfortably within one 160-character GSM-7 SMS.
Add an emoji:
Your order is ready 😊 Please collect it today.
and the phone may encode the entire message as Unicode.
The emoji itself might not consume 70 characters. Instead, its presence can change the character capacity of the entire SMS segment from 160 to 70.
That is the detail people often miss.
How many characters does a typical emoji use?
There is no universal number because emojis are encoded differently.
Some basic emoji characters can be represented by a single Unicode code point, while others use multiple code points. When software works with UTF-16, some characters also require a surrogate pair, meaning they occupy two UTF-16 code units.
For example, a simple emoji such as:
😀
is represented differently at the encoding level from a compound emoji such as:
👨👩👧👦
The family emoji is visually one emoji, but it is constructed from multiple Unicode characters joined using special invisible characters called zero-width joiners (ZWJ).
Skin-tone variations can also add additional Unicode components.
This is why asking “Does an emoji count as one character?” does not have a universal yes-or-no answer.
For visual counting, you might reasonably call 😀 one emoji.
For Unicode processing, it can involve one or more code points or UTF-16 code units.
For SMS billing and segmentation, the message’s encoding and the carrier’s SMS handling are what ultimately matter.
The difference between an emoji and an SMS character
This distinction becomes much easier if you separate the terms.
An emoji is a visible pictographic symbol.
A Unicode code point is a numerical representation assigned to a character or component in the Unicode standard.
A UTF-16 code unit is one of the units used by UTF-16 encoding to represent Unicode text.
An SMS character limit refers to how many encoded characters can fit into an SMS segment under a particular encoding scheme.
These are related, but they are not interchangeable.
Imagine you type:
Hello 😊
You see six visible letters, a space, and an emoji. But the underlying representation contains more information than that visual count suggests.
This is why a basic character counter can sometimes give you a different result from an SMS counter.
What happens when you use multiple emojis?
Multiple emojis can make the situation even more noticeable.
Suppose you write:
Great job! 🎉🎉🎉
The three party-popper emojis are visually three symbols. Depending on the counting system, however, the underlying text representation can involve multiple code points or UTF-16 units.
More importantly, because the emojis generally require Unicode, the entire SMS may be subject to the smaller Unicode segment limit.
This is why adding several emojis to an otherwise short marketing SMS can unexpectedly increase the number of SMS segments.
For businesses sending thousands of messages, that difference can matter because SMS providers commonly charge according to message segments rather than simply the number of visible sentences.
Does every emoji automatically make an SMS Unicode?
Most standard modern emojis require Unicode, so using an emoji commonly causes an SMS to switch away from GSM-7. However, the exact behavior depends on the messaging system, carrier, and character set being used.
This is one reason you should test the actual text rather than assuming every phone, app, and SMS provider will behave identically.
A smartphone messaging app may display a message normally while handling segmentation behind the scenes.
An SMS API such as Twilio may expose encoding and segment information differently from the default Messages app on an iPhone or Android phone.
If you are sending business SMS, always test with the provider you actually use.
A practical example: a 100-character message
Consider this message:
Your appointment is confirmed for Friday at 3 PM. Please arrive 10 minutes early. Thank you for choosing us.
At 100 characters, it could fit inside one 160-character GSM-7 segment if all characters belong to the supported GSM-7 set.
Now add an emoji:
Your appointment is confirmed for Friday at 3 PM 😊 Please arrive 10 minutes early. Thank you for choosing us.
The message may now be encoded as Unicode.
Even though the message is still only around 100 visible characters, it can exceed the 70-character single-segment Unicode limit, causing it to be divided into multiple SMS segments.
So the important lesson is:
A message does not need to contain 160 visible characters to become a multi-segment SMS.
Encoding can be the deciding factor.
Note: Also use this tool for generating Random Wheel of Names !
How to check how many SMS characters your message uses
If you are preparing an SMS and want to know whether an emoji will cause segmentation, an SMS character counter is more useful than a basic character counter.
A good SMS counter should ideally show:
- Total characters
- SMS encoding
- Number of SMS segments
- Characters remaining
- GSM-7 or Unicode status
- Potential segmentation caused by special characters or emojis
How to use an SMS character counter
- Open an SMS character-counting tool.
Use a counter that identifies SMS encoding rather than simply counting letters. - Paste your complete message into the text box.
Include emojis, punctuation, symbols, and spaces exactly as you intend to send them. - Check the encoding.
Look for an indication such as GSM-7 or Unicode. - Check the segment count.
A Unicode message may show a 70-character limit for one segment and a 67-character limit for subsequent concatenated segments. - Add or remove an emoji and test again.
This is a useful way to see whether the emoji changes the encoding. - Replace unnecessary emojis if needed.
If one emoji causes your message to split into additional segments, removing it may reduce the SMS count. - Test the final version before sending at scale.
This is particularly important for business SMS campaigns and automated notifications.
Real-world example: checking a delivery notification
Suppose you operate an online store and want to send:
Your order #4821 has shipped 📦. Track your package using the link below.
Before sending it through an SMS provider, paste the exact message into an SMS counter.
If the tool reports Unicode encoding, do not assume that the message’s visual length tells you the whole story.
You could compare it with:
Your order #4821 has shipped. Track your package using the link below.
The second version removes the emoji and may allow GSM-7 encoding, depending on the rest of the text.
That small change can affect the number of SMS segments.
For occasional personal messages, the difference may not matter much. For automated messages sent to hundreds or thousands of recipients, it is worth checking.
Common mistakes when counting emojis in SMS
Mistake 1: Assuming every emoji equals exactly one character
This is probably the most common misunderstanding.
A visible emoji is not necessarily one Unicode code point or one UTF-16 code unit. Compound emojis can contain several components.
Mistake 2: Using a normal character counter
A basic online counter might tell you:
80 characters
but that does not necessarily mean you can send those 80 characters as one SMS.
An SMS-aware counter should also consider encoding and segmentation.
Mistake 3: Forgetting about punctuation
Emojis are not the only things worth checking. Certain Unicode symbols and punctuation marks can also cause a message to leave GSM-7 encoding.
For example, replacing a standard apostrophe with a typographic curly apostrophe can change SMS encoding in some circumstances.
Mistake 4: Testing only the visible text
Copy and paste the exact final message into your counter.
Do not test a shortened version and then add the URL, emoji, personalization field, or tracking parameters afterward.
Mistake 5: Assuming iPhone and Android will behave exactly the same
Apple Messages, Google Messages, mobile carriers, and SMS service providers can handle messaging differently.
If you are developing an SMS workflow, test the actual service and devices your recipients use.
Can you use emojis without increasing SMS segments?
Sometimes, yes, but there is no universal trick that guarantees it.
The key issue is whether the character can be represented within the encoding being used. Most familiar modern emojis cannot be represented using the basic GSM-7 character set, so they commonly result in Unicode SMS.
If keeping the message to one segment is important, the practical approach is simple: test the exact message with an SMS-aware counter and remove unnecessary Unicode characters when needed.
For marketing messages, you can also create two versions:
Emoji version:
Your weekend offer is here 🎉 Shop now before it ends.
GSM-friendly version:
Your weekend offer is here. Shop now before it ends.
Then compare the encoding and segment count before choosing the final copy.
What about ❤️, skin tones, and family emojis?
Compound emojis deserve extra attention.
The red heart with a variation selector, for example:
❤️
is not necessarily represented in the same way as a plain single-code-point emoji.
Likewise:
👍🏽
combines a thumbs-up emoji with a skin-tone modifier.
A family emoji such as:
👨👩👧👦
can contain several individual emoji characters connected with zero-width joiners.
Visually, each appears as one emoji. Internally, they can contain multiple Unicode components.
If you are writing an SMS where every character matters, treat complex emojis as potentially variable-length rather than assuming one visible symbol equals one underlying character.
What should you do if your SMS suddenly shows multiple messages?
First, check whether you recently added an emoji or special symbol.
Then:
- Copy the exact message.
- Paste it into an SMS character counter.
- Check whether it reports GSM-7 or Unicode.
- Look at the segment count.
- Remove the emoji or unusual symbol temporarily.
- Check the message again.
- Compare the two results.
- If it is a business SMS, verify the final segmentation with your SMS provider.
This quick comparison usually reveals whether the encoding is responsible.
Frequently Asked Questions
Does one emoji count as one character in SMS?
Not necessarily. An emoji may consist of one or multiple Unicode code points or UTF-16 code units, depending on the emoji and the counting method.
How many characters can an SMS contain with an emoji?
If the emoji causes the message to use Unicode encoding, a single SMS segment generally supports up to 70 characters, compared with 160 characters for GSM-7. Longer Unicode messages are commonly segmented at 67 characters per segment.
Why did adding one emoji make my SMS longer?
The emoji may have caused the entire message to switch from GSM-7 to Unicode encoding. The important change is therefore not simply the number of characters added by the emoji; it is the smaller character capacity of Unicode SMS.
Do compound emojis count as multiple characters?
They can. Emojis such as skin-tone combinations and family emojis may contain multiple Unicode code points or UTF-16 code units even though they appear as one visual emoji.
Should I remove emojis from business SMS messages?
That depends on your message length, SMS provider, and cost or segmentation requirements. If adding an emoji changes a message from one segment to multiple segments, compare both versions before sending a large campaign.
The easiest way to think about emoji SMS length
When I need to check an SMS containing emojis, I don’t rely on the number of symbols I can see on the screen. I check the encoding first, then the character count, and finally the number of SMS segments.
That approach avoids the most common mistake: assuming that a 90-character message is automatically a one-SMS message.
So, if you remember only one thing, make it this: an emoji is not always one SMS character, and even one emoji can change the encoding of the entire message. When message length matters, paste the exact final text into an SMS-aware counter before sending it. That small check can save you from unexpectedly splitting a short-looking message into multiple SMS segments.