Development · free tool

JWT decoder and encoder for headers, payloads and token claims

Decode, inspect and regenerate test JSON Web Tokens with HS256.

Input and result

Use it well

How to use JWT Decoder / Encoder

Steps

  1. Paste the JWT token.
  2. Inspect the decoded header and payload.
  3. Edit test claims if needed.
  4. Optionally enter a HS256 secret.
On this page

Common use cases

API debugging
Read token claims while investigating authentication issues.
Expiration checks
Inspect exp, iat and nbf timestamps before testing access flows.
Test token generation
Regenerate an HS256 token after editing test header or payload data.
Auth documentation
Prepare readable token examples for integration notes.

Good to know

A JWT decoder reads the Base64URL-encoded header and payload of a JSON Web Token. A JWT encoder can regenerate a test token from edited header and payload data.

  • Decode header and payload
  • Inspect common claims
  • Regenerate HS256 test tokens
  • Local browser processing

FAQ

Frequently asked questions

Does decoding a JWT verify its signature?

No. Decoding only reads the token content. Signature verification requires the correct key or secret.

Can this tool encode a JWT?

Yes. It can regenerate an HS256 test token from the header, payload and secret you provide.

Is JWT content encrypted?

Most JWTs are signed but not encrypted. Anyone with the token can decode and read the payload.

What are common JWT claims?

Common claims include exp, iat, nbf, iss, aud, sub and custom application fields.

Are my inputs sent to a server?

OnSubmit tools run in the browser whenever the task can be processed locally. Avoid pasting production secrets, real banking details or personal data into public tools.

Quick search

Find a tool

Search all OnSubmit tools, favorites and recently opened tools.