Timestamp decoder
Decode one raw number under every common epoch interpretation at once (Unix, Windows FILETIME, HFS+, Cocoa, LDAP, GPS, .NET ticks, Excel), flagging which give a plausible 1990-2040 date.
Timestamp decoder feeds a raw number through twelve epoch readings at once, Unix seconds among them, plus Excel serial, GPS, LDAP, .NET ticks, HFS+, Cocoa and Windows FILETIME. It prints the ISO date each one implies. A row earns a plausible flag only when its year sits between 1990 and 2040. A non-finite value is refused before any interpretation runs.
Questions
Which epochs does it try?
Twelve: Unix seconds, milliseconds, microseconds and nanoseconds, Windows FILETIME, WebKit/Chrome, HFS+, Cocoa/CFAbsoluteTime, LDAP/AD, GPS, .NET ticks and Excel serial.
What makes a row plausible?
Its resulting year falling between 1990 and 2040; every other row is still shown, flagged not plausible.
What if the value is not a finite number?
The tool refuses before trying any interpretation.
Does it tell me which interpretation is correct?
No, it only flags which are plausible; picking the right one is left to you.
What format is each date shown in?
ISO 8601, alongside whether it fell inside the plausible range.
Compare
| Tool | Runs on the CLI | Live as you type |
|---|---|---|
| Timestamp decoder | Yes | Yes |
| Timestamp & date converter | Yes | Yes |
| Cron parser / builder | Yes | Yes |
| Discord timestamp | Yes | Yes |