Supported Cryptocurrencies in Trezor Suite 2024: Complete List and Network Access

A cryptocurrency holder with a Trezor hardware wallet faces a straightforward practical question: which assets can I actually manage through Trezor Suite, and on which networks are they accessible? The official Trezor Suite application serves as the management interface for these devices, but support varies. Some cryptocurrencies are available on mainnet and testnet; others are restricted by region, firmware version, or device capability. A complete and current understanding of this catalog prevents confusion during setup and clarifies which assets remain accessible versus which require alternative tooling.

Trezor Suite runs on Windows, macOS, Linux, Android, and iOS, with web access available through Chromium-based browsers supporting WebUSB. The application does not hold private keys—the hardware wallet retains complete custody and requires physical confirmation for sensitive operations. This architecture means that support is determined partly by the device firmware, partly by the application’s routing and display logic, and partly by the networks and service providers that Suite integrates. Understanding what is supported and under what conditions is essential for confident asset management.

Major layer-one blockchains and their native assets

Trezor Suite supports the primary networks that represent significant value and user adoption. Bitcoin (BTC) remains the foundational asset, with access to mainnet and testnet, along with SegWit address types and Taproot functionality. The application handles Bitcoin’s UTXO model, coin selection, and fee estimation through connected nodes or public services. Ethereum (ETH) is fully supported on mainnet, with access to account-based transactions, smart contract interaction, and ERC-20 token transfers through the application interface.

Litecoin (LTC), Bitcoin Cash (BCH), Dogecoin (DOGE), and Zcash (ZEC) round out the UTXO-based layer-one offerings. Litecoin benefits from SegWit and fee management similar to Bitcoin’s. Zcash access includes transparent addresses; shielded address functionality depends on device capabilities and application version. Polkadot (DOT), Cosmos (ATOM), Solana (SOL), Tron (TRX), and XRP Ledger (XRP) each have distinct transaction models and address standards that Trezor Suite accounts for in its signing logic.

Cardano (ADA) is supported with full UTxO model integration, and Algorand (ALGO) benefits from the application’s account-based handling. Ripple’s XRP Ledger operates on its own consensus without mining or smart contracts in the Ethereum sense; Trezor Suite displays balances and manages transactions accordingly. These assets represent different cryptographic assumptions, fee mechanisms, and recovery phrase compatibility. A user migrating from one wallet to another should verify that address derivation matches expected standards, as incompatibilities can lead to lost funds or inaccessible accounts.

ERC-20 tokens and Ethereum ecosystem assets

Because Ethereum serves as the foundation for the largest token ecosystem, Trezor Suite’s ERC-20 support is particularly extensive. This includes stablecoins such as USDC, USDT, DAI, and others that track fiat currencies. The application displays token balances, manages token transfers, and integrates token metadata so that users see recognizable names rather than contract addresses. Token transfers require ETH for gas fees, and the application calculates dynamic gas costs based on network conditions.

Less commonly known but often essential are bridge tokens and wrapped versions of other assets. Wrapped Bitcoin (WBTC), Wrapped Ether (when interacting with non-Ethereum chains), and similar cross-chain representations are supported where the underlying ERC-20 standard applies. The Suite application does not provide an integrated swap interface for token exchange, so conversion between assets typically requires interaction with external decentralized exchanges or centralized services. This separation maintains the principle that Trezor Suite is a management interface, not a trading platform.

Ethereum’s second-layer and sidechain assets introduce a complexity boundary. Polygon (MATIC), Arbitrum (ARB), Optimism (OP), and Base are supported as distinct networks within the Ethereum ecosystem, each with their own gas tokens and ERC-20 variants. A user must ensure they are sending tokens to the correct network destination; accidentally bridging or sending to the wrong layer can result in funds held on an incompatible contract or chain. The application’s network selector is meant to prevent this, but verification at the address and network level remains a user responsibility.

Stablecoin support across multiple networks

