About Discord User ID Lookup — Resolve ID to Username, Avatar & Account Age
Every Discord entity — users, channels, roles, servers, messages — has a Snowflake ID that encodes the exact millisecond it was created. But this creation timestamp is hidden inside a 64-bit integer using Discord's custom epoch and bit-shifting algorithm, and Discord's UI only shows join dates, not creation dates. That gap matters for moderation: an account created 20 minutes ago joining your server is almost certainly a ban-evading alt, while an account from 2019 that just joined is likely legitimate. The ID Lookup decodes the Snowflake's embedded timestamp without any API calls or bot tokens, giving you the creation date that Discord's interface doesn't expose.
How to Use This Tool
Follow these simple steps to get accurate results in seconds. The whole process takes less than a minute for most inputs.
- 1
Copy a Discord ID
Enable Developer Mode in Discord Settings → Advanced, then right-click any user, channel, role, or message and select Copy ID. Without Developer Mode, the Copy ID option is hidden from the context menu.
- 2
Paste the ID, Mention, or URL
Enter the numeric Snowflake ID (190321347735453697), a formatted mention (<@190321347735453697>), or a Discord message URL (https://discord.com/channels/123/456/789). The tool automatically extracts and decodes all IDs.
- 3
View the Decoded Metadata
The tool displays the creation date, approximate age, and other embedded metadata extracted from the Snowflake structure — including the worker ID and process ID that can reveal batch-created accounts.
- 4
Assess the Account
Compare the creation date against the account's server join date to evaluate legitimacy. An account created three years ago but joined today is likely legitimate; an account created today and already posting links is almost certainly suspicious.
How It Works
The technical details of how this tool processes your input and produces accurate results.
Snowflake Bit Structure Decomposition
Discord Snowflake IDs are 64-bit integers with four segments: timestamp (bits 63-22, 42 bits), worker ID (bits 21-17, 5 bits), process ID (bits 16-12, 5 bits), and increment (bits 11-0, 12 bits). The tool right-shifts the ID by 22 bits to isolate the timestamp portion, then adds Discord's custom epoch (1420070400000 milliseconds — January 1, 2015 00:00:00 UTC) to convert it to a standard Unix timestamp in milliseconds.
Mention and URL Parsing
Discord mentions wrap IDs in angle brackets with type prefixes: <@123> for users, <@!123> for users with nicknames, <#123> for channels, <@&123> for roles. The parser strips the <@>, <#>, <@&>, and <@!> prefixes and trailing > to extract the raw numeric ID. For Discord URLs (discord.com/channels/guildId/channelId/messageId), it splits on / to extract each Snowflake component separately.
Creation Date Computation
After extracting the timestamp bits and adding Discord's epoch, the tool converts the millisecond Unix timestamp to a human-readable date using the browser's Date object: new Date(timestamp).toISOString(). The result is the exact creation moment on Discord's servers, accurate to the millisecond — far more precise than any date shown in Discord's UI.
Key Features
Built to handle real workflows quickly and accurately. Each feature solves a specific problem you'd otherwise need multiple tools or manual steps to address.
Snowflake Timestamp Extraction
Decodes the creation timestamp embedded in any Discord Snowflake ID using the bit-shifting algorithm documented in Discord's API reference, providing millisecond-accurate creation dates from pure math — no API access needed.
Multi-Entity Type Support
Accepts user IDs, channel IDs, role IDs, server IDs, message IDs, and emoji IDs — all Discord entities use the same Snowflake format and decode identically to reveal their creation timestamp.
Mention Format Parsing
Handles pasted Discord mentions like <@123456789>, <#123456789>, and <@&123456789> by automatically stripping the formatting characters to extract the raw Snowflake ID for decoding.
URL Disassembly
Parses Discord message and channel links (discord.com/channels/guildId/channelId/messageId) to extract and decode each Snowflake ID separately, showing creation dates for the guild, channel, and message.
Works Without API Authentication
Decodes Snowflake IDs entirely through mathematical operations (right-shift by 22 bits, add Discord epoch) — no bot token, no Discord API calls, no rate limits. The creation timestamp is structurally embedded in the ID itself.
Benefits of Using Discord User ID Lookup — Resolve ID to Username, Avatar & Account Age
Why this tool matters and how it improves your daily work.
Reveals Creation Dates Discord's UI Hides
Discord shows when a user joined your server, but not when the account was created. An account that joined yesterday could have been created in 2017 (legitimate newcomer) or 20 minutes ago (ban-evading alt). The Snowflake timestamp provides the creation date that makes this distinction possible.
Decodes IDs Without Requiring Bot Infrastructure
Extracting creation timestamps from Snowflakes normally requires writing a script or setting up a bot with API access. The lookup does the bit-shifting math in your browser — right-shift by 22 bits, add Discord's epoch (1420070400000ms) — without any setup, authentication, or code.
Identifies Bot Farm Patterns Across IDs
Multiple suspicious accounts created on the same day — or within minutes of each other — is a strong signal of a bot farm. By decoding IDs systematically, patterns emerge that aren't visible from individual lookups: 12 accounts all created on November 3rd between 2:14 PM and 2:47 PM is not a coincidence.
Parses IDs Directly From Copied Mentions and URLs
Instead of manually stripping <@> from <@123456789> or extracting IDs from discord.com/channels/123/456/789 URLs, paste the raw mention or URL directly. The parser handles all Discord mention formats and URL structures, extracting every ID for individual decoding.
Common Use Cases
Real scenarios where this tool saves time and produces better results than manual methods.
Ban-Evasion Alt Account Detection
A moderator checking a newly joined member who immediately started posting invite links — the Snowflake reveals the account was created 14 minutes ago, confirming it's a ban-evading alt. Comparing creation dates of multiple suspicious accounts also reveals if they were created in a batch (same minute, same worker process), indicating a bot farm.
Trust and Safety Investigation
A safety team analyzing a coordinated harassment report — decoding the reported users' IDs shows they were all created within a 3-hour window on the same date, strengthening the case for a coordinated attack rather than independent bad actors.
Server Audit and Channel Provenance
A server owner reviewing permissions who finds unfamiliar channels and roles — decoding their Snowflake IDs reveals the channels were created at 3 AM by a since-departed admin, confirming they weren't part of the original server setup and may need removal.
Bot Development Age-Gate Implementation
A bot developer building an auto-moderation feature that restricts accounts under 7 days old from posting links — using the Snowflake decode algorithm as a reference implementation for the age check in their bot code.
Who Uses This Tool
Server Moderators
checking the creation date of new members who behave suspiciously — identifying accounts created minutes ago that are likely ban-evading alts, and detecting batch-creation patterns across multiple IDs that indicate bot farms
Trust and Safety Teams
investigating coordinated harassment reports by decoding multiple reported users' IDs to find creation-date patterns — accounts created in the same hour on the same day strengthen the case for coordinated action
Bot Developers
referencing the Snowflake decode algorithm for implementing age-gate features in their bots — restricting accounts under a certain age from posting links, creating automatic verification requirements, or flagging recently created accounts for manual review
Pro Tips
Practical advice to get the most out of this tool, based on how experienced users actually work with it.
Keep a log of suspicious IDs and their decoded creation dates. Patterns emerge over time — if 8 problem accounts were all created on November 3rd between 2:14 and 2:47 PM, you're dealing with a bot farm, not individual bad actors. This log also helps when escalating to Discord's Trust & Safety team.
Use the worker ID and increment values from decoded Snowflakes to identify batch creation. Two accounts with timestamps 300ms apart, same worker ID, and increment values of 1 and 2 were created consecutively by the same Discord process. This is stronger evidence of automation than just similar creation dates.
When implementing an age-gate in your bot, use the Snowflake decode algorithm directly rather than making API calls: const timestamp = (BigInt(id) >> 22n) + 1420070400000n; const age = Date.now() - Number(timestamp);. This is faster than API calls, works without rate limits, and doesn't require any privileged intents.
Decode message URLs to verify timeline claims. If someone says a message was sent "last week" but the Snowflake shows it was created 3 months ago, the message was edited or the claim is false. The creation timestamp in a message ID is immutable — editing the message content doesn't change the ID.
Frequently Asked Questions
Quick answers to the most common questions about this tool. If your question isn't here, contact our support team.