Декодер JWT
Заголовок, полезная нагрузка, срок
Inspect JWT claims without touching production
Authentication bugs are often token bugs — a missing claim, a wrong audience, an expired exp, the wrong algorithm. Decoding a JWT in the browser shows you the header, payload, and expiry instantly without sending the token to any server, so you can debug login, authorization, and API access issues with confidence.
Use the decoder when you need to
Debug an expired or rejected token
Look at the exp, nbf, and iat claims to confirm whether the token is past its lifetime or not yet valid.
Verify the claims your backend expects
Check that the audience, issuer, scopes, and custom claims match what your authorization layer requires.
Audit a token before pasting it into a ticket
Decode the payload to confirm there's nothing sensitive inside before sharing the token in a bug report.
How to decode a JWT quickly
- 1
Paste the JWT (the long string with two dots) into the input field.
- 2
Inspect the decoded header, payload, and expiry status.
- 3
Copy specific claims or the full payload for use in a bug report or test.
Keep going
Decode arbitrary Base64
Use the encoder/decoder when the value isn't a JWT but is still Base64-encoded.
Test an authenticated request
Replay the request that produced the token to verify auth end-to-end.
Format the payload
Beautify the decoded payload before pasting it into another tool.
Validate the payload
Run a syntax check on custom claims if your decoder produced unusual output.
Common JWT debugging workflows
Decode the token to see if the expected claim is missing or the audience is wrong.
Confirm a freshly minted token's expiry matches your auth provider's configured lifetime.
Verify the user has the right scopes before troubleshooting authorization in your code.
Похожие инструменты
Часто задаваемые вопросы
Вставьте полный JWT (длинная строка с двумя точками между тремя частями). Инструмент сразу декодирует заголовок (алгоритм, тип) и полезную нагрузку (claims, срок, issuer) без секретного ключа.
Да. Декодирование выполняется в браузере на JavaScript; данные не уходят на сервер. JWT закодированы (Base64URL), а не зашифрованы — секрет для чтения не нужен.
Три части в Base64URL, разделённые точками: Header (алгоритм и тип токена), Payload (claims: id пользователя, exp, роли), Signature (доказательство целостности).
После вставки токена смотрите claim exp в payload: показываются Unix-время и читаемая дата, плюс индикатор, истёк ли токен сейчас.