Current epoch — epochtime.tools · A precision instrument for time
Try:

One box for every time-carrying ID

Many IDs carry the time they were created. A UUID v7, a ULID, a Discord message ID and a MongoDB ObjectId all start with a timestamp. Paste any of them above and the decoder pulls the time out, shows it in UTC and in your timezone, and lists the other fields the ID holds.

Everything runs in your browser. Nothing you paste is sent to a server, which matters for JWTs and internal IDs. JWTs are also kept out of the page address, so they never end up in your history.

When an input fits more than one format

A long number can be several things. 132000000000000000 is a valid Windows FILETIME, a valid .NET tick count and a valid Unix nanosecond value, and each gives a different date. The decoder shows every reading that lands between 1990 and 2100, puts the one closest to today first, and labels it "most likely". If you know where the number came from, use that reading instead.

Bare Unix numbers count as certain only when they land between 2000 and 2099. A 9-digit number such as 694224000 could be Unix seconds (1992) or Apple Cocoa seconds (2023), so both are shown.

Supported formats

FormatExampleTime precisionGuide
Unix seconds, ms, µs, ns1700000000Digit count (10, 13, 16, 19)Epoch converter
ISO 8601 / RFC 3339, RFC 28222026-11-14T10:00:00ZExact to the nanosecondISO 8601 guide
UUID v1, v6, v7017f22e2-79b0-7cc3-…100 ns (v1, v6), 1 ms (v7)UUID timestamp
ULID01ARYZ6S41TSV4RRFFQ69G5FAV1 msULID decoder
Discord and X/Twitter snowflakes1759288472991170631 msSnowflake to date
MongoDB ObjectId507f1f77bcf86cd7994390111 sObjectId timestamp
KSUID0ujtsYcgvSTl8PAuAdqWYSMnLOv1 sKSUID decoder
JWT iat, nbf, expeyJhbGciOi…1 sJWT expiry
Firebase push ID-JhLeOlGIEjaIOFHR0xd1 msPush ID timestamp
Bluesky / AT Protocol TID3jzfcijpj2z2a1 µsTID decoder
Windows FILETIME / LDAP132000000000000000100 nsLDAP timestamp
.NET DateTime ticks637134336000000000100 ns.NET ticks
Chrome / WebKit time133000000000000001 µsChrome time
Apple Cocoa / Core Data6942240001 sCocoa time
Excel / OLE Automation date45000.5Fraction of a dayExcel date
Hex Unix time0x65538b801 sHex timestamp

What the decoder does not do

  • It does not verify JWT signatures. It reads the iat, nbf and exp claims so you can see when a token was issued and when it expires.
  • UUID v4 and other random IDs carry no time, so there is nothing to decode. The decoder says so instead of guessing.
  • Firestore auto-IDs are fully random, unlike Realtime Database push IDs, so they carry no time either.

Working with JSON that holds these values? jsontools.tools formats and validates it. Need a checksum for an ID or a file? hashgenerator.tools.

Last updated: