Skip to content
Tutorials

Server Emojis

Reuse this server's Discord emojis as icons across packs, builds, requirement pages, and scheduling templates instead of relying on generic icons.

Customization
Who uses it
Guild managers and staff who curate packs, templates, and requirement pages
Where it lives
Dashboard > Server Emojis
Goal
Staff can register a Discord emoji as a GearCheck emoji, tell native emojis apart from custom ones, and keep a readable fallback everywhere the emoji shows up.
On This Page5 sections

Before You Start

  • Builds: edit permission in GearCheck to sync, add or remove emojis. Uploading a new emoji to Discord also needs a server admin (Manage Server in Discord).
  • GearCheck installed in the server you're managing.
  • A Discord emoji already uploaded to the server, if you plan to register one instead of uploading a new file.

Steps

  1. Sync existing Discord emojis

    Open Dashboard > Server Emojis and use Sync from Discord to pull every emoji already uploaded to this server into GearCheck's emoji library. Sync only reads emojis that already exist; it does not create new ones. It refreshes the emojis you have, never adds back one you removed (use Add one emoji by its code for that), and on Free stops adding new ones at the limit.

  2. Upload a new emoji

    If the emoji doesn't exist in Discord yet, open Upload a new emoji to Discord under Add an emoji another way (a server admin can). GearCheck creates the emoji on the server through the bot first, then adds it to the library. PNG, JPEG, GIF, and WebP files up to 256 KiB are supported, and the page checks the name and the file before anything is sent.

  3. Add an existing emoji by its code

    Already have the emoji's code or ID? Open Add one emoji by its code and paste the full code, like <:name:id>, or the ID alone. GearCheck verifies the emoji belongs to this server before adding it to the library.

  4. Pick it wherever GearCheck shows an icon

    Once an emoji is registered, it appears in the icon picker for pack artwork, build categories, requirement page labels, and scheduling role templates, so your packs and templates can match the visual language your server already uses.

  5. Give it a readable fallback

    Add a readable fallback such as :fire_staff: to every emoji. Shared templates, marketplace exports, and any surface that can't render the raw emoji fall back to this text instead of showing nothing. The Emoji library's Your server and GearCheck tabs and its In Discord column show what's registered and whether Discord still has it.

Check It Worked

  • The emoji shows up under Your server in the Emoji library, not just in Discord.
  • The emoji has a readable fallback, so a shared template or exported requirements page still makes sense without it.
  • The emoji appears in the pickers where you expect it (pack icons, categories, requirement pages, scheduling roles).
  • No emoji you still use reads Gone from Discord or Off in Discord in the state column.

Common Pitfalls

  • Deleting or renaming the source emoji in Discord, which breaks any GearCheck emoji built from it.
  • Skipping the fallback text, so a shared template or exported requirements page shows nothing where the emoji used to be.
  • Uploading a file that doesn't meet the format or size limit instead of checking PNG/JPEG/GIF/WebP and 256 KiB first.