What it can do
- URL-decode copied token text
- Separate JWT segments
- Decode the JOSE header and claims
- Drop the binary signature segment
- Pretty-print both JSON documents
How the recipe works
URL Decode
Remove URL percent-encoding when a token came from a query string.
Fork
Split the compact token on periods.
From Base64
Decode every Base64url-like segment.
Filter
Keep only decoded JSON objects and discard the signature bytes.
JSON Beautify
Format the header and claims for review.
Demonstration
Sample input
eyJhbGciOiJub25lIiwidHlwIjoiSldUIn0.eyJzdWIiOiJkZW1vLXVzZXIiLCJyb2xlIjoiYW5hbHlzdCIsImlhdCI6MTcwNDA2NzIwMH0.Expected result
demo-userWhen to use it
- Debugging authentication flows
- Reviewing token claims
- Explaining JWT structure
Adapt it
Use JWT Verify when you also have the correct verification key. Decoding alone does not prove authenticity.
Source and verification
Adapted from kraven-security CyberChef recipes. The explanation and sample are written for Serialize, use synthetic or documentation-safe data, and are checked against the current operation catalogue. The workflow runs locally without an external API call.