Trezor Suite Web Supported Tokens: Complete List and How to Add Custom Networks

November 26, 2025 | By user12

A user holds Ethereum and wants to consolidate several ERC-20 tokens into a single hardware wallet. They also use layer-2 networks like Arbitrum and Optimism, and prefer not to manage multiple wallets across different interfaces. The practical question is not whether tokens can be stored—any private key can authorize transactions on any blockchain—but which tokens appear natively in the portfolio view, which require manual address tracking, and how to safely add networks that Trezor does not list by default.

Trezor Suite Web is the browser-based counterpart to the desktop application, allowing cryptocurrency management from any device with an internet connection while the hardware wallet remains offline and in control of all signing operations. The web interface displays Ethereum, ERC-20 tokens, and other supported networks automatically, but the full list of compatible tokens and the process for adding custom chains involves several distinct workflows, each with different security implications. Understanding what is natively supported versus what requires manual configuration is essential for efficient portfolio management without accidentally exposing private keys or sending funds to the wrong contract.

A Trezor hardware device connected to a desktop environment displaying the Trezor Suite Web interface showing multiple token balances and account management options

Which tokens are natively supported in Trezor Suite Web

Trezor’s official token support list includes the major ERC-20 standards on Ethereum mainnet, such as USDC, USDT, DAI, WETH, LINK, AAVE, UNI, and hundreds of others that have been vetted and added to the Trezor Suite Web token database. This curated list reduces the risk that a user accidentally interacts with a counterfeit token or misconfigured smart contract. When a token appears in the native list, Trezor Suite Web displays the balance, transaction history, and address verification directly in the application interface without requiring the user to manually import or track the contract address.

The distinction matters operationally. A natively supported token shows a dedicated row in the portfolio, displays accurate decimal formatting, and provides a receive address specific to that token type. If a token is not on the official list, the user can still hold it at their Ethereum address—the private key controls all ERC-20 tokens at that account—but the balance will not appear in the portfolio overview unless manually added through custom token import.

Beyond Ethereum mainnet, Trezor Suite Web supports several layer-2 networks and alternative blockchains. Polygon, Arbitrum, Optimism, Avalanche, BNB Chain, and Solana are among the commonly available networks. Each network has its own set of natively recognized tokens. For example, Arbitrum includes native Arbitrum tokens as well as bridged versions of Ethereum tokens, while Optimism displays both L2-specific assets and wrapped counterparts. The important limitation is that token availability differs by network. A token available on Arbitrum may not be recognized on Polygon, even if it exists and is held in a cross-chain contract.

Users can verify current support by opening Trezor Suite Web, connecting their device, navigating to the accounts view, and selecting a specific network to see which tokens are listed. The list is regularly updated as new tokens gain prominence and security review. However, the absence of a token from the native list does not mean it is unsafe to hold or transact. It simply means the user must exercise additional care when confirming the contract address and transaction destination.

How to manually add custom ERC-20 tokens in Trezor Suite Web

Adding a token that is not on the native list requires locating its contract address and importing it into the application. The process begins with finding the correct contract address on a block explorer such as Etherscan, Arbiscan, or Optimismscan, depending on the network. The contract address is typically a 42-character string beginning with 0x. Copying the wrong address or finding a counterfeit token—a common threat—is why this manual step requires deliberate verification rather than a single-click import.

Once the address has been obtained from an authoritative source such as the token issuer’s official website or a reputable block explorer, the user can open Trezor Suite Web, select the correct account and network, and look for an “Add Custom Token” or “Import Token” option. Entering the contract address prompts the application to query the blockchain for the token’s name, symbol, and decimal places. The application displays these details for confirmation before the token is added to the portfolio. At this point, the token balance should appear if any of that token is held at the account’s address.

