Algorithm
HS256
Inspect a JWT locally in your browser, pretty-print the header and payload, and convert common timestamp claims into readable dates. This tool decodes tokens but does not verify trust or signatures.
Paste a compact three-part JWT. The signature segment is shown as text only and is not validated.
A JWT normally has three Base64URL-encoded segments separated by dots: header, payload, and signature. This page decodes the first two segments, parses them as JSON when possible, and shows common claims such as iat, nbf, and exp in your local time.
Decoding is not the same as verification. The signature must be checked by your application or identity provider using the correct key material. Treat the payload as untrusted until it has been verified elsewhere.
JWTs follow the JSON Web Token compact serialization format defined by the JOSE standards. The typical wire format is header.payload.signature.