Base64Url Encoder Decoder
Encode or decode UTF-8 text with the URL-safe Base64 alphabet.
Result for the values shown.
Calculations run in your browser.
What to enter
| Input | Meaning and units |
|---|---|
| Text or encoded input | Text is processed in your browser. Maximum input: 1 MiB of UTF-8 text. |
| Calculation mode | encode/decode |
| Include Base64 padding | boolean |
Understanding your result
The output applies the selected format or address convention. Encoding is not encryption; a valid address representation does not establish availability, reachability or security.
Common mistakes
- Using a different alphabet, padding, base, delimiter or address-prefix convention than the tool expects.
Check your calculation
- Where a reverse operation exists, round-trip a short known example. Compare structural results with the reference example rather than executing decoded text.
Calculation checks, sources and review limits
How do I encode or decode URL-safe Base64 text with an explicit padding policy?
Encode or decode UTF-8 text with the URL-safe Base64 alphabet.
Common uses
- Encode or decode UTF-8 text with the URL-safe Base64 alphabet.
How it works
Use - and _ in place of + and /. Choose whether encoded output includes padding; decoding accepts canonical padded or unpadded URL-safe Base64. Invalid pad bits and malformed UTF-8 are rejected. This is an encoding, not encryption.
Worked example
Enter Text or encoded input: f; Calculation mode: encode; Include Base64 padding: false. The result is Text: Zg.
FAQ
How do I encode or decode URL-safe Base64 text with an explicit padding policy?
Use - and _ in place of + and /. Choose whether encoded output includes padding; decoding accepts canonical padded or unpadded URL-safe Base64. Invalid pad bits and malformed UTF-8 are rejected. This is an encoding, not encryption.
What assumptions and limits apply?
URL-safe base64 is distinct from percent encoding.