The security principle is straightforward: never trust a token import suggestion from an unverified source, and always verify the contract address independently before confirming. If a token is being imported to prepare for a transfer in, the user should also verify the receiving address on the hardware device’s screen before signing the transaction. Trezor Suite Web displays a confirmation screen on both the device and the application, allowing the user to cross-check that the amount, recipient, and contract address all match the intended transaction.

Layer-2 networks and how to configure them

Layer-2 solutions reduce transaction costs and increase speed by bundling transactions off the main Ethereum chain and settling them periodically. Arbitrum, Optimism, and other layer-2 networks are already integrated into Trezor Suite Web, meaning users can add accounts on these networks without additional setup. Selecting a layer-2 network from the network dropdown automatically derives addresses from the same seed phrase as the main Ethereum account, maintaining the security model: one hardware wallet, one recovery phrase, multiple networks and balances.

The user experience differs slightly from mainnet because layer-2 networks have their own token ecosystems. Some tokens exist only on layer-2; others are bridged versions of mainnet tokens. For example, USDC on Arbitrum is a native token that may differ slightly from USDC on mainnet, particularly if different bridge contracts are involved. Trezor Suite Web recognizes the most popular layer-2 tokens natively, but custom token import is still available if a specific token needs to be tracked.

One practical consideration is the distinction between “canonical” and “non-canonical” bridges. A canonical bridge is an official or widely trusted route for moving an asset from mainnet to layer-2. Using a token from a non-canonical bridge increases the risk of holding a less liquid or potentially compromised version. When adding a token on layer-2, the user should verify that the contract address and bridge path are consistent with the token issuer’s official documentation. Trezor Suite Web does not validate bridge authenticity, only the token contract itself.

Bridging tokens between mainnet and layer-2 itself requires moving funds through a bridge contract and waiting for confirmation on both sides. This is separate from the token import process. The bridge transaction is initiated like any other transaction—the user provides a destination address on the destination network and confirms the amount. The hardware wallet signs the transaction, and the bridge contract processes the asset movement. Because bridge transactions are irreversible and may take minutes or hours to complete, extreme care with the destination address is warranted.

Adding entirely new blockchains to Trezor Suite Web

Trezor Suite Web supports a fixed set of networks maintained by the Trezor development team. If a user holds assets on a blockchain not officially supported—such as a newer layer-1 chain, a specialized rollup, or a privacy-focused network—the hardware wallet itself may still support that chain at the firmware level, but Trezor Suite Web may not provide a ready-made interface. In such cases, users have two main options: use a third-party wallet that supports both Trezor and the target blockchain, or configure a custom RPC endpoint and blockchain parameters manually.

Adding a custom blockchain via manual RPC configuration is a more advanced workflow. The user would typically need to access custom network settings in Trezor Suite or use a third-party wallet with Trezor integration, providing the RPC endpoint URL, chain ID, block explorer URL, and native token details. The security consideration is significant: an incorrect or malicious RPC endpoint can display fake balances, relay false transaction data, or attempt to trick the user into signing unintended transactions. The hardware wallet still controls the actual signing, so funds cannot be stolen directly, but the user might be deceived into sending to the wrong address or confirming a transaction they did not intend.

Before adding a custom blockchain, verify that the RPC endpoint is operated by a trustworthy provider—often the blockchain’s official node operators, services like Infura or Alchemy, or the user’s own node if they operate one. The chain ID and block explorer should also match official documentation. Many users prefer to avoid custom RPC configuration altogether and instead use third-party wallets that have already integrated their target blockchains, accepting the trade-off of a different application interface in exchange for avoiding manual configuration.

For users who do proceed with custom networks, testing with a small transfer before moving larger balances is prudent. Send a minimal amount to verify that the destination address is correct, the wallet recognizes the transaction, and the balance updates as expected. Once the configuration is confirmed, larger transfers can proceed with more confidence.

Multi-asset wallet principles: why native support matters

