JSON Validator
Check JSON syntax and get the exact line, column and cause of any error.
Encode and decode Base58 in the Bitcoin, Ripple or Flickr alphabets.
The Base58 Encoder & Decoder handles the Bitcoin, Ripple and Flickr alphabets, including the leading-zero rule that a base change cannot express arithmetically and has to spell as literal leading characters.
Base58 is Base64 with the ambiguous characters taken out: no zero, no capital O, no capital I and no lowercase l, and no plus or slash. What remains is 58 characters that cannot be misread in a monospace font or mistyped from a handwritten note.
That is why it became the encoding for Bitcoin addresses, IPFS content identifiers and a lot of short-link schemes. Unlike Base32 and Base64 it is not a bit-packing but a change of numeric base, so it has to be computed with repeated division — which is also why leading zero bytes need special handling, each becoming one leading "1". Three alphabets are supported: Bitcoin, Ripple and Flickr, which order the same 58 characters differently.
The alphabet leaves out 0, O, I and l, so a value cannot be misread in a monospace font or mistyped from a note.
Each leading zero byte becomes one literal "1", which is the only way a base change can represent it — and the part naive implementations lose.
Bitcoin, Ripple and Flickr order the same 58 characters differently, and each is available.
Pasting a string with a 0 or an O explains that the alphabet omits them deliberately, rather than just failing.
Encode raw bytes written as hex, or ordinary text — whichever the value actually is.
Encode text or hex to Base58, or decode a Base58 string back.
Bitcoin is the default and by far the most common; Ripple and Flickr order the characters differently.
Invalid characters are named, including the ones the alphabet deliberately omits.
Take the output to your clipboard.
The digit 0, capital O, capital I and lowercase l — because they are easy to confuse — plus the plus and slash characters, which have meaning in URLs and filenames.
Base58 with a version byte prefixed and a four-byte checksum appended before encoding, which is what a real Bitcoin address uses. This tool does plain Base58; it does not add or verify the checksum.
Because Base58 is a base change, and arithmetic has no way to represent a leading zero. Each leading zero byte is encoded as one literal "1" character instead.
Yes. They contain the same 58 characters in different orders, so a string encoded with one will not decode correctly with another.
What people who use the Base58 Encoder & Decoder think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Base58 Encoder & Decoder. It takes half a minute and no account.
Write the first reviewCheck JSON syntax and get the exact line, column and cause of any error.
Generate believable company names, domains and details for mockups.
Explore a JSON document as a collapsible tree with paths you can copy.
Validate an IBAN's length, country and mod-97 checksum, and generate test ones.
Generate deterministic UUIDs from a namespace and a name.
Convert HTML back into clean Markdown, keeping lists, tables and code.
Re-indent a SQL query into readable clauses, joins and conditions.
Draw a grid layout and get the CSS, including named template areas.