Swap ETH to SOL from MetaMask to Phantom: Get Native SOL

Ethereum to Solana · Wallet workflow

By Marcus Richardson — Founder & Privacy Research Lead. Published September 19, 2026.

If you want to swap ETH to SOL from MetaMask to Phantom, begin with the assets and networks, not the app names. MetaMask and Phantom are wallet interfaces. The exchange you need is usually ETH on Ethereum into native SOL on Solana. Copying an address from one app into the other does not perform that conversion.

A useful outcome is simple to describe: spendable SOL in the Solana account you intended to fund. Reaching it requires checking where your ETH currently lives, selecting a route that actually outputs native SOL, and sending the deposit on the network that route accepts. This guide helps you make those decisions before you move funds.

First, identify which of these three jobs you actually need

“Move my crypto from MetaMask to Phantom” can mean three different things. You may want the same ETH in a different wallet interface, native SOL to pay Solana transaction fees, or another asset represented on Solana. Each job has a different correct endpoint. Treating all three as “bridging ETH” makes it easy to receive something you cannot use for your intended purpose.

This article follows the second job. You hold ETH, you want SOL, and you intend to use a Solana account in Phantom. If you only want a different app for the same Ethereum account, pause here: a crypto swap may be unnecessary. Changing your wallet software and changing your cryptocurrency are separate decisions.

MetaMask can hold Solana assets

Older instructions saying MetaMask cannot receive SOL are outdated. MetaMask’s current Solana documentation describes native Solana support and a separate Solana address for each account. You can therefore choose a Solana receiving account in MetaMask if that better suits your setup. Phantom is an option, not a technical requirement for owning SOL.

You do not need to import a recovery phrase between apps just to make an exchange. A supported receiving address is enough for an address-based payout. Keeping the current wallet arrangement and copying the correct public address avoids changing your key management merely to complete one swap.

Read the network attached to your ETH balance

The letters ETH are not a complete description of a deposit. Your balance might be on Ethereum mainnet, Base, Arbitrum or another supported network. A route accepting ETH on Ethereum mainnet expects a transaction on Ethereum mainnet. A familiar-looking address does not make a transfer on another network equivalent.

Open the asset details in MetaMask and identify the network shown for the balance you intend to spend. If the wallet combines assets in an overview, expand the specific holding. Record the network before comparing quotes. The sending network is a requirement to match, not a preference you can change at the last second to reduce fees.

Also distinguish ETH from wrapped ETH or another token. A service may list both, but an order expecting native ETH should not receive a token transfer simply because the wallet shows a similar value. Choose a route that explicitly accepts the asset you actually hold, or resolve that mismatch before creating the order.

A useful one-line specification: “I am sending native ETH on Ethereum mainnet and receiving native SOL on Solana in my Phantom account.” If your source is different, change that sentence first and find a quote that matches it exactly.

Compare routes by the result you receive

There are several ways to exchange assets across these networks. A wallet’s built-in cross-chain function may handle routing inside the app. An address-based service may ask for a destination address and a deposit transfer. A custodial exchange can provide a trading and withdrawal route where you already have an eligible account. Their costs and steps differ.

Phantom distinguishes same-network swaps from cross-network exchanges in its help documentation. Seeing a Swap button is not enough to know what route it will use. Read the selected source and destination networks, output token and quote details in the actual interface.

No row is universally cheapest or fastest. Compare the same amount on the same networks within a short period, because both asset prices and network conditions can move. A route that looks attractive before withdrawal costs may produce less SOL in your wallet than another quote with a higher advertised service fee.

For the address-based route, the AceChange ETH-to-SOL page describes sending ETH on Ethereum and receiving SOL on Solana. Confirm current availability and the actual selected pair in the live form. You remain responsible for the sending transaction; the exchange provider processes the deposit and payout according to the order conditions.

“Without a bridge” needs a precise meaning

People often search for a way to swap ETH to SOL without a bridge because they do not want to choose bridge contracts, manage wrapped assets or complete several transactions. An address-based exchange can offer a simpler user-facing workflow. That does not establish that no bridging or other routing happens anywhere in the provider’s infrastructure.

The useful promise to verify is narrower: you send the supported input and receive native SOL at the selected address, under the displayed terms. Do not choose a route based solely on a slogan about how its backend works. Choose it because its output, costs, funding method and conditions meet your needs.

Build a fair quote comparison

Write down the source amount, the destination amount and every separately charged cost. If you hold a total ETH balance, first decide how much you can send after paying the transaction fee. Sending your entire displayed balance into a quote does not make the separate Ethereum fee disappear.

For example, imagine a wallet holds 0.050 ETH. An illustrative transfer estimate is 0.001 ETH. A proposed 0.050 ETH deposit would exceed that budget once the fee is added. A smaller deposit might fit, but you must calculate it from the wallet’s actual preview. These numbers explain the arithmetic; they are not current gas estimates or recommended transaction amounts.

Now compare the SOL receive amounts for that affordable deposit. Label each output as fixed, estimated or a minimum under the particular route’s conditions. Those labels are not interchangeable. An estimate may move before execution, while a fixed quote can depend on sending the exact amount within the stated time window.

Do not subtract a payout fee twice if it is already included in the receive amount. Do include an additional withdrawal or transfer cost that the route will charge separately. If you cannot tell whether a cost is included, obtain clarification before treating the quotes as comparable. Our swap fee comparison guide provides a fuller worksheet.

Leave usable SOL after the swap

If your next step involves a Solana application, receiving SOL is only the funding stage. You will need resources for later transactions too. Solana’s official fee documentation explains that transaction fees are paid in SOL and can include a prioritization fee. A sponsored transaction may have another fee payer, but that is a feature to verify, not an assumption to make.

