Phantom Wallet Download: Import From MetaMask, Coinbase Wallet, and Trust Wallet (Recovery Phrases)

A user holds crypto across multiple wallets—some in MetaMask, some in Coinbase Wallet, perhaps Solana tokens in Trust Wallet. Consolidating assets into one application reduces the number of recovery phrases to secure and simplifies day-to-day management. Yet moving funds between wallets without understanding address derivation, seed phrase compatibility, and network selection can result in permanent loss. The process is straightforward only if the underlying mechanics are clear beforehand.

Phantom Wallet supports Solana, Ethereum, Base, Polygon, Bitcoin, HyperEVM, Robinhood Chain, Arc, and BNB Chain through a single self-custody interface available as browser extensions and mobile apps. Importing an existing recovery phrase from MetaMask, Coinbase Wallet, or Trust Wallet into Phantom is possible but requires verification at every step. This guide walks through the technical reality: why seed phrases work, how address derivation differs across wallets, what can go wrong, and how to confirm that funds arrive intact.

Understanding seed phrases and derivation paths

A seed phrase is a standardized sequence of 12 or 24 words that generates cryptographic keys used to control cryptocurrency. Cryptocurrency wallets use hierarchical deterministic (HD) derivation to create separate addresses from a single seed. That is the foundation of wallet portability: the same 12-word phrase can theoretically unlock funds across different applications if they follow the same derivation standard.

In practice, « the same seed phrase » masks critical differences. Two wallets that read identical recovery words may still generate different addresses because they apply different derivation paths. A derivation path is a formula that transforms the master seed into specific account addresses. MetaMask, for example, may use the path m/44’/60’/0’/0 for Ethereum, while another wallet might use m/44’/60’/0’/0/0 or a non-standard variation. The difference is one character, but it points to completely separate addresses on the blockchain.

Solana adds another layer of complexity. Unlike Ethereum wallets, which often default to a single account, Phantom supports multiple accounts derived from the same Solana seed phrase. A user migrating from Trust Wallet may find that their funds are in account zero, but Phantom displays account one by default. This is not a bug; it is the result of different wallet developers making different choices about which derived account to show first. Confusion here is the leading cause of false « missing funds » reports.

Understanding derivation paths is therefore not optional detail for advanced users. It is the bridge between a seed phrase and actual asset recovery. Before moving funds, a user should verify which account holds the assets in the source wallet, confirm the exact derivation path if possible, and test with a small amount first.

Phantom wallet setup and importing a recovery phrase

The first decision when installing Phantom is whether to create a new wallet or import an existing one. For migration from another wallet, the import path is the correct choice. After completing the phantom wallet download on a desktop browser extension or mobile device, the setup wizard offers options to either generate a new seed phrase or enter an existing one.

Entering the recovery phrase requires typing or pasting all 12 or 24 words in the correct order. This is a critical vulnerability: if the device is compromised, malware can observe the input. If the paste buffer is monitored, the phrase is exposed. The safest method is to type the words manually, character by character, without using copy-paste from email, cloud notes, or any other synced location. A screenshot or photograph of the seed phrase should never exist on a connected device.

After entering the seed phrase, Phantom derives accounts and displays the associated addresses. This is the moment to verify. Open the source wallet (MetaMask, Coinbase Wallet, or Trust Wallet) on a separate device or browser tab without importing anything, and compare the first address Phantom shows with the first address in the source wallet for the same network. If they match, the import succeeded. If they do not, the derivation path is different or the words were entered incorrectly.

A common mistake is assuming that mismatched addresses mean the import failed completely. Instead, it usually means the wallets are deriving from different account indices. Most wallets allow switching between accounts. In Phantom, clicking the account icon and selecting « Add Account » or « Derive Account » can reveal addresses from different derivation indices. Check each one against the source wallet until a match appears. Once the correct account is identified, fund movements can proceed safely.

Moving Ethereum and Polygon assets across wallets

Ethereum and Polygon share the same address format and largely compatible tooling, which creates a false sense of interoperability. Ethereum addresses follow the ERC-55 checksum standard, and Phantom generates the same Ethereum addresses as MetaMask or Coinbase Wallet when using the standard derivation path m/44’/60’/0’/0. Polygon addresses are also identical across wallets because Polygon uses the same address space as Ethereum.

The risk is not address derivation but network selection. A user can enter a Phantom-generated Ethereum address into a Solana send screen by mistake, or send Polygon assets to an Ethereum address because they look the same. The blockchain will reject a Solana transaction sent to an Ethereum address format, causing the transaction to fail and the funds to return. Polygon to Ethereum sends, however, will appear to work but the funds will land on Polygon forever, inaccessible on Ethereum despite matching address appearance.

