I have text that I base 64 encoded in several places and have gotten the same value. When I put this data into the payload area of the JWT debugger, it comes up without the 2 equal signs at the end. Why is this? Is it appropriate to strip off the equal signs when building the JWT value?

A JWT uses Base64url Encoding ( RFC 4648 - The Base16, Base32, and Base64 Data Encodings ) which is a variant of Base64 where the 62nd and 63rd are different and also where the padding (equal signs at the end) are not mandatory so you won’t see padding in the encoding of JWT’s.

Why no equal signs at the end of Base 64 encoding?

JWT.io

Topic		Replies	Views
JWT.io is decoding the JWT header "wrong" Get Help jwt	3	2399	September 16, 2021
JWT.io different result compared to base64decode.org JWT.io	4	4320	October 24, 2019
Have the jwt.io debugger error if token is base64 encoded Get Help jwt , debugger	2	4239	March 2, 2018
JWT token validation issue JWT.io jwt-security , jwt , jwt-validation	4	6846	February 29, 2020
How do I need to decode secret on jwt.io when using base64 checkbox JWT.io	2	2447	January 13, 2023

Why no equal signs at the end of Base 64 encoding?

Related topics