64U

Base64URL Encode/Decode

URL-safe variant, convertible with standard Base64

Input

Output

—

Base64URL differs from standard Base64 in three places: + becomes -, / becomes _, and trailing = is usually dropped. That is because + and / carry meaning in URLs (+ reads as a space, / as a path separator) and = needs escaping in a query string. JWT segments use this variant, which is why a plain Base64 decoder often chokes on a JWT.

All processing happens locally in your browser. Your data is never uploaded to a server.