Codificador Base64 URL
Encode text to URL-safe Base64 (Base64url) instantly
Input
Output (URL-safe, no padding)
Base64 URL Encoding Examples
URL-safe Base64 replaces + with - and / with _, and strips = padding. Example:
Text with URL-unsafe characters
Input:
Base64url output (no +, /, or = characters):
Click Sample above to load example data.
What Is Base64 URL Encoding?
Base64url is defined in RFC 4648 Section 5 as a URL- and filename-safe variant of Base64.
For standard Base64, use the Base64 Encoder. To decode Base64url, use the Base64 URL Decoder.
How to Use This Tool
Paste Your Text
Type or paste your text into the left editor. Click Sample to load example text.
Read the URL-Safe Output
The right panel shows the Base64url result.
Copy or Download
Click Copy or Download. To decode, use the Base64 URL Decoder.
Standard Base64 vs Base64url
The only differences are three characters and the padding rule:
The Base64 URL Decoder handles this automatically.
Where Base64url Is Used
JWTs, OAuth 2.0 PKCE, WebAuthn, and URL-safe identifiers use Base64url.
For standard Base64, use the Base64 Encoder. For decoding, use the Base64 Decoder.
Frequently Asked Questions
Is my data private?
Yes. Encoding runs entirely in your browser.
Why is there no = padding?
RFC 4648 Section 5 defines Base64url without padding. The Base64 URL Decoder handles it automatically.
Can I use this for JWTs?
Yes. This tool encodes text to Base64url, the format used in JWT header and payload segments.
What's the difference from the Base64 Encoder?
The Base64 Encoder outputs standard Base64. This tool outputs Base64url—safe for URLs.
Does it support Unicode?
Yes. Text is encoded to UTF-8 first, then converted to Base64url.
Related Tools
Ver RFC 4648 Sección 5.