Base58 encoder and decoder
Encode text or bytes to Base58 with the Bitcoin alphabet, or decode Base58 back.
Input
Result
Fill in the input and press Run.
Your input is processed in memory and then discarded. It is not stored or logged. Even so, don't paste live passwords or keys into any online tool.
Use it from code or an agent
curl -s https://setget.net/v1/tools/base58 \
-H 'Content-Type: application/json' \
-d '{"input":{"text":"Hello World!"}}'
import json, urllib.request
body = {'input': {'text': 'Hello World!'}}
request = urllib.request.Request("https://setget.net/v1/tools/base58", json.dumps(body).encode(),
{"Content-Type": "application/json"})
print(json.load(urllib.request.urlopen(request))["result"])
const response = await fetch("https://setget.net/v1/tools/base58", {
method: "POST",
headers: {"Content-Type": "application/json"},
body: JSON.stringify({"input":{"text":"Hello World!"}}),
});
console.log((await response.json()).result);
Tool: run_tool
Arguments:
{
"slug": "base58",
"input": {
"text": "Hello World!"
}
}
{
"input": {
"text": "Hello World!"
}
}
Endpoint: POST /v1/tools/base58. Over MCP: run_tool with slug: "base58".
Machine-readable: input schema, Markdown. Connect an agent.
Inputs
| Name | Type | Required | What it does |
|---|---|---|---|
text |
string | yes | The value to encode, or the Base58 to decode. |
action |
string | no | Encode to Base58, or decode Base58. One of: encode, decode. Default: "encode". |
input_encoding |
string | no | When encoding, how the input is written: plain text (UTF-8), hex digits or base64. One of: text, hex, base64. Default: "text". |
Examples
Input
{
"text": "Hello World!"
}Result
{
"text": "2NEpo7TZRRrLZSi2U",
"bytes": 12
}Leading zero bytes become leading 1s
Input
{
"text": "0000287fb4cd",
"input_encoding": "hex"
}Result
{
"text": "11233QC4",
"bytes": 6
}Input
{
"text": "2NEpo7TZRRrLZSi2U",
"action": "decode"
}Result
{
"text": "Hello World!",
"encoding": "utf-8",
"binary": false,
"bytes": 12
}Questions
- Is this Base58Check?
- No. This is plain Base58. Base58Check, used for Bitcoin addresses, also appends a four-byte checksum, which is not added or verified here.
- Why are 0, O, I and l missing?
- The Bitcoin alphabet leaves them out because they look alike when read or typed.
- What if the decoded data is not text?
- Bytes that are not valid UTF-8, such as keys and addresses, are returned as hex with "binary" set to true.
Related tools
- Base64 encoder and decoderEncode text to Base64 or decode it back, in the standard or URL-safe alphabet.
base64 - Base32 encoder and decoderEncode text to Base32 (RFC 4648) or decode it back, with or without padding.
base32 - Hex encoder and decoderConvert text to hexadecimal bytes and back, with optional upper case and separators.
hex - Hash generatorCompute an MD5, SHA-1, SHA-256, SHA-384, SHA-512, SHA3-256 or BLAKE2b hash of text or bytes.
hash - All hashes at onceCompute every supported hash of one input at once: MD5, SHA-1, SHA-2, SHA3-256 and BLAKE2b.
hash-all - CRC-32 and Adler-32 checksumCompute the CRC-32 and Adler-32 checksums of text or bytes, as decimal and hex.
crc32