JWT Decoder
Inspect a JWT header and payload without uploading the token.
Open tool →Convert Unix timestamps to ISO and local dates, or turn a local or UTC date into exact Unix seconds and milliseconds.
Set the source unit before converting. UTC output describes an instant; a timezone-free date entry uses the selected local or UTC interpretation. Local displays depend on the device timezone.
| Input or check | Expected result or decision |
|---|---|
| 0 seconds | 1970-01-01T00:00:00.000Z |
| 1 second or 1000 milliseconds | 1970-01-01T00:00:01.000Z |
| 2026-10-05T12:00 interpreted as UTC | The intended instant is 2026-10-05T12:00:00.000Z; local interpretation may differ. |
| New York DST overlap: 2026-11-01 01:30 | 1793511000 seconds (2026-11-01T05:30:00.000Z, UTC−04:00) or 1793514600 seconds (2026-11-01T06:30:00.000Z, UTC−05:00). The wall-clock time occurs twice. Enter explicit seconds; local displays depend on the device timezone. |
A seconds-versus-milliseconds mismatch produces a very different date. Check the unit used by the source API before converting.
These tools open separately; inputs are not transferred.
Inspect a JWT header and payload without uploading the token.
Open tool →Pretty-print, minify, and validate JSON directly in your browser.
Open tool →Convert between common length, weight, and temperature units instantly.
Open tool →Convert text to Base64 and back, entirely in your browser.
Open tool →Timestamp conversion happens in your browser and is not sent to an Anvil processing server.
Seconds and milliseconds can be confused. Local output depends on the device time zone, and historical or future daylight-saving rules may differ by platform.
Unix time counts elapsed seconds from 1970-01-01 00:00:00 UTC. Many JavaScript APIs use milliseconds instead.
A Unix timestamp identifies one instant. The tool shows that instant in UTC and your browser’s local zone. Date input is interpreted according to the option you choose.
Confirm whether the source uses seconds or milliseconds and whether you are reading UTC or local output. The device timezone affects local values. Out-of-range numbers and invalid calendar input need correction before conversion.
They display the same instant using different timezone rules. Share the UTC value or an explicit timezone when communicating timestamps between systems.
No. Local time displays and comparisons depend on the device and browser. Confirm your device clock and the source timestamp unit when results look unexpected.
Debug API Data with JSON, Base64, and Browser Tools
Work through JSON types, encoding, URL components, JWT claims, hashes, CSV conversion, and timestamps with small reproducible examples.