Center Text
Centre every line within a width using real spaces.
Encode text to Base64, including URL-safe output.
The Base64 Encoder converts text into the 64-character alphabet that lets binary travel through text-only channels — email, JSON, data URIs and HTTP headers. Text is encoded as UTF-8 first, which is the only correct way and the step naive encoders skip.
Base64 turns arbitrary data into 64 printable characters, which is how binary travels through systems that only accept text: email attachments, JSON payloads, data URIs and HTTP headers all rely on it.
This encoder handles the two things that catch people out. Non-English text is encoded as UTF-8 first, which is the only correct way — the naive approach fails outright on any character above 255. And the URL-safe variant is available, which swaps the + and / characters for - and _ so the result can go in a URL or a filename without being percent-encoded. Line wrapping at 76 characters is there too, which the MIME email standard requires.
Text becomes UTF-8 bytes before encoding, so non-English input works rather than throwing an error.
Swaps + and / for - and _ so the result is safe in a URL or a filename, which is what JWTs use.
Wrap at 76 characters when the output is going into an email, as the standard requires.
Drop the trailing = characters for the contexts that omit them.
The encoded length beside the original, so the roughly one-third overhead is visible before you commit to it.
Any text, in any language — UTF-8 is handled correctly.
Standard Base64, or the URL-safe alphabet for use in a URL or filename.
Wrap at 76 characters for MIME email, or leave it as one continuous string.
The encoded size is shown, which is always about a third larger than the input.
No. It is an encoding, not a cipher — anyone can decode it instantly and no key is involved. Never use it to hide a password or anything else that matters.
Base64 represents every three bytes as four characters, so the output is about 33 per cent larger, plus padding. That overhead is the price of being able to send binary through a text-only channel.
A variant that replaces + with - and / with _, because those two characters have special meanings in a URL. The padding = is often dropped too. It is what JWTs use.
The text is encoded as UTF-8 bytes first, then those bytes are Base64 encoded. That is the standard and correct approach; encoders that skip it fail on any character above 255.
What people who use the Base64 Encoder think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Base64 Encoder. It takes half a minute and no account.
Write the first reviewCentre every line within a width using real spaces.
Combine two lists side by side, line by line.
Count and list every symbol that is not a letter, digit or space.
Put any list into alphabetical order, numbers handled properly.
Convert accented letters to their plain forms without losing the word.
Count how many distinct words a text uses and how varied it is.
Reverse text so it reads correctly in a mirror.
Strip filler words so the meaningful terms stand out.