All tools

Base58 / Base62 Encoder

Encode / Decode

Encode and decode text as Base58 (Bitcoin-address style) or Base62 (alphanumeric, URL-safe)

Encode text into Base58 or Base62 and decode it back, using the same big-integer conversion Bitcoin addresses and short-URL generators rely on. Base58 drops the four characters people most often mistype or misread when copying by hand (0, O, I, l), which is why it shows up in cryptocurrency addresses and other identifiers meant to be read aloud or typed manually. Base62 keeps the full alphanumeric set (0-9, A-Z, a-z) for a denser, fully URL-safe encoding with no punctuation, commonly used for short IDs and slugs. Both preserve leading zero bytes correctly on decode, matching the standard Bitcoin-style convention rather than silently dropping them.

base58base62encodedecodebitcoinurl-safe

How to use Base58 / Base62 Encoder

  • 1.Choose Base58 or Base62, then paste text into the input to see it encoded instantly.
  • 2.Switch to Decode mode and paste an encoded string to get the original text back, with a validity indicator flagging characters outside the chosen alphabet.
  • 3.Use Base58 when the output needs to avoid ambiguous characters (e.g. an identifier a person might type by hand), and Base62 when you want a denser, purely alphanumeric encoding.

Frequently asked questions

What's the difference between Base58 and Base62?
Base58 excludes 0, O, I, and l to avoid visual ambiguity, the same alphabet Bitcoin addresses use. Base62 uses the full alphanumeric set (0-9, A-Z, a-z) for a slightly denser encoding with no excluded characters.
Is this the same as Base64?
No. Base64 includes + and / (or - and _ in the URL-safe variant) and uses padding, while Base58 and Base62 avoid punctuation entirely and encode the input as one big number in a different base, which changes both the alphabet and the output length.
Are leading zero bytes preserved?
Yes. A leading null byte in the input becomes a leading character at position 0 of the alphabet in the output, and decoding correctly restores it, matching the standard convention used by Bitcoin's Base58Check encoding.
Is my data sent anywhere?
No, the browser tool encodes and decodes entirely client-side. The REST API and SDKs process whatever text you send them, same as any other API call.

Use via API, SDK, or MCP

cURL# Free: 1,000 req/day · Pro: 10,000 req/day
curl -X POST https://api.utilix.tech/v1/tools/base58-base62-encoder \
  -H "Authorization: Bearer utx_live_..." \
  -H "Content-Type: application/json" \
  -d '{"input":"hello world","mode":"encode","variant":"base58"}'

Get an API key from your dashboard · Full API docs →

Related tools

Base32 Encode / DecodeEncode and decode Base32 with Standard, Extended Hex, Crockford, and z-base-32 alphabetsEncode / DecodeBase64Encode and decode Base64 stringsEncode / DecodeHTML EntitiesEncode and decode HTML entitiesEncode / Decode