Emoji Unicode कनवर्टर

इमोजी को Unicode कोड पॉइंट (U+XXXX) में कनवर्ट करें या इमोजी प्राप्त करने के लिए कोड पॉइंट पेस्ट करें।

इमोजी → Unicode

Unicode → इमोजी

वर्ण विवरण

वर्ण विवरण देखने के लिए ऊपर एक इमोजी रूपांतरित करें।

कैसे उपयोग करें

  1. इमोजी या कोड पॉइंट दर्ज करें: इमोजी वर्ण पेस्ट करें या इसका Unicode कोड पॉइंट टाइप करें (जैसे U+1F600)।
  2. सभी प्रतिनिधित्व देखें: टूल दशमलव कोड, हेक्स मान, HTML एंटिटी, CSS एस्केप, UTF-8 बाइट्स आदि प्रदर्शित करता है।
  3. कोई भी प्रारूप कॉपी करें: HTML, CSS या JavaScript में उपयोग के लिए तुरंत कॉपी करने हेतु परिणाम पर क्लिक करें।

इमोजी Unicode कन्वर्टर क्यों इस्तेमाल करें?

इमोजी Unicode कोड पॉइंट के रूप में एन्कोड होते हैं, लेकिन अलग-अलग सिस्टम अलग-अलग प्रारूपों का उपयोग करते हैं। HTML को 😀 या 😀 एंटिटी की आवश्यकता होती है। CSS pseudo-element के लिए एस्केप्ड रूप \1F600 चाहिए। JavaScript स्ट्रिंग के लिए \u{1F600} चाहिए। इन्हें मैन्युअली ढूँढना धीमा है, यह टूल एक ही इमोजी इनपुट से तुरंत हर प्रारूप तैयार कर देता है। डेवलपर्स, डिज़ाइनर और कंटेंट क्रिएटर इसका उपयोग कोडबेस में इमोजी को सुरक्षित रूप से जोड़ने के लिए करते हैं, जहाँ कच्चे अक्षरों को सीधे कॉपी-पेस्ट करने से एन्कोडिंग समस्याएँ हो सकती हैं।

समर्थित आउटपुट प्रारूप

A short history of emoji, and the parts everyone gets wrong

The most-repeated origin story credits Shigetaka Kurita at NTT DoCoMo with creating "the first emoji" in 1998–1999. That story is true but incomplete. Two pre-Kurita developments deserve a mention:

How emoji crossed over to the rest of the world

For a decade after Kurita's set, emoji were a Japanese carrier phenomenon, with three competing and incompatible vendor sets (DoCoMo, KDDI, SoftBank). The crossover happened in three stages:

The Unicode Consortium's standardisation work ran in parallel. October 2010, Unicode 6.0 was the first version of the standard to add emoji as a recognised set, contributing roughly 722 emoji from the union of Japanese carrier sets. August 2014, Unicode Technical Report #51 was published (later promoted to UTS #51 in May 2017), the formal specification of how emoji are encoded, sequenced and presented.

Why most emoji code points live above U+FFFF

Unicode organises every character into 17 "planes" of 65,536 code points each. Plane 0 is the Basic Multilingual Plane (BMP), U+0000 through U+FFFF. Most everyday written language lives here. Planes 1–16 are supplementary planes (informally "astral planes"), U+10000 through U+10FFFF. The vast majority of emoji live in Plane 1, the Supplementary Multilingual Plane, specifically in blocks like Emoticons (U+1F600–U+1F64F), Miscellaneous Symbols and Pictographs (U+1F300–U+1F5FF), Transport and Map Symbols (U+1F680–U+1F6FF), and Supplemental Symbols and Pictographs (U+1F900–U+1F9FF). The newer Symbols and Pictographs Extended-A block sits at U+1FA70–U+1FAFF.

This matters for developers because of UTF-16. UTF-16 encodes BMP code points as a single 16-bit unit, but supplementary code points must be encoded as a surrogate pair: two 16-bit units, one from the high-surrogate range U+D800–U+DBFF and one from the low-surrogate range U+DC00–U+DFFF. JavaScript's string type is internally UTF-16, which is why "😀".length returns 2 instead of 1: the engine is counting code units, not code points. Modern JS code uses Array.from("😀").length or the Intl.Segmenter API to count grapheme clusters correctly.

UTF-8 handles the same emoji as a 4-byte sequence. The character 😀 (U+1F600) is F0 9F 98 80 in UTF-8. This is why MySQL's older utf8 charset (which is really utf8mb3, capped at 3-byte sequences) cannot store emoji, you need utf8mb4. MySQL 8.0 made utf8mb4 the default, but legacy databases still fail to store emoji and silently truncate or error depending on SQL mode. This is a frequent real-world bug.

Variation selectors, why the same heart can look black or red

A handful of Unicode characters have a "dual personality": they can appear as a plain monochrome text symbol or as a colourful emoji, depending on context. Two presentation selectors were added to Unicode 3.2 (March 2002): U+FE0F (Variation Selector-16, VS16) requests emoji presentation, and U+FE0E (VS15) requests text presentation. Example: ❤ (U+2764, "Heavy Black Heart") is a text-default symbol; ❤️ (U+2764 U+FE0F) is the emoji-presentation red heart that most apps render in colour. The same code point with and without VS16 looks completely different.

