JWS Parser & Decoder

By Anish Nath - Security Engineer & Cryptography Expert | @anish2good | Last Updated: January 23, 2025
Privacy-First No Tokens Stored 100% Free

JWS Input
Format: header.payload.signature (Base64URL encoded)
Parsed Output

Parsed JWS components will appear here

Paste a JWS token and click "Parse JWS"


Support This Free Tool

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.

500K+ users
200+ tools
100% private
Privacy Guarantee: Private keys you enter or generate are never stored on our servers. All tools are served over HTTPS.

Understanding JWS Structure

A JSON Web Signature (JWS) in compact serialization format consists of three Base64URL-encoded parts separated by dots, as defined in RFC 7515.

JWS Compact Serialization Format

BASE64URL(UTF8(JWS Protected Header)) || '.' ||
BASE64URL(JWS Payload) || '.' ||
BASE64URL(JWS Signature)

JWS Components

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

JWT Registered Claims

When the JWS payload contains a JWT, these registered claims may be present:

Claim Name Description
issIssuerIdentifies the principal that issued the JWT
subSubjectIdentifies the subject of the JWT
audAudienceIdentifies the recipients the JWT is intended for
expExpiration TimeTime after which the JWT must not be accepted
nbfNot BeforeTime before which the JWT must not be accepted
iatIssued AtTime at which the JWT was issued
jtiJWT IDUnique identifier for the JWT
Security Note: Parsing a JWS only decodes its contents - it does NOT verify the signature. An attacker can modify the payload of an unsigned or improperly verified token. Always verify signatures before trusting token contents in production systems.