Built locally by Token Studio
When the pair is supported by EDGE, Token Studio constructs the transaction locally from the Jupiter route, adds its safety instrumentation, and enables stacked execution.
Token StudioBack to HomeToken Studio uses Jupiter liquidity while exposing the price impact, value change, costs, route, account complexity, quote age, and safety boundaries behind each Solana token swap.
Choose tokens from wallet-aware browsers, enter an amount or use balance shortcuts, then inspect the complete trade before execution.
Token Studio chooses the mode from the selected token pair. The user does not need to understand or manually select the execution path.
When the pair is supported by EDGE, Token Studio constructs the transaction locally from the Jupiter route, adds its safety instrumentation, and enables stacked execution.
If either side of the pair is not supported by EDGE, Token Studio automatically uses Jupiter ULTRA for execution.
Warnings are based on the projected change in wallet value, not only the route's displayed price impact.
Projected wallet-value loss requires a separate, explicit confirmation before execution can continue.
The swap is terminated. Confirmation cannot override the hard-stop threshold.
Quotes move from fresh to aging and then stale. A stale quote expires rather than executing silently.
Destination-value changes receive warning emphasis above 1% and a stronger warning above 4%.
Account complexity limits how many accounts a route may require. Lower levels can be easier for wallets to simulate, but may exclude a better route or return no route for a difficult pair.
EDGE mode can prepare four independent swap transactions for one wallet confirmation flow. Each transaction remains independently atomic.
Token Time Vault collectors can use higher stacking levels where the route and connected wallet allow them.
The pair determines the Token Studio fee. See the service fees page for the authoritative current schedule and the costs that remain separate.
The Token Studio fee is disclosed before signing. Pool fees, Jupiter fees, network fees, account rent, slippage, and market price impact are separate.
| Swap pair | Token Studio fee |
|---|---|
| Established token pairs | 0%–0.04% |
| Eligible non-pegged token with first known pool under 24 hours old | 0.1% |
| Token Time Vault collectors | 0% |
No. Token Studio uses routes from Jupiter's liquidity infrastructure. Its own contribution is the execution interface, route controls, fee logic, local EDGE builder, stacking, and safety firewall.
A simpler route can be easier for a wallet to simulate and sign. The tradeoff is that excluding account-heavy routes may reduce output quality or leave no available route.
No. Read-only mode can inspect public wallet data but cannot sign a token swap or any other transaction.
No. Every transaction is atomic internally, but a stack contains multiple independent transactions. One transaction can fail without reversing a different transaction that already succeeded.
No. Token Time Vault collectors pay zero Token Studio service fees across the entire app. Network, liquidity-pool, Jupiter, rent, and market costs can still apply.
Choose the route complexity, inspect every cost, and let the firewall stop the swap that should never reach your wallet.