Before any cross-wallet transfer, verify the receiving network explicitly. In Phantom, switch to the correct network tab (Ethereum, Polygon, or other) and confirm the address. In the source wallet, do the same. If sending from MetaMask to Polygon via Phantom, the address looks identical, but MetaMask must be set to Polygon network and Phantom must have Polygon selected. A small test transaction is advisable: send 0.001 ETH or equivalent, wait for confirmation, and verify receipt before moving larger amounts.

Hardware wallet integration with Ledger devices adds another verification step. Phantom supports hardware wallet connections, which can increase security by keeping private keys on an offline device. However, this also requires confirming every transaction on the Ledger screen itself, which is slower but more transparent. The tradeoff is worth evaluating based on the account balance and frequency of transfers.

Importing Solana assets from Trust Wallet to Phantom

Solana presents a specific migration challenge because account derivation on Solana differs from Ethereum. Solana uses ed25519 keypairs derived from a seed phrase, but different wallets may use different derivation paths or even different seed phrase standards. Trust Wallet, for instance, may derive Solana accounts using one path, while Phantom uses another.

When importing a Trust Wallet recovery phrase into Phantom, the Solana addresses will likely not match immediately. This is expected and not a sign of failure. Open Phantom and look for an account switcher, which typically appears as a dropdown or account list. Click through the available accounts—most wallets support at least four derived accounts by default. One of them should match an address visible in Trust Wallet under the Solana network.

If no match appears, the source wallet may have used a non-standard derivation path or the recovery phrase may be specific to one wallet application. In this case, the only reliable method is to send funds from Trust Wallet to a newly derived Phantom Solana address. Verify the destination address in Phantom by copying it to a text editor, then pasting it into Trust Wallet’s send screen. Do not rely on manual typing; the address is too long and a single character error will send funds to a different wallet.

Phantom supports multiple Solana accounts and encourages creating separate accounts for different purposes. A user migrating from Trust Wallet should label their imported Solana account clearly—for example, « Imported from Trust Wallet »—to avoid confusion with newly created accounts. This labeling is visible only in the local wallet and does not appear on the blockchain, but it prevents operational errors during subsequent transfers.

Bitcoin, Base, and other supported networks

Bitcoin recovery requires special attention because Bitcoin uses a different derivation standard than Ethereum-compatible chains. Bitcoin addresses follow the BIP32 standard, and most wallets derive Bitcoin addresses from path m/44’/0’/0’/0. Phantom supports Bitcoin and will generate addresses matching MetaMask, Coinbase Wallet, or Trust Wallet if all three use the standard derivation.

However, Bitcoin addresses come in three formats: legacy (starting with « 1 »), SegWit (starting with « 3 »), and native SegWit (starting with « bc1 »). A wallet may support one or more formats, and a single seed phrase can generate addresses in all three formats using different derivation sub-paths. When importing a Bitcoin seed phrase, confirm which format the source wallet used and verify that Phantom generates an address matching that format. A legacy address and a SegWit address, derived from the same seed phrase, are not interchangeable.

Polygon and other EVM-compatible chains including Base, Robinhood Chain, and Arc use Ethereum address derivation. Base, a layer-2 network built on Ethereum, shares the same address format and standard derivation path as Ethereum itself. This means an imported recovery phrase will generate identical addresses on Ethereum and Base. The distinction is purely which network the address is registered on. Sending to a Base address on Ethereum will cause funds to appear in an account that is controlled by the same private key but perceived as a different application chain.

Phantom’s network selector is the critical safety tool here. Before sending funds, ensure that the destination network matches the sending network unless a cross-chain bridge is intentionally being used. Most user errors involve selecting Ethereum network on the Phantom side while the receiving address is a Base address, or vice versa.

Fees, asset validation, and avoiding counterfeit wallets

Phantom charges 0.85% for asset swaps within the wallet and 0.095% for perpetuals trading on Hyperliquid. These are disclosed fees, but users should verify them within the app before confirming any transaction. Fees can also vary based on network congestion and the specific route taken by liquidity. When swapping between assets, the preview screen should display the exact fee, slippage estimate, and final amount received. Never approve a transaction without reviewing these figures.

Asset validation is another critical step during migration. A user may have held tokens in Trust Wallet or MetaMask that are not supported or visible in Phantom by default. If a token does not appear in Phantom after importing the seed phrase, the address is correct but the wallet is not displaying that particular token. Custom token import is possible: Phantom allows users to add any token by its contract address. However, this is also a vector for scams. Pasting a random contract address into a wallet import screen can add a fraudulent token to the portfolio, creating confusion or potentially facilitating phishing.

