What it is
A JSON Web Token (JWT) is a compact, URL-safe way to represent claims between two parties. It has three Base64URL-encoded parts separated by dots — header.payload.signature — where the header names the signing algorithm, the payload carries claims like who the token is for and when it expires, and the signature lets whoever holds the right key prove the first two parts weren't tampered with.
When to use it
Paste the synthetic example to see alg HS256 and sub demo. This sample has a deliberately invalid signature. Reading its claims does not authenticate them; optional HMAC checks require the correct secret.
Safe input: eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJkZW1vIn0.c2ln
Expected result: Header alg is HS256 and payload sub is demo. The synthetic signature must not be treated as valid.
Gotchas & limits
Use synthetic tokens, not production bearer tokens or secrets. This tool supports HMAC signature checks for HS256/HS384/HS512, not RSA/ECDSA. Maximum token length is 10,000 characters; malformed segments fail. Header/payload can be copied; there is no file export. Refresh resets the example, and decoding is not an authorization decision.
Complete the JSON debugging task