Skip to content
Discord Tool

ID Lookup

Decode Discord snowflake IDs to extract creation date, internal IDs, and more. Supports bulk decoding.

Decode Settings

How Discord Snowflakes Work

Discord IDs are 64-bit integers called snowflakes. They encode:

  • Timestamp: First 42 bits (milliseconds since Discord Epoch: 2015-01-01)
  • Worker ID: Next 5 bits (internal worker)
  • Process ID: Next 5 bits (internal process)
  • Increment: Last 12 bits (auto-incrementing)

timestamp = (id >> 22) + 1420070400000

Results

#

Enter a Discord ID to decode

Introduction

Every user, channel, role, guild, and message in Discord is identified by a unique snowflake ID, and many bots, audit logs, and moderation tools require those raw numeric IDs rather than names. ID Lookup resolves a snowflake ID back to its entity type and creation timestamp, or lets you extract IDs from Discord mention strings and message links without manually stripping angle brackets.

What Is ID Lookup?

ID Lookup is a snowflake parser that decodes Discord's 64-bit integer IDs into their constituent metadata. Discord snowflakes encode three pieces of information: a timestamp (milliseconds since the Discord epoch of January 1, 2015), an internal worker ID, and an internal process ID. By extracting the timestamp bits, the tool can tell you the exact second a user account, channel, or guild was created — a detail that is useful for identifying bot or alt accounts created moments before a raid.

The tool also handles the inverse operation: given a mention like <#123456789012345678> or a message URL like https://discord.com/channels/guild/channel/message, it extracts the raw snowflake IDs embedded in those strings. Moderators frequently need channel IDs for bot configuration files and message IDs for report references, but Discord's interface makes copying those IDs require developer mode. This tool saves the step of enabling developer mode when you already have a mention or link on hand.

Snowflake IDs are stable and never change, which makes them the authoritative reference for auditing. Display names, usernames, and channel names can all be renamed, but the underlying snowflake remains constant. ID Lookup leverages this permanence to help moderators correlate audit-log entries with specific entities even after renames have occurred.

ID Lookup Examples

InputOutput
190321347735453697Type: User | Created: 2016-07-12 22:14:03 UTC | Worker: 1 | Process: 0 | Increment: 1
<@&813421569370112001>Raw ID: 813421569370112001 | Mention type: Role | Created: 2021-02-19 16:33:41 UTC
https://discord.com/channels/695309783934328832/695309784414392351/1107708424104050768Guild: 695309783934328832 | Channel: 695309784414392351 | Message: 1107708424104050768 | Message sent: 2023-05-15 09:22:18 UTC
<#734921586092453899>Raw ID: 734921586092453899 | Mention type: Channel | Created: 2020-07-24 18:05:30 UTC

Key Features of ID Lookup

  • Snowflake binary decomposition extracting timestamp, worker ID, process ID, and increment from any valid Discord ID
  • Automatic mention-string stripping that handles <@>, <#>, <@&>, and <@!> formats without manual cleanup
  • Message-URL parsing that splits guild, channel, and message snowflakes from full Discord links
  • Discord-epoch timestamp conversion showing the exact UTC creation date and time of the entity
  • Batch mode accepting up to 50 IDs at once for audit-log reconciliation or moderation report generation
  • Copy buttons for each output field so you can grab just the raw ID or just the timestamp without selecting text

How It Works

1

Enter the Discord Snowflake ID

Paste the numeric ID you want to look up — this can be a user ID, role ID, channel ID, or server ID. Discord assigns every entity a unique Snowflake ID, and the tool decodes this number to extract the embedded metadata without requiring any API authentication.

2

Decode the Snowflake Metadata

The tool parses the Snowflake ID using Discord's documented bit-shifting algorithm to extract the creation timestamp. Since every Snowflake encodes the exact moment the entity was created, you get a reliable creation date even for users who have hidden their profile details from public view.

3

Review the Extracted Information

View the decoded creation date and approximate account age in a clear, readable format. For suspicious accounts, the creation date reveals whether the account was made recently — a common red flag for alt accounts, spammers, or ban-evaders trying to re-enter a server.

Who Uses This

Server Moderators

checking the creation date of new members who behave suspiciously, quickly identifying accounts that were created minutes ago and are likely spammers or ban-evading alts

Trust and Safety Teams

investigating reported users by analyzing account age as part of a broader risk assessment, flagging freshly created accounts that match patterns of coordinated harassment

Bot Developers

decoding Snowflake IDs programmatically to understand the age of users, channels, or roles in their systems, using the creation timestamp to implement age-gate features or audit logging

Frequently Asked Questions

What information can I get from a Discord ID?
A Discord Snowflake ID encodes the creation timestamp of the entity. The tool extracts this to show you when the user, channel, role, or server was created. It cannot reveal usernames, avatars, or any other profile data without authentication — those require Discord API access with a bot token.
Can I look up private or hidden profiles?
The tool decodes the Snowflake ID itself, which only contains the creation timestamp. It does not access Discord's user API, so it works on any valid ID regardless of the user's privacy settings. You get the creation date even for accounts with fully private profiles.
How accurate is the creation date?
Extremely accurate. Discord Snowflake IDs encode the creation timestamp down to the millisecond based on Discord's epoch. The decoded date reflects the exact moment the entity was created on Discord's servers, which is far more reliable than the join date displayed on public profiles.