|While SharpSpring supports Unicode, SharpSpring emails can support only certain emojis.
These emojis can be placed in the email body, or in the subject line.
This article will detail the limitations of using emojis in SharpSpring emails.
Unicode is the current standard for displaying text and visual characters on computers and smart devices. Unicode displays characters by way of numbers, known as code points, and not individual glyphs. This allows for Unicode characters to be rendered visually—often in subtly different ways—by web browsers, word processors, and other software.
Emojis are visual characters that represent emotions, places, or things. They are perhaps the most popular non-text characters that can be displayed in Unicode format. Emojis are primarily rendered in a specific Unicode format known as Unicode Transformation Format—8-bit (UTF-8).
UTF-8 encodes over a million different code points. It does so by using a collection of bytes. As such, UTF-8 characters can be encoded with up to four eight-bit bytes. UTF-8 encoding can be represented in the following manner:
Each number set following a backslash (\) is considered a byte.
Currently, SharpSpring does not support four-byte UTF-8 encoding. When adding emojis, subject lines or otherwise, the only emojis that are supported and will work correctly in an email are those emojis that have three bytes or fewer. Consider the following emojis:
Available for Use?
If you insert emojis with four bytes into an email, you can send them in a preview. But, if you save your email and refresh the page, the emojis will not be supported and will be gone from the email.
For a list of relevant emojis, refer to the following external help documentation: