Base65536 Encoder And Decoder
Encode readable text as qntm Base65536 Unicode text, or decode compatible Base65536 text back to UTF-8.
What is Base65536?
Base65536 is qntm's binary-to-text encoding for text systems that count Unicode code points rather than bytes. It represents most byte pairs as one selected Unicode character, with a separate character set for an odd final byte.
This tool follows qntm's base65536 alphabet, ordering, and final-symbol behavior. Characters outside the qntm alphabet, or final-byte symbols before the end of input, are rejected, and decoded output must be valid UTF-8 text.
Exact alphabet compatibility matters. Base65536 is different from Base32768, Base4096, Base2048, Base131072, private-use alphabets, and emoji encodings. Changing the repertoire, byte ordering, normalization assumptions, or final-byte handling creates incompatible text even when the name looks similar.
Base65536 is an encoding, not encryption, compression, signing, authentication, or privacy protection. qntm now considers it obsolete for Twitter-style sharing compared with Base2048, but it remains useful for controlled Unicode-clean workflow experiments and comparisons.
Unicode and transport cautions
Base65536 output is high-radix Unicode text, 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, storage systems, and sanitizers may transform, reject, escape, wrap, or display encoded text differently.
The qntm repertoire is selected to avoid many unsafe code points and to remain stable under common Unicode normalization forms, 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 strip unfamiliar Unicode.
If the target system needs printable ASCII, use Base64, Base64url, Base32, Base58, or another encoding designed for that transport. If another system claims Base65536 support, confirm it uses the qntm alphabet, byte-order mapping, and odd-final-byte repertoire.