Counterfeit Phantom downloads are a persistent threat. The legitimate wallet is distributed through official channels only: the browser extension stores (Chrome Web Store, Brave Store, Edge store), the Apple App Store for iOS, and Google Play for Android. Never install Phantom from any other source, including direct file downloads, third-party app stores, or links in unverified emails. Verify the publisher: official Phantom extensions show « Phantom Technologies » as the developer. Fake versions may have similar names or slightly altered icons designed to deceive.

Before importing any recovery phrase into a downloaded wallet, verify the wallet’s legitimacy. Visit the official Phantom website directly through a bookmarked link or typed URL—never through a search result or email link. Compare the extension or app version number with the current release shown on the official site. If in doubt, contact Phantom support through official channels only. This verification step can prevent total loss of funds to a fake wallet.

Testing, troubleshooting, and confirming successful migration

The safest migration procedure involves four stages: preparation, testing, execution, and verification. In preparation, write down or export the existing wallet’s addresses and balances from the source wallet. Document which assets are on which networks. In testing, install Phantom, import the recovery phrase, and verify that the addresses displayed match the source wallet. Do not send funds yet.

If addresses do not match, do not proceed. Instead, review the account selection process again. Most wallets allow viewing multiple derived accounts. Check each one. If still no match, the recovery phrase may not be compatible with Phantom. In this case, the safe approach is to create a new Phantom wallet and send all funds from the source wallet to the new Phantom addresses instead of importing. This takes longer but avoids the risk of sending to wrong addresses.

Once address matching is confirmed, execution can begin. Start with a very small test amount: 0.001 ETH, 0.0001 BTC, or an equivalent in other assets. Send this from the source wallet to the corresponding Phantom address. Wait for blockchain confirmation, which typically takes 1–3 minutes on Ethereum or Polygon, 10 minutes or more on Bitcoin, and seconds on Solana. Once confirmed, verify that the amount appears in Phantom and is accessible (the wallet can view the transaction history).

After the test succeeds, send the remaining balance in larger batches if preferred, or in one transfer. Avoid sending the entire balance immediately if the test was successful; batching allows recovery if an unexpected issue occurs during one transfer. Once all funds are in Phantom and have at least one blockchain confirmation, securely backup the Phantom seed phrase. This is now the authoritative recovery phrase for these assets. The old seed phrase from MetaMask or Coinbase Wallet should be retained until absolutely certain the migration is complete, but it is no longer the primary security key for these funds.

Common errors include funds appearing as a different token type (usually the result of a wrapped version on a different network), transactions appearing pending far longer than expected (usually because a low gas fee was paid), or balances showing zero (usually because the wrong account is selected). In each case, verify the transaction ID on the blockchain explorer for the relevant network, confirm that the address is controlled by Phantom’s seed phrase, and check account selection once more. These errors almost always have solutions and are not permanent fund loss.

Security after import and ongoing best practices

Importing an existing recovery phrase into Phantom creates a new access point to those funds. The same assets are now controlled by both the original wallet and Phantom simultaneously. This is not a duplication or copy; it is the same private keys being accessed through two different applications. If either application is compromised, the funds are at risk. Consolidating into one wallet and deleting the recovery phrase from other applications is therefore a logical next step after confirming the import succeeded.

Deleting a recovery phrase means uninstalling the original wallet application or deliberately discarding the written backup. Do not simply uninstall the app thinking the phrase is gone. A record of the phrase may exist elsewhere: cloud backups, email, screenshots, or written notes. After importing into Phantom, locate every copy of the old recovery phrase and securely destroy it. This is not paranoia; it is the difference between one recovery path being compromised versus two.

NIST cryptographic standards emphasize that the security of a system is limited by its least-secure component. A recovery phrase printed on paper and hidden is only as secure as the physical location where it is kept. A phrase stored in a password manager is only as secure as the master password and the password manager application itself. FinCEN guidance on cryptocurrency wallet regulation emphasizes that users bear primary responsibility for securing their own keys when using self-custody wallets like Phantom.

Best practices after import include enabling all available security features in Phantom: PIN locks, biometric authentication if supported, and confirmation prompts for transactions. Phantom also supports hardware wallet connections via Ledger, which moves key storage off the device entirely. For accounts holding significant value, hardware wallet integration substantially increases security. For smaller balances used for frequent transactions, device-based security with strong backup procedures is adequate but must be genuinely executed, not merely intended.