Trezor Suite Web is fundamentally a multi-asset wallet, meaning a single hardware device and interface can manage Bitcoin, Ethereum, and dozens of other blockchains simultaneously. This consolidation reduces the number of recovery phrases to protect, simplifies account management, and keeps all transactions within one ecosystem. The trade-off is that cryptocurrency management becomes a matter of network and token selection rather than simply opening a dedicated application.

Native token support in Trezor Suite Web reduces friction and error. When a token is listed, the application handles decimal conversion, displays the correct symbol, and integrates the token balance into the portfolio view. All of this is done by the application, not by the blockchain. The blockchain itself does not know what a token “is”—it only knows smart contracts and account balances. Trezor Suite Web interprets those balances and presents them in human-readable form. This interpretation is only accurate if the application has the correct contract address and token metadata.

For tokens not on the native list, the user is responsible for providing and verifying the contract address. This is not a weakness of Trezor Suite Web; it is a design decision that prevents the application from automatically listing countless tokens, many of which may be counterfeit or malicious. The security boundary remains clear: the hardware wallet signs transactions, and the application displays information. A user cannot accidentally send to a wrong address if they verify the destination address on the device’s screen before confirming.

The cryptocurrency management best practice is therefore to use native token support whenever available, reserve custom imports for tokens that have been thoroughly verified, and treat each transaction as an opportunity to double-check the destination. This habit applies regardless of whether the user is managing a small portfolio or thousands of dollars in assets.

Blockchain security and transaction verification on the device

The security strength of any hardware wallet depends on the separation between a device that controls signing and an internet-connected interface that displays information. Trezor’s design keeps private keys exclusively on the hardware device. When a transaction is initiated in Trezor Suite Web, the application generates the transaction data but cannot sign it. The user must connect the hardware device, and the device itself displays the transaction details on its own screen. The user verifies the details—destination address, amount, token, network, gas fee—on the hardware device’s screen before physically confirming the transaction using the device’s button.

This verification step is essential when working with ERC-20 tokens or unfamiliar networks. If a user accidentally imports a custom token with the wrong contract address, or if Trezor Suite Web displays misleading information due to a bug or misconfiguration, the hardware device’s display is still the authoritative source. The address shown on the device is the actual destination. The amount displayed on the device is the actual amount. If the transaction details on the device do not match the transaction details in the browser, the user should cancel and investigate before proceeding.

For standard tokens, this verification is straightforward. For novel or suspicious tokens, additional precautions may apply. Some users verify the contract address on a separate block explorer window or with an independent tool before confirming on the device. Others require a second person to validate the address. These practices are optional, but they can prevent costly mistakes when significant value is at stake.

Practical workflows for managing diverse token portfolios

A user managing a diversified portfolio across Ethereum mainnet, Arbitrum, Polygon, and Optimism can organize accounts by network within Trezor Suite Web. Creating separate accounts for each network improves clarity and reduces the cognitive load of switching contexts. Each account derives from the same recovery phrase, so the security model remains unified. The interface displays the account list, and selecting an account shows only the tokens on that network.

For tokens on the native list, no additional setup is required beyond account selection. Balances appear automatically, and sending or receiving is straightforward. For custom tokens, the initial import step is required once per network. After the first import, the token remains in the portfolio unless manually removed, and future transactions use the already-configured contract address.

Portfolio tracking across multiple networks benefits from periodic review of addresses. Trezor Suite Web displays transaction history, but the history is organized by account and network, not chronologically across all holdings. Users managing significant balances often maintain an external spreadsheet or portfolio tracker to consolidate views across networks and derive asset allocation insights. This external tool does not compromise security, as it typically references only public addresses and does not involve private keys.

Backup and recovery practices should account for multi-network usage. The recovery phrase restores all accounts on all supported networks. However, if a user has manually added custom tokens to specific networks, that custom configuration is not part of the recovery seed. After recovering a Trezor from a seed phrase, custom tokens must be re-imported if they were not part of the native token list. Documenting which custom tokens are held and their contract addresses, stored securely offline, can speed recovery if the device is lost.

