Cost components
A swap can include Solana network fees, priority fees or tips, product commission, price impact, rent for token accounts and route-specific effects. Jupiter outlines the categories in its fee docs.
Jupiter Exchange — Swap Solana tokens through Jupiter's routing interface while reviewing route, slippage and token risk before signing.
Live preview — open Jupiter Exchange to swap on Solana.
Jupiter compares routes across Solana liquidity venues, then returns a transaction for your wallet to review and sign. The final result still depends on live liquidity, settings and network conditions.
There is no single Jupiter Exchange fee that applies to every flow. Costs and risks depend on the product, route, wallet and Solana transaction path.
A swap can include Solana network fees, priority fees or tips, product commission, price impact, rent for token accounts and route-specific effects. Jupiter outlines the categories in its fee docs.
Jupiter is an interface to wallet-signed transactions. Keep seed phrases private, verify URLs and understand Solana token accounts before approving spend. The Solana token docs explain how token accounts work.
Slippage, price impact, token impersonation, freeze authority, liquidity removal, MEV and failed transactions remain possible. Jupiter's risk page is worth reading before using advanced features.
Jupiter has grown beyond a basic swap box. Treat each product as a separate risk surface, especially perps, lending and automated orders.
For most users, Jupiter Exchange starts with spot swaps on Solana. The Swap overview covers Ultra mode, Manual mode and wallet support.
Limit and recurring orders can automate entries or exits, but fills are not certain when liquidity, slippage settings or market movement interfere.
Jupiter Perps is a separate perpetual futures product with liquidation, oracle and collateral risk. Read the Perps and JLP docs before treating it like a spot swap.
These are the main Jupiter surfaces a Solana trader is likely to encounter.
Spot token routing Core
Use Swap for ordinary Solana token trades. Review route, price impact and token warnings before signing.
Docs ↗Automated execution settings Mode
Ultra handles more routing, slippage and transaction landing choices for the user. It is convenient, but every quote still needs review.
Docs ↗Custom trade controls Mode
Manual mode fits users who want to set slippage, speed and broadcast preferences themselves. It also places more responsibility on the signer.
Docs ↗Conditional spot orders Order
Limit orders can trigger at a target, subject to execution conditions. Partial fills and missed fills are part of the risk profile.
Docs ↗Scheduled entries Order
Recurring orders spread buying or selling over intervals. Failed suborders, token support and vault behavior should be checked first.
Docs ↗Leverage and LP pool Risk
Perps and JLP are not simple swaps. Liquidation, pool counterparty exposure and oracle behavior make this a higher-risk area.
Docs ↗These widely used Solana assets often appear in Jupiter routes; verify the exact mint before trading.
Native Solana asset Native
SOL is used for network fees and as a common input or output token on Jupiter.
Docs ↗Circle dollar token Stable
USDC is a common quote asset across Solana markets. Confirm you are using the intended Solana mint.
Docs ↗Jupiter governance token Gov
JUP is tied to Jupiter governance and ecosystem participation. Do not confuse it with the interface itself.
Docs ↗Liquid staked SOL LST
jupSOL represents liquid staking exposure and can trade differently from native SOL in a live route.
Docs ↗Perps liquidity token LP
JLP represents exposure to the Perps liquidity pool. It is not a stablecoin or a protected deposit.
Docs ↗Jupiter documents two main spot trading modes: Ultra Mode and Manual Mode. The right choice depends on how much control you want over execution settings.
| Area | Ultra Mode | Manual Mode |
|---|---|---|
| Slippage | Estimated automatically from route and market conditions. | Set or adjusted by the user. |
| Broadcasting | Handled by Jupiter's execution flow. | Chosen through user-facing transaction settings. |
| MEV handling | Includes built-in protections described by Jupiter. | Depends on the selected broadcast path and settings. |
| Use case | Routine users who prefer managed settings. | Experienced users who want more direct control. |