Why Is My Emoji Black and White? Text vs Emoji Style
An emoji-looking character can appear black and white without being broken. Unicode allows some characters to use either text presentation, which is commonly monochrome, or emoji presentation, which is commonly colorful. An invisible variation selector can request one style or the other, while the app, font, and operating system still influence the final artwork.
If you see an empty square, replacement box, or question mark instead, that is a different problem. A box usually points to missing character support or a broken sequence; a black-and-white symbol can be a valid presentation of a supported character.
Start with the symptom, not the color
Black-and-white symbol
The character may be using text presentation, a text-oriented font, or an app that chooses a monochrome style.
Color emoji
The same base symbol can request emoji presentation with an emoji variation selector when that standardized sequence exists.
Box or question mark
This is more likely a support or encoding problem. Use the separate box-and-question-mark troubleshooting guide.
Why the same symbol can have two presentations
Unicode distinguishes the character from the artwork used to draw it. For characters that support standardized presentation variants, U+FE0E VARIATION SELECTOR-15 requests text style and U+FE0F VARIATION SELECTOR-16 requests emoji style. These selectors are invisible, so two strings that look almost identical in an editor can contain different code points.
| What you see | Typical sequence | Requested presentation | Important limitation |
|---|---|---|---|
| ♥︎ | U+2665 + U+FE0E | Text presentation | Usually monochrome, but exact glyph design depends on the font and platform. |
| ♥️ | U+2665 + U+FE0F | Emoji presentation | Usually colorful, but the artwork is not standardized to one vendor design. |
| ✈︎ / ✈️ | U+2708 + VS15/VS16 | Text or emoji | An app may still apply its own rendering behavior. |
| ☺︎ / ☺️ | U+263A + VS15/VS16 | Text or emoji | Copying only the base character can change which style appears next. |
Not every emoji has this two-style choice. Many modern emoji characters default to emoji presentation, while some older symbols have standardized text and emoji presentation sequences. The Unicode Emoji 18.0 charts list which characters support these variants.
Why copy and paste can change the style
Copying an emoji does not copy a screenshot of its artwork. It copies Unicode text. If the source includes a variation selector and the destination preserves it, the requested style can travel with the character. If a selector is removed, normalized differently, or ignored by the destination, the base character may be rendered according to that app's default font and presentation rules.
That is why a heart can look colorful in a messaging app, monochrome in a document, and colorful again after you paste it somewhere else. The underlying text may be the same base character with different presentation information, or the apps may simply render the same sequence differently.
A useful diagnostic: paste the character into a plain text field and then into a current messaging app. If both places recognize the character but choose different artwork, the problem is presentation. If one place shows a box, troubleshoot character support instead.
Use this order to fix a black-and-white emoji
- Confirm that the character is supported. If it appears as a box or question mark, update the app or operating system first and use the unsupported-emoji guide.
- Copy the emoji form from a reliable picker. Use the built-in emoji keyboard or Mojitap's All Emojis page instead of copying a decorative icon from an image, PDF, or random font.
- Paste without manually deleting invisible characters. Removing a variation selector can change the requested presentation even though you cannot see the removed character.
- Try a normal system font. A text-oriented or symbol font may prefer a monochrome glyph even when another app uses a color emoji font.
- Compare apps before changing the text repeatedly. If the sequence is correct but one app insists on a different style, the app or font may be choosing the rendering.
- Keep meaning in words when appearance matters. Color and artwork vary between platforms, so do not make an important instruction depend only on whether a symbol is red, black, filled, or outlined.
When adding U+FE0F can help—and when it cannot
For a character with a standardized emoji presentation sequence, U+FE0F requests emoji presentation. That can help when the plain base character defaults to text style. It is not a universal “make this colorful” switch. Adding U+FE0F to arbitrary characters does not create a supported emoji, and software can still have rendering limitations.
Likewise, U+FE0E requests text presentation where that variation is standardized. This is useful when you intentionally want a text-like symbol rather than a colorful emoji. The safest approach is to copy a known standardized sequence instead of inserting invisible selectors by hand unless you are inspecting code points deliberately.
Black and white is different from a missing emoji
| Symptom | Likely category | What to check first |
|---|---|---|
| Recognizable symbol, but monochrome | Text presentation or font/app rendering | Presentation sequence, font, and destination app |
| Empty square, tofu box, or replacement mark | Character not available to the renderer | OS/app/font support and whether the emoji is newer than the device supports |
| Separate pieces instead of one combined emoji | Sequence support problem | Whether the app supports the ZWJ or modifier sequence |
| Looks different but remains recognizable | Normal vendor artwork difference | No repair may be necessary; compare meaning rather than exact artwork |
What Mojitap can and cannot control
Mojitap works with Unicode text in the browser. The All Emojis page provides standardized fully-qualified emoji sequences, and the main tool can add emoji characters to text. Mojitap cannot force another app to use a particular color font, vendor artwork, or presentation policy after the text leaves the browser.
Practical rule: if the character is recognizable but only the visual style changed, check presentation and rendering. If the character becomes a box or falls apart into pieces, check support and sequence integrity.
Three copy-paste cases that look similar but need different fixes
Case 1: ♥︎ becomes ♥️. The base heart is supported, but the presentation changed. Recopy the intended standardized form and check whether the destination preserves its variation selector.
Case 2: a new emoji becomes □. This is not merely a color-style choice. The destination may not support that Unicode character yet. Update the relevant OS/app or use words until recipients can display it.
Case 3: a family, profession, or other combined emoji separates into pieces. The destination may not support the full sequence. Recopy the complete sequence, avoid editing inside it, and test on the target platform.
Official references
- Unicode Technical Standard #51: Unicode Emoji
- Unicode FAQ: Emoji & Pictographs
- Unicode Emoji 18.0: Emoji Presentation Sequences
- Unicode Emoji 18.0: Text vs Emoji
- Unicode Emoji 18.0: Emoji Default Style Values