What signing algorithms are supported?

The tool supports HMAC-based algorithms: HS256, HS384, and HS512, which use a shared secret key for signing and verification.

Can I use this to test my authentication API?

Yes. Generate a token with your API's expected claims and secret to create test tokens for your development or staging environment.

What claims should I include?

Common standard claims are "sub" (subject/user ID), "exp" (expiration Unix timestamp), "iat" (issued at), and "iss" (issuer). Add any custom claims your application needs.

Is my secret key safe?

Token generation happens entirely in your browser. Your secret never leaves your device. Still, avoid using real production secrets with any online tool.

Outils de Développement

Générer des tokens JWT avec des en-têtes et charges utiles personnalisés

Générateur JWT

Générer des tokens JWT avec des en-têtes et charges utiles personnalisés

100% OfflinePrivacy FirstInstant

Génération JWT

En-tête (JSON)

Charge Utile (JSON)

Clé Secrète

Token JWT Généré

JWT

Le token JWT généré apparaîtra ici...

Learn more about JWT Generator

About JWT Generator

Create signed JSON Web Tokens with custom payloads for testing, development, and debugging. Choose your signing algorithm, set the secret key, add any claims, and generate a valid JWT instantly.

Key features

Supports HS256, HS384, and HS512 algorithms
Custom payload with any JSON claims
Set expiration time and issued-at claims
Copy generated token with one click
Runs entirely in browser — secret never transmitted

How to use JWT Generator

1Enter your signing secret key
2Choose the algorithm (HS256, HS384, or HS512)
3Add your payload claims as JSON key-value pairs
4Click "Generate JWT" and copy the result

Frequently asked questions

What signing algorithms are supported?: The tool supports HMAC-based algorithms: HS256, HS384, and HS512, which use a shared secret key for signing and verification.
Can I use this to test my authentication API?: Yes. Generate a token with your API's expected claims and secret to create test tokens for your development or staging environment.
What claims should I include?: Common standard claims are "sub" (subject/user ID), "exp" (expiration Unix timestamp), "iat" (issued at), and "iss" (issuer). Add any custom claims your application needs.
Is my secret key safe?: Token generation happens entirely in your browser. Your secret never leaves your device. Still, avoid using real production secrets with any online tool.