Developer tools
Decode, test, and convert the things you meet every day.
- JWT DecoderDecode a JSON Web Token, read its claims and expiry, and verify HS256 signatures with a secret.
- Base64 Encode & DecodeEncode text or files to Base64 and decode it back. Base64 to image preview, URL-safe option.
Which tool do I need?
If you have a long token starting with eyJ from a login or an API header, paste it into the JWT Decoder to read who it belongs to and when it expires. If you have a block of letters, numbers, + and / (often ending in =), or you need to put a file or image into text, use Base64 Encode & Decode.
Is Base64 encryption?
No. Base64 only rewrites bytes as plain text characters so they can travel through email, URLs and JSON. Anyone can decode it in a second, with no key. Never use it to hide passwords or secrets.
Does decoding a JWT mean it is valid?
No. The header and claims of a JWT are just Base64 text, so anyone can read them, and anyone can write a token that says anything. Only the signature proves who issued it. The JWT Decoder can check HS256, HS384 and HS512 signatures if you have the shared secret. Tokens signed with RS256, ES256 and other public-key methods must be checked by your server or library with the issuer's public key.
Is it safe to paste tokens here?
Decoding and verifying run in your browser, so nothing is sent to a server. Even so, treat live tokens and secrets like passwords, and prefer expired or test tokens when you can.