Every coffee helps keep the servers running. Every book sale funds the next tool I'm dreaming up. You're not just supporting a site — you're helping me build what developers actually need.
A JSON Web Signature (JWS) in compact serialization format consists of three Base64URL-encoded parts separated by dots, as defined in RFC 7515.
BASE64URL(UTF8(JWS Protected Header)) || '.' ||
BASE64URL(JWS Payload) || '.' ||
BASE64URL(JWS Signature)
| Component | Description | Example Content |
|---|---|---|
| Header | Contains algorithm (alg) and token type (typ). May include key ID (kid) for key selection. |
{"alg":"HS256","typ":"JWT"} |
| Payload | Contains the claims (data). For JWT, includes registered claims like iss, sub, exp, etc. |
{"sub":"1234567890","name":"Anish Nath","iat":1516239022} |
| Signature | Cryptographic signature over the header and payload, computed using the specified algorithm. | 9tFLrurxXWKBDh317ly24fP03We-uzSZtPf7Yqy_oSw |
When the JWS payload contains a JWT, these registered claims may be present:
| Claim | Name | Description |
|---|---|---|
iss | Issuer | Identifies the principal that issued the JWT |
sub | Subject | Identifies the subject of the JWT |
aud | Audience | Identifies the recipients the JWT is intended for |
exp | Expiration Time | Time after which the JWT must not be accepted |
nbf | Not Before | Time before which the JWT must not be accepted |
iat | Issued At | Time at which the JWT was issued |
jti | JWT ID | Unique identifier for the JWT |