A swap preview is the screen that shows what a crypto app or DEX expects to happen before a token swap is confirmed. It usually displays the token you will send, the token you expect to receive, the selected network, estimated rate, fees, slippage, route, minimum received amount, and wallet request. If you are new to the broader idea of crypto assets, start with What Is Cryptocurrency?.

This guide explains how to read a swap preview in a careful, beginner-safe way. You will learn how to check the input token, output token, network, price impact, slippage tolerance, route, approval request, transaction confirmation, and explorer result. For the basic structure behind swaps, read How DEX Swaps Work.

Quick answer

A swap preview is a pre-confirmation summary of a token swap. It matters because the preview helps users notice wrong tokens, wrong networks, high slippage, large price impact, unsafe approvals, unexpected fees, or suspicious routes before confirming. Before using it, users should check the official source, token contracts, selected network, expected output, minimum received amount, wallet request, and transaction result.

Simple example: A user wants to swap Token A for Token B on a DEX. The preview shows that the swap will use one network, route through a liquidity pool, charge a network fee, apply slippage tolerance, and return an estimated amount of Token B. Before confirming, the user checks that both token contracts and the selected network are correct.

Why this matters

A swap preview is one of the last checkpoints before a wallet action becomes an on-chain transaction. If the preview is misunderstood, a user may confirm a swap with the wrong token, accept an unexpected rate, approve the wrong spender, use the wrong network, or miss a warning about liquidity and price impact.

Token symbols and app interfaces can be misleading. A familiar token name does not always mean the token contract is official, and a successful transaction does not always mean the user received the intended token at the expected rate. Users should compare the preview with trusted sources, especially when using a new DEX, new token, new route, or link from social media. For broader safety checks, read How to Avoid Crypto Scams.

Useful next step: If this topic feels unfamiliar, read What Is Blockchain? and What Is a Blockchain Network? first. Those pages explain the basic structure behind wallets, transactions, tokens, explorers, and many Web3 actions.

The basic idea

A swap preview turns a technical blockchain action into a readable summary. It does not guarantee every outcome perfectly, but it helps users review the main parts of the action before signing. A careful reader looks at the token, network, route, numbers, permissions, and final wallet confirmation together instead of trusting only one line.

1. The preview shows the expected swap, not just the token names

A swap preview usually shows an input token and an output token. Users should check more than the symbol. The token contract, network, token decimals, and official source matter because copied token names can appear on many networks. For deeper token checks, read How to Check Token Before Swapping.

2. The preview estimates the route and received amount

A DEX or swap tool may route a trade through one pool, multiple pools, or several intermediate tokens. The preview may also show the estimated output, price impact, minimum received amount, and slippage tolerance. These numbers help users understand whether the swap looks normal for the size of the trade and the available liquidity.

3. The wallet request is the final confirmation layer

After the app preview, the wallet may show a separate approval or swap transaction request. Users should not assume the wallet request is safe just because the website preview looked normal. The wallet request should match the intended action, network, token, spender contract, estimated fee, and expected result. If a balance does not show after the action, read Why Wallet Balance Does Not Show.

How it works in practice

Reading a swap preview is a step-by-step review process. The goal is not to predict markets or rank tokens. The goal is to verify that the action shown on the screen matches what the user intended to do.

  1. Start with the source page. Check that the DEX, swap tool, or app is opened from an official source, not a copied domain, ad, or random social link.
  2. Check the selected network. Confirm that the chain, gas token, network fee, and explorer match the token and wallet you intend to use.
  3. Check the input token and output token. Compare token contracts with official sources or a reliable explorer page before trusting the symbol.
  4. Read the numbers. Review estimated output, minimum received, slippage tolerance, price impact, route, liquidity warning, and network fee.
  5. Compare the wallet popup with the preview. Confirm that the wallet request matches the swap you reviewed before signing or confirming.
  6. After confirmation, check the transaction hash on the correct explorer and confirm the token, amount, address, fee, and status.

Related guide: If the action involves connecting a wallet, approving token spending, signing a message, or confirming a swap, also read How to Check Before Connecting a Wallet, How to Check Before Approving a Token, and How to Check Official Links.

What users should check

Use this checklist before confirming a swap preview. It is useful for DEX swaps, wallet-integrated swaps, aggregator routes, custom tokens, new networks, and unfamiliar token pages.

  • Official source: Check the domain, app link, documentation, social profile, token page, and contract source before trusting a swap page or imported token.
  • Network: Confirm the selected chain, chain name, gas token, network fee, explorer, and whether both tokens are available on the same network.
  • Input token: Check the token you are spending, its contract address, balance, decimals, and whether the wallet request is asking for an approval first.
  • Output token: Check the token you expect to receive, its contract address, symbol, name, and whether it matches the official source.
  • Estimated rate: Read the estimated exchange rate and compare it with the expected market context without treating the estimate as a guarantee.
  • Minimum received: Check the minimum output amount after slippage. This is often more important than the optimistic estimated output.
  • Slippage tolerance: Review whether the allowed slippage is unusually high for the action. High slippage can lead to a worse result than expected.
  • Price impact: Check whether the trade size may move the pool price significantly, especially for low-liquidity tokens.
  • Route: Review whether the swap route uses expected pools, routers, or intermediate tokens. Unexpected routing deserves extra caution.
  • Wallet request: Before approving or confirming, read the action type, spender contract, token amount, network, fee, and expected result.
  • Result: After the swap, check the transaction status, tokens transferred, final balance, fee, and explorer record.

