What changes in Base64URL?

The 62nd and 63rd alphabet symbols are - and _ instead of + and /. This preset also omits padding and wrapping. Some protocols still require padding, so use the Omit = padding control according to the consuming protocol.

Can I convert standard Base64 into Base64URL?

Decode the original first. For text, copy the decoded text back and encode it with URL-safe selected. For binary data, download the decoded file and use Encode a file with URL-safe selected. Pasting an encoded payload while Encode is selected encodes its literal characters again.

Is this a JWT encoder or a URL percent encoder?

No. JWT signing and claim validation require additional cryptographic and application steps; JWT Decoder reads an existing token. URL Encoder and Decoder handles percent escapes such as %2F and form spaces. A file data URI uses standard Base64 even while its separate raw payload uses these URL-safe settings.

Base64URL Encoder

Encode UTF-8 text or local file bytes with the URL-safe Base64 alphabet. This page opens Encode with - and _ in place of + and /, no = padding and no MIME wrapping. The same tool can decode either alphabet, and each encoding control remains available.

Inputencode

Output

Converted output appears here.

Direction

Alphabet

Encoding options: Omit = paddingWrap at 76 (MIME)

Auto is a guess based on decoded UTF-8 text. Select Encode to treat a Base64-looking string as literal text, or Decode for binary files. Both alphabets and omitted padding are accepted when decoding. Dropping a file encodes its original bytes.

Common questions

What changes in Base64URL?: The 62nd and 63rd alphabet symbols are - and _ instead of + and /. This preset also omits padding and wrapping. Some protocols still require padding, so use the Omit = padding control according to the consuming protocol.
Can I convert standard Base64 into Base64URL?: Decode the original first. For text, copy the decoded text back and encode it with URL-safe selected. For binary data, download the decoded file and use Encode a file with URL-safe selected. Pasting an encoded payload while Encode is selected encodes its literal characters again.
Is this a JWT encoder or a URL percent encoder?: No. JWT signing and claim validation require additional cryptographic and application steps; JWT Decoder reads an existing token. URL Encoder and Decoder handles percent escapes such as %2F and form spaces. A file data URI uses standard Base64 even while its separate raw payload uses these URL-safe settings.

Encoding preserves valid UTF-8 text or the original file bytes. Decoding restores those bytes; invalid UTF-8 is kept as binary data for download. Auto direction and inferred file types are best-effort guesses, and no file-format conversion or validation is performed.