TON Address Converter
Convert a TON address between bounceable (EQ), non-bounceable (UQ), raw and testnet formats. Paste one address or a whole list — everything is validated and converted locally in your browser.
| Address A bounceable address is one that can receive messages that require a response, such as transactions. For more info, visit the documentation.Bounceable | Address A non-bounceable address cannot receive messages that require a response, such as transactions. For more info, visit the documentation.Non-Bounceable | Raw Address String The raw address represents the binary format of a TON address. It is encoded as a 32-byte hash combined with an 8-bit workchain identifier. Raw addresses are not user-friendly and are primarily used programmatically or in low-level implementations. For more info, visit the documentation.(info) | Normalized Address | Explorer |
|---|---|---|---|---|
| No addresses yet. Paste one above to get started. | ||||
Frequently asked questions
- What is a TON address?
- A TON address identifies a wallet or smart contract on The Open Network. It combines a workchain ID with a 256-bit account ID and can be shown in several equivalent formats — raw and user-friendly (bounceable or non-bounceable).
- What is the difference between bounceable and non-bounceable addresses?
- A bounceable address (prefix EQ) returns the funds if the destination contract cannot process the message, so it is used for smart contracts. A non-bounceable address (prefix UQ) does not return funds and is typically used for wallets and exchange deposits.
- What is a raw TON address?
- The raw format is the low-level representation written as workchain:hex, for example 0:83dfd552e63729b472fcbcc8c45ebcc6691702558b68ec7527e1ba403a0f31a8. It is a 32-byte hash with an 8-bit workchain ID and is used programmatically rather than shared with users.
- What is a normalized TON address?
- A normalized address is the canonical user-friendly form (URL-safe base64 with the bounceable flag off). Normalizing lets you reliably compare or deduplicate addresses that point to the same account.
- What do the EQ and UQ prefixes mean?
- In user-friendly base64 addresses, EQ marks a mainnet bounceable address and UQ marks a mainnet non-bounceable address. Both encode the same account and differ only by the bounceable flag.
- What do the kQ and 0Q prefixes mean?
- They are the testnet counterparts of EQ and UQ: kQ is a bounceable testnet address and 0Q is a non-bounceable testnet address. Only the testnet-only bit in the flag byte is set, so the underlying account is the same.
- How long is a TON address?
- A user-friendly TON address is exactly 48 base64 characters. A raw address is the workchain ID, a colon, and 64 hexadecimal characters — for example 0: followed by the 32-byte account ID.
- Are TON addresses case-sensitive?
- Yes. User-friendly addresses are base64, so upper- and lower-case letters are different characters. Copy addresses instead of retyping them and rely on the built-in checksum — TONify flags any address that fails it.
- How do I convert a TON address?
- Paste it into the field above. TONify detects the format automatically, accepts raw, bounceable, non-bounceable and testnet input, and shows every equivalent form at once. You can paste several addresses together and export the result as CSV.
- Is TONify free and safe to use?
- Yes. TONify is a free, open-source tool and all conversion happens locally in your browser — the addresses you paste are never sent to any server.