# Have the jwt.io debugger error if token is base64 encoded

**URL:** <https://community.auth0.com/t/have-the-jwt-io-debugger-error-if-token-is-base64-encoded/7694>\
**Category:** Get Help\
**Tags:** debugger, jwt\
**Created:** [July 31, 2017, 6:36am UTC](https://community.auth0.com/t/have-the-jwt-io-debugger-error-if-token-is-base64-encoded/7694 "2017-07-31T06:36:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![keno](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/keno/32/4266_2.png) [@keno](https://community.auth0.com/u/keno)\
**Post date:** [July 31, 2017, 6:36am UTC](https://community.auth0.com/t/have-the-jwt-io-debugger-error-if-token-is-base64-encoded/7694/1 "2017-07-31T06:36:48Z")

</div>

The debugger on [jwt.io](http://jwt.io) accepts both base64 and base64url encoded tokens. However, since the standard specified base64url, it would be nice if the debugger generated an error for base64 tokens.

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [July 31, 2017, 8:07pm UTC](https://community.auth0.com/t/have-the-jwt-io-debugger-error-if-token-is-base64-encoded/7694/2 "2017-07-31T20:07:53Z")

</div>

Thanks for the feedback, your observation is correct and that situation seems to being already tracked [here](https://github.com/jsonwebtoken/jsonwebtoken.github.io/issues/160). Having said that, the age of the existing report seems to indicate that it may be something that will continue like that for a while.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 2, 2018, 5:55am UTC](https://community.auth0.com/t/have-the-jwt-io-debugger-error-if-token-is-base64-encoded/7694/3 "2018-03-02T05:55:40Z")

</div>


