Base64URL example
🐒 → standard: 8J+Qkg==URL-safe, unpadded: 8J-QkgBoth values represent the same four UTF-8 bytes. Only the alphabet and padding convention differ.
100% local. No uploads. No storage.
0 characters
Files never leave your device.
Files over 25 MiB may use significant browser memory. Maximum: 64 MiB per file.
Options apply to encoding text and files. Decoding accepts standard and URL-safe Base64, with or without padding, and ignores whitespace. Data URLs always use standard, padded Base64 without wrapping.
Saved you some time? Buy me a coffee ☕
Base64URL replaces the standard + and / characters with - and _. Padding uses the same = character, but many protocols omit it. This makes the alphabet useful in URLs and token formats. Follow the receiving protocol’s padding requirements.
🐒 → standard: 8J+Qkg==URL-safe, unpadded: 8J-QkgBoth values represent the same four UTF-8 bytes. Only the alphabet and padding convention differ.
A JWT’s encoded header and payload use Base64URL and may contain readable JSON. Paste one encoded segment at a time; a complete dot-separated JWT is not one Base64URL string. Reading a payload does not verify its signature, issuer, or authenticity.
All conversions run locally in your browser. No input, files, filenames, or results are uploaded or saved by Base64Baboon. Copies and downloads you request are yours to manage. Read the privacy details. Base64 is encoding, not encryption.
No. Base64URL encodes bytes using a URL-safe alphabet. Percent encoding escapes characters using sequences such as %2F. This tool does not percent-decode input.
It depends on the receiving format. This page defaults to unpadded output. Enable Include = padding if the protocol requires it. The decoder accepts either form when valid.
Yes. Select Files → Base64 → File. The decoder accepts URL-safe binary data as well as standard Base64.
Work with the URL-safe Base64 alphabet. URL-safe output is enabled and padding is off by default; Decode accepts either alphabet.