Skip to main content
Jupiter Limit Orders let you choose the price at which you want to buy or sell a token. Instead of executing at the current market price (like a market swap), a limit order waits until your specified price level is reached before executing.
  • Market price is the current trading price of the token.
  • Limit price is your specified target for order execution.
If your limit price is significantly higher than the current market price, a regular market swap may be more appropriate. Jupiter Limit Orders differ from a traditional Central Limit Order Book (CLOB). CLOBs match buyers and sellers directly and require dedicated market makers. Jupiter Limit Orders instead execute against onchain liquidity from multiple DEXes, offering broader token coverage but with different execution behavior. Jupiter currently offers two versions: Limit Order v1 and Limit Order v2.

v1 vs v2

Limit Order v1Limit Order v2
Trigger typePool rate between the two tokensToken’s USD price or market cap
Output amountGuaranteed (follows pool pricing)Not guaranteed (prioritizes execution with minimal slippage)
Orders below market priceNot supportedSupported (Buy Below)
Take Profit / Stop LossNot supportedSupported (including both on the same position)
Edit an orderMust cancel and create a new oneCan edit in place
Partial fillsSupportedSupported
Fees0.1% flat0.03–0.1% base + Ultra routing fee (0–0.5%)

Limit Order v2

How it works

In Limit v2, orders are triggered based on the token’s USD price or market cap. When the desired price level is reached, the order is executed using available liquidity. When you place an order, your selling tokens are moved into an intermediate vault where they remain locked while the order is active. Jupiter continuously monitors market prices to check if your trigger condition has been met. Once the trigger is reached, a keeper executes the trade on your behalf through Jupiter Ultra, which searches for the best available route across supported liquidity sources. Because execution happens at the moment the trigger is reached, the final amount you receive may differ from the estimate shown during order creation. The exact output amount is not guaranteed — v2 prioritizes executing the order with minimal slippage when the price trigger is hit.

Trigger types

  • Buy Below — Triggers when the token price or market cap goes below your set level.
  • Buy Above — Triggers when the token price or market cap goes above your set level.
Triggers can be based on either the token’s USD price or its market cap.

Slippage

Slippage tolerance controls how much the execution price can move from your trigger price during execution. Limit Orders are executed using Jupiter Ultra, which applies a small amount of slippage by default to improve execution success. This can be adjusted manually, or set to 0% to execute only at the exact trigger price.

Order expiry

Each Limit v2 order has an expiry. If the trigger condition is not reached before expiry, the order is cancelled automatically and the locked tokens are returned to your wallet.

Partial fills

Orders may execute partially depending on available liquidity. If an order executes partially, the filled portion is settled immediately. The remaining amount stays active and continues waiting for execution until it is fully filled, cancelled, or expires.

Managing orders

Open and past orders can be viewed from the Limit page on jup.ag/limit or from the Portfolio sidebar under the Limit tab. Orders can be edited or cancelled from either location.

Take Profit & Stop Loss

Take Profit and Stop Loss let you automate exits from a position based on price levels. On Limit v2, these are set using the same trigger system as regular Limit orders. Take Profit — A sell order that triggers when the price rises above your target. Stop Loss — A sell order that triggers when the price falls below your stop level.
If the price drops past your Stop Loss trigger by more than your set slippage tolerance, the order will not execute.
How they work When you set a Take Profit or Stop Loss, the exit condition is attached to the entry order. If the entry order triggers and executes:
1

Exit order created

The bought tokens are automatically used to create the exit order.
2

Tokens held in vault

These tokens remain in the vault instead of being sent to your wallet.
3

Exit order active

The exit order stays active until it triggers, is cancelled, or expires.
Because of this, you may not see the bought tokens in your wallet immediately after the entry executes. If you cancel the order while the exit condition is still active, the locked tokens are returned to your wallet. Using both together You can set both a Take Profit and a Stop Loss on the same entry order. Once the entry executes, both exit orders become active, but only one will execute — whichever condition triggers first cancels the other automatically.
This is known as OTOCO (One Triggers the Other, One Cancels the Other). Only one exit order will ever execute per entry.

Fees

Limit v2 orders apply the following fees during execution:
Fee typeRate
Base fee (stable or pegged pairs)0.03%
Base fee (all other pairs)0.1%
Ultra routing fee0–0.5%, depending on token pair and execution mechanism
Fees are deducted automatically when the order executes.

Privacy & MEV protection

Jupiter implements several protections to reduce the risk of MEV (Maximal Extractable Value) and frontrunning on Limit v2 orders. While MEV cannot be fully eliminated on any blockchain, these measures make attacks harder and less profitable:
  • Price checks before execution — If the price is unfavorable at execution, your order will not be filled. It will remain active and attempt to execute again when the price matches your trigger.
  • Ultra routing — Includes built-in MEV protection.
  • Order privacy — Pending orders are not visible via watch-only wallets. Order details are not directly tied to the user’s primary wallet onchain, making them harder to target by bots.

Limitations

Token-2022 standard tokens with transfer tax features are not supported on Limit Orders v2. This limitation exists because these token types allow creators to modify transfer tax rates at their discretion, which could lead to unexpected execution results and cause users to receive fewer tokens than expected.

Limit Order v1

How it works

In Limit v1, the trigger price is based on the pool rate between the two tokens you are trading (not the token’s USD price or market cap). When you place an order, your selling tokens are locked until the order is executed or cancelled. Jupiter continuously monitors market prices. When the trigger price is reached, a keeper executes the trade on your behalf, and the bought tokens (minus fees) are sent to your wallet. On Limit v1, the output amount is guaranteed because it follows pool pricing directly. However, the order may not execute if the market moves too quickly. Limit v1 supports partial fills.

Parameters

When setting up a Limit Order on v1, you can customize:
  • Token pair (sell side and buy side)
  • Amount
  • Limit price (based on pool rate)
  • Expiry time
On Limit v1, you cannot set orders below the current market price. Take Profit and Stop Loss are not available — both are supported on Limit v2.

Managing orders

Open and past orders can be viewed from the Limit page on jup.ag/limit (under the Open Orders or Past Orders tabs) or from the Portfolio sidebar under Limit → v1. To modify an order on v1, you must cancel it and create a new one. In-place editing is not supported (this is available on v2).

Fees

A flat 0.1% fee applies to all Limit v1 orders. This fee is charged only when the order is successfully executed.

MEV protection

Limit Orders v1 include protections to reduce the risk of MEV frontrunning:
  • Price checks before execution — Ensures the order is still valid and fair at the time of execution.
  • Automatic cancellation — If the price moves beyond the acceptable range, the order is cancelled.
While MEV cannot be fully eliminated on any blockchain, these measures make frontrunning more difficult and less profitable.

Limitations

Token-2022 standard tokens with transfer tax features are not supported on Limit Orders v1.