BrowserTools

Discord ID Lookup

Decode IDs into account & server dates

By Guga — BrowserTools maintainer, Tbilisi, Georgia Updated 2026-08-25
Free Private No uploads
What is Discord ID Lookup?

Discord identifiers are snowflakes: 64-bit numbers whose top 42 bits hold a creation time in milliseconds counted from Discord's epoch of 1 January 2015. Paste one and the page shifts the value right by 22, adds the epoch, and prints a genuine date. The remaining 22 bits are decoded too — five bits of internal worker id, five of process id, twelve of a per-process increment — which is what makes the numbers sequential within a process rather than random. Up to twenty-five identifiers can be pasted at once, separated by spaces, commas or line breaks, and each earns its own card with the date in your timezone, the same instant in UTC, an age in days and that age restated in years. Anything that is not one to twenty digits is flagged as invalid on its own card instead of corrupting the batch. No request is made.

Paste any Discord ID (user, server, message, channel) and decode the snowflake to reveal the exact creation date and time of that object — plus account age in days.

Private Discord ID Lookup In Your Browser

Discord ID Lookup is processed locally with client-side JavaScript. Your files never touch a server, and there is no queue to wait in.

Step-by-Step

How to use Discord ID Lookup

1

Turn on Developer Mode in Discord, then right-click a user, server, channel or message and choose Copy ID.

2

Paste the ID — or up to 25 of them separated by spaces, commas or line breaks — into the Discord ID(s) field.

3

Read each card for the creation date in local time, the same instant in UTC, and the age in days and in years.

4

Press Try a sample ID on an empty field to load 175928847299117063 and see the decoded layout.

Key Capabilities
  • All four snowflake fields are decoded — timestamp, worker id, process id and increment — rather than only the date.
  • Up to 25 identifiers can be pasted in one go, split on whitespace, commas and semicolons, each rendered as its own card.
  • Non-numeric input is rejected per item with an explicit message, so one bad value does not spoil the rest of the batch.
  • The epoch constant 1420070400000 is applied with BigInt shifts, so no precision is lost in the 64-bit arithmetic.
Common Use Cases
  • A moderator dates a new account from its identifier to judge whether a fresh registration meets the server's age rule.
  • A developer checks whether two accounts were created seconds apart, which is a strong hint that one person owns both.
  • Someone vetting a server reads the creation instant of its identifier to find out how long that server has actually existed.
Clear Answers

Frequently Asked Questions

Which kinds of object can be decoded this way?
Any snowflake: user, guild, channel, message, role or webhook. They all come from the same counter, so the leading bits mean the same thing for all of them. What the number does not reveal is the object's type, its name, or any detail about the account behind it.
Why does one id decode to a date before 2015?
The low 42 bits of a snowflake timestamp are not validated when the value is created, so a number whose decoded instant predates the epoch can be produced by hand rather than issued by Discord. Treat anything earlier than 1 January 2015 as a sign the digits were not generated by the real counter.
Should I be careful about pasting an ID into a public page?
An id is not a credential — it cannot be used to sign in or to act as the account. It does let anyone who already has access to the object look it up, which is the reason Discord hides identifiers behind Developer Mode in the first place. Nothing is transmitted by this tool either way.
Can it tell me when somebody joined a server?
No. Joining is a separate record with its own timestamp, and this only reads the creation instant encoded in the number itself. For join dates you would need the server audit log, or a bot holding the permissions that expose it.