Text & code / MULTIVERTO
Base32 groups UTF-8 bits into five-bit symbols using RFC 4648 letters A–Z and digits 2–7. Convert locally in your browser.
Apply each text tool to the previous result.
01 / Guide
Base32 groups UTF-8 bits into five-bit symbols using RFC 4648 letters A–Z and digits 2–7.
Base32 is reversible encoding, not encryption. This tool uses RFC 4648, accepts optional padding on input, and requires the bytes to be valid UTF-8 text.
02 / Example
Café!INQWNQ5JEE======03 / Guide
Base32 groups UTF-8 bits into five-bit symbols using RFC 4648 letters A–Z and digits 2–7. Convert locally in your browser. For example, entering "Café!" produces "INQWNQ5JEE======". Compare both sides character by character; the visible spelling can hide different bytes or combining marks. In this direction readable text becomes a transport representation. Preserve accents and punctuation in the input; the converter first reads their Unicode values and, when needed, UTF-8 bytes. Copy the complete output including padding or escape signs. Truncating one symbol can make the reverse conversion impossible.
Base32 is specified by RFC 4648. Eight output characters represent at most five input bytes; the final block may use = padding to fill the eight-character group. The alphabet uses capital A through Z and digits 2 through 7. That is not the same as an arbitrary base-32 number or the similarly named Crockford alphabet. Encoding first converts the entered Unicode text to UTF-8 bytes. Decoding reverses the bit groups and then validates the resulting UTF-8. Padding can be omitted on input, but impossible lengths and nonzero unused bits are rejected. The result is useful when a protocol wants case-insensitive printable symbols, but its length grows and it gives no integrity check. Base32 groups UTF-8 bits into five-bit symbols using RFC 4648 letters A–Z and digits 2–7.
A text transformation has a direction. First identify whether your source is readable Unicode text, a list of bytes, code points or an already encoded string. Paste one short value whose meaning you know, inspect the result and only then process a larger input. Keep a copy of the source. An encoded sequence can be reversible while still revealing every original byte to anyone who knows the format; encoding alone is not a privacy measure. Processing runs in this browser, so the converter does not send your pasted content to a conversion server. The result still becomes sensitive if you copy it into a shared document, issue tracker or URL.
Base32 is reversible encoding, not encryption. This tool uses RFC 4648, accepts optional padding on input, and requires the bytes to be valid UTF-8 text. Use the exact alphabet, byte encoding and normalization form required by the receiving system. Similar looking formats are not automatically compatible. A decoded string can contain markup or control characters and must be treated as untrusted input by the next application. A valid conversion also does not prove that the data is authorized, safe or semantically correct. Try a round trip when the operation is intended to be reversible, and compare Unicode code points or UTF-8 bytes if two strings look equal but fail an exact comparison. For records that will be stored or signed, document the transformation as part of the data contract rather than relying on a visual preview.