Calculate CREATE2 address

Precompute a deterministic contract address from a deployer, salt, and init-code hash.

freeworks offlinenothing uploaded
ToolCREATE2 Address Calculator
Input
Output
—
Put this on your own site

The frame below runs the same code as this page, in the reader's own browser. Nothing is sent to us, and nothing is sent to you.

Pick a dark background and the text and panels follow it, so the frame stays readable on a dark page.

Preview

How it works

The address is the low 20 bytes of keccak256(0xff || deployer || salt || keccak256(init code)). The companion CREATE address uses keccak256 of the RLP list containing deployer and nonce; both results are shown in checksum case.

  • Zero salt, zero hash, and nonce zero make the derivation easy to compare with the standard example.
  • The salt and init-code hash are fixed 32-byte values.

Worked example

The EIP-1014 worked example
Zero deployer and salt, with the init code hash of a single 0x00 byte
Input
											Deployer address: 0x0000000000000000000000000000000000000000
Salt: 0x0000000000000000000000000000000000000000000000000000000000000000
Init code hash: 0xbc36789e7a1e281436464229828f817d6612f7b477d66591ff96a9e064bcc98a
Nonce: 0
Output
												Create2 address: 0x4D1A2e2bB4F88F0250f26Ffff098B0b30B26BF38
Create address: 0xBd770416a3345F91E4B34576cb804a576fa48EB1

When to use this

Factories precompute addresses, counterfactual wallets publish destinations before deployment, and scripts compare CREATE2 with nonce-based CREATE.

Edge cases

  • Changing init-code hash changes the address; runtime bytecode is not the hashed input.
  • A short salt is not a decimal number and must represent a complete 32-byte value.
  • The factory address, not the end user choosing the salt, determines the deployment address.

References