# Decode an SD-JWT or SD-JWT VC online

> Free SD-JWT decoder for RFC 9901 and SD-JWT VC: split disclosures, recompute digests, check the KB-JWT and verify the issuer signature in your browser.

- URL: https://iamops.dev/tools/sd-jwt/
- Markdown: https://iamops.dev/tools/sd-jwt.md
- Language: en
- Runs in your browser, nothing is uploaded.

Paste an SD-JWT or a presentation with a Key Binding JWT. I split it, decode every disclosure, recompute the digests and show which claims the holder revealed.

## What can I paste here

The compact SD-JWT string, including the ~ separators and, if present, the Key Binding JWT at the end. Optionally paste the issuer JWK or JWKS to verify the signature. Line breaks are ignored.

## What it does

- Splits the issuer JWT, the disclosures and the Key Binding JWT, and decodes each disclosure.
- Recomputes every digest with _sd_alg and matches it against _sd arrays and ... array entries, then rebuilds the processed payload.
- Checks sd_hash and the KB-JWT signature with cnf.jwk, and verifies the issuer signature against a JWK you paste.

## Example use

Paste a presentation from a test wallet, see which claims were disclosed, and check that the digests and the KB-JWT hold.

## How to read the result

- A disclosure is base64url JSON: [salt, name, value] for an object property, [salt, value] for an array element. Its digest is the hash of the base64url text as sent.
- A digest that has no disclosure stays hidden. That is either a claim the holder kept back or a decoy. Nobody can tell which, and that is the point.
- A disclosure whose digest appears nowhere in the signed payload is an error. Usually it was edited, or it belongs to another credential.
- The KB-JWT proves the holder has the key in cnf.jwk. Its sd_hash covers the issuer JWT and the disclosures exactly as presented, so dropping or adding one breaks it.

## What it does not do

- It reads the compact form only. The JWS JSON serialization of section 8 is not supported.
- It does not fetch issuer keys, type metadata (vct) or status lists. Paste the issuer JWK or JWKS yourself.
- It does not decide whether a verifier should accept the credential. Trust in the issuer and the vct is your policy.

## Questions people ask

### What can I paste here

The compact SD-JWT string, including the ~ separators and, if present, the Key Binding JWT at the end. Optionally paste the issuer JWK or JWKS to verify the signature. Line breaks are ignored.

### What is an SD-JWT?

A signed JWT where some claims are replaced by salted hashes. The holder sends the matching disclosures only for the claims it wants to reveal. RFC 9901 defines it, and SD-JWT VC builds credentials on top of it.

### Why does a disclosure show as not referenced?

Its digest is not in any _sd array or ... entry of the signed payload. The disclosure was changed after issuance, was copied from another credential, or the hash algorithm in _sd_alg does not match.

## Related

- [Certificate decoder](https://iamops.dev/tools/certificate-decoder.md): Decode an X.509 certificate, chain or CSR and read SANs, expiry, key size, fingerprints and chain order. Paste PEM, base64 DER or hex. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/certificate-decoder/)
- [SAML decoder and verifier](https://iamops.dev/tools/saml.md): Decode a SAMLRequest or SAMLResponse, check the XML signature and decrypt an EncryptedAssertion. Paste base64, raw XML or a redirect URL. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/saml/)
- [JWT decoder and verifier](https://iamops.dev/tools/jwt.md): Decode a JSON Web Token, show claims and expiry as dates, and verify the signature. Paste a compact JWT, then an HMAC secret, PEM key, JWK or JWKS. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/jwt/)
- [ID-JAG inspector](https://iamops.dev/tools/id-jag.md): Inspect an Identity Assertion JWT Authorization Grant against the IETF draft and get the curl requests. Paste a compact ID-JAG token. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/id-jag/)
- [DPoP proof builder and checker](https://iamops.dev/tools/dpop.md): Build a DPoP proof with a fresh ES256 key, or check typ, htm, htu, iat, ath, nonce and the cnf.jkt thumbprint. Paste a DPoP JWT and the method and URL. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/dpop/)
- [PKCE generator](https://iamops.dev/tools/pkce.md): Generate a PKCE code verifier and S256 challenge, or check that a pair matches, with authorize and token snippets. Paste a verifier and optional challenge, or generate them here. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/pkce/)
- [OIDC discovery and JWKS viewer](https://iamops.dev/tools/oidc-discovery.md): Read an OpenID Provider discovery document and JWKS, and flag missing PKCE, weak keys or risky grants. Type the issuer, or paste the JSON if CORS blocks the fetch. Runs in your browser. Nothing is uploaded to this site; the fetch goes from your browser to the issuer. (https://iamops.dev/tools/oidc-discovery/)
- [Encoder and decoder](https://iamops.dev/tools/encoder-decoder.md): Encode or decode Base64, URL, hex, HTML entities, Unicode, gzip, deflate and the SAML redirect chain, with auto-detect. Paste the text. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/encoder-decoder/)
- [HAR inspector](https://iamops.dev/tools/har-inspector.md): Inspect a HAR file: filter requests, follow the OAuth or SAML flow, decode JWTs, and copy as curl with secrets redacted. Drop a HAR export from DevTools. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/har-inspector/)
- [HTTP client](https://iamops.dev/tools/http-client.md): Call an API from your browser with Basic, Bearer, an API key, or OAuth 2.0 (client credentials, authorization code with PKCE, device code, refresh, token exchange) and optional DPoP. Enter the URL and auth details, or paste a curl command, HAR or OpenAPI definition. The request goes from your browser, not through this site. If CORS blocks the call, the page offers curl instead. (https://iamops.dev/tools/http-client/)
- [Passkey and WebAuthn decoder](https://iamops.dev/tools/webauthn.md): Decode a WebAuthn or passkey response: attestationObject, clientDataJSON and authenticator data, including flags, AAGUID, sign count and the COSE public key. Paste the credential JSON or the individual fields. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/webauthn/)
- [MCP auth discovery checker](https://iamops.dev/tools/mcp-auth.md): Check MCP authorization discovery: Protected Resource Metadata (RFC 9728) and the authorization server metadata, and flag missing PKCE S256, CIMD/DCR or resource indicators. Enter the server URL, or paste the JSON if CORS blocks the fetch. Requests go from your browser, nothing is uploaded to this site. (https://iamops.dev/tools/mcp-auth/)
- [Shared Signals SET decoder](https://iamops.dev/tools/shared-signals.md): Decode a Shared Signals Security Event Token (CAEP or RISC), explain the event type and the sub_id formats, and optionally verify the signature. Paste the SET JWT and optionally the transmitter JWKS. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/shared-signals/)
