Batch convert between Cosmos(cosmos1), Ethereum(0x) with checksum and different cosmos or EVM based chains using bech32 address prefixes. Process multiple addresses at once with export support.
Enter one or multiple addresses (separated by newlines) for instant batch conversion. Connect a wallet to auto-fill.
Please input address
---Bech32 is an address format used by many blockchain networks, especially Cosmos-based chains. The prefix (like 'cosmos', 'osmo', 'juno') identifies which specific blockchain network the address belongs to. For example: 'cosmos1abc...' is a Cosmos Hub address, while 'osmo1abc...' is an Osmosis address. The part after the prefix contains the same underlying account information.
Efficiently process multiple addresses at once. Enter addresses one per line and instantly convert them to all supported formats. Use the column toggle to customize your view and export results as CSV or JSON for integration with other tools.
Note that the derivation path (SLIP44) of Cosmos/ATOM (118) addresses is usually different from Ethereum/ETH (60)!
This means this tool CANNOT calculate conversion between Cosmos and EVM addresses from a SEED PHRASE (HD Wallet).
Some EVM-compatible Cosmos-SDK based chains (e.g., Evmos, Dymension) use 60 as the derivation path. Please be careful when you are converting prefixes based on these chains.
Even with the same private key, Cosmos and EVM addresses will be different due to secp256k1 public key are compressed or not. This tool converts between address formats, not between keys.
For an example list of derivation paths for different chains, please refer to this document by Cosmostation.
A checksum address (EIP-55) is a system for Ethereum addresses that adds a mix of uppercase and lowercase letters to help catch typing mistakes. By using a special method to decide which letters should be capitalized, it makes errors more obvious and helps ensure transactions go to the correct address.
Explore the GitHub repository to view the source code, contribute to pull requests and issues.
Visit my blog for more developer tips and stories.