Security tools

JWT debugger

Decode JWTs and explicitly verify HS256 or RS256 signatures.

See result and limits ↓

Security tools

Files are processed in your browser, without uploads.

50,000 UTF-16

Everything runs in this tab. Clear results after use; exported files remain on your device. Decoding is not verification. Only HS256 and RS256 are supported; use a trusted key. Signature verification does not establish issuer, audience or authorization.

Inspect input and result

Real sample input and the result produced by this tool.

eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJkZW1vIn0.c2FtcGxl
Input / settingsTXT · 49 B · 49 characters
{
  "header": {
    "alg": "HS256"
  },
  "payload": {
    "sub": "demo"
  },
  "expired": null,
  "notActive": null,
  "verified": null
}
ResultTXT · 138 B · 138 characters

Example settings: source: local tool export; synthetic public sample

Samples contain public test data. Text previews may be shortened; downloads contain the complete files.

JWT debugger

Decode JWTs and explicitly verify HS256 or RS256 signatures.

Everything runs in this tab. Clear results after use; exported files remain on your device. Decoding is not verification. Only HS256 and RS256 are supported; use a trusted key. Signature verification does not establish issuer, audience or authorization.

Generate / process

01

Prepare

Add or set: Input.

02

Process and inspect

Set Operation / Algorithm / HMAC secret / RSA public JWK, then choose “Generate / process” and inspect Output.

03

Save the result

Use “Copy result”; review the final text before using it elsewhere.

questions

FAQ

How long can the JWT input be?

50,000 UTF-16

What should I check before using the result?

Decoding is not verification. Only HS256 and RS256 are supported; use a trusted key. Signature verification does not establish issuer, audience or authorization.