Base32768 Encoder And Decoder

Encode a string of text as qntm Base32768 Unicode text, or decode Base32768 text back into standard text.



Question

What is Base32768?

Base32768 is qntm's binary-to-text encoding optimized for UTF-16 text. It uses a carefully chosen Basic Multilingual Plane repertoire to represent text compactly while staying inside selected Unicode ranges.

This tool follows qntm's base32768 repertoire and padding behavior. Malformed padding, a final-length character in the middle, or a character outside the qntm alphabet is rejected, and decoded output must be valid UTF-8 text.

Exact alphabet compatibility matters. Base32768 is different from qntm Base2048, Base4096-style encodings, Base65536, private-use alphabets, and emoji encodings. Changing the repertoire, normalization assumptions, or final-bit handling creates incompatible text even when the name looks similar.

Base32768 is an encoding, not encryption, compression, signing, authentication, or privacy protection. Use it for controlled Unicode-clean workflows and comparisons, and verify the same algorithm before exchanging encoded values with another tool.


Code

Unicode and transport cautions

Base32768 uses selected Unicode BMP characters, not ASCII. Fonts, copy and paste, Unicode normalization, JSON escaping, HTML, Markdown, SMS, social networks, databases, old browsers, source code editors, command lines, terminals, logs, and storage systems may transform, reject, escape, wrap, or display encoded text differently.

The qntm repertoire is designed to avoid many unsafe code points and be normalization-stable, but that does not make the output universally transport-safe. Do not assume it is suitable for URLs, shell commands, programming-language string literals, ASCII-only protocols, old browser workflows, or systems that sanitize unfamiliar Unicode.

If the target system needs printable ASCII, use Base64, Base64url, Base32, Base58, or another encoding designed for that transport. If the target system claims Base32768 support, confirm it uses the qntm alphabet and the same final-length padding behavior.