All Developer Utilities
100% Client-Side · Tokens Never Leave Your Browser
JWT Token Decoder & Expiration Inspector
Inspect JSON Web Token headers, claims, and human-readable expiration timestamps, or verify HMAC signatures locally.
Token Active (Expires in 2191d)
Encoded JWT String
● Header● Payload● Signature
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6ImJpZ29zbGF0ZS1lZGdlLWtleS0wMSJ9.eyJzdWIiOiJ1c3JfOTRhOGYzMmMiLCJuYW1lIjoiSmFzcGFsIEFycm9yYSIsInJvbGUiOiJzdGFmZl9lbmdpbmVlciIsImlzcyI6Imh0dHBzOi8vd3d3LmJpZ29zbGF0ZS5jb20iLCJhdWQiOiJiaWdvc2xhdGUtYXBpIiwiaWF0IjoxNzMxNzQ0MDAwLCJleHAiOjE5MjEwNDY0MDB9.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
For HS256 / HS384 / HS512 tokens, enter your signing secret to verify authenticity locally:
Decoded HeaderAlgorithm & Token Type
{
"alg": "HS256",
"typ": "JWT",
"kid": "bigoslate-edge-key-01"
}Decoded PayloadClaims & Data
{
"sub": "usr_94a8f32c",
"name": "Jaspal Arrora",
"role": "staff_engineer",
"iss": "https://www.bigoslate.com",
"aud": "bigoslate-api",
"iat": 1731744000,
"exp": 1921046400
}Claims Breakdown & Timestamp Inspector
subSubject — Identifier of the user or entity
usr_94a8f32c
nameFull Name — Profile claim
Jaspal Arrora
roleAuthorization Role — Custom RBAC claim
staff_engineer
issIssuer — Principal that issued the JWT
https://www.bigoslate.com
audAudience — Recipient(s) that the JWT is intended for
bigoslate-api
iatIssued At — Unix timestamp when the token was issued
1731744000 (2024-11-16T08:00:00.000Z · in 0m)
expExpiration Time — Unix timestamp after which token is invalid
1921046400 (2030-11-16T08:00:00.000Z · in 2191d)
How Stateless JWT Authentication Works
Base64URL Encoding Is Not Encryption
Anyone who intercepts a JWT can decode its Header and Payload in O(N) time because they are simply Base64URL-encoded JSON strings. What prevents tampering is the third segment: the cryptographic signature. If an attacker modifies "role": "admin" in the payload, the server's HMAC/RSA hash check immediately fails.