Multi-Codec Text Encoder and Decoder

Encode or decode supported byte formats with Base32, Base58 and Ascii85 examples.

On-device No sign-up Free to use

Convert encoding controls

Showing an example. Edit to see your own.

?

Up to 4,096 UTF-8 bytes when encoding and 40,000 characters in either direction. Decoding rejects malformed or noncanonical groups. Unpaired surrogates are refused.

?

Each format has a specific alphabet and padding rule. None of these formats encrypts data.

Processed in your browser. Your inputs stay on this device.

Result

Showing an example.

Encode the three UTF-8 bytes in foo as padded RFC 4648 Base32.

Encoded UTF-8 bytes with RFC 4648 Base32 (A-Z, 2-7, padded). This is encoding, not encryption.
MZXW6===

Loading the tool. Your result will appear here.

https://usefreetools.net/multi-codec-encoder · 20 November 2026

Was this helpful?

How to use Multi-Codec Text Encoder and Decoder

  1. Choose Encode or Decode and select the exact codec variant. The Base32, Base58 and ASCII85 example buttons fill an encoding example.
  2. Paste UTF-8 text for encoding, or a value written in the selected encoded format for decoding.
  3. Copy the result after checking its alphabet and padding. If decoded bytes are not valid UTF-8, inspect the hex representation or download decoded.bin.

Example: Multi-Codec Text Encoder and Decoder

Encode the three UTF-8 bytes in foo as padded RFC 4648 Base32.

You add
Action: encode; Format: base32; Text or encoded value: foo
You get
Encoded UTF-8 bytes with RFC 4648 Base32 (A-Z, 2-7, padded). This is encoding, not encryption. MZXW6===

Options

Codec variant
Base32 uses uppercase A–Z, 2–7 and canonical padding. Raw Base58 uses the Bitcoin alphabet without a Base58Check checksum. Adobe Ascii85 uses <~ and ~> markers, with z allowed for a complete four-zero-byte group.
Byte-number formats
Binary expects whitespace-separated eight-bit groups. Octal expects adjacent three-digit byte escapes from \000 to \377, and hexadecimal expects adjacent \xNN escapes. Select the format yourself; it is not detected automatically.
Decoded bytes
Valid UTF-8 is shown as text. Invalid UTF-8 remains available as a hex representation and a binary download; replacement characters are not inserted to invent readable text.

Supported inputs and limits

  • Up to 40,000 input characters and 4,096 decoded or encoded bytes.
  • Text encoding uses strict UTF-8 and refuses unpaired surrogates.
  • Base32 is uppercase RFC 4648 with standard padding and canonical unused bits;
  • Base58 is the raw Bitcoin alphabet without Base58Check, with a tighter encoded-input cap of 5,600 characters.
  • Adobe Ascii85 requires <~ and ~>, supports z only for a full zero group and accepts ASCII whitespace.
More details

Binary uses whitespace-separated 8-bit groups.

Octal uses adjacent three-digit byte escapes and hex uses adjacent \xNN escapes.

Invalid UTF-8 remains available as byte values.

Example buttons select an explicit encoding.

Automatic codec detection is not provided; the visitor must choose the intended grammar.

Where your input is processed

This tool does not upload your inputs. See the limits for anything saved on your device.

Name the variant when sharing a value

Alphabet, padding and marker rules determine how a recipient decodes a value. Base32 and Adobe Ascii85 have different group sizes, while Base58 has its own alphabet and leading-zero behavior. Include the selected variant with an exported value rather than calling every compact representation Base64.

Questions about Multi-Codec Text Encoder and Decoder

Does Base58 include a Bitcoin checksum?

This mode uses the Bitcoin Base58 alphabet for raw bytes. It does not add or verify Base58Check version bytes or a checksum.

Which Base85 form is supported?

The supported form is Adobe Ascii85, with the marker and zero-run rules stated by the controls. Other Base85 alphabets are not interchangeable with it.

Why does decoding return bytes without readable text?

The decoded bytes may not be valid UTF-8. They can still be inspected as bytes, but the page does not silently replace invalid sequences to invent a text result.

Does encoding protect a secret?

These codecs change a representation and can be reversed. They do not encrypt the input or make a token confidential.

Page updated · Project managed by Tony Hines · Report a problem with Multi-Codec Text Encoder and Decoder