A user with a Trezor hardware wallet may wonder which assets can actually be managed through the official interface. Trezor Suite Web provides access to cryptocurrency and token holdings from any device with a browser, but the list of supported assets is neither infinite nor static. Understanding what can be added, traded, staked, or bought through the platform directly affects workflow decisions and whether alternative tools or exchanges become necessary.
The scope of asset support in Trezor Suite Web reflects both technical integration decisions and market demand. Bitcoin, Ethereum, and major altcoins are universally available, but support for smaller tokens, newer blockchain networks, and specialized assets requires active development and testing. This article examines which cryptocurrencies and tokens the Trezor Suite Web interface actually supports, how that list evolves, and what happens when a user holds an asset that is not yet integrated.
Core layer-one networks in Trezor Suite Web
Bitcoin remains the foundational asset in any Trezor Suite Web installation. The platform supports the Bitcoin mainnet with full account setup, balance tracking, transaction broadcasting, and verification on the hardware device itself. Users can generate multiple accounts under a single seed phrase, control UTXO selection for privacy-conscious spending, and implement transaction batching to reduce fees. The integration includes support for legacy, SegWit, and native SegWit address formats, allowing users to choose between compatibility and efficiency.
Ethereum is the second pillar of asset support. Trezor Suite Web manages ETH holdings, ERC-20 tokens deployed on Ethereum mainnet, and transaction signing on the hardware device. The interface displays account balances, transaction history, and gas estimates before confirmation. Users can interact with decentralized finance protocols, approve token spends, and manage multiple Ethereum accounts from the same wallet seed. Staking is available through integrated partners, allowing users to earn rewards while maintaining custody of their private keys on the Trezor device.
Litecoin, Bitcoin Cash, Dogecoin, and Zcash represent additional layer-one networks with native support. Litecoin benefits from SegWit and similar transaction optimization techniques available in Bitcoin. Dogecoin, despite its origin as a joke, has maintained network security and a user base, making it a reasonable inclusion for comprehensive asset management. Zcash’s optional privacy features—shielded transactions and transparent addresses—are accessible through the Trezor Suite Web interface, though the privacy guarantees depend on whether users consistently employ shielding.
Dash, Vertcoin, and Namecoin are supported for users who hold balances in these networks, though they receive less frequent updates and smaller development attention compared to Bitcoin and Litecoin. The core distinction is that these are separate blockchains with independent validation rules, distinct from tokens running on top of larger networks. When Trezor Suite Web adds support for a layer-one network, it means the platform can generate addresses, broadcast transactions, and verify signatures without reliance on external wallet software.
ERC-20 token support and the Ethereum ecosystem
The majority of Trezor Suite Web’s asset diversity comes from ERC-20 tokens running on Ethereum. Rather than integrating each token individually, the platform supports any ERC-20 token that adheres to the Ethereum token standard. Users can add custom tokens by entering a contract address, and the interface will fetch the token’s name, symbol, and decimal places. This design choice makes Trezor Suite Web extraordinarily flexible: thousands of tokens are theoretically accessible without requiring Trezor to maintain an explicit allowlist.
In practice, Trezor Suite Web includes a curated list of popular ERC-20 tokens with verified metadata. This list includes stablecoins such as USDC, USDT, DAI, TUSD, and BUSD, which are commonly used for trading pairs and transfers. Major governance tokens like UNI (Uniswap), AAVE (Aave), MKR (Maker), and SNX (Synthetix) are pre-loaded. Wrapped Bitcoin (WBTC) is available, allowing users to access Bitcoin-like assets within the Ethereum ecosystem. The list also covers protocol tokens for major decentralized finance platforms, NFT marketplaces, and layer-two scaling solutions.
The curation serves a practical function: it reduces the friction of adding frequently used tokens and decreases the likelihood that users will accidentally send funds to an incorrect or fraudulent contract. However, new tokens, lesser-known projects, and experimental assets can still be added manually by contract address. This flexibility is powerful but introduces responsibility: users must verify contract addresses carefully, as entering a wrong address will result in a token that has no balance and cannot be traded or transferred meaningfully.
One important limitation is that Trezor Suite Web’s ERC-20 support is specifically for Ethereum mainnet. Layer-two solutions such as Optimism, Arbitrum, Polygon, and Zksync are discussed separately because they involve different networks, different tokens, and different bridges or bridges to move assets between layers. A user holding tokens on Polygon or Arbitrum cannot directly access them through Trezor Suite Web unless they bridge the assets back to Ethereum mainnet.
Layer-two scaling solutions and alternative networks
Polygon (formerly Matic) represents one category of broader ecosystem support. Trezor Suite Web allows users to manage Polygon accounts and view MATIC balances, but the interface’s treatment of layer-two tokens remains incomplete. Users can hold and transfer MATIC, and they can interact with some Polygon applications, but accessing ERC-20 tokens on Polygon requires either manually configuring MetaMask integration or using alternative tools. This gap reflects the complexity of layer-two ecosystems: each layer-two solution has different security assumptions, different token representations, and different bridging mechanisms.
Arbitrum and Optimism are similar in their partial integration. Native assets (ARB and OP) can be managed within Trezor Suite Web to some degree, but comprehensive support for all tokens on these networks is not yet implemented. Users who primarily operate on layer-two platforms may find that Trezor Suite Web is not their most convenient interface, even though the hardware wallet can still sign transactions through compatible software like MetaMask combined with Trezor hardware verification.
The philosophy behind current layer-two support appears to be pragmatic: Trezor Suite Web prioritizes mainnet assets and the most commonly used scaling solutions. As layer-two ecosystems mature and standardization increases, support typically improves. However, users should not assume that holding tokens on an alternative chain automatically means Trezor Suite Web will display them. The accurate approach is to check the official documentation or attempt to add the network through the settings interface.
Solana represents a different architecture entirely. Unlike ERC-20 tokens that can be accessed through Ethereum network support, Solana is a separate layer-one blockchain with its own token standard (SPL tokens). Trezor hardware devices do support Solana signing through third-party integrations such as Phantom Wallet using Trezor as a signer, but the official Trezor Suite Web interface does not yet provide native Solana account management. This gap is significant for Solana ecosystem users and represents an area where Trezor’s support lags behind competitors like Ledger.
Asset discovery and the role of blockchain explorers
When a user imports a seed phrase into Trezor Suite Web or connects an existing hardware wallet, the platform automatically discovers Bitcoin and Ethereum accounts and displays balances. The discovery process searches standard derivation paths for transactions and balances on public blockchains. This automatic detection works reliably for major networks but may miss accounts that were created through non-standard paths or used on different platforms.
The interface allows users to manually add additional accounts for networks where automatic discovery is less reliable. This requires understanding HD wallet derivation paths or simply adding accounts one at a time and checking whether they contain funds. For layer-one networks like Litecoin or Dogecoin, the process is straightforward: the user selects the network and account number. For ERC-20 tokens, the user either selects from the curated list or enters a contract address for a custom token.
Blockchain explorers such as Etherscan for Ethereum or blockchair.com for multiple networks can help verify what assets a user actually holds. If a user knows they hold a token but cannot find it in Trezor Suite Web, checking the explorer with their public address will confirm the token contract and allow them to add it manually. This is a useful troubleshooting step that clarifies whether the problem is a missing integration or a misunderstanding about what was actually purchased.
Trezor Suite Web also provides transaction history and balance verification through these explorers. Users can click through from the suite to view detailed transaction data, contract interactions, and full audit trails. This integration preserves privacy by not requiring users to share address information with Trezor’s servers while still allowing detailed investigation when needed. For compliance or tax purposes, this information is essential; for everyday use, the suite’s built-in balance display is usually sufficient.
Buying, selling, and swapping within supported assets
Beyond simple holding and transfer, Trezor Suite Web includes integrated tools for buying and selling cryptocurrencies. These features typically connect to regulated partners such as Changelly, ShapeShift, or other exchange providers. When a user initiates a buy through Trezor Suite Web, they are not purchasing directly from Trezor; they are being routed to a third-party exchange with which Trezor has a partnership.
The supported assets for buying and selling depend on the exchange partner’s offerings and regulatory status. A user in the United States may see different available pairs than a user in Europe due to regional restrictions. The interface displays applicable fees, expected output amounts, and settlement timeframes before the user confirms. Importantly, the transaction is signed on the Trezor device, so even though an external exchange is involved, the final transfer to the user’s own address can be verified and controlled through the hardware wallet.
Swapping between different cryptocurrencies within Trezor Suite Web works similarly. If a user wants to exchange Bitcoin for Ethereum or USDC, the swap function routes the request through aggregators that search multiple liquidity sources for favorable rates. The routing occurs on external services, but the final transaction signing happens on the Trezor device. This design maintains key control while providing convenience similar to software wallets like MetaMask or Trust Wallet.
The exact assets available for swapping depend on the exchange partner’s liquidity and support. Major cryptocurrencies like Bitcoin, Ethereum, stablecoins, and popular altcoins are almost always available. Smaller tokens, newer projects, or assets with limited trading volume may not have liquid pairs. Users attempting a swap with an unsupported or illiquid pair will see an error message rather than receiving a quote, signaling that the transaction cannot be completed through this route.
Staking and rewards across supported networks
Ethereum staking is available through Trezor Suite Web partnerships, typically with services like Lido or similar staking providers. Users can initiate staking transactions that lock their ETH and earn annual percentage yields. The mechanism works by having users approve a staking contract through their Trezor device, then the platform handles the deposit into the staking pool. Users receive staking tokens or receive periodic reward distributions while their original ETH remains locked.
Staking on other networks is less comprehensively integrated into Trezor Suite Web. Some altcoins with proof-of-stake consensus or reward mechanisms may be stakeable through integrations, but the interface does not offer universal staking support. Users holding Polkadot (DOT), Cosmos (ATOM), or other networks with native staking should check the official documentation to understand whether Trezor Suite Web supports their chosen staking method.
The important consideration with staking is that rewards depend on the specific contract and protocol being used. Ethereum staking through a custodial provider differs from solo staking or running a validator node. Trezor Suite Web’s approach prioritizes ease of use and accessibility over maximum decentralization: users maintain custody of their keys through the hardware device, but they do not run the actual validator infrastructure. This is a reasonable trade-off for most users, though those seeking maximum control should understand the delegation model being used.
Updates, future roadmap, and asset additions
The list of supported assets in Trezor Suite Web is not static. New networks and tokens are added periodically as development resources allow and market demand justifies integration. The official trezor suite web documentation and GitHub repositories provide the most current information about supported networks and planned additions. Users should not assume that an asset they hold is supported until they have actually attempted to add it or checked the official documentation.
The development roadmap appears to prioritize commonly used layer-one networks, major tokens, and critical infrastructure updates. Layer-two solutions are gradually receiving better support as their adoption grows and standardization improves. Emerging networks and experimental protocols typically take longer to integrate because they require security review, testing, and ongoing maintenance as the network matures.
For users who hold assets not yet supported in Trezor Suite Web, alternative options exist. The hardware wallet can often be used as a signer for other applications: MetaMask can use Trezor for key management, Electrum can integrate Trezor for Bitcoin and similar networks, and specialized wallets for less common assets can connect to the device for transaction verification. This flexibility means that the lack of native support in Trezor Suite Web is typically not a fatal limitation—it is an inconvenience rather than a barrier.
The broader trend suggests that as cryptocurrency adoption matures and certain token categories become standard, Trezor Suite Web will add support. Stablecoins are essentially universally supported now because their utility and regulatory clarity make them essential. More experimental or speculative tokens may never receive native integration if their lifespans are short or their user bases remain small. This selectivity is appropriate: attempting to support every possible token would dilute focus from security and usability.
Frequently asked questions
Can I manage any ERC-20 token through Trezor Suite Web?
Trezor Suite Web supports any ERC-20 token on Ethereum mainnet by contract address, though a curated list of popular tokens is pre-loaded for convenience. To add an unsupported token, enter its contract address in the add token interface. Verify the address carefully: using an incorrect contract address will result in a token with no value and no way to recover the transaction.
Does Trezor Suite Web support layer-two networks like Polygon or Arbitrum?
Partial support exists for some layer-two solutions. MATIC and certain tokens on Polygon can be managed, but comprehensive ERC-20 token support on layer-two networks is incomplete. For full layer-two functionality, users may need to use MetaMask or other compatible wallets with Trezor hardware verification, or bridge assets back to Ethereum mainnet.
What should I do if I hold a cryptocurrency that Trezor Suite Web doesn’t support?
Check the official Trezor documentation to confirm lack of support. If the asset is not supported, your Trezor device can often be used as a signer for alternative wallets like MetaMask, Phantom, or specialized applications. You can also bridge or convert the asset to a supported token if liquidity exists on a decentralized exchange or centralized platform.
