Ethereum Checksum Address Converter

Convert Ethereum addresses to EIP-55 checksum form in your browser. Paste one address or a list, see which letters are capitalized from Keccak-256 of the hex string, and optionally apply an EIP-1191 chain id. A mixed-case address that does not match is flagged as a typo.

Ethereum addresses

One address per line, or several separated by spaces or commas. The 0x prefix is optional.

Leave blank for the EIP-55 checksum Ethereum wallets expect. A number switches to EIP-1191.

Checksummed addresses

Checksum added

0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed

Why each character has this case

A letter is uppercase when its hash nibble is 8–f. Digits never change.

Keccak-256 of the hex string: d385650ce8fdc6db7ee3a091d34814dbc4ce18219ffae52182efff4034d707e5

5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed

Converted in your browser. The address is not uploaded.

What an Ethereum checksum address is

An Ethereum address is 20 bytes, written as 40 hex characters with an optional 0x. Hex letters have no case of their own, so 0x5aae… and 0x5AAE… are the same account. EIP-55 uses the capital letters as a checksum: a wallet can reject an address when one character was mistyped. The checksum does not change which account you are paying. It only makes a typo visible. All-lowercase and all-uppercase addresses are still valid accounts; they just do not carry a check. A mixed-case address is either exactly right or it should be treated as a typo.

How the EIP-55 checksum is calculated

Strip 0x and lowercase the 40 hex characters. Hash that 40-character string with Keccak-256 — the hex text, not the raw 20 address bytes. Walk the address and the hash together. When the hash nibble at that position is 8, 9, a, b, c, d, e, or f, write the address letter in uppercase. Otherwise leave it lowercase. Digits never change. If you also type a chain id, the hash is Keccak-256 of the decimal chain id glued in front of the hex string (EIP-1191). Leave the chain id blank for the checksum MetaMask, ethers, and viem use on Ethereum. Hashing the 20 raw bytes instead of the hex string produces a different, wrong checksum.

EIP-55 worked examples

  1. A lowercase address gets its checksum

    Input: 0x5aaeb6053f3e94c9b9a09f33669435e7ef1beaed. No chain id.

    Keccak-256 of the 40-character string starts d385650c…. The first letters are decided by nibbles 3, 8, and 5: 3 leaves a lowercase, 8 makes the next a uppercase, 5 leaves e lowercase. The address begins 0x5aAe.

    0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed

  2. The same address, already checksummed

    Input: 0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed

    The mixed case matches the EIP-55 result character for character, so nothing is rewritten.

    Checksum already correct. Same address: 0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed

  3. One flipped letter is a bad checksum

    Input: 0x5aaeb6053F3E94C9b9A09f33669435E7Ef1BeAed — the third hex character is lowercase, and later letters are mixed.

    The correct third character is A, because hash nibble 8 is at least 8. This input is mixed case and does not match, so it is a failed checksum rather than a new encoding.

    Rejected. The EIP-55 form is still 0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed.

  4. Hashing the raw bytes gives the wrong address

    Same lowercase address, but Keccak-256 of the 20 raw bytes instead of the hex string.

    The byte hash starts 793f8874… and capitalizes a different set of letters. That string will not match ethers or MetaMask.

    Wrong result: 0x5AaEB6053F3E94c9b9a09F33669435E7ef1beAED. EIP-55 is 0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed.

  5. A chain id changes the letters

    Same address with EIP-1191 chain id 30, then with chain id 1.

    Chain 30 hashes 30 plus the lowercase hex. Chain 1 hashes 1 plus the hex. Neither is the blank-field Ethereum checksum.

    Chain 30: 0x5aaEb6053f3e94C9B9A09f33669435E7Ef1beaEd. Chain 1: 0x5AAeB6053f3E94c9B9A09f33669435E7EF1bEaeD. Ethereum: 0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed.

Ethereum checksum address FAQ

What is an EIP-55 checksum address?
It is the same 20-byte Ethereum address with some hex letters capitalized. The capitals are chosen from Keccak-256 of the lowercase hex string, so a single wrong character usually breaks the pattern and a wallet can warn you.
Does the checksum change the account?
No. 0x5aaeb6053f3e94c9b9a09f33669435e7ef1beaed and 0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed are the same account. Only the spelling of the letters changes.
Are all-lowercase addresses invalid?
No. EIP-55 says an all-lowercase or all-uppercase address has no checksum to check, so wallets accept it. Some addresses are all lowercase even after checksumming, because every relevant hash nibble was below 8. 0xde709f2102306220921060314715629080e2fb77 is one of those.
Should I enter chain id 1 for Ethereum?
No. Leave the chain id blank. The address Ethereum tools expect does not include the chain id in the hash. Typing 1 produces a different EIP-1191 spelling that ethers and viem reject.
What is EIP-1191?
EIP-1191 is an optional checksum that prefixes the decimal chain id before hashing, so the same account can have a different capitalisation on another chain. Use it only when that chain’s tooling asks for it.
Is this the same as an ICAP address?
No. ICAP is an IBAN-like encoding of an address. EIP-55 keeps the normal 0x hex form and only changes letter case.
Is the address uploaded?
No. Keccak-256 runs in your browser. Do not paste a private key or a seed phrase here — this tool is for public addresses only.

Related developer tools

How it works

  • Paste one or more 20-byte Ethereum addresses. The 0x prefix is optional.
  • Leave the chain id blank for the EIP-55 checksum Ethereum wallets expect, or enter a chain id for EIP-1191.
  • The checksum is Keccak-256 of the lowercase hex string, calculated in your browser. A mixed-case address that does not match is marked as a typo.

For education only — not financial advice. Past performance does not guarantee future results.