RLP & Base58
Encode and decode RLP, Base58 and Base64.
Runs offline
Encoding
Paste a JSON array of hex strings to encode, or hex to decode.
What RLP is for
RLP is how Ethereum serialises transactions and account state. A JSON array of hex strings encodes to a list; a hex string encodes as a single item and also decodes if it is already RLP.
About rlp & base58
Three encodings that show up constantly and are awkward to do by hand. RLP is how Ethereum serialises transactions and account state. Base58 is what Bitcoin and Solana use for addresses, with the visually ambiguous characters removed so an address cannot be misread. Base64 appears in NFT data URIs and JSON-RPC payloads.
Common questions
What is RLP encoding?
Recursive Length Prefix — Ethereum binary serialisation for transactions, blocks and some trie structures. If you inspect raw tx bytes or build tooling, you meet RLP constantly; ordinary token transfers hide it inside the wallet.
When do I need Base58 versus Base64?
Base58 avoids ambiguous characters and appears in many Bitcoin and Solana addresses; Base64 is common in APIs and files. This page converts both directions so you can move between hex and those alphabets without a separate utility.
Does encoding here broadcast anything?
No. It only transforms bytes in the tab. An encoded transaction still needs signing and submission elsewhere before it exists on a network.