JWT sign and verify

Create a signed JSON Web Token from a header and payload, or verify a token's signature, with HS256/384/512, RS256/384/512, PS256/384/512 and ES256/384/512. Keys stay in your browser.

About JWT sign and verify

Creates a signed JSON Web Token from a header and payload you write, and verifies the signature of an existing token. It supports HMAC (HS256/384/512), RSA (RS and PS) and ECDSA (ES256/384/512), using your browser's built-in Web Crypto, so keys never leave the page.

When you would use it

How to use it

  1. Choose the algorithm, then edit the header and payload JSON. The alg field is set for you, and typ defaults to JWT.
  2. For HS algorithms enter a shared secret (as UTF-8 text or base64url). For RS, PS and ES algorithms paste a private key, or use the button that generates a key pair.
  3. Copy the signed token. To verify, paste a token into the verify section with the secret or the public key and read the result.

Things worth knowing

Frequently asked questions

What is the difference between HS256 and RS256?
HS256 uses one shared secret for both signing and verifying, so every party that can verify can also forge tokens. RS256 signs with a private key and verifies with a public key, which lets you share verification without sharing the ability to sign.
Why does verification say the signature is invalid?
The most common causes are a different secret or key, a secret decoded with the wrong encoding (UTF-8 text versus base64url), a token whose header names another algorithm than the one you expect, or a token that was edited after signing.

All the tools