JWT decoder
I-decode ang JWT
Tumatakbo sa iyong browser · Walang upload
Nasa Ingles pa sa ngayon ang tool na ito at ang mga tagubilin sa pahinang ito. Pareho itong gumagana: lahat ay tumatakbo sa iyong browser.
Header
Payload
Claims
| Claim | Value | Meaning |
|---|
Check the signature
Masyadong luma ang iyong browser para patakbuhin ang tool na ito. Paki-update ito, o gumamit ng kasalukuyang bersyon ng Chrome, Edge, Firefox o Safari.
- Walang umaalis sa iyong device
- Walang limitasyon sa laki mula sa server
- Walang sign-up, walang watermark
- Libre
How to decode a JWT
- Paste the token (with or without "Bearer ").
- Read the header, payload and claims; times such as exp and iat are shown as dates.
- To check that it is genuine, open "Check the signature" and enter the secret or public key.
Why decode it here?
Tokens are keys to accounts and APIs. Many online decoders send what you paste to a server. This page can't: its security policy blocks every connection, so the token, and any key you enter, stay on your device.
Decoding is not verifying
- Anyone can read a JWT: the header and payload are only Base64-encoded, not encrypted.
- Only the signature check proves the token was issued by the key holder and wasn't changed.
- Supported: HS256/384/512 (shared secret), RS256/384/512, PS256/384/512, ES256/384/512 (public key as PEM or JWK) and EdDSA where the browser supports it.
- Encrypted tokens (JWE, five parts) can't be read without the private key.
Mga madalas itanong
Should I paste a private key?
No, and you never need to: signatures are checked with the public key. Only HMAC tokens (HS256…) use a shared secret.
Is my token uploaded?
No. It is decoded and checked in your browser with the built-in WebCrypto API.