Common mistakes

Crypto swap mistakes are common because interfaces often compress complex routing and contract information into a few short labels. A user may see a token symbol, route, rate, network name, approval request, transaction hash, or explorer page and assume it proves more than it actually proves. Safer usage starts with slowing down and checking the same information from more than one trusted place.

Mistake 1: Trusting the token symbol only

Many tokens can share the same or similar symbols. A swap preview may show a familiar ticker, but users should still check the token contract, selected network, and official source. For contract verification, read How to Check a Token Contract on an Explorer.

Mistake 2: Ignoring minimum received

The estimated output is not always the amount the user will receive. The minimum received field shows the lowest output accepted under the current slippage setting. If the minimum received amount looks much lower than expected, the user should slow down and review the trade again.

Mistake 3: Accepting high slippage without understanding it

High slippage tolerance can make a transaction more likely to execute, but it can also allow a worse result. Users should not raise slippage just because a page asks them to, especially on unfamiliar tokens, new pools, or links from social media.

Mistake 4: Ignoring price impact

Price impact can become large when a trade is big compared with available liquidity. A high price impact warning may mean the user is receiving a much worse rate than expected. This is especially important for low-liquidity tokens.

Mistake 5: Confusing approval with the swap itself

Some tokens require an approval transaction before the actual swap. An approval gives a contract permission to spend a token up to a certain amount, while the swap performs the exchange. Users should review approval requests separately from swap confirmations. For more, read How to Check Before Approving a Token.

When to be extra careful

Some swap previews deserve more caution because they may expose funds, permissions, or wallet activity to unnecessary risk. Users should slow down when a swap involves a new token, high slippage, low liquidity, unknown route, custom token import, bridge-related asset, presale token, airdrop token, or a link from social media.

  • Before connecting a wallet: Check the official website, domain spelling, social links, and whether the app is asking for a reasonable connection.
  • Before approving token spending: Check the token, spender contract, network, amount, and whether the approval matches the action you intended.
  • Before confirming the swap: Check input token, output token, minimum received, slippage, price impact, route, fee, and wallet request.
  • After the swap: Check the transaction hash, status, token transfers, final balance, and correct explorer page.

FAQ

What does a swap preview show?

A swap preview usually shows the token being spent, the token expected in return, the estimated rate, network fee, route, slippage setting, minimum received amount, and any warnings. The exact fields depend on the wallet, DEX, or swap tool.

Is the estimated output guaranteed?

Not always. The estimated output is based on the current route and market conditions at the time of the preview. The final result may depend on slippage, liquidity, transaction timing, route changes, and whether the transaction executes successfully.

What is minimum received in a swap preview?

Minimum received is the lowest output amount the swap is allowed to accept based on the current slippage setting. If the final expected output falls below that amount, the transaction may fail instead of completing at a worse rate.

Why does a swap need approval first?

Some token swaps require a separate approval before the swap transaction. The approval gives a contract permission to spend a token from the user's wallet. Users should check the spender contract, token, network, and amount before approving.

How do I check the result after a swap?

Use the transaction hash on the correct block explorer. Check the status, wallet address, token transfers, input amount, output amount, fee, and whether the final result matches the action you intended. For more, read How to Check a Transaction on an Explorer.

Related concepts

Reading a swap preview connects to several nearby crypto concepts. Understanding these pages can help readers move through the Eonwell archive in a safer order, especially if they are learning how wallets, networks, token contracts, transactions, explorers, and Web3 apps fit together.

Summary

A swap preview is the pre-confirmation screen that helps users review a token swap before signing or confirming. It matters because token names, estimates, routes, fees, approvals, and wallet popups can be misunderstood when users move too quickly. Users should check the official source, selected network, token contracts, estimated output, minimum received, slippage, price impact, route, wallet request, and final explorer result. Common mistakes include trusting token symbols only, ignoring minimum received, accepting high slippage without understanding it, overlooking price impact, and confusing approval with the swap itself. Reading the swap preview carefully supports safer DEX usage, wallet safety, token verification, and transaction review.

Eonwell does not recommend any specific wallet, token, exchange, protocol, DEX, router, liquidity pool, bridge, service, or transaction. This page is for neutral crypto education only.