Base92 decode
Base92 decode. Runs on your device, nothing is uploaded.
Base92 decode treats this build's own 92-symbol alphabet as one big number, the same technique decode-base58 and decode-base62 use, and converts it back into bytes. A leading run of the alphabet's first symbol becomes that many zero bytes at the start. Base92 has no agreed standard, so output here is not guaranteed to match another base92 tool's.
Questions
What alphabet does it use?
This build's own 92-symbol printable-ASCII alphabet, not a shared external standard.
How are leading zero bytes handled?
Each leading character equal to the alphabet's first symbol becomes one leading zero byte in the output.
Will output match another base92 tool?
Not guaranteed; unlike base64, there is no single de facto base92 standard, so different implementations can choose different alphabets.
What happens with an invalid character?
The tool refuses, naming the character and its offset.
Can I use this from the command line?
Yes, the same code runs on the page, the CLI and MCP.