Skip to main content

Snowflake ID Decoder — Timestamp, Machine ID, Sequence

Decode a 64-bit Snowflake into timestamp, machine id and sequence, with Twitter, Discord and custom epochs, all in BigInt, browser-only

  • Runs locally
  • Category Developer & DevOps
  • Best for Formatting, validating, shrinking, or inspecting code-adjacent text.
A Snowflake ID is a 64-bit integer: a 41-bit millisecond timestamp on top, then a machine/worker id, then a per-ms sequence counter. The timestamp counts from a platform-specific epoch (Twitter and Discord differ), so pick the right one to read the real time. All decoding runs on BigInt in your browser.

Twitter default: 10 machine (5 datacenter + 5 worker) + 12 sequence. Discord uses 10 + 12 as well.

Decoded

Paste a Snowflake ID above to decode its timestamp, machine id and sequence.

What this tool does

Free Snowflake ID decoder for Twitter/X, Discord, Instagram and any custom 64-bit distributed ID. Paste a Snowflake and read its embedded millisecond timestamp (as raw ms, UTC, and your local time), the machine/worker id, and the per-millisecond sequence counter. A Snowflake packs a 41-bit timestamp into its high bits, then a machine region, then a sequence, so the value is roughly time-sortable. The timestamp is counted from a platform-specific epoch, not the Unix epoch, so the tool ships the Twitter and Discord epochs as presets and lets you set a custom epoch and bit widths for in-house schemes. Everything decodes with BigInt to stay exact past the 2^53 limit a plain Number would round at. 100% client-side, one-click copy, and a shareable URL that reopens your exact decode.

Tool details

Input
Numbers
The page exposes text boxes, numeric controls, file pickers, or structured inputs depending on the tool.
Output
Live result + Copy
The result area focuses on usable output, with copy, download, or preview actions when supported.
Privacy
Browser-side processing
The main tool logic does not call an external API, so inputs normally stay in the current tab.
Save / share
Shareable URL state
Key settings are encoded in the URL so another person can reopen the same setup.
Performance budget
Initial JS <= 9 KB
No WASM budget is declared, keeping the tool quick to open on mobile.
Best fit
Developer & DevOps · Developer
Category and role tags drive related tools, internal links, and quick fit checks.

How to use

  1. 1. Input

    Paste or drop your content into the tool panel.

  2. 2. Process

    Click the button. All processing is local in your browser.

  3. 3. Copy / Download

    Copy the result or download to disk in one click.

How Snowflake ID Decoder fits into your work

Use it in the small gaps between coding, reviewing, debugging, and shipping.

Developer jobs

  • Formatting, validating, shrinking, or inspecting code-adjacent text.
  • Preparing snippets for documentation, tickets, commits, or handoff.
  • Checking a small payload quickly without switching tools.

Developer checks

  • Run irreversible transforms like minify or obfuscate on a copy.
  • Keep secrets out of pasted snippets unless the tool explicitly stays local.
  • Use your normal tests or linter before shipping transformed code.

Good next steps

These links move the current task into a more complete workflow.

  1. 1 Bitwise Calculator AND, OR, XOR, NOT and bit shifts on integers, with decimal, hex and binary side by side, all in your browser Open
  2. 2 Number Base Converter Number base converter — binary, octal, decimal, hex, and any base 2-36. Bitwise too. Open
  3. 3 UUIDv7 Generator Time-ordered, sortable UUIDs by RFC 9562: batch generate, monotonic mode, decode the embedded timestamp, all in your browser Open

Real-world use cases

  • Audit when a Discord account was actually created

    A moderator suspects a brand-new account is evading a ban. Copy the user's Discord ID, paste it here with the Discord epoch, and the decoder shows the exact UTC creation time down to the millisecond. An account whose snowflake decodes to "three minutes ago" is a fresh alt; one from 2017 is probably genuine. No bot, no API token, no rate limit — just the time baked into the ID itself.

  • Debug out-of-order rows in a Snowflake-keyed table

    Your service generates Snowflake primary keys and a query returns rows that look mis-ordered. Paste two suspect IDs, decode both, and compare the timestamp plus the machine id. If two IDs share a millisecond and differ only by sequence, ordering by ID is correct. If one carries a wildly wrong time, you have caught a worker whose clock drifted — exactly the failure Snowflake schemes are prone to.

  • Reverse-engineer an unfamiliar platform's ID scheme

    You are integrating with an API that hands back long numeric IDs and the docs say nothing about the format. Try the Twitter and Discord epochs first; if the decoded date lands far in the future or before the company existed, adjust the custom epoch and bit widths until the time looks sane. The binary layout view makes the timestamp boundary obvious so you can lock the config down.

  • Verify a Snowflake generator you just wrote

    You built a distributed ID generator and want to confirm it stamps the right epoch, machine id and sequence. Mint an ID, paste it here with your custom epoch and bit widths, and check that the decoded timestamp matches the clock at mint time and the machine id matches the node. A round-trip that comes back clean is a quick unit-test substitute before you trust the generator in production.

Common pitfalls

  • Decoding a Discord ID with the Twitter epoch (or vice versa). The number parses fine but the date lands years off, because each platform counts ms from its own epoch. Always match the epoch preset to where the ID came from.

  • Feeding the ID through parseInt or Number first. That rounds anything past 2^53, silently corrupting the machine id and sequence. Paste the raw decimal string and let the tool's BigInt math handle the full 64 bits.

  • Assuming every Snowflake uses 10 machine + 12 sequence bits. In-house and Sonyflake-style schemes shift those widths, so the machine id and sequence come out wrong unless you set the bit widths to match the generator.

Privacy

Every step — parsing the 64-bit number, the BigInt shifts and masks, the epoch offset, and the date formatting — runs as plain JavaScript in your browser tab. No Snowflake ID is ever uploaded, logged, or sent to any server, and there is no analytics call carrying your input. The one caveat is the share link: it encodes the ID, epoch and bit widths in the URL query string, so a link pasted into chat will record those values in the recipient server's access log. For a sensitive account ID, use the copy button instead of sharing the URL.

FAQ

Tool combos

Folks in your role tend to reach for these alongside this tool.

Browse all tools for this role
Made by Toolora · 100% client-side · Updated 2026-05-29