Base58 Encoder and Base32 Converter

Convert text to Base58 or Base32 and back. Pick the scheme, switch between encode and decode, and copy the result. Base58 uses the Bitcoin alphabet; Base32 follows RFC 4648. It runs in your browser.

This base58 encoder turns plain text into a Bitcoin-style Base58 string and decodes it straight back, and the same panel handles Base32 both ways. Base58 leaves out the characters that are easy to mix up — zero, capital O, capital I and lowercase l — which is why it shows up in wallet addresses and short IDs. Switch the scheme to run Base32 decode online against RFC 4648 output, or flip to encode to produce it. Every step of the base32/base58 conversion is computed by hand in your browser, so nothing you paste leaves the page.

Plain text
Base58

How it works

  1. 1

    Pick Base32 or Base58

    Choose the scheme with the toggle. Base58 uses the Bitcoin alphabet; Base32 follows the RFC 4648 standard alphabet with = padding.

  2. 2

    Encode or decode

    Switch direction to turn text into a code, or to read a base58/base32 string back into text.

  3. 3

    Copy the output

    Grab the result with one click, or download it as a text file.

Instant & 100% private — nothing is uploaded

Everything runs locally in your browser. Your code, text and files are processed on your own device and are never sent to a server — so there are no upload waits, no size limits from us, and nothing is ever stored or logged.

Frequently asked questions

What is Base58 used for?
It encodes bytes as text while skipping characters that look alike, so a hand-copied string is harder to get wrong. You see it in Bitcoin addresses, IPFS hashes and short public IDs.
How is Base58 different from Base64?
Base64 keeps a compact fixed-width scheme but includes +, / and easily confused letters. Base58 drops 0, O, I, l and the symbols, so it is longer but safer to read and retype.
Does the Base32 side follow RFC 4648?
Yes. It uses the standard A–Z and 2–7 alphabet with = padding, so the output matches what other RFC 4648 tools and libraries produce.
Can I decode a Base32 or Base58 string back to text?
Switch to decode and paste the string. Base32 decoding is case-insensitive and ignores padding; Base58 expects the Bitcoin alphabet. Invalid characters are flagged instead of guessed.
Is my data uploaded anywhere?
No. The encode and decode both run in your browser with hand-written logic, so the text never leaves your machine.