Timestamp & ID decoder
Paste a UUID, ULID, snowflake, ObjectId, JWT or any timestamp. The decoder finds the format and shows the time it carries. Nothing leaves your browser.
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
| Format | Example | Time precision | Guide |
|---|---|---|---|
| Unix seconds, ms, µs, ns | 1700000000 | Digit count (10, 13, 16, 19) | Epoch converter |
| ISO 8601 / RFC 3339, RFC 2822 | 2026-11-14T10:00:00Z | Exact to the nanosecond | ISO 8601 guide |
| UUID v1, v6, v7 | 017f22e2-79b0-7cc3-… | 100 ns (v1, v6), 1 ms (v7) | UUID timestamp |
| ULID | 01ARYZ6S41TSV4RRFFQ69G5FAV | 1 ms | ULID decoder |
| Discord and X/Twitter snowflakes | 175928847299117063 | 1 ms | Snowflake to date |
| MongoDB ObjectId | 507f1f77bcf86cd799439011 | 1 s | ObjectId timestamp |
| KSUID | 0ujtsYcgvSTl8PAuAdqWYSMnLOv | 1 s | KSUID decoder |
| JWT iat, nbf, exp | eyJhbGciOi… | 1 s | JWT expiry |
| Firebase push ID | -JhLeOlGIEjaIOFHR0xd | 1 ms | Push ID timestamp |
| Bluesky / AT Protocol TID | 3jzfcijpj2z2a | 1 µs | TID decoder |
| Windows FILETIME / LDAP | 132000000000000000 | 100 ns | LDAP timestamp |
| .NET DateTime ticks | 637134336000000000 | 100 ns | .NET ticks |
| Chrome / WebKit time | 13300000000000000 | 1 µs | Chrome time |
| Apple Cocoa / Core Data | 694224000 | 1 s | Cocoa time |
| Excel / OLE Automation date | 45000.5 | Fraction of a day | Excel date |
| Hex Unix time | 0x65538b80 | 1 s | Hex timestamp |
What the decoder does not do
- It does not verify JWT signatures. It reads the
iat,nbfandexpclaims 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: