Text Input
Ready

Characters

0

Bytes

0

Output

0

Settings

Bitcoin

info

Validation

Uses the Bitcoin Base58 alphabet. UTF-8 text is encoded locally in your browser.

Encoding Tools / Base58 Encode

Base58 Encode for browser-based encoding workflows

Use this Base58 encode tool when you need to turn plain text into a compact alphabet that avoids visually ambiguous characters. Paste text, encode it through UTF-8 bytes, choose Bitcoin, Flickr or Ripple Base58, then add grouping or line wrapping for readable handoff. It is useful for compact identifiers, test strings, QR-friendly text, wallet-adjacent debugging and systems where Base64 characters such as plus, slash and equals signs are awkward. Encoding runs in the browser, so quick checks stay close to the value you are testing.

vpn_key

Encode text to Base58

Convert pasted text into Base58 using UTF-8 bytes, with optional ASCII-only validation for stricter compatibility checks.

tune

Choose the alphabet

Use Bitcoin Base58 by default, or switch to Flickr or Ripple when the receiving system expects one of those alphabets.

download

Format and export output

Group or wrap long output, review character and byte counts, then copy or download the Base58 result.

What Base58 encoding does

Base58 is a binary-to-text encoding that represents bytes with 58 printable characters. The Bitcoin alphabet removes characters that are easy to confuse, including 0, O, I and l, which helps when values are typed, copied, printed or scanned.

This encoder starts with text and turns it into UTF-8 bytes before applying the selected Base58 alphabet. It does not add padding, and it preserves leading zero bytes as leading alphabet-zero characters when such bytes are present in the encoded input.

Base58 is not encryption and it is not the same as Base58Check. Base58Check adds version bytes and checksum behavior on top of Base58; this page creates plain Base58 output from text.

Common Base58 encode use cases

Compact identifiers: Generate short text-derived values that avoid visually ambiguous characters.

Wallet-adjacent debugging: Create plain Base58 test strings while keeping Base58Check checksum behavior separate.

QR-friendly text: Produce values that avoid punctuation commonly found in Base64 output.

Fixture generation: Create safe encoded samples for docs, unit tests and parser checks.

Alphabet comparisons: Compare Bitcoin, Flickr and Ripple output when integrating with systems that name a specific alphabet.

Transport format checks: Compare Base58 with Base64, Base32 and UTF-8 bytes before choosing a representation.

Base58 encode examples

Start with short safe samples so you can confirm alphabet behavior before using longer values.

Text input:
devbruh.dev

Bitcoin Base58 output:
RtxP3Vddzae9PJM

Text input:
Hello world

Bitcoin Base58 output:
JxF12TrwXzT5jvT

Format and compatibility notes

Alphabet: Bitcoin Base58 is the default. Flickr and Ripple use different orders, so choose the alphabet that matches the tool or library that will decode the value.

No padding: Base58 does not use = padding. If a protocol expects padded output, it probably wants Base64 or Base32 instead.

Text input: This page encodes pasted text as UTF-8 bytes. It is not an arbitrary binary file encoder or a Base58Check address generator.

Related encoding tools

Encoding Tools - use the hub when you need to choose between Base58, Base64, Base32, URL, HTML, JSON, UTF-8 and byte tools.

Base58 Decode - use this to decode Bitcoin, Flickr or Ripple Base58 into UTF-8 text or byte fallback output.

Base64 Encode/Decode - use this when a system expects standard Base64 text instead of Base58.

Base32 Encode - use this for RFC 4648 Base32 output with padding, case, grouping and wrapping controls.

QR Code Generator - use this when the encoded value needs to move from screen to phone.

UTF-8 Converter - use this to inspect the bytes that text will feed into Base58 encoding.

Base58 Encode FAQ

What does this Base58 encoder do?

This Base58 encoder converts pasted text into Base58 using UTF-8 bytes in the browser. It supports optional ASCII-only validation, Bitcoin, Flickr and Ripple alphabets, grouping, line wrapping, copy, download and length stats.

Why use Base58 instead of Base64?

Base58 avoids visually confusing characters and does not use plus, slash or equals padding characters. That can make short identifiers easier to copy, read aloud, scan in QR codes or place in text-oriented systems.

Is Base58 the same as encryption?

No. Base58 is reversible encoding, not encryption, hashing or secure storage. Anyone with the encoded value can decode it back to the original bytes.

Can I choose a Base58 alphabet?

Yes. Bitcoin Base58 is the default, and the page also includes Flickr and Ripple alphabet options. Alphabet choice matters because each alphabet maps byte values to characters differently.

Can I wrap or group the output?

Yes. The encoder can group output into 4- or 8-character chunks and wrap long Base58 strings at a chosen line width. Remove whitespace later if the receiving system expects a compact value.

Is Base58 encoding processed locally?

Yes. Text-to-UTF-8 conversion, Base58 encoding, alphabet selection, grouping, wrapping, copy and download actions are handled by JavaScript in your browser on this static page.

Learn more about Base58

Base58 compatibility depends on alphabet choice, leading zero handling and whether a higher-level format such as Base58Check is required. Use this page for plain text-to-Base58 output, then verify important wallet, key or checksum-bearing values in the final toolchain.