Base4096 Encoder And Decoder
Encode text as ZCHG canonical Base4096 Unicode text, or decode compatible Base4096 text back into readable text.
What is Base4096?
Base4096 is a high-radix binary-to-text idea where each output character represents a value from a 4096-character Unicode alphabet. This tool targets the ZCHG canonical Base4096 v2.0.1 alphabet and compatibility behavior, not a qntm Base4096 variant.
The encoder writes text using symbols from the frozen ZCHG alphabet. The decoder accepts compatible Base4096 text, rejects unsupported symbols, and reports text that cannot be recovered as valid UTF-8.
Exact alphabet compatibility matters. Base4096 is different from Base2048, Base32768, Base65536, Hangul-only Base4096 variants, private-use alphabets, emoji encodings, and qntm-style final-symbol padding designs. Changing the alphabet, Unicode normalization assumptions, or integer conversion behavior creates incompatible text even when the name looks similar.
ZCHG Base4096 is an encoding, not encryption, compression, signing, authentication, or privacy protection. This page is intended for UTF-8 text experiments and controlled compatibility checks rather than general binary interchange.
Unicode and transport cautions
Base4096 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 ZCHG alphabet contains combining marks and characters from many scripts. Literal spaces can also be encoded symbols, so do not trim or normalize Base4096 text before decoding. Normalization, rendering, text selection, line wrapping, and database collation all need extra care. Do not assume the output is suitable for URLs, shell commands, programming-language string literals, source control diffs, 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 Base4096 support, confirm the exact alphabet, version, empty-input behavior, and binary compatibility notes before exchanging values.