A famous related example is the sun. U+2600 "Black Sun With Rays" defaults to text-style monochrome; adding VS16 (U+2600 U+FE0F) gives the colourful ☀️. By contrast, U+1F31E "Sun With Face" is a separate code point added in Unicode 6.0 (October 2010), default emoji presentation, and renders as the smiling 🌞 without needing any selector. Two different code points, two different histories, both informally called "the sun emoji."

Skin-tone modifiers and the Fitzpatrick scale

In Unicode 8.0 (released 17 June 2015) the standard added five modifier characters that adjust the skin tone of any human-presenting emoji. The modifiers are based on the Fitzpatrick scale, a dermatological classification developed in 1975 by American dermatologist Thomas B. Fitzpatrick at Harvard. The medical scale has six types (I to VI). For emoji purposes, types I and II are merged into a single modifier, leaving five emoji modifiers:

Usage is positional: the modifier comes immediately after a supported human emoji. For example, 👋 (U+1F44B, waving hand) + U+1F3FD produces 👋🏽, the medium-tone wave. If a recipient's font doesn't support a particular base+modifier combination, the modifier renders as a separate brown square, a common failure mode on older systems.

Zero-Width Joiner sequences) how compound emoji are built

The Zero-Width Joiner, code point U+200D, is the "glue" character that lets multiple emoji combine into one composite glyph when the renderer recognises the sequence. ZWJ is invisible and has no width, it exists purely to signal to the rendering engine that the surrounding characters should fuse. Three patterns dominate:

Used heavily in Unicode 15.1 (released 12 September 2023): 118 new emoji were added in 15.1, of which 108 were directional variants of existing emoji (people facing right rather than the default left). Crucially, 15.1 added zero new base code points: every new emoji was a sequence built from existing components.

Keycaps, regional indicators, and the flag mechanism

Keycap sequences. A keycap emoji such as 1️⃣ is built from three code points: a digit (U+0031 = "1"), VS16 (U+FE0F), and the Combining Enclosing Keycap character U+20E3. The combining keycap was approved as part of Unicode 3.0 in 1999. The full set of keycap emoji covers 0–9 plus # and *. The three-character sequence trips up naive .length checks all the time.

Regional indicator pairs (flags). Unicode does not encode national flags as single characters. Instead, it defines 26 Regional Indicator Symbols, code points U+1F1E6 through U+1F1FF, each corresponding to a Latin letter A through Z. A flag is a pair of regional indicators that spells out an ISO 3166-1 alpha-2 country code. The French flag 🇫🇷 is U+1F1EB U+1F1F7: the regional-indicator letters F and R. Of the 26 × 26 = 676 possible pairs, only about 270 correspond to valid ISO country codes; the rest render as two letter symbols on most platforms.

Recent emoji versions, briefly

Vendor designs, same code point, different artwork

Unicode standardises the meaning and the code point, never the artwork. Every platform ships its own emoji font, and the visual differences are real enough to have caused documented miscommunication in academic studies (Hecht et al., CSCW 2018, on cross-platform emoji misinterpretation). The major fonts:

When a device's font has no glyph for a particular code point or sequence, browsers and operating systems display a blank rectangle, commonly called tofu. Tofu is the strongest possible signal that the recipient's device is older than the sender's. New emoji typically take six to eighteen months to propagate from a Unicode release to all major platforms.

Accessibility, what content authors should know

Modern screen readers (NVDA, JAWS, VoiceOver, TalkBack) read out the CLDR short name of each emoji from the Unicode Common Locale Data Repository, for example "grinning face" for 😀, "family: man, woman, girl, boy" for 👨‍👩‍👧‍👦. The Unicode CLDR maintains official short names and keywords in 90+ languages, which is what every major screen reader on Apple and Microsoft platforms uses. WCAG technique H86 recommends wrapping meaningful emoji in <span role="img" aria-label="thumbs up">👍</span>; decorative emoji should be hidden with aria-hidden="true". Three pitfalls: repeated emoji become verbose (😂😂😂😂😂 reads as "Face with tears of joy" five times); text-style emoticons (:)) read as "colon close-paren" with no Unicode short name; skin-tone modifiers are read aloud (👋🏽 reads as "waving hand: medium skin tone", informative but slower).

Emojipedia and the cultural infrastructure

Emojipedia was founded in 2013 by Jeremy Burge, an Australian designer who registered the domain on a whim after a birthday dinner. It is now the de facto reference site for emoji meanings, vendor designs, and release coverage, serving roughly 590 million page views in 2021. Burge sat on the Unicode Emoji Subcommittee, served as Emojipedia's "Chief Emoji Officer" until 2022, and created World Emoji Day (17 July): chosen because Apple's calendar emoji 📅 displays the date 17 July, itself a nod to the original launch date of Apple's iCal at Macworld Expo in 2002. Emojipedia was acquired by Zedge, Inc. (NYSE: ZDGE) in August 2021 and continues to operate under the same brand. The Unicode Emoji Subcommittee, which evaluates new emoji proposals, is currently chaired by Jennifer Daniel, a former Google design lead, the first woman to chair the subcommittee.

Quick-reference numbers

संबंधित टूल

मुफ़्त इमोजी चयनकर्ता HTML एंटिटी एन्कोडर मोर्स कोड अनुवादक वर्ण काउंटर