Stablecoins amplify the multi-chain reality. USDC exists on Ethereum, Polygon, Arbitrum, Optimism, Base, and others. USDT is similarly distributed. A Trezor user holding USDC on Arbitrum cannot directly spend it on Ethereum mainnet without a bridge transaction. Trezor Suite manages the assets on each chain separately, displaying them in the portfolio view with network identifiers. The application does not automatically rebalance or bridge between chains; that remains a separate transaction operation.

This multi-chain fragmentation has become a practical limitation for stablecoin users. If liquidity or a transaction requirement appears on one network but the user’s balance is on another, manual bridging is necessary. Some bridge services integrate third-party providers, but the process still requires sending funds through an intermediary contract and waiting for settlement. The security assumption changes during a bridge: funds leave Trezor’s signing protection and become subject to the bridge protocol’s security, which may differ substantially from the signing device’s guarantees.

Decentralized stablecoins such as DAI are also supported on their respective networks. DAI on Ethereum mainnet, Polygon, Arbitrum, and others are recognized as distinct assets within the Suite interface. The application distinguishes between them to prevent user confusion, though the underlying economic relationship (that all are supposed to represent one dollar) can sometimes diverge during market stress or network congestion.

Testnet access for development and verification

Trezor Suite includes testnet access for Bitcoin, Ethereum, and several other major chains. Bitcoin testnet provides a sandbox environment where users can verify transaction construction, fee calculation, and address derivation without risking real funds. Ethereum testnet variants, such as Sepolia and Goerli (deprecated but sometimes still used), allow developers and users to practice smart contract interaction and token transfers in a non-production setting.

Testnet access is particularly valuable for users performing significant transactions for the first time or testing recovery procedures. A user can restore a Trezor from a recovery phrase, send a test transaction to testnet, and verify that address derivation is consistent and funds arrive as expected. This validation step is advisable before moving substantial value through the same setup on mainnet. The application clearly separates testnet from mainnet in the account list, reducing the likelihood of accidental misdirection, though human error remains possible if attention lapses during account selection.

Some testnet coins can be obtained from faucets or testnet exchanges. The acquisition process is not trivial; testnet Bitcoin faucets are often slow or require proof-of-work tasks. However, the value of testing critical workflows before mainnet operation—especially for users unfamiliar with a particular blockchain—justifies the effort. A failed test transaction costs only time; a failed mainnet transaction of significant value can result in permanent loss.

Alternative layer-ones and emerging networks

Beyond the major chains, Trezor Suite extends support to networks with more specialized use cases. Monero (XMR) is supported with a distinct signing process that accommodates its privacy model and key derivation rules. Zcash (ZEC) is supported with transparent address functionality; shielded address support depends on the device capability and Suite version. Neither privacy coin offers the same transaction preview and fee management interface as Bitcoin or Ethereum, reflecting their different cryptographic requirements.

Cosmos ecosystem chains such as Atom leverage a shared SDK, allowing Trezor to support multiple Cosmos-based networks with similar signing logic. Osmosis, Evmos, and others in the Cosmos ecosystem can be accessed once the appropriate chains are added to the Suite’s network list. This extensibility reduces the work required to add new networks but also places greater responsibility on the user to ensure they are adding legitimate networks with accurate RPC endpoints, not phishing or compromised alternatives.

Newer or smaller-cap networks are often added incrementally. A network’s inclusion in Trezor Suite depends on community demand, firmware support, security review, and the application’s maintainer capacity. Users seeking support for a less common chain can propose it through official channels, but there is no guarantee of timeline or inclusion. In the interim, alternative wallet software or hardware-wallet-compatible tools may be necessary, introducing additional attack surface if those alternatives are not equally well-maintained.

NFT viewing and asset metadata integration

Trezor Suite includes NFT viewing functionality for Ethereum and compatible networks. Users can see ERC-721 and ERC-1155 tokens associated with their addresses, along with metadata such as images, collection information, and descriptions. This viewing is non-custodial; the Suite displays assets stored on the blockchain and retrieved through indexing services. Transferring NFTs still requires transaction signing through the hardware wallet, maintaining the security model.

