Discord Mention Formatter
Discord mentions are the clickable pings that link to a specific user, role, channel, or custom emoji inside a message. Each type uses a distinct bracket-and-prefix syntax that Discord's parser reads and converts into a styled, interactive element. The mention formatter above takes the numeric ID and type and outputs the exact syntax you paste into a message, bot config, or webhook payload.
How Discord mention syntax works
Every mention type wraps the ID in angle brackets with a type indicator. User mentions use <@id>, role mentions use <@&id>, and channel mentions use <#id>. Custom emoji use <name:id> with an optional a prefix for animated emoji.
Discord renders these tags when the message is posted, converting them into styled links that click through to the target. A user mention becomes a blue username that pings the person. A channel mention becomes a clickable link that jumps to that channel.
The syntax is consistent everywhere: messages, thread descriptions, forum post content, embed descriptions, and webhook payloads all accept the same tags. Embed titles do not render mentions, so put mention syntax in the description or a field value instead.
User mentions
User mentions look like <@123456789012345678>. When sent, Discord shows the username in blue and notifies that person. If the user is not on the server or has notifications set to None, they do not receive a ping.
You can mention someone inside a code block — the mention still renders because Discord processes the content before applying code block formatting. However, mention syntax inside an inline code span does not render.
User mentions also work with the @someone syntax when you type the first few letters of a name. The numeric ID version is necessary in bot configurations, webhook templates, and when drafting announcements before the bot has joined the server.
Role mentions
Role mentions look like <@&123456789012345678>. Members who have that role receive a notification if the channel allows role mentions. Channels can disable @everyone and @here, and individual roles can be set to not trigger notifications even when mentioned.
Role mentions are useful in announcement channels where you want to notify a specific group: <@&AdminTeam>, <@&EventPing>. In rules or general chat channels, mass role mentions can be spammy — use them sparingly.
The ampersand (&) after the @ is what distinguishes a role mention from a user mention. Mixing them up is the most common reason a mention does not render.
Channel mentions
Channel mentions look like <#123456789012345678>. They render as a clickable channel name prefixed with #. Clicking the mention jumps the reader to that channel. They work in any text field that supports Discord markdown.
Channel mentions are useful in rules posts to link to <#rules> and <#announcements>, in welcome messages to direct new members to <#introductions>, or in staff docs to reference <#mod-chat>.
Channel mentions do not notify anyone — they are purely navigational. Unlike user and role mentions, there is no notification behavior tied to a channel mention.
Custom emoji mentions
Custom emoji mentions look like <:pepewave:123456789012345678> for static emoji or <a:animatedname:123456789012345678> for animated emoji. The a prefix only appears before the first colon, not after.
Custom emoji from other servers can only render in messages if your server has that emoji available — either because you share the source server or because you have Discord Nitro. If the emoji is not available, Discord shows the raw tag text instead of rendering it.
When using emoji mentions in a webhook message, the emoji must exist on a server the webhook's bot is in. If the bot switches servers and loses access to that emoji, the mention breaks in all messages sent from that bot.
Finding IDs to use with this tool
Enable Developer Mode in Discord's Advanced settings. This adds Copy ID to right-click context menus for users, roles, channels, and emoji. Right-click any username, role, channel name, or custom emoji and select Copy ID.
User IDs and role IDs are long numbers. Channel IDs look similar to user IDs — the auto-detect option in the ID lookup tool tries to guess which you have pasted, but you can also select the correct type manually to skip the failed attempt.
Emoji IDs are also snowflakes. When you copy a custom emoji's ID, the numeric part is the snowflake. You also need the emoji's name as it appears on that server for the mention to render correctly.
Where mentions work and where they do not
Mentions work in regular messages, thread posts, forum content, and embed descriptions. They do not render in channel topics, user status messages, or the channel name field itself.
Some channels disable role mentions entirely through the permissions setting "Allow anyone to @mention this role". If a role mention is not triggering notifications, check the channel's permission overwrites before assuming the syntax is wrong.
In bot and webhook configurations, mention syntax is usually placed inside message content strings. The exact field varies by library — some use content, some use embed description, some have a dedicated mentions field. The raw syntax from this tool is the same regardless of where it is used.
Tips and troubleshooting
If a mention renders as plain text instead of a styled link, check that the angle brackets are actual < and > characters and not Unicode left/right angle quotes. Copy-pasting from some word processors introduces smart quotes that break the syntax.
When drafting bot announcements, store raw IDs in a config object and format them with this tool when building the message. This keeps the config readable (just numbers) and the output correct (proper mention syntax).
Animated emoji mentions only render on servers that have that animated emoji available. If you are testing in a server that does not have the emoji, the raw tag appears — the mention syntax itself is still correct, it is the availability that is the limiting factor.
Explore more discord tools on Tolz.me.