Show all emojis

It’s a known limitation:

Oh I see. I guess they didn’t update their emoji set to the latest version yet.
Thanks for the fast response!

The puzzle emoji seems to be on of them that works only in the layers panel, but not in a text field.

1. There’s been many instances where some emoji’s are rendered invisible when used as part of design. For example, 🧱

^ I can use it to name my layers and files fine but not as part of my design.

2. Also, any emoji past like a size 18px is rendered pretty pixelated. So, I have to resort to downloading & importing .PNG for each emoji, which can be pretty time consuming & difficult to maintain.

It’s VERY common for us to use emojis in textfields during our design/documentation process. Would appreciate having access to all emojis. It’s currently about 1/3 the time I want to use one it doesn’t work. Not a show stopper but it’s a bit irritating.

Come on! You can support ALL emojis, cant you? It’s 2021?! You can do better Figma, look at your counterparts at Notion.

Is this update on Figma’s roadmap any time soon? Appreciate knowing if we can expect this for anytime in the near future. Appreciate it!

I continuously run into this over and over. You can use all emoji in layer names, but not on the actual artboard. Super frustrating, please make this more of a priority!

+1 for supporting Emojis. We use them in various text fields, and really need to be able to display them.

I picked the 🧠 emoji from the Figma Emoji Picker and it came up blank in my text field, which makes me very 😔

Exactly which emojis work inside a canvas (text object)? Because every one I try shows blank. Thanks!

I discovered that emoji don’t display inside of components or component instances. They work fine inside of a stand-alone text component. Does anyone know a workaround for making them display inside of components? I’m working on a project that doesn’t allow me to break components.

Thanks!

I too am looking for a workaround or implementation of this feature. Thanks!

plz! i love emoji! the world loves emoji! 🥺

This is so F annoying. Nothing ever works in this S.

@Figma_Support, now that comments are far more functional, could you please support more emojis? Even extending the existing sets of very basic emojis like the circles can help with productivity.

Thank you!

I feel this is a bug, I have one Figma file where the emojis show up fine and another where they are missing. Using the latest version of Figma at the time.

This is how Figma renders the Warning emoji (⚠️). Some other emojis are also show up as webding characters. Sick, isn’t it? And no progress with it.

@Steve_Baker Hi! Yes, I think it is a bug. Yesterday, I had many files open in Figma and one of the files had some emojis. However, when I opened Figma today, some emojis were missing (same problem as you). I closed all Figma files and a prototype window, then opened Figma again and the emojis appeared. I don’t know if this bug is a problem with the memory in my computer or if it’s a Figma issue that doesn’t support emojis when using prototypes and multiple files.

Hey All, thank you for your patience! We’ve updated our emoji picker library to Unicode 14.0, adding more than 300 new emojis for you to use in comments, text boxes, and more! 🎉

Hello this is still happening for me. How do I fix this?

To clarify - emojis show up in one file but when I paste the same text box into another file a bunch are missing.

I was having the same issue with the 🌈 emoji. If I open the emoji menu while typing out text it will fail to render the emoji however if I copy and paste the emoji into my string of text it renders just fine.

Hey @alafritz and @tyler.richardson, thanks for flagging this!

Emojis seems to be appearing as expected when typing text or using copy + paste in the desktop app and browser for macOS.

Is this happening both in browser and using the desktop app? What OS are you using? We’ll pass this onto the team to try to reproduce.

Hi @dvaliao 👋 I first noticed the issue in the desktop app. I’m running macOS 14.4.1 on a MacBook Pro with a M1 chip. I was also able to recreate the issue in the browser with Chrome version 124.0.6367.119 on the same machine.