AES-Verschlüsselung erklärt: Wie sie funktioniert und warum sie wichtig ist
Jun 23, 2026
Validate the signature of the JWT token pasted in the Decode tab.
Generate a new JWT token with custom header and payload.
JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way to securely transmit information between parties as a JSON object. This information can be verified and trusted because it is digitally signed.
JWTs are commonly used for authentication and authorization in web applications, mobile apps, and API services. A JWT consists of three parts separated by dots (header.payload.signature), each encoded in Base64url format.
JWT stands for JSON Web Token, an open standard for securely transmitting information between parties as a JSON object.
Yes! The header and payload of a JWT are only Base64url-encoded, not encrypted. Anyone can decode them to read the contents. The signature is what prevents tampering — you need the key to verify it.
Yes. All processing happens 100% client-side in your browser. Your tokens are never sent to any server. You can verify this by checking the Network tab in your browser's developer tools.
HS256 (HMAC with SHA-256) uses a single shared secret key for both signing and verification. RS256 (RSA with SHA-256) uses a private key to sign and a public key to verify, making it suitable for scenarios where the verifier shouldn't be able to create new tokens.
The tool checks the exp (expiration) claim in the payload. If the token's expiration time has passed, it shows "Expired". If there is no exp claim, it shows "No expiration set" — which is generally not recommended for security.
Blog
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026