Text & code / MULTIVERTO
Encode text as Base64 or Base64URL with selectable character set and padding.
Apply each text tool to the previous result.
01 / Guide
The selected character set produces bytes; the alphabet and padding controls determine the Base64 representation.
Match the alphabet, padding and character set to the destination; Base64 increases size and provides no secrecy.
02 / Example
Hello, world!SGVsbG8sIHdvcmxkIQ==03 / Guide
Use this direction when a receiving format permits printable Base64 characters but you start with ordinary text. The input becomes bytes in the selected character set before the chosen Base64 alphabet is applied. UTF-8 is the default; ISO-8859-1 and UTF-16LE are available when the receiving format calls for them. A greeting with accents or emoji may need more bytes than its visible character count suggests. Recovery requires the receiver to decode the same alphabet and byte character set.
This is useful for inspecting an API payload or preparing text for a field that explicitly specifies Base64. The alphabet control selects standard Base64 with + and / or Base64URL with - and _. The padding control adds or removes trailing = characters; standard Base64 normally includes them, while URL-safe uses often omit them. Match both settings to the receiving specification. Anyone with the encoded string can recover its content, so avoid treating the result as password protection or placing secrets in URLs and logs.
Base64 is a way to write binary bytes using a restricted alphabet of printable characters. It groups three source bytes into four characters, each character carrying six bits. If the last group is incomplete, an equals sign may appear as padding. The output can be placed in text-only channels such as some data URLs, messages or configuration files. Because four characters often replace three bytes, the representation is approximately one third larger before any other transport overhead. This is a tradeoff for compatibility, not a compression method.
Text must become bytes before Base64 can represent it. UTF-8 is the default character set, so an accented letter or emoji can occupy several bytes even though it looks like one character. The character-set control also offers ISO-8859-1 for characters in that single-byte repertoire and UTF-16LE for two-byte code units. Decode with the same character set that produced the bytes, or the text can be wrong or rejected. Base64URL uses - and _ in place of + and /; choose the alphabet required by the destination. Padding with = can be included or omitted for encoding. Base64 is not encryption, does not prove authenticity and cannot hide a secret.
Start with the original text and confirm that the receiving application actually asks for an encoded representation. Paste the text or load the example, then inspect the output before copying it. The conversion happens in this browser; the entered text is not uploaded to a conversion service. This direction changes how information is written, not the meaning of a sentence. Keep the source beside the result when debugging, and avoid applying an encoding twice unless the destination format explicitly requires two layers.
Keep the original input when you need to audit a result. An encoded representation may look very different from the underlying text, especially when accents, emoji, punctuation or line breaks are present. If you exchange the result with another program, check which character encoding and exact format that program expects. Try a short known example before processing a large value, and compare the output with the receiving application rather than assuming every similar-looking format is interchangeable.