Need help with twemoji?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

13.4K Stars 1.5K Forks Other 395 Commits 51 Opened issues


Emoji for everyone.

Services available


Need anything else?

Contributors list

Twitter Emoji (Twemoji) Build Status

A simple library that provides standard Unicode emoji support across all platforms.

Twemoji v13.1 adheres to the Unicode 13.0 spec and supports the Emoji 13.1 spec. We do not support custom emoji.

The Twemoji library offers support for 3,521 Unicode-defined emojis.


CDN Support

The folks over at MaxCDN have graciously provided CDN support.

Use the following in the

 tag of your HTML document(s):

This guarantees that you will always use the latest version of the library.

If, instead, you'd like to include the latest version explicitly, you can add the following tag:



If instead you want to download a specific version, please look at the

branch, where you will find the built assets for both our latest and older versions.


Following are all the methods exposed in the


twemoji.parse( ... ) V1

This is the main parsing utility and has 3 overloads per parsing type.

Although there are two kinds of parsing supported by this utility, we recommend you use DOM parsing, explained below. Each type of parsing accepts a callback to generate an image source or an options object with parsing info.

The second kind of parsing is string parsing, explained in the legacy documentation here. This is unrecommended because this method does not sanitize the string or otherwise prevent malicious code from being executed; such sanitization is out of scope.

DOM parsing

If the first argument to

is an
, generated image tags will replace emoji that are inside
nodes only
without compromising surrounding nodes or listeners, and completely avoiding the usage of

If security is a major concern, this parsing can be considered the safest option but with a slight performance penalty due to DOM operations that are inevitably costly.

var div = document.createElement('div');
div.textContent = 'I \u2764\uFE0F emoji!';


var img = div.querySelector('img');

// note the div is preserved img.parentNode === div; // true

img.src; // img.alt; // \u2764\uFE0F img.className; // emoji img.draggable; // false

All other overloads described for

are available in exactly the same way for DOM parsing.

Object as parameter

Here's the list of properties accepted by the optional object that can be passed to the

    callback: Function,   // default the common replacer
    attributes: Function, // default returns {}
    base: string,         // default MaxCDN
    ext: string,          // default ".png"
    className: string,    // default "emoji"
    size: string|number,  // default "72x72"
    folder: string        // in case it's specified
                          // it replaces .size info, if any


The function to invoke in order to generate image


By default it is a function like the following one:

function imageSourceGenerator(icon, options) {
  return ''.concat(
    options.base, // by default Twitter Inc. CDN
    options.size, // by default "72x72" string
    icon,         // the found emoji as code point
    options.ext   // by default ".png"


The default url is the same as

, so if you modify the former, it will reflect as default for all parsed strings or nodes.


The default image extension is the same as

which is

If you modify the former, it will reflect as default for all parsed strings or nodes.


The default

for each generated image is
. It is possible to specify a different one through this property.

The default asset size is the same as

which is

If you modify the former, it will reflect as default for all parsed strings or nodes.


In case you don't want to specify a size for the image. It is possible to choose a folder, as in the case of SVG emoji.

twemoji.parse(genericNode, {
  folder: 'svg',
  ext: '.svg'

This will generate urls such
instead of using a specific size based image.


Basic utilities / helpers to convert code points to JavaScript surrogates and vice versa.


For a given HEX codepoint, returns UTF-16 surrogate pairs.

 // "\ud83c\udde8"


For given UTF-16 surrogate pairs, returns the equivalent HEX codepoint.

 // "1f1e8-1f1f3"

twemoji.convert.toCodePoint('\ud83c\udde8\ud83c\uddf3', ''); // "1f1e81f1f3"


Inline Styles

If you'd like to size the emoji according to the surrounding text, you can add the following CSS to your stylesheet:

img.emoji {
   height: 1em;
   width: 1em;
   margin: 0 .05em 0 .1em;
   vertical-align: -0.1em;

This will make sure emoji derive their width and height from the

of the text they're shown with. It also adds just a little bit of space before and after each emoji, and pulls them upwards a little bit for better optical alignment.

UTF-8 Character Set

To properly support emoji, the document character set must be set to UTF-8. This can be done by including the following meta tag in the document

Exclude Characters (V1)

To exclude certain characters from being replaced by twemoji.js, call twemoji.parse() with a callback, returning false for the specific unicode icon. For example:

twemoji.parse(document.body, {
    callback: function(icon, options, variant) {
        switch ( icon ) {
            case 'a9':      // © copyright
            case 'ae':      // ® registered trademark
            case '2122':    // ™ trademark
                return false;
        return ''.concat(options.base, options.size, '/', icon, options.ext);

Legacy API (V1)

If you're still using our V1 API, you can read our legacy documentation here.


The contributing documentation can be found here.

Attribution Requirements

As an open source project, attribution is critical from a legal, practical and motivational perspective in our opinion. The graphics are licensed under the CC-BY 4.0 which has a pretty good guide on best practices for attribution.

However, we consider the guide a bit onerous and as a project, will accept a mention in a project README or an 'About' section or footer on a website. In mobile applications, a common place would be in the Settings/About section (for example, see the mobile Twitter application Settings->About->Legal section). We would consider a mention in the HTML/JS source sufficient also.

Community Projects

Committers and Contributors

  • Justine De Caires (Twitter)
  • Jason Sofonia (Twitter)
  • Bryan Haggerty (ex-Twitter)
  • Nathan Downs (ex-Twitter)
  • Tom Wuttke (ex-Twitter)
  • Andrea Giammarchi (ex-Twitter)
  • Joen Asmussen (WordPress)
  • Marcus Kazmierczak (WordPress)

The goal of this project is to simply provide emoji for everyone. We definitely welcome improvements and fixes, but we may not merge every pull request suggested by the community due to the simple nature of the project.

The rules for contributing are available in the

Thank you to all of our contributors.


Copyright 2019 Twitter, Inc and other contributors

Code licensed under the MIT License:

Graphics licensed under CC-BY 4.0:

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.