JWT Signer & Verifier
Create and verify JSON Web Tokens (JWT) with HMAC (HS256) or RSA (RS256) signatures. All keys remain completely in your browser.
JWT Signing Options
KI-Diagnosebericht freischalten
Gib deine E-Mail-Adresse ein, um den detaillierten KI-Lösungsbericht mit konkreten Optimierungsvorschlägen und Schritt-für-Schritt-Anleitungen kostenlos freizuschalten.
Guide & best practices
JWT Signer to create signed tokens
Build test JWTs with the right algorithm, claims and validity – ideal for developing and debugging auth flows.
Typical use cases
Useful for API testing, OAuth/OIDC development, reproducing token scenarios and learning the JWT structure.
How Balou signs JWTs
Choose algorithm and key/secret, set claims and times; Balou generates the signed token client-side.
JWT signing best practices
Use sufficiently long secrets or real key pairs for RS256/ES256, set short exp times and never enter production keys.
Frequently asked questions
What is the difference between HS256 and RS256?
HS256 is symmetric (one shared secret), RS256 is asymmetric (private signing key and public verification key).
Which claims should I set?
Sensible ones are iss, sub, aud, exp and iat; aud and iss help with targeted validation.
Does my secret/key stay client-side?
Yes, signing runs locally; never enter real production secrets or keys.
What is the kid header for?
The Key ID points to the key used and eases key rotation with multiple keys.