Base64 Encoder/Decoder
Encode text to Base64 or decode it back, with full Unicode support.
Inspect the header, payload and signature of a JSON Web Token and see when it was issued and when it expires.
Runs in your browser. Your input is never uploaded.
Paste a JWT (three dot-separated parts).
Review the decoded header and payload.
Check the status badge for expiry and the timestamps for iat, nbf and exp.
Input
Use the Sample button to load an unsigned demo token.Encode text to Base64 or decode it back, with full Unicode support.
Convert Unix timestamps to dates and back, in UTC and local time.
Generate SHA-256, SHA-384 and SHA-512 hashes with Web Crypto.
Format, beautify and minify JSON with custom indentation.
No. Decoding only reads the Base64URL-encoded parts. Anyone can create a token with any claims, so never trust a decoded token without verifying its signature on your server.
Processing is local and the token is not stored, but treat live tokens as secrets anyway and prefer test tokens when possible.
The exp claim is a Unix time in seconds. If it is earlier than your device clock, the token is expired.
A beginner-friendly explanation of JSON Web Tokens: structure, claims, signing, expiry, and the security mistakes to avoid.
How Base64 works, why it exists, how much it inflates data, URL-safe Base64, Unicode pitfalls and when not to use it.
Decoding is not verification. This tool only reads the token; it does not check the signature, so a decoded token may be forged. Your token is processed in this browser tab only, is never sent to any server and is never stored.