Timestamp decoder
Paste a timestamp, ID or date in any format. You get every way to read it, most likely first, and any time written in every format.
Most likely
Example: paste your own timestamp, date or ID above.
- UTC (ISO 8601)
- 2022-02-22T19:22:22Z
- UTC (ISO 8601)
- 2022-02-22T19:22:22Z
- Unix seconds
- 1645557742
The first 48 bits are Unix time in milliseconds; the rest is random.
A time in every format
now, liveThe current time in every format appears here once the page has loaded.
How it works
Programs store time in many ways. Most count something from a fixed starting point, called an epoch: Unix time counts seconds from 1 January 1970, Windows counts 100-nanosecond steps from 1601, and Excel counts days from 1900. The same number can mean very different dates, so this page tries every format it knows and ranks the readings that land between 1990 and 2100 first.
Some IDs carry their creation time. UUID versions 1, 6 and 7, ULIDs, Snowflake IDs (used by X and Discord), MongoDB ObjectIds and KSUIDs all start with a timestamp. That's useful when you need to know when a record or message was made. A version 4 UUID is random and holds no time.
Watch for zones. Unix time and most IDs are UTC. Excel serials, .NET ticks and ISO 8601 dates without an offset carry no zone at all, so they're shown as if they were UTC. GPS time ignores leap seconds and is 18 seconds ahead of UTC; that's corrected here.
For plain Unix timestamps, the epoch converter has more detail, and the batch epoch converter handles a whole log. To check the Date line of an email, use the Email Date checker.