Base64 URL Encode / Decode

Encode and decode URL-safe Base64 strings. Safe for use in URLs, query parameters, cookies, and JWT tokens.

URL-safe Base64 replaces + with - and / with _, and removes trailing = padding. This is used in JWT tokens, URL parameters, and cookies.

Frequently Asked Questions

Got questions? We've got answers. Search below or browse through our most commonly asked questions.

Standard Base64 uses '+' and '/' characters which have special meanings in URLs. URL-safe Base64 replaces '+' with '-' and '/' with '_', and removes trailing '=' padding. This makes it safe to use in URLs, query parameters, and JWT tokens without additional encoding.
Use URL-safe Base64 whenever you need to include Base64 data in URLs, query parameters, or cookies. It's also the standard for JWT (JSON Web Tokens) and various web API signatures.
No, they use different character sets. A standard Base64 decoder will not correctly decode URL-safe Base64 and vice versa. Our tool handles both formats correctly when you use the appropriate mode.
Yes! JWT tokens use URL-safe Base64 encoding. Paste your JWT payload (the middle part between the dots) into the decoder to view the decoded JSON content.