Snowflake ID Decoder (Discord, Twitter)
A Snowflake is a 64-bit ID that packs a millisecond timestamp, a machine identifier, and a per-millisecond sequence counter into one sortable number. Discord, Twitter/X, Instagram, and many distributed systems use them. This decoder splits the ID back into its parts: it shifts out the high bits to recover the raw timestamp, adds the platform's custom epoch to get the real UTC date and time, and breaks the low bits into the worker, process, datacenter, shard, or sequence fields that platform uses. Pick Discord (epoch 2015-01-01, 5-bit worker + 5-bit process + 12-bit increment), Twitter/X (epoch 2010-11-04, 5+5+12), Instagram (13-bit shard + 10-bit sequence), or Custom with your own epoch. The timestamp is shown as ISO UTC, your local time, a relative "x ago", and the raw epoch milliseconds. Everything runs locally; nothing is uploaded.
Timestamp
Fields
Discord epoch 2015-01-01 · Twitter/X 2010-11-04 · Instagram 2011-08-24. Decode with the platform that issued the ID.
How to use
- Choose the platform (Discord, Twitter/X, Instagram, or Custom).
- Paste the Snowflake ID — for example a Discord user or message ID.
- Read the creation timestamp and the worker / sequence fields; copy the UTC time or epoch as needed.
Frequently asked questions
- Where do I find a Snowflake ID?
- On Discord, enable Developer Mode and right-click a user, message, channel, or server to copy its ID. On Twitter/X it's the long number at the end of a tweet URL. Instagram media IDs are returned by its API. Any of these long numeric IDs can be decoded here.
- Why does each platform need a different epoch?
- A Snowflake's timestamp counts milliseconds since a chosen 'epoch' rather than the Unix epoch, which lets it fit in fewer bits. Discord uses 2015-01-01, Twitter/X uses 2010-11-04, and Instagram uses 2011-08-24. Decode with the wrong platform and the date will be off by years — pick the source that issued the ID.
- What are the worker and sequence fields?
- To generate IDs without coordination, each machine embeds its own identifier (worker/process on Discord, datacenter+worker on Twitter, shard on Instagram) plus a sequence counter that increments for multiple IDs created in the same millisecond. They let you tell which node produced an ID and roughly how busy it was.
- Is the timestamp exact?
- Yes — the millisecond timestamp is encoded directly in the ID, so the creation time is exact to the millisecond (assuming the generating server's clock was correct). The relative time is computed against your device's current clock.
Guides on this topic
Related tools
UUID Generator
Generate random version-4 UUIDs in bulk, with copy.
ULID / NanoID / CUID2 Generator
Bulk-generate ULIDs, NanoIDs, and CUID2 — modern UUID alternatives that are shorter, sortable, or collision-resistant.
Open Graph & Twitter Card Generator
Fill out a form, get a ready-to-paste `<meta>` block — Open Graph for Facebook / LinkedIn / Slack and Twitter Card tags for X / Discord.
ULID Decoder (Timestamp & Randomness)
Decode a ULID into its 48-bit creation timestamp and 80-bit randomness — Crockford Base32, case-insensitive, with the time as ISO UTC, relative, and epoch milliseconds — entirely in your browser.
UUID Inspector (Version, Variant, Time)
Paste any UUID to see its version (1–8), variant, and — for time-based v1, v6, and v7 — the embedded creation timestamp, clock sequence, and node/MAC, all decoded in your browser.
Base64 Encoder / Decoder
Encode text to Base64 or decode Base64 back to text, instantly.