OpSecForge
JWT
JSON
.env
UUID
Base64
Password
Lorem
URL
Text Case
Counter
QR
SHA
Color
Markdown
Diff
SQL
Unix
Webhook
dark
Blog
OpSecForge
JWT
JSON
.env
UUID
Base64
Password
Lorem
URL
Text Case
Counter
QR
SHA
Color
Markdown
Diff
SQL
Unix
Webhook
dark
Blog
JWT Encoder
Encode and sign JSON Web Tokens client-side
Algorithm
HS256 (HMAC + SHA-256)
HS512 (HMAC + SHA-512)
Header (JSON)
{ "alg": "HS256", "typ": "JWT" }
Payload (JSON)
{ "sub": "1234567890", "name": "John Doe", "iat": 1516239022 }
Standard Claims
Admin User
API Key
Secret Key
This key is never sent to any server
Encode & Sign JWT
Reset
Generate Secret
How it works
• JWT consists of Header, Payload, and Signature separated by dots
• Header and Payload are Base64URL encoded JSON
• Signature is HMAC using the algorithm you selected
• All encoding happens in your browser — no data is sent to any server
← Decode an existing JWT
Report a Bug
🐞
Share this:
Report a Bug
🐞