base converter
type text to encode it, or paste encoded text to read it. every base here follows its published standard, so what you copy decodes in other tools too.
questions
which standard does each base follow?
base32 and base64 follow RFC 4648. base58 uses the bitcoin alphabet, base85 is ascii85 (the one in PDF and PostScript), base91 is basE91, base1024 is ecoji v2, base2048 is qntm's base2048 and base4096 is Base4096Hangul. binary, octal, decimal and hex write each UTF-8 byte on its own, spaced, like other text-to-binary tools.
why do base4096 tools disagree?
there is no base4096 standard. each tool picks its own 4096 characters, so text from one only decodes in the same tool. this one follows Base4096Hangul, which uses the hangul syllables from U+AC00. base2048 is different: qntm's alphabet is the one every base2048 tool uses, and this matches it exactly.
what about base36 and base62?
neither has a standard for text. both read the bytes as one big number and write a 0 for each leading zero byte, the way base58 does. base62 uses 0-9, A-Z, a-z, the order most base62 tools use.
why not base 7 or base 300?
no other tool would read the result. every base here has a published encoding, so what it writes decodes elsewhere, and what other tools write decodes here.
is there a size limit?
not for most bases. base36, base58 and base62 read the whole text as one number, so they stop at 20,000 bytes to stay fast.