JWT Encoder & Signer

Edit a JWT header and payload, sign it with HMAC, RSA, RSA-PSS or ECDSA, and copy the compact token.

Header and payload

Edit the JSON. The token is signed again after each valid change, in this browser only.

Time claims
exp =

Signing key

Signed token

—

Header · Payload · Signature

Opens in a new tab. Paste the copied token there; it is never put in the link.

How is a signed JWT built from a header and a payload?

A compact JWT joins the Base64URL-encoded header, the Base64URL-encoded payload and the signature with dots. The signature covers the first two parts exactly as written (RFC 7515 §5.1). For HMAC, use a key at least as long as the hash output: 32 bytes for HS256 (RFC 7518 §3.2).

Keep HS256 and press Random secret. Use exp +1 hour, copy the token, and paste it into the decoder with the same secret to see Signature verified. For RS, PS or ES algorithms, generate a test key pair here and give the decoder the public key. Sign only test tokens in a web page.