Does decode jwt payload base64 segment verify signatures?

No. This tool only decodes Base64 payload bytes for inspection; validating signatures requires your auth library and public keys.

What about Base64URL padding?

JWT segments may omit padding. If decode fails, add = characters until length is a multiple of four.

Yes. Paste the first segment the same way; it is also Base64URL-encoded JSON.

JWTs use dot-separated segments; the payload is Base64URL-encoded JSON listing claims such as sub, exp, and scopes.

Copy only the middle segment (between dots) or paste the full token and strip header/payload parts before decoding here.

Developers debug auth issues during integration—this is not signature verification and must not replace server-side validation.

Responsive

in-content · Ad slot ready

Payload segment only

eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkRldiIsImlhdCI6MTUxNjIzOTAyMn0

Decoded claims JSON

{"sub":"1234567890","name":"Dev","iat":1516239022}

Does decode jwt payload base64 segment verify signatures?: No. This tool only decodes Base64 payload bytes for inspection; validating signatures requires your auth library and public keys.
What about Base64URL padding?: JWT segments may omit padding. If decode fails, add = characters until length is a multiple of four.
Can I decode the header too?: Yes. Paste the first segment the same way; it is also Base64URL-encoded JSON.