Discord ID Lookup
Discord IDs are large numbers that identify every user, server, channel, role, and message on the platform. The ID lookup tool above takes any snowflake ID and decodes when it was created. When Discord allows it, the tool also fetches the current username, avatar, and server name. Right-click menus in Discord do not show IDs by default — you need Developer Mode enabled first.
What is a Discord snowflake ID?
A snowflake is Discord's name for the large integer it assigns to every entity. The number is not random — the first 42 bits encode a Unix timestamp in milliseconds, measured from Discord's epoch of January 1, 2015. The remaining bits store a worker ID, a process ID, and an incrementing counter Discord uses to keep the numbers unique even when multiple servers create accounts at the same millisecond.
Because the timestamp is embedded in the number, you can decode a snowflake to find when something was created without calling Discord's API. A user ID from 2024 will have a higher numeric value than one from 2016, because Discord has issued more IDs as the platform has grown.
Snowflakes are assigned at creation time. A user ID tells you when the account was created, not when they joined a specific server. A server ID tells you when the server was created, not when a particular bot was added to it.
How the decode works
The tool extracts the timestamp bits and converts them to a human-readable date. This calculation runs entirely in your browser — no data is sent to Discord for the decode step. The result shows the approximate creation moment in your local timezone.
The other bits in the snowflake (worker, process, increment) are internal to Discord's ID generation service. For routine moderation and development tasks, you do not need to interpret them. They matter mainly if you are building ID generation tooling yourself.
Snowflake decode is always available. It works regardless of whether the user or server exists now, has blocked the bot, or is set to private. The creation date is baked into the number itself.
When live API lookup works
Beyond the timestamp decode, the tool can fetch live data from Discord when our bot has access to that entity. For a user ID, this means the bot must share at least one server with that person and that server must have not restricted the bot. For a server ID, the bot must be a member of that server.
If the bot cannot reach the entity, the lookup returns an error but the snowflake decode still runs. The creation date is always shown, even when the username is unavailable.
Username and avatar data can also become stale. If someone changes their username after the lookup runs, the cached name may differ from their current display name. The ID itself never changes — it is the stable identifier tied to the account forever.
Finding IDs in Discord
Enable Developer Mode first: User Settings, Advanced, toggle Developer Mode. This makes Copy ID appear in right-click context menus for users, messages, channels, roles, servers, and emoji.
To copy a user ID: right-click the username or avatar in a message or the member list. To copy a server ID: open Server Settings while holding Shift (or right-click the server name on the left sidebar). To copy a channel ID: right-click the channel name in the channel list.
Message IDs require you to hover over the message and click the three-dot menu, then Copy Message ID. Channel and role IDs only appear in the right-click menu after Developer Mode is on.
Use cases for ID lookup
Moderators use ID lookup to verify when a spam account was created. Very new accounts — hours or minutes old — that are already posting in your server are a common ban evasion signal. Cross-reference the creation date against when the message was posted to spot suspiciously fresh accounts.
Bot developers need user and channel IDs to configure commands and webhooks. Rather than guessing the ID format, paste it here to confirm it is a valid snowflake before using it in a config file.
Server owners verifying a bot or integration: if a tool asks for your server ID and you are not sure where to find it, open Server Settings and look for the ID field, or right-click the server name with Developer Mode on.
Limits and privacy
The tool does not expose private accounts or restricted data. If a user has disabled friend requests or locked their privacy settings in a way that blocks API access, the lookup returns an error for the username but the decode still shows the creation date.
Do not use ID lookups to track users across servers without their consent, or to compile lists of users for harassment. The lookup is intended for moderation, development, and server management tasks.
Our bot does not log or store ID lookups beyond the session needed to return the result. The snowflake decode is purely client-side and never leaves your browser.
Troubleshooting failed lookups
If the lookup returns an error but the decode succeeds, the snowflake itself is valid but Discord's API did not return data. The most common reasons are that the bot is not in the target server, the user has blocked the bot, or the server has enabled privacy restrictions that prevent member data from being accessed.
If the decode itself is wrong or blank, the ID may not be a valid snowflake. Discord IDs are 17 to 19 digits. Shorter numbers or values with letters are not valid snowflakes.
When using Auto-detect, the tool tries user lookup first, then server. If you know the type already, selecting User ID or Server ID directly skips the failed attempt and runs the correct lookup immediately.
Explore more discord tools on Tolz.me.