What is an SD-JWT?

SD-JWT (Selective Disclosure for JSON Web Tokens) is a signed token where some claims are hidden. The issuer signs only salted hashes, called digests, of those claims. The holder then decides which claims to reveal by sending their disclosures along with the token. A verifier sees the claims the holder chose, can check that each one matches a digest the issuer signed, and learns nothing about the rest.

SD-JWT VC builds verifiable credentials on top of it: a vct type says what kind of credential it is, and a cnf key binds the credential to the holder's device. It's one of the two credential formats of the EU Digital Identity Wallets, which every EU country must offer its citizens by December 2026, and OpenID for Verifiable Credentials uses it too.

What an SD-JWT looks like

An SD-JWT is a string of parts separated by tildes (~):

  • The issuer-signed JWT, header.payload.signature.
  • One disclosure per revealed claim, each a Base64url-encoded JSON array of a random salt, the claim name and its value. Disclosures of array elements leave out the name.
  • An optional key binding JWT at the end, which the holder signs to show the presentation is theirs and meant for this verifier. Without one, the string ends with a tilde.

How to use it

Paste the SD-JWT. Line breaks and spaces are ignored, so a wrapped token copied from a log works too.

To check the issuer's signature, enter the issuer's public key as a JWK, a JWK set (the key with the token's kid is used), a PEM public key or an X.509 certificate. A pasted private JWK works as well; only its public part is used. When the key field is empty, the certificate in the token header's x5c is used, if there is one.

What you see

  • Checks for the signature, the disclosures, the key binding, the validity period and the hash algorithm.
  • Header of the issuer JWT, with its algorithm, type (dc+sd-jwt for SD-JWT VC) and key ID.
  • Payload as signed, with the digests (_sd) of the hidden claims and {"...": digest} placeholders for hidden array elements.
  • Claims with disclosures, the payload with every disclosure put in its place, as a verifier would read it.
  • Disclosures, a table of each disclosure's claim, value, where it lands in the claims and its digest.
  • Key binding JWT, its header and payload with the audience (aud), the nonce and the sd_hash.

What the checks mean

  • Signature: the issuer JWT is signed by the key you entered. When the tool falls back to the header's certificate, it shows that the token matches its own certificate. Whether that certificate belongs to a trusted issuer, for example one on the EU's trusted lists, is beyond what this check covers.
  • Disclosures: every disclosure's digest appears in the signed token exactly once. A changed disclosure has a different digest, so it no longer matches, and a disclosure sent twice is flagged.
  • Key binding: the key binding JWT's sd_hash is the hash of this exact presentation (the SD-JWT up to the last tilde), and the key in the credential's cnf signed it. Dropping or adding a disclosure breaks the hash.
  • Validity period: the token's expiry (exp) and start (nbf) times against your device's clock.
  • Hash algorithm: the digests use the algorithm in _sd_alg, SHA-256 when the token names none. Browsers can compute SHA-256, SHA-384 and SHA-512.

Privacy

Decoding and every check run in your browser, so the token and the keys aren't sent anywhere. Real credentials contain personal data, so use test credentials when you share screenshots.