Security considerations when adding tokens and networks

The primary risk when adding custom tokens is inadvertently importing a counterfeit or scam token. If a user searches for “Uniswap” in Etherscan and selects the first result without verifying the official Uniswap website, they might copy a contract address that looks correct but is not. Trezor Suite Web will happily import this fake token, display a balance, and even allow transactions—the application has no way to know the contract is not the intended one. The blockchain does not validate that a contract is “legitimate”; it only validates that the contract exists and that the user’s private key authorizes the transaction.

Protecting against this risk requires adopting a discipline around contract address verification. Never copy a contract address from a search result, a social media post, or an unverified source. Always navigate directly to the official project website, locate the token information there, and copy the contract address from that authoritative location. Many projects list their contract addresses prominently to enable exactly this verification step.

A secondary risk involves configuring custom RPC endpoints. A malicious or compromised RPC can display fake transaction history, misrepresent balances, or relay unintended transaction data. The hardware wallet’s signing protection means that funds cannot be stolen without authorization, but the user might be deceived into signing a transaction they did not intend. Using official RPC providers, well-known infrastructure services, or operating a personal node mitigates this risk.

Network configuration mistakes are also possible. If a user adds a blockchain with an incorrect chain ID or mismatches the network parameters, the hardware wallet might sign a transaction for one chain that the user intended for another. The signature itself would still be valid, but the transaction might execute on an unexpected blockchain or fail outright. Before finalizing custom network configuration, test with a small transaction and verify on the destination block explorer that the transaction landed where intended.

Frequently asked questions

Does Trezor Suite Web support all ERC-20 tokens?

Trezor Suite Web natively displays hundreds of popular ERC-20 tokens, but not all tokens in existence. Any ERC-20 token can be held at a Trezor Ethereum address because the address is derived from the private key, which controls all token balances at that account. Tokens not on the native list can be manually imported by contract address so they appear in the portfolio view. Always verify the contract address against an official source before importing.

How do I add a custom token to Trezor Suite Web on Arbitrum or Polygon?

Select the Arbitrum or Polygon network from the network dropdown in Trezor Suite Web. Then look for an “Add Custom Token” option in the token list or settings. Enter the token’s contract address on that specific network—note that the contract address differs by network. The application will fetch the token name, symbol, and decimal places, which you should verify before confirming. Once added, the token remains in your portfolio for that network.

What happens if I import the wrong contract address when adding a custom token?

If you import a wrong or counterfeit contract address, Trezor Suite Web will display that token in your portfolio, but the balance will be zero unless you have actually received that specific token. If you later send real funds to that token address, they will be sent to the wrong contract and may be lost. This is why verifying the contract address on an official source before importing is critical. If you accidentally add the wrong contract, simply remove it from your portfolio and import the correct one.

Does Trezor Suite Web support layer-2 networks like Arbitrum and Optimism?

Yes, Trezor Suite Web fully supports Arbitrum, Optimism, Polygon, and other major layer-2 networks. You can create accounts on these networks and manage tokens there just as you would on Ethereum mainnet. The hardware wallet signs all transactions, and the same recovery phrase restores all accounts. Native tokens on these networks are automatically recognized; custom tokens can be imported as needed. Bridging assets between mainnet and layer-2 requires initiating a bridge transaction, which the hardware wallet signs like any other transaction.

Can I add a blockchain that Trezor Suite Web does not officially support?

Trezor Suite Web supports a fixed set of official networks. If you need to use a blockchain not on that list, you have two options: use a third-party wallet that supports both Trezor and your target blockchain, or configure a custom RPC endpoint if your Trezor firmware supports it. Custom RPC setup is advanced and requires careful verification of the endpoint, chain ID, and block explorer URL. Always test with a small transfer before moving significant funds to a custom network.