Snowflake ID & UUID v1 Timestamp Decoder

Q: What is a Twitter/X Snowflake ID?

A 64-bit ID: **41 bits ms timestamp** (epoch 2010-11-04) + 10 bits machine + 12 bits sequence. Decoding the top 41 bits gives creation time.

Q: What is a Discord snowflake?

Same structure as Twitter snowflakes but with a **2015-01-01 epoch** and 42-bit timestamp. Bigger IDs = later messages.

Q: How is time encoded in a UUID v1?

UUID v1 stores a **60-bit count of 100ns intervals since 1582-10-15** in a shuffled byte order (time-low, time-mid, time-high).

Q: How is time encoded in a MongoDB ObjectId?

The first **4 bytes (8 hex chars) are seconds since the Unix epoch**, giving creation time at second resolution.

Distributed ID schemes embed timestamps: Twitter/X Snowflake (41-bit ms since 2010-11-04), Discord snowflakes (42-bit ms since 2015-01-01), UUID v1 (100ns since 1582-10-15) and MongoDB ObjectId (4-byte seconds since epoch). Decoding them reveals creation time and sort order.

This converter takes your date-time and renders the corresponding snowflake ID, UUID v1 timestamp component, and ObjectId hex — or paste an ID to decode it back to a timestamp.

Timezone:

Enter a date-time above to see the conversion results.

Snowflake ID & UUID v1 Timestamp Decoder Quick Reference

Format	Pattern / Description	Example 1	Example 2
Twitter Snowflake	ID generated from time	2087909538001846272	2006515713438646272
Discord Snowflake	ID generated from time	1537468268544000000	1456074443980800000
UUID v1 Timestamp	Time-based UUID	1f1972376eba400	1f0e6a4d0c3c000
MongoDB ObjectId	Generated from timestamp	6a7dd4e8507f1f77bcf8	6955b900507f1f77bcf8

* Examples are rendered in UTC for the fixed sample instants above.

When to Use Snowflake ID & UUID v1 Timestamp Decoder

Event ordering forensics

Sort Discord messages or X posts by decoding snowflake timestamps when API metadata is unavailable.

Distributed ID design

Generate snowflake IDs from a chosen instant to test ordering, collision and epoch behavior before deploying.

Database key inspection

Extract creation time from MongoDB ObjectIds to profile data age without a `created_at` column.

Frequently Asked Questions

What is a Twitter/X Snowflake ID?

A 64-bit ID: 41 bits ms timestamp (epoch 2010-11-04) + 10 bits machine + 12 bits sequence. Decoding the top 41 bits gives creation time.

What is a Discord snowflake?

Same structure as Twitter snowflakes but with a 2015-01-01 epoch and 42-bit timestamp. Bigger IDs = later messages.

How is time encoded in a UUID v1?

UUID v1 stores a 60-bit count of 100ns intervals since 1582-10-15 in a shuffled byte order (time-low, time-mid, time-high).

How is time encoded in a MongoDB ObjectId?

The first 4 bytes (8 hex chars) are seconds since the Unix epoch, giving creation time at second resolution.

Related Time Format Converters

Unix Timestamp Converter (Epoch Time)

Free Unix timestamp converter. Convert epoch seconds, milliseconds, microseconds and nanoseconds to human-readable dates instantly. UTC & local time, one click copy.

Social Media Timestamp Converter

Convert dates to social media timestamp formats: Facebook, X/Twitter, Discord display and snowflake IDs. Free converter for social API development.

UTC Time Converter (Coordinated Universal Time)

Convert any local time to UTC (Coordinated Universal Time) instantly. See the UTC string, Z-suffixed ISO form and GMT equivalent. Free UTC converter.

All Format Guides

Unix Timestamp ISO 8601 ISO Week Date ISO Ordinal Date Military Time Decimal Time RFC 2822 RFC 3339 SQL Datetime Julian Date HTTP Date Excel Serial Date GPS Time UTC Time Cron Expression

Browse all 50 format guides →

Need to Convert Between All Formats?

Use the main Time Format Converter for instant conversion across 100+ formats — epoch, ISO 8601, RFC 3339, SQL datetime, military time and more in one click.

Open Time Format Converter