Read instructions, examples, and limits
Decodes only. Signatures are not verified. Do not use this output to decide whether a token is authentic.
Decode JWT headers and payloads, with readable dates and expiry.
Paste a three-part token and compare the header and payload with the claims your application expects. Numeric iat, nbf, and exp values are interpreted as Unix seconds and shown as ISO dates. A milliseconds value in one of these claims therefore produces an unexpected date and is a useful clue when debugging the issuing code.
Expired describes the numeric exp claim relative to the current clock. Not expired only means that claim lies in the future; it does not mean the signature is valid, the issuer is trusted, or the token authorizes an action. This tool performs decoding only. Use a server-side verification library and the expected signing keys for authentication decisions. Treat actual tokens as credentials and avoid sharing their decoded contents in public bug reports.
Processing stays in this tab. Input and generated content are not uploaded or stored.
All processing runs locally in your browser. This tool is provided as-is without warranty. Keep backups of your original files before processing.
By selecting media, you confirm you own the content or have permission to modify it. Please read the Terms and Conditions.