Base32 / Base58 / Base62 / Base85 Encoder

What it does

The Base Encoder converts text into four common byte-array base encodings - Base32 (RFC 4648), Base58 (Bitcoin), Base62, and Base85 (Ascii85) - and decodes them back to text. Each encoding operates on the UTF-8 bytes of your input, so multibyte characters and emoji round-trip perfectly. These encodings show up everywhere: Base32 in TOTP authenticator secrets and

DNSSECDNSSECA DNS extension that cryptographically signs zone records, letting resolvers verify answers were not forged or altered in transit.Learn more

, Base58 in Bitcoin addresses and short share links, Base62 in URL shorteners, and Ascii85 (btoa) in PDF and PostScript streams. Everything runs 100% client-side: nothing you type is ever sent to a server, so it’s safe for secrets and credentials.

How to use it

1. Pick the scheme - Base32, Base58, Base62, or Base85 - from the segmented toggle.
2. Choose Encode (text → encoded) or Decode (encoded → text).
3. Type or paste into Input (or hit Sample for a multibyte demo string).
4. Read the result in Output, or the error message if the input is invalid for the chosen scheme.
5. Copy the result, or Copy share link to send the exact input, mode, and scheme to a teammate.

Examples

Base32 (RFC 4648, padded)

Input: hello → Output:

NBSWY3DP

Input: foo (3 bytes) → Output (padded with = to a multiple of 8 chars):

MZXW6===

Base58 (Bitcoin alphabet - leading zero bytes become leading 1s)

Input: A → Output:

28

Base62 (BigInt base-conversion)

Input: A → Output:

13

Base85 / Ascii85 (4 bytes → 5 chars; a full zero group shortens to z)

Input: hi → Output:

BP@

Good to know

• Multibyte-safe: all four schemes encode the UTF-8 bytes of your text, so emoji and non-ASCII round-trip cleanly.
• Base32 uses the RFC 4648 alphabet (A-Z2-7) and pads with = to multiples of 8 chars. Base58 uses the Bitcoin alphabet (no 0, O, I, l) and preserves leading zero bytes as leading 1s. Base62 is 0-9A-Za-z with no leading-zero special-casing. Base85 is Ascii85 (!-u) with the z zero-group shorthand and no <~ ~> delimiters.
• Invalid input → error: a character outside the chosen alphabet (or a malformed trailing group) shows an error instead of garbage - decode rejects it rather than guessing.
• Shareable: your input, mode, and scheme are encoded in the URL, so a link reproduces the exact view.
• Private: all computation is 100% client-side - safe for secrets and credentials.
• Related tools:

  Base64Base64An encoding representing binary data as 64 safe ASCII characters, so it survives transport through text-only channels. It encodes — it does not encrypt.

  , Hex Converter,

  HashHashA one-way function that maps data of any size to a fixed-length digest. Same input, same digest; any change, different digest; not reversible.

  (SHA),

  HMACHMACA construction that combines a hash function with a secret key to prove a message is intact and came from someone holding the key.

  Generator.