UseFreeTools

Multi-Codec Text Encoder and Decoder

Encode UTF-8 text or decode supported Base32, Base58, Ascii85 and byte-number representations.

Inputs stay on your device No sign-up Free to use
How this works

The tool runs in this browser. Your file or text is not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.

Privacy details

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.

How to use Multi-Codec Text Encoder and Decoder

  1. Choose Encode or Decode and select the named codec variant.
  2. Paste text for UTF-8 encoding, or a value written in the selected encoded format.
  3. Convert it and read any alphabet, padding or decoding error.
  4. Copy the encoded value or inspect the decoded text and bytes.

Example: Multi-Codec Text Encoder and Decoder

Encode the RFC 4648 Base32 example.

You add
Encode; codec: Base32; text: foo.
You get
The encoded value is MZXW6===. Decode in the same mode returns foo.

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. Adobe Ascii85 requires <~ and ~>, supports z only for a full zero group and accepts ASCII whitespace. 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.

Where your input is processed

This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save 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.

Project manager: Tony Hines · Content updated 1 October 2026 · Report a problem

Related tools

All tools in Developer