PIPELINE Security & Privacy Intermediate 1 step

Decode JWT and inspect payload

When debugging authentication issues you often need to read the claims inside a JWT. This chain decodes the JWT (without verifying the signature — see the security note below) and then formats the resulting JSON so the claims are easy to read. Remember: decoding a JWT only confirms its structure, not its authenticity.

What it solves

Decode a JWT token to its header and payload, then pretty-print the JSON for inspection.

Input → Output

JWT Decoder input → JWT Decoder output across 1 step.

Runs in

2–3 minutes · fully local in your browser.

Before you start

A compact JWT string (header.payload.signature)

The pipeline

1 JWT Decoder jwt

Decode and inspect JWT header, payload, and time claims with expiry status. Free, private, and 100% client-side.

Open in Toolchain

Runs locally in your browser. The recipe defines the pipeline only — your input never leaves this tab.

▶Run this workflow

Enter your input below and click Run. All processing happens locally in your browser — nothing is uploaded.

Input data

Pipeline progress

JWT Decoderjwt

Sample input

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0IiwibmFtZSI6IkFsaWNlIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c

Expected output

Header:
{
  "alg": "HS256",
  "typ": "JWT"
}

Payload:
{
  "sub": "1234",
  "name": "Alice",
  "iat": 1516239022
}

Issued at (iat): 2018-01-18T01:30:22.000Z (Thu Jan 18 2018 09:30:22 GMT+0800 (中国标准时间))

Status: VALID (time claims)

Signature:
SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c

Note: Local decoding is not server-side signature verification.

This pair is executed against the real tools at build time (tests/unit/recipes.test.ts) — the expected output is verified, not illustrative.