Do not immediately exchange every last unit of native SOL into another token unless the application clearly handles the later fees. Review the next transaction’s preview and retain enough for your intended activity. The appropriate amount depends on the actions you plan to take; a universal reserve quoted in a blog would be unreliable.

Walkthrough: ETH in MetaMask, SOL in Phantom

Prepare Phantom before creating the order

Open the Phantom account you intend to fund and use its receiving function for Solana. Copy the Solana address, not an Ethereum address displayed elsewhere in the same app. Phantom’s receive-crypto instructions explain how to select a network and copy the corresponding address.

Use the regular Solana token receiving account for SOL, not a separate Cash account. Phantom documents Cash deposits for selected stablecoins; it is not the destination to choose for a native SOL payout.

Check which account is active, especially if you use several accounts for different purposes. Give the address a clear label in your private notes. If you use a hardware-backed account, follow the wallet’s device-verification procedure. A successful format check in a swap form cannot tell whether you copied your preferred account or a different valid account.

Configure the swap around your actual source

Open the ETH-to-SOL quote and verify both network labels. Enter the amount you intend to deposit, paste your Solana receiving address, and inspect the quoted output. Check the route’s minimum, maximum if shown, rate type and any temporary availability notice. Read the conditions before creating the order.

Do not assume a URL or page heading has selected everything correctly. The live fields are the final check. If you discover that your ETH is on Base rather than Ethereum, stop and select a route supporting that source network. Sending on the wrong chain and asking support to repair it later is not a conversion method.

Copy the order’s Ethereum deposit instructions

Once an order is created, keep its page and identifier. Copy the deposit address from that specific order and note the requested amount and deadline. Old orders, a previous transaction in wallet history and another person’s screenshot are not substitutes for the current instructions.

For this workflow, the Ethereum deposit address belongs to the exchange process. Your Solana destination address belongs to the receiving account. Keep those two roles separate. The deposit address goes into MetaMask’s send screen; the Solana address goes into the swap’s receive-address field.

Review the send in MetaMask

In MetaMask, choose the source account and network, then initiate the ETH send to the order’s deposit address. Enter the amount specified by the order. Review the full destination, asset, network and fee before confirming. MetaMask’s official sending guide explains how to inspect the transaction and its later status.

A straightforward native-ETH transfer should correspond to the intended deposit. If a page unexpectedly asks you to expose a recovery phrase, install an unknown extension or authorize unrelated token spending, stop. Reopen the official service independently and verify the workflow. A public receiving address never requires disclosure of your private keys.

Follow both sides of the exchange

After sending, save the Ethereum transaction hash and track the order. The source transaction’s confirmation shows progress on Ethereum. The SOL payout is a separate transaction on Solana. Record that destination transaction identifier when the order provides it, and compare the recipient with the account you prepared.

Once the payout is confirmed, check Phantom’s Solana balance. If the interface has not refreshed, inspect the destination transaction before sending anything again. You want evidence of what happened on the network, not a second deposit created because an app display appeared slow.

Six situations that deserve a pause

The receive token says wrapped SOL

Check whether the output is native SOL or a wrapped token. They are related, but a wrapped representation is not automatically the spendable native balance expected for ordinary Solana fee payment. If the goal is native SOL, choose a route that says so or understand the additional supported unwrapping step before proceeding.

The source balance appears on more than one network

Choose the specific balance you intend to spend. A portfolio total can combine assets across networks, but a single deposit transaction cannot spend that combined total. Recheck the source account and network after opening the send screen; do not rely only on the app’s aggregate dollar value.

You have just enough ETH for the deposit

The sending fee still has to come from somewhere. Review the wallet’s total debit and reduce the proposed deposit if needed before creating an order. If the order already exists and the required amount is no longer fundable, follow its expiry or support instructions rather than sending a smaller amount without checking the consequences.

A tiny test transfer seems attractive

A test can help verify a workflow, but it must be a valid order that meets the service’s minimum. Do not send a small fraction into a larger fixed-amount order and assume the service will treat it as a harmless test. If you use a test, create and complete it as its own eligible exchange before considering another order.

The Ethereum transaction failed

Inspect its actual on-chain status. A failed transaction and a pending transaction are different problems. Before resending, establish whether the intended deposit reached the order address, whether the quote remains valid and whether your wallet has enough ETH for the next attempt. A failed transaction can still incur a network fee.

The order completed but SOL is not where you expected

Compare the payout address with the exact Phantom account you intended to fund. If they match, check the correct network and app display. If they do not, gather the order details and contact the provider promptly. A valid address is not proof of ownership, and a completed blockchain transfer cannot simply be recalled through a browser button.

Answers to the questions people ask before an ETH-to-SOL swap

Can I swap without connecting MetaMask to the exchange website?

An address-based order can be funded through an ordinary send from your wallet. It requires the destination address and deposit transfer rather than a website connection for signing the exchange. Follow the actual interface and verify the official domain. Other routes, including in-wallet or contract-based flows, can legitimately use different signing steps.

Can I send ETH to Phantom first and swap there?

If your Phantom account supports the source network, that can be another route to evaluate. It may add a transfer before the exchange, so compare the complete cost and steps. Receiving ETH in Phantom does not by itself make the asset SOL; you still need an appropriate exchange route.

Do I need a second wallet if MetaMask already supports Solana?

No. You can use a supported Solana account in the wallet you prefer. This guide uses Phantom because it addresses that specific workflow, not because two applications are necessary. Whichever interface you choose, verify the public Solana address that will receive the payout.

How long should I allow?

There is no dependable universal completion time. The source transaction, required confirmations, provider processing and destination payout all contribute. Check the current order status and network conditions. If a swap is already delayed, use the pending-order guide to identify the stage before contacting support.