Base58 Encoder Decoder
Encode bytes as Base58 or decode Base58 with the Bitcoin alphabet or your own explicit 58-character alphabet.
Open toolUse an explicit input representation and strict Base32 padding. Provide Operation, Encoding input, Text, hex bytes or Base32 to compute results directly in your browser. Decode requires uppercase standard Base32 with canonical = padding, zero unused pad bits and no whitespace. Hex encoding requires full byte pairs. Empty input is valid. Decoded non-UTF-8 data stays available as original bytes. Input up to 100,000 UTF-16 units. Decoded UTF-8 containing NUL characters is shown as an escaped JSON string. The binary download keeps the original bytes.
Enter the inputs, then select Process input.
Result will appear here
The Base32 Encoder Decoder evaluates Operation, Encoding input, Text, hex bytes or Base32 in client-side JavaScript using the deterministic rule below and updates the output panel immediately without uploading data to a server.
Eight input bits are regrouped into 5-bit symbols from ABCDEFGHIJKLMNOPQRSTUVWXYZ234567.
Decode requires uppercase standard Base32 with canonical = padding, zero unused pad bits and no whitespace. Hex encoding requires full byte pairs. Empty input is valid. Decoded non-UTF-8 data stays available as original bytes. Input up to 100,000 UTF-16 units. Decoded UTF-8 containing NUL characters is shown as an escaped JSON string. The binary download keeps the original bytes.
Review the input parameters, allowed value ranges, and worked reference cases for the Base32 Encoder Decoder below before running your calculation.
| Parameter / Scenario | Default / Sample Value | Rule or Allowed Range | Output / Usage Note |
|---|---|---|---|
| Input: Operation | (User supplied) | Options: Encode, Decode | Required workspace parameter |
| Input: Encoding input | (User supplied) | Options: UTF-8 text, Hex bytes | Required workspace parameter |
| Input: Text, hex bytes or Base32 | foo | Input type: textarea | Required workspace parameter |
| Worked Case 1: Starting inputs | Preloaded / test values | Eight input bits are regrouped into 5-bit symbols from ABCDEFGHIJKLMNOPQRSTUVWXYZ234567 | Operation = Encode; Encoding input = UTF-8 text; Text, hex bytes or Base32 = foo |
| Worked Case 2: Comparison scenario (encoder decoder example) | Preloaded / test values | Eight input bits are regrouped into 5-bit symbols from ABCDEFGHIJKLMNOPQRSTUVWXYZ234567 | Operation = Decode; Text, hex bytes or Base32 = MZXW6=== |
Follow these three steps to configure Operation, Encoding input, Text, hex bytes or Base32, verify unit and boundary rules, and export your Base32 Encoder Decoder output.
Copy the result or save TXT. Decode also offers decoded-bytes.bin; Encode produces text without a binary file.
These concrete scenarios illustrate how the Base32 Encoder Decoder processes baseline inputs, comparison checks, and boundary constraints.
Operation = Encode; Encoding input = UTF-8 text; Text, hex bytes or Base32 = foo
Operation = Decode; Text, hex bytes or Base32 = MZXW6===
When solving for 'base32 encoder decoder', verify that Operation, Encoding input, Text, hex bytes or Base32 use consistent units and stay within the documented scope: Decode requires uppercase standard Base32 with canonical = padding, zero unused pad bits and no whitespace. Hex encoding requires full byte pairs. Empty input is valid. Decoded non-UTF-8 data stays available as original bytes. Input up to 100,000 UTF-16 units. Decoded UTF-8 containing NUL characters is shown as an escaped JSON string. The binary download keeps the original bytes.
The output panel reports the exact result derived from Operation, Encoding input, Text, hex bytes or Base32 alongside any unit or formatting notes.
Every calculation follows the rule: Eight input bits are regrouped into 5-bit symbols from ABCDEFGHIJKLMNOPQRSTUVWXYZ234567. Because JavaScript uses IEEE 754 double-precision floating-point arithmetic, numeric outputs display up to 12 significant digits where applicable.
Always cross-check the displayed result against the scope note (Decode requires uppercase standard Base32 with canonical = padding, zero unused pad bits and no whitespace. Hex encoding requires full byte pairs. Empty input is valid. Decoded non-UTF-8 data stays available as original bytes. Input up to 100,000 UTF-16 units. Decoded UTF-8 containing NUL characters is shown as an escaped JSON string. The binary download keeps the original bytes) before applying the value to production specifications, financial models, or lab records.
Review these boundary constraints and validation rules before relying on the Base32 Encoder Decoder output.
Operational scope: Decode requires uppercase standard Base32 with canonical = padding, zero unused pad bits and no whitespace. Hex encoding requires full byte pairs. Empty input is valid. Decoded non-UTF-8 data stays available as original bytes. Input up to 100,000 UTF-16 units. Decoded UTF-8 containing NUL characters is shown as an escaped JSON string. The binary download keeps the original bytes. Inputs that violate minimum/maximum bounds or required format rules are rejected with a clear diagnostic prompt.
Need an adjacent calculation in Developer Tools? Use the related tools linked below to chain your workflow without leaving your browser.
Encode bytes as Base58 or decode Base58 with the Bitcoin alphabet or your own explicit 58-character alphabet.
Open tool
Convert UTF-8 strings to and from RFC 4648 Base64URL format (- and _ alphabet) with optional '=' padding control in your browser.
Open tool
Convert hex, decimal, or binary byte arrays to UTF-8 strings with strict validation, or encode text into hex, decimal, and JSON byte arrays.
Open toolChoose another tool for your next calculation, conversion, or text task.

Validate pairs of hexadecimal digits and decode the bytes as strict UTF-8.
Open tool
Encode text as lowercase hexadecimal UTF-8 bytes.
Open toolEncode Unicode text to Base64 or decode UTF-8 Base64 text.
Open tool
Group binary digits into eight-bit bytes and decode them as strict UTF-8.
Open toolAnswers about using Base32 Encoder Decoder and understanding its results.
The Base32 Encoder Decoder applies the rule: Eight input bits are regrouped into 5-bit symbols from ABCDEFGHIJKLMNOPQRSTUVWXYZ234567. Enter Operation, Encoding input, Text, hex bytes or Base32 into the workspace and the tool computes the exact output in your browser.
Yes. Provide Operation, Encoding input, Text, hex bytes or Base32 using the documented units and format shown in the quick reference table above. Preloaded default values let you test the workflow immediately.
Decode requires uppercase standard Base32 with canonical = padding, zero unused pad bits and no whitespace. Hex encoding requires full byte pairs. Empty input is valid. Decoded non-UTF-8 data stays available as original bytes. Input up to 100,000 UTF-16 units. Decoded UTF-8 containing NUL characters is shown as an escaped JSON string. The binary download keeps the original bytes. Confirm that your inputs fall within the allowed ranges before exporting the result.
Yes. All calculations for the Base32 Encoder Decoder execute 100% locally in your browser's JavaScript runtime. No inputs or results are uploaded to any external server.
Choose another tool for your next calculation, conversion, or text task.