When the JWT Decoder seems to misbehave, the cause is usually one of two things: something stopped the tool from running, or it ran but the result is not usable. This guide starts with the fastest checks, then walks through the common problems and exact fixes.
Quick Checks First
- Refresh the page - a stalled session is the most common cause of nothing happening.
- Confirm the input is not empty and actually contains what you meant to submit.
- Try the smallest possible input; if that works, the issue is size, not the tool.
- Turn off browser extensions that block scripts, then reload and test again.
- Update or switch browsers if the problem repeats across sessions.
Common Problems and How to Fix Them
It says the token is malformed.
Copy the token in one piece - a missing dot or clipped segment breaks the three-part split.
The payload shows as gibberish.
Spaces or line breaks damage the base64 segment - paste the raw token with no added characters.
The claims look right but login still fails.
Decoding proves nothing about the signature - verify the token with your secret or public key.
I cannot read the expiry claim.
exp is a Unix timestamp in seconds - convert it to a date to see when the token stops working.
My token will not decode at all.
It may be an opaque token - a real JWT always has two dots separating three base64 parts.
I am worried about leaking a live token.
Decoding runs in your browser, but a shared screenshot still exposes claims - redact before posting.
When It Works but the Output Is Poor
If the tool runs fine but the result misses, the problem is almost always the brief, not the software:
- Treating decode as verification
- Pasting a truncated token
- Screen-sharing live tokens
- Expecting signature validation
How to Stop It Happening Next Time
- Keep a saved prompt template for every task you repeat.
- Change one setting per generation so causes stay obvious.
- Run a two-minute sanity test with known input after any update.
- Note every failure and its fix; a short troubleshooting log pays for itself.
Still Stuck?
Reproduce the problem with the smallest possible input and note the exact steps that triggered it. A one-line description of what you did, what you expected and what happened is enough to get a precise answer from support or a colleague.
Frequently Asked Questions
Does it verify the token signature?
No - decoding is read only; verification needs your secret or public key and belongs to your server.
Why are there three parts?
A JWT carries a header, a payload and a signature, each separated by a dot.
What if the token is not a JWT?
Opaque tokens have no dot separated structure, so the tool reports that it cannot decode it.
Is my token stored?
No - decoding runs locally in your browser and the token is never transmitted.
Related Guides
- JWT Decoder - free online tool
- How to Use JWT Decoder
- What Is a JWT Decoder and How Does It Work?
- JWT Decoder Examples: Real Scenarios and Results
- JWT Decoder for Software Engineers and DevOps Teams
- Best JWT Decoder Alternatives Worth Trying
- JWT Decoder Tips and Best Practices
- Is JWT Decoder Safe? Free vs Paid
- More code tools and guides