The NFT metadata relies on third-party providers to fetch and display images and details. If a metadata service becomes unavailable, the visual representation may not load, though the NFT itself remains on the blockchain. Users should not assume that an NFT’s appearance in the Suite represents its current market value or authenticity; the application shows what is on the blockchain, not whether the underlying project remains active or legitimate. Rug pulls, abandoned projects, and counterfeit collections are visible in the Suite if they exist on the chain.

NFT support is also limited by network availability. NFTs on Ethereum, Polygon, Arbitrum, and other EVM-compatible chains can be viewed if those networks are enabled in the Suite. NFTs on non-EVM chains, including those on Solana or other platforms, are not displayed by default. Users holding NFTs on multiple networks must check each separately or use multi-chain viewing tools outside of Trezor Suite.

Hardware compatibility and firmware requirements

Support for specific cryptocurrencies and networks depends on which Trezor device is used. Trezor Model T supports the full range of assets and networks covered in Suite. Trezor Model One, the older hardware wallet, has more limited support; some newer assets and networks are unavailable due to firmware constraints and device memory limitations. Before purchasing a device or planning a migration, users should verify that their target assets are supported on their specific device model.

Firmware updates can add new asset support, fix security issues, or improve address derivation standards. Users should keep their Trezor firmware current; Trezor Suite prompts for updates when available. The update process itself requires physical confirmation on the device, ensuring that updates cannot be forced remotely. However, some assets or networks may remain unavailable until firmware reaches a certain version, creating a sequential dependency between updates and functionality.

WebUSB support in Trezor Suite requires a modern browser. Chromium-based browsers including Chrome, Brave, and Edge support WebUSB, while Firefox and Safari do not. Users relying on Safari or Firefox for web access must use the desktop Suite application instead. Mobile versions of Suite on Android and iOS use platform-specific APIs rather than WebUSB, offering comparable functionality with better integration into the operating system. A user’s choice of device and browser can affect which assets and networks are accessible, making advance verification necessary.

Regional restrictions and service availability

Some assets and services integrated into Trezor Suite may be subject to regional restrictions. Certain exchanges and rate providers used for price feeds may be unavailable in specific jurisdictions. Trezor Suite displays market prices and exchange rates through third-party APIs; if those services are blocked in a user’s region, price information may not load. This limitation is cosmetic if the user is holding assets long-term, but it prevents real-time market monitoring and price-based decision making.

Cryptocurrency regulation varies by jurisdiction, and some assets face explicit restrictions in certain countries. Monero, for example, has faced regulatory scrutiny in several regions. Trezor Suite itself does not enforce geographic restrictions on asset support within the application, but users in restricted jurisdictions who attempt to transact may encounter obstacles at the blockchain or exchange level. The hardware wallet itself remains functional; the friction increases when trying to convert between cryptocurrencies and fiat currency through regulated services.

Users should verify current regulatory status in their jurisdiction before assuming an asset is accessible for trading or settlement. A cryptocurrency supported by Trezor Suite may be accessible for viewing and self-custody but not for regulated exchange or banking conversion. This distinction between technical support and regulatory accessibility is crucial for practical planning.

How to verify current support and plan asset management

The official source for current cryptocurrency and network support is the Trezor website and the Suite application’s own settings. Users can download the application and navigate to the settings to see the full list of supported coins and networks. This current view is more reliable than documentation that may lag behind actual implementation. The Suite also displays a network status indicator showing whether connectivity to each network is active.

For users planning to migrate assets or set up accounts, a practical workflow is to first download and explore the application without connecting hardware. Many Suite features, such as portfolio viewing and account setup, can be examined without a Trezor device. Once comfortable with the interface and confident that desired assets are supported, the user can then purchase or connect hardware and initialize their accounts. You can manage crypto and NFTs with the official app by downloading from the official trezor.io domain.

When setting up a Trezor with Trezor Suite for the first time, users should verify that the application is genuine by confirming the download source and checking the application signature. Installing from an untrusted copy defeats the security guarantees of the hardware wallet. After setup, users can gradually enable networks and accounts, testing with small amounts before consolidating larger balances. This staged approach reduces the risk of address derivation mismatches, incompatible network selections, or other configuration errors that could result in lost or inaccessible funds.