Saltar al contenido

JWT Debugger

Debug JSON Web Tokens quickly and easily with our free online JWT Debugger. Inspect token structure, claims, signatures, and potential issues during development and testing.

 

JWT Token Paste your JSON Web Token below to analyze and debug it
Ready
Signature Debugging Optionally verify the JWT signature with its signing secret
Used only when checking the JWT signature.
Leave empty to inspect the token without verifying its signature.
Header JWT header information
Payload JWT claims and payload data
Signature Encoded signature from the token
✓ Your token and signing secret are processed locally in your browser. Nothing is uploaded to a server.
Note: JWT debugging checks token structure, encoding, claims, timestamps, and optionally the signature. A successful signature check does not by itself determine whether a token should be trusted by your application.
EVERYTHING YOU NEED TO KNOW

How to use the JWT Debugger?

A JWT Debugger helps developers inspect and troubleshoot JSON Web Tokens. It provides a clear view of the token’s components and helps identify common issues with its structure, claims, or signature.

Simply enter your JWT into the debugger and start the analysis. The tool examines the token’s components and provides information that can help you identify and understand potential problems.

A JWT Debugger can help identify issues such as malformed tokens, incorrect claims, expired timestamps, or signature validation problems. It makes troubleshooting authentication-related issues easier.

Yes. An invalid JWT can still be inspected to help determine what is wrong. The debugger can display the available token components and provide information about potential structural or validation issues.

No. CodeLiqo’s JWT Debugger processes your input directly in your browser. Your JWT does not need to be uploaded to a remote server for debugging, helping keep your data on your device.

What Does JWT Debugger Do?

JWT Debugger helps diagnose problems with a JSON Web Token by checking its structure, encoding, claims, signing algorithm, expiration and signature. Enter the JWT Token, then provide the information required for signature debugging, such as the HS256 algorithm and the signing secret.

For example, you can debug this JWT using HS256 and the signing secret codeliqo:

 
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJ1c2VyLTAwMSIsImlzcyI6ImNvZGVsaXFvLmNvbSIsImF1ZCI6ImRldmVsb3BlcnMtYXBpIiwibmFtZSI6IkFsaWNlIEpvaG5zb24iLCJyb2xlIjoiZGV2ZWxvcGVyIiwiaWF0IjoxNzg5NTkzMDAzLCJuYmYiOjE3ODk1OTMyNDMsImV4cCI6MTc4OTU5NjkwMywianRpIjoiZGVidWctdGVzdC0wMDEifQ.xDc3rPJoD_6MF64MW8ijdIyQWg2NtbqUhSm2OhSRFZg
 

Check the example image below to see how JWT Debugger displays the diagnostic results. ↓

The Diagnostics section performs several checks on the token. It can report whether the JWT structure and its Header, Payload and Signature are correctly encoded, identify the signing algorithm and token type, and check important timestamps such as exp, nbf and iat.

The diagnostic results can also identify problems with the signature. For example, if the signature does not match the provided signing secret and algorithm, the debugger reports a Signature verification issue. This can help identify an incorrect secret, algorithm mismatch or another signing-related problem.

In addition to the diagnostics, JWT Debugger displays the decoded Header, Payload and Signature, allowing you to inspect the individual components of the token after reviewing the checks.

JWT Debugger is useful when troubleshooting authentication tokens and investigating why a JWT is not behaving as expected. Instead of manually checking each part of the token, you can use the diagnostic results to quickly identify potential problems with its structure, encoding, timestamps or signature.