Convert epoch seconds or milliseconds to a human date and back, with timezone awareness.
Tools for engineers who would rather not context-switch into yet another tab to validate a JWT or generate a UUID. Everything runs in your browser, your payloads never leave the machine, and the pages load fast enough that you can leave them open in a sidebar while you debug.
Count the digits: ten digits is seconds, thirteen is milliseconds. The failure mode is quiet rather than loud - a millisecond value read as seconds lands decades away from the date you expected, and a seconds value read as milliseconds collapses towards January 1970.
The epoch itself is UTC; only the display is local. Store and transmit UTC and convert at the edges, and when a value comes from a system that stored a local time without a zone there is no correct conversion - only a decision about which zone was meant.
Any system holding the value in a signed 32-bit integer runs out of range in January 2038. Modern 64-bit platforms are fine, but the value can still be narrowed on the way through a database column or a language binding - worth checking before you build something with a long horizon.