utility·Updated 2026-05-20

Discord ID Lookup

Decode any Discord snowflake into its creation timestamp, worker / process / counter fields — all client-side via BigInt. No API call, no rate limit.

Client-side BigInt · No Discord API call · No rate limit

Snowflake decoder

Discord IDs (one per line)

Up to 50 IDs at once. Works on user / message / channel / guild / role IDs.

15514910818369536010.3yr ago

Created

2016-03-04 03:07:09 UTC

Worker

Process

Counter

Age

10.3yr ago

12098765432109876542.3yr ago

Created

2024-02-21 14:57:26 UTC

Worker

Process

Counter

134

Age

2.3yr ago

No sign-up required. Use the tool, share the result, leave — no account needed.

Client-side computation. Calculations run entirely in your browser; we never see your inputs.

Embed in OBS / Discord. Append ?embed=1 to the URL for a bare iframe-ready widget.

How to use this tool

3 steps · ~30 seconds

Each step is a single action — no setup, no sign-up. Outputs are client-side; nothing is uploaded.

Step 01

Paste IDs

Copy a Discord ID — right-click a user / message / channel in Developer Mode → "Copy ID" — and paste it into the field. One ID per line; up to 50 at once.

Step 02

Read the decoded fields

Each row shows the embedded creation timestamp, age (e.g. "2.4yr ago"), worker / process IDs, and counter — all extracted client-side, no API call.

Step 03

Copy the date or share the link

Click "Copy date" to grab the timestamp, or use the share-bar to send a link with all your inputs encoded so the recipient sees the same decoded result.

FAQ · methodology & caveats

Frequently asked.

Calculator outputs are estimates. Each Q below names the source data and the assumptions baked in.

What is a Discord snowflake?

Every Discord ID — user, message, channel, guild, role — is a 64-bit integer called a snowflake. The top 42 bits encode milliseconds since Discord's epoch (2015-01-01 UTC), the next 5 bits encode the worker ID, the next 5 bits the process ID, and the last 12 bits a per-process counter. The decoder pulls all four fields out without any API call.

Is decoding a Discord ID against ToS?

No — Discord snowflakes are public by design. The creation timestamp is embedded in every ID and is meant to be readable. The decoder does NOT contact Discord, does NOT look up user data, and does NOT reveal anything Discord considers private (username, email, IP, server membership, etc).

Does it work on message / channel / guild / role IDs?

Yes — every snowflake follows the same bit layout regardless of what kind of entity it points to. Paste any Discord ID and the decoder extracts the embedded timestamp.

Why are some IDs flagged "wrong length"?

Discord IDs are 17–19 digits (sometimes 20 in 2026+). Anything shorter is from a different platform (Twitter, YouTube, Steam — different snowflake formats) or simply malformed. The decoder rejects IDs outside that length to avoid silently producing nonsense timestamps.

Why BigInt?

JavaScript Number is only safe up to 2^53 — but snowflakes are 64-bit, so naive Number parsing loses the bottom bits and gives wrong timestamps. We parse via BigInt to preserve all 64 bits, then narrow to Number only for the millisecond timestamp (which fits in 53 bits comfortably).

Done with the tool? Ship the channel.

Streamrise delivers real Twitch and Kick viewer floors — residential IPs, geo-targeted, with chat presence. Same engineering rigor you saw in the calculator, on the paid side. No password requested. Cancel anytime.

See Twitch viewer pricing Or Kick viewers