Base64 URL-Safe Encoder
Encode text using URL-safe Base64 (RFC 4648). Standard Base64 uses + and / characters that break URLs and filenames. URL-safe Base64 replaces them with - and _, and removes trailing = padding. Used in JWTs, OAuth tokens, and URL parameters.
Text
Frequently Asked Questions
›What is URL-safe Base64?
URL-safe Base64 (defined in RFC 4648) replaces the + character with - and / with _, and omits trailing = padding. This makes the output safe to use directly in URLs, query parameters, and filenames without percent-encoding.
›Where is URL-safe Base64 used?
JWT tokens, OAuth 2.0 state parameters, Amazon S3 keys, URL shorteners, cookie values, and any context where Base64 data appears in URLs or filenames.
›Can I decode URL-safe Base64 here too?
Yes. Switch to Decode mode and paste any URL-safe Base64 string. The decoder automatically handles both standard and URL-safe variants.