Check JWT expiry values
Turn iat, exp, and nbf numbers into readable dates when debugging auth flows.
브라우저 내부 처리
Convert between Unix timestamps and human-readable dates.
Turn iat, exp, and nbf numbers into readable dates when debugging auth flows.
Compare epoch values against both local time and UTC so incident timelines line up with alerts, dashboards, and user reports.
Move between seconds and milliseconds when checking campaigns, scheduled jobs, or delayed message sends.
Ten digits usually means seconds and thirteen usually means milliseconds, but the safest check is always the source system documentation.
Local time is easier for people, while UTC is the safer reference for systems, logs, and cross-region debugging.
The conversion runs in the browser. You should still account for your own device, extensions, and operational security policies.
A ten-digit Unix timestamp is seconds; thirteen digits is milliseconds. Reading milliseconds as seconds lands in the 1970s, and the reverse lands tens of thousands of years out. An absurd result usually means the wrong unit, not bad arithmetic.
A Unix timestamp carries no time zone. The same number displays as 18:00 in Seoul and 09:00 in London. When comparing logs from servers with different display zones, one event appears at two different times.
Systems storing seconds in a signed 32-bit integer overflow in January 2038. It still turns up in older embedded devices and legacy database columns. If you handle expiry or future dates, check the column type.