Developer

Snowflake ID Decoder

Decode a Snowflake ID into its creation timestamp, worker, process and sequence numbers. Presets for Discord, Twitter/X, Instagram and Mastodon, plus a custom epoch mode.

Last reviewed by the Radiatus Cloud team

Decoded fields appear here.

Build an ID from a date

The smallest ID for that instant appears here.

Need this built for your product?

We design, build & host secure software & APIs.

Talk to an engineer

An ID that carries its own timestamp

A Snowflake is a 64 bit integer with structure. The high bits hold a millisecond timestamp measured from a custom epoch chosen by the platform, the middle bits identify the machine and process that minted it, and the low bits are a per millisecond counter. Twitter designed the scheme so that a distributed system could generate roughly ordered unique identifiers without coordinating through a central sequence, and Discord, Instagram, Mastodon and many internal systems adopted the same layout.

Why the epoch matters

The timestamp is not a Unix timestamp. Each platform subtracts its own epoch before storing the value, so decoding a Discord ID with the Twitter epoch gives an answer that is wrong by about four and a half years. Discord uses 1 January 2015, Twitter uses 4 November 2010, and Instagram uses 1 January 2011. Getting this wrong is the single most common decoding mistake, and it produces a plausible looking date rather than an obvious error.

What the fields are useful for

Reading the timestamp out of an ID answers questions that otherwise need an API call: when an account was created, when a message was posted, whether two records were created in the same millisecond. The worker and process fields identify which node generated the ID, which is occasionally useful when investigating duplicates or a clock skew incident. The sequence counter shows how many IDs that node issued within the same millisecond.

Related tools

  • JSON Formatter — Format and beautify JSON in your browser. Pinpoints syntax errors by line and column, flags unsafe integers, and never uploads your data to a server.
  • JSON Validator — Validate JSON syntax with precise line and column errors, and check documents against a JSON Schema. Runs locally in your browser, nothing uploaded.
  • Regex Tester — Test regular expressions against sample text with live match highlighting, capture groups and flag control. Runs entirely in your browser.
  • HTML Minifier — Minify HTML by removing comments and redundant whitespace, without breaking inline elements or pre blocks. Runs entirely in your browser.

Frequently Asked Questions

Which epoch should I choose?

Match the platform the ID came from. Discord uses 2015-01-01, Twitter and X use 2010-11-04, Instagram uses 2011-01-01 and Mastodon stores a plain Unix millisecond timestamp. If the decoded date looks wrong by a few years, the epoch is the reason.

Why does JavaScript get the wrong answer in my own code?

Because a 64 bit Snowflake exceeds the 53 bit safe integer range of a JavaScript number, so ordinary arithmetic loses the low bits. This tool uses BigInt, which is the correct approach in any browser code that touches these IDs.

Can I get the ID back from a timestamp?

Yes. Enter a date in the reverse section and the tool builds the smallest ID for that instant, which is exactly what Discord API pagination before and after parameters expect.

Is the worker ID meaningful to me?

Only operationally. It identifies the machine and process inside the issuing platform, so it is useful for spotting that a run of duplicate looking records all came from one node, and not much else.

Does decoding an ID reveal private information?

It reveals only the creation time and the issuing node, both of which are already implied by the ID. Nothing is looked up and nothing is sent anywhere: the arithmetic happens in your browser.

Privacy & Security

Everything runs in your browser; nothing is uploaded.

Data: None
Client-side-Side
Active
v1.0

How to Use

Paste a Snowflake ID, choose the platform whose epoch it uses, and read the decoded timestamp and fields.

Disclaimer: This tool is provided "as is" without warranty of any kind. Results are for educational and utility purposes.