URL-safe Base64 (- _ , no padding).
Base64URL Encode / Decode converts text to and from URL-safe Base64, the variant that uses - and _ instead of + and / and omits the trailing = padding. This makes the output safe to drop into URLs, query strings, JWT segments, and filenames without extra escaping. Switch between encode and decode modes to round-trip UTF-8 text in either direction.
No. Encoding and decoding run entirely in your browser using the built-in btoa, atob, TextEncoder, and TextDecoder APIs. Nothing you type is uploaded or stored remotely.
Base64URL replaces the + character with - and the / character with _, and it strips the trailing = padding. This keeps the output safe for use in URLs and filenames, whereas standard Base64 would need additional escaping.
Yes. Text is encoded as UTF-8 before conversion via TextEncoder and decoded back with TextDecoder, so multi-byte characters and emoji round-trip correctly.
No. The decoder automatically restores any missing = padding before decoding, so you can paste an unpadded Base64URL string directly.
If the input is not valid Base64URL, decoding fails and the tool reports an 'Invalid Base64URL input' error rather than returning garbled output.