Base64 Encoder example
Hello WorldSGVsbG8gV29ybGQ=These eleven UTF-8 bytes become sixteen Base64 characters, including one padding character.
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 ☕
Standard Base64 uses letters, digits, + and /, with = padding when needed. Use it when an API or format asks for Base64. The output describes bytes; it does not encrypt them or keep them secret.
Hello WorldSGVsbG8gV29ybGQ=These eleven UTF-8 bytes become sixteen Base64 characters, including one padding character.
Most API fields expect raw Base64. A Data URL also includes a media type and a data: prefix. In Files, enable Include Data URL prefix only when the destination expects a complete Data URL. This option always produces standard, padded, unwrapped Base64.
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.
Base64 uses four characters for every three input bytes, rounded up to a complete group. Expect roughly 33% overhead before line breaks or a Data URL prefix.
Keep No wrapping for most API and JSON values. Choose 64 or 76 characters only when the receiving format requires it.
The converter makes no network requests and does not save input. Base64 itself offers no secrecy: anyone with the result can decode it.
Turn text or file bytes into Base64 for APIs, text-based formats, and developer debugging. Everything is encoded locally.