JWT Decoder Local

How to use the JWT Decoder Local

What does the JWT Decoder Local do?

Read the header and payload of a JWT locally without verifying, uploading, or sending the token; It applies this page-specific rule: a JWT stores Base64URL-encoded JSON in its header and payload.

Which inputs does this tool use?

To read the header and payload of a jwt locally without verifying, uploading, or sending the token, enter JSON Web Token, Decoded header and payload; keep every value in the same example; select Decode JWT locally when the values are ready; Start with a familiar case covered by this rule - This page only decodes locally - so the expected result can confirm the settings.

How should the tool result be read?

For a result intended to read the header and payload of a jwt locally without verifying, uploading, or sending the token, this page only decodes locally; read decoded header and payload together with the original json web token rather than as an isolated answer, and confirm that its units or structure match the intended use.

Does a readable payload mean the token is valid?

When the goal is to read the header and payload of a jwt locally without verifying, uploading, or sending the token, no.

Is the signature checked?

When using the page to read the header and payload of a jwt locally without verifying, uploading, or sending the token, no.

Limits and accuracy

When using this tool to read the header and payload of a jwt locally without verifying, uploading, or sending the token, treat real access tokens as sensitive; check the result in its intended destination before relying on it for important work; keep json web token until the output has been checked in its intended destination. For a repeatable check when you need to read the header and payload of a jwt locally without verifying, uploading, or sending the token, record JSON Web Token alongside the final output and selected options.