How to Use the GitHub Emoji Picker to Add an Emoji to GitHub

Updated

Open github-emoji-picker.vercel.app in a browser with JavaScript enabled, find the emoji you want, copy it (or its :shortcode:), and paste it into any GitHub text field—an issue, comment, pull request description, or Markdown file. The picker is a simple reference tool that displays all the emojis GitHub supports; it does not connect to your GitHub account or insert anything for you.

What the picker actually does

The site describes itself as "a simple emoji picker that displays all the supported GitHub emojis." That is its whole job: it shows you the set of emojis GitHub recognizes so you can pick one and move it into your own text.

Two practical consequences follow:

  • You copy, you don't insert. There is no GitHub login, no repository connection, and no button that posts an emoji for you. The picker hands you the character or code; pasting is your step.
  • JavaScript is required. The page only renders with JavaScript enabled—visiting it with scripts blocked shows just a "You need to enable JavaScript to run this app" message. If the page looks blank, check your browser's script settings or any content blocker.

Step by step

  1. Open the picker. Go to github-emoji-picker.vercel.app in a normal browser tab with JavaScript on. Confirm the emoji grid loads.
  2. Find your emoji. Browse the displayed set, or use the search/browse controls on the page to narrow it down. Because the list is limited to GitHub-supported emojis, anything you find here is safe to use on GitHub.
  3. Copy what you need. Take either the emoji character itself (😄) or its shortcode (:smile:), depending on what the field you're pasting into accepts.
  4. Paste into GitHub. Put the cursor where you want the emoji in an issue, comment, PR description, README, or other Markdown field, and paste.

Expected result: the emoji appears in your GitHub text. In a Markdown preview, a shortcode like :smile: renders as the emoji; the raw character renders directly.

Character vs. shortcode: which to paste

Paste this Use it when Watch out for
The emoji character (😄) You're typing in a field that accepts Unicode directly, or you want it to display everywhere Some older tools or plain-text contexts may not render it
The shortcode (:smile:) You're writing Markdown on GitHub and want readable source text It only renders where GitHub's Markdown processing applies; pasted as plain text elsewhere it stays literal

A common snag: pasting a shortcode into a field that doesn't process Markdown leaves :smile: visible as text. If that happens, switch to the emoji character instead.

Where this is useful

  • Issue and PR triage: add reaction-style markers (✅, 🐛, 🚀) to comments or titles for quick scanning.
  • README and docs: pick a supported emoji for headings or status tables without guessing whether GitHub will render it.
  • Commit messages and reviews: drop in an emoji character where your team's conventions allow it.

Because the picker only lists GitHub-supported emojis, it doubles as a check: if an emoji isn't in the picker, don't count on GitHub rendering its shortcode.

Common issues

  • Blank page: JavaScript is disabled or blocked. Enable it or try another browser.
  • Shortcode shows as plain text: the destination field doesn't parse Markdown—paste the character instead.
  • Emoji looks different than expected: GitHub renders emojis with its own image set, so the final look can differ slightly from your system font's version. The meaning and shortcode stay the same.