Base92 encode

No, and that matters. Unlike Base64 there is no single agreed 92-symbol alphabet, so this build uses its own: printable ASCII in a fixed order beginning with exclamation mark and ending with the double quote. A library elsewhere calling itself base92 is unlikely to decode this output. Use it for your own round trips, not for interchange.

Ninety-two printable ASCII characters: exclamation mark, hash, dollar, percent, ampersand, parentheses, asterisk, plus, comma, minus, period, slash, the digits, the usual punctuation, A to Z, brackets, caret, underscore, backtick, a to z, braces, pipe, tilde, and finally the double quote. Space, backslash, apostrophe and semicolon are absent.

It is the densest encoder in this set. Ninety-two symbols carry more bits per character than 85, 64 or 58, so the text is the shortest of the family for the same input. That is useful when you control both ends and only need a compact printable form of some bytes.

The encoder treats the entire input as a single large number and divides it down, the same technique the Base58 and Base62 tools use. There are no chunk boundaries, so a change near the start propagates through the rest of the output. Leading zero bytes are handled separately and written as leading exclamation marks.

Not on this site, and not reliably with an outside library, because the alphabet is this build's own. If you need a round trip, keep a decoder that uses exactly this ordering, or pick Base64 or Base85 where the alphabet is settled.

No. The conversion is done by a Web Worker in this tab and nothing is sent to a server. That is worth knowing here in particular, because a non-standard encoding is usually something you are using inside your own system, and the values you test it with are often real ones.