RS384 JWT Decoder & Verifier
Paste an RS384-signed JWT to decode its claims. Enter the RSA public key (PEM or JWK) to verify the RSASSA-PKCS1-v1_5 + SHA-384 signature — all locally in your browser.
100% in-browser — nothing uploadedEncoded JWT
Decoded Header
Paste a token to decode this segment.
Decoded Payload
Paste a token to decode this segment.
Verify Signature
Features
100% private
Your token is decoded entirely in your browser. Nothing is uploaded, logged, or sent to any server or API.
Instant decoding
Paste a JWT and the header, payload, and claims are decoded in real time — no button required.
Human-readable claims
Standard claims like exp, iat, and nbf are explained and shown as readable dates with expiry status.
Signature verification
Verify HS256/384/512 with a secret, or RS, PS, and ES algorithms with a public key — all client-side.
What is RS384 in a JWT?
RS384 is RSASSA-PKCS1-v1_5 using SHA-384. It uses the same RSA public/private key infrastructure as RS256 but hashes the data with SHA-384 before signing. The result is a slightly larger signature and a higher hash-level security margin, while the RSA key size (and thus the primary security parameter) remains the same.
RS384 is relatively rare in production — most applications that need asymmetric JWT signing use RS256, which is sufficient for the vast majority of use cases. RS384 may be selected to satisfy compliance requirements specifying SHA-384 or to align with other parts of a system already using SHA-384 for consistency.
Verify an RS384 JWT above by pasting the token and entering the RSA public key (PEM or JWK) in the signature panel. The same RSA key pair works for RS256, RS384, and RS512 — the algorithm choice only affects the hash function applied before signing.
RS384 at a glance
- Full name
- RSASSA-PKCS1-v1_5 using SHA-384
- Algorithm family
- RSA (asymmetric)
- Signing key
- RSA private key (≥ 2048 bits)
- Verification key
- RSA public key (PEM or JWK)
- Signature size
- Equals key size (256 bytes for 2048-bit key)
- Security level
- ~112 bits (2048-bit key)
How to decode a JWT token online
Paste your token
Copy a JSON Web Token and paste it into the encoded box. You can also load the example token to try it out.
Read the decoded data
The header and payload are decoded instantly. Switch to the Claims tab for plain-English explanations and expiry status.
Verify the signature
Enter the secret (HMAC) or public key (RSA/ECDSA) to confirm the token is authentic and hasn't been tampered with.