> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/features/advanced/add-custom-tokens.md).

# Add custom tokens

How to show, hide and add custom tokens in Cake Wallet by contract address on Ethereum, Polygon, Base, Arbitrum, BNB Smart Chain, Solana, Tron and Zano.

Token-chain wallets (Ethereum, Polygon, Base, Arbitrum, BNB Smart Chain, Solana, Tron and Zano) can show extra assets alongside their native coin. On the EVM chains, Solana and Tron a curated set of popular tokens comes out of the box — stablecoins like USDT and USDC are already there, just toggled on. Anything else, you can add yourself in about a minute.

## Show or hide tokens

On the wallet home screen, open the `Assets` tab and tap the `Tokens` button. The `Home screen settings` page lists available tokens with toggles — flip one on and it appears on your home screen. You can also sort assets and switch the combined-balance display here.

![Home screen settings with token toggles](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/tokens_01_list_hl.png)

## Add a token by contract address

If a token isn't in the list, add it with its contract address:

{% stepper %}
{% step %}

### Get the address from a source you trust

Copy the token's contract address from the project's official website or a reputable block explorer (like Etherscan). Never use an address someone sent you in a DM or comment thread — fake lookalike tokens are the oldest scam in the book, and Cake Wallet will warn you about exactly that.
{% endstep %}

{% step %}

### Fill in the form

On `Home screen settings`, tap `+`. Paste the contract address — the token's name, symbol, and decimals usually fill in automatically. Tap `Save`.

![Add Token form with scam warning](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/tokens_02_add-form_hl.png)

{% hint style="danger" %}
A contract address identifies a token — it is not a deposit address. As the form says: **never send tokens to the contract address.** Funds sent there are unrecoverable.
{% endhint %}
{% endstep %}

{% step %}

### Done

The token appears on your home screen with your balance. Receiving works with your wallet's normal address — one address covers the native coin and every token on that chain (see [Receive funds](https://docs.cakewallet.com/features/basic/receive-funds)).
{% endstep %}
{% endstepper %}

## Which standard am I adding?

The form is the same everywhere — only the token standard differs by chain:

| Chain                                              | Standard   | Address to paste               |
| -------------------------------------------------- | ---------- | ------------------------------ |
| Ethereum, Polygon, Base, Arbitrum, BNB Smart Chain | ERC-20     | Token contract address (`0x…`) |
| Solana                                             | SPL        | Token mint address             |
| Tron                                               | TRC-20     | Token contract address (`T…`)  |
| Zano                                               | Zano asset | Asset ID                       |

{% hint style="info" %}
Zano has no curated default asset list, so every extra asset on a Zano wallet is one you add yourself by asset ID.
{% endhint %}

{% hint style="warning" %}
The same ticker can exist on many chains — USDT lives on Ethereum, Tron, Solana, and more. Add the token on the chain you'll actually receive it on, and make sure senders use that network.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cakewallet.com/features/advanced/add-custom-tokens.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.