Black Friday: a whole free December, until 27 November. See the offer →
SonarSignal
Guide6 min read

Bybit stop loss setup: triggers, take profit and common mistakes

Where to set stop loss and take profit on Bybit, whether Last, Mark or Index Price should trigger, and why a stop sometimes fails to trigger or fills at a worse price.

Share:XTelegramWhatsAppRedditFacebookLinkedIn

A stop loss is only as good as its settings. On Bybit, three things decide whether it protects you: where it is attached (to the order or to the position), which price triggers it and how it is executed. This guide explains all three and shows why a stop sometimes "doesn't work" even though it was entered correctly. The labels are written exactly as Bybit shows them in its English interface.

Where to set stop loss and take profit

For futures, there are two places.

– When opening a trade: In the order panel, tick the TP/SL box. In Basic mode you enter take profit and stop loss as a price; they apply to the entire position and are executed as market orders. Advanced mode lets you do more: choose the trigger price (Reference Price), whether TP/SL applies to the entire position or only this order (Entire Position or Current Order) and how it is executed (Market, Limit and others, only with Current Order).

– On the open position: Go to the Positions tab and click + Add in the TP/SL column. In the Add TP/SL window you choose Entire Position (the whole position) or Partial Position (partial quantities).

With Partial Position you can stagger several take profits and stops, each with its own quantity and its own execution. In Partial mode, Bybit allows at most 20 TP/SL per position. A handy option is "Set SL at entry price after TP is filled": once the first take profit is filled, the stop moves to your entry price. Entire and Partial can be combined on the same position.

When take profit or stop loss triggers, Bybit cancels the opposite order.

Last, Mark or Index: which price triggers?

Bybit lets the stop be triggered by one of three prices. The default is the Last Traded Price.

– Last Traded Price: the latest traded price on Bybit, close to the price at which orders are actually executed. The downside: liquidation is based on the Mark Price. A stop on the Last Price can therefore come too late if it sits close to the liquidation price.

– Mark Price: Bybit describes it as the price commonly used for stop losses, because it helps the stop trigger before liquidation. Execution still happens at the Last Price, and slippage can occur in between.

– Index Price: an average from several spot exchanges. It protects against short spikes on a single exchange but can lag behind in fast markets.

What this means for wicks: by default, the charts show the Last Traded Price. A wick that only appears there hits a stop on the Last Price, but not necessarily a stop on the Mark or Index Price.

By the way, take profit and stop loss can use different triggers.

Why your stop loss doesn't trigger

The most common reasons, backed by Bybit's own help center and API documentation:

– Liquidation before the stop: Liquidation runs on the Mark Price. If your stop on the Last Price sits close to the liquidation price, the position can be liquidated before the Last Price reaches the stop. Bybit gives an example: long, liquidation price 12,000, stop at 12,030 on Last Price; the Mark Price drops to 12,000, the Last Price stays at 12,050, and the position is liquidated.

– Market stop with slippage: A market stop is filled at the best available price. With little liquidity this runs through several price levels, and your exit is worse than the stop.

– Limit stop without a fill: Once triggered, a limit stop places a limit order in the order book. If the price keeps moving, it won't get filled. Bybit explicitly states that execution is not guaranteed.

– Triggered but rejected: A conditional order can be rejected when it triggers, for example if there is not enough margin, if the order price is more than 10 percent away from the Last Price, or if a "Close on Trigger" order no longer finds a position.

– Price Protection: When enabled, it blocks stops on the Last Price as long as the Last and Mark Price are too far apart. This protects against spikes but can also prevent your exit during a real move. It only applies to stops on the Last Price and not to orders placed via the API.

– Wrong position side: In hedge mode, each direction has its own position. A stop has to be attached to the right side.

– Remaining size too small: If the remaining position is too small, Bybit rejects new TP/SL.

Reduce-Only: when you need it

A Reduce-Only order can only reduce a position, never increase or reverse it. Bybit explains it with an example: a long gets stopped out, then the price rises to the level of your take-profit limit order. Without Reduce-Only this would open a new short; with Reduce-Only the order is cancelled. Without an open position, Bybit rejects Reduce-Only orders. An order with Reduce-Only cannot carry a TP/SL itself.

TP/SL on the position or conditional order?

– TP/SL on the position grows and shrinks with the position and is cancelled when the position is closed. You'll find it under Positions and Open Orders → TP/SL.

– Conditional orders (Conditional) are standalone orders with a trigger price. They don't tie up any margin until they trigger. Without Reduce-Only or Close on Trigger, they can also increase or reverse a position. You'll find them under Open Orders → Conditional.

For simply protecting a position, TP/SL on the position is usually the safe choice.

Stop loss in spot trading

Spot also has TP/SL: on its own via TP/SL in the order panel, or together with a limit order. In spot, the trigger is always the Last Traded Price. After a buy order is filled, Bybit places the sell TP/SL; if one triggers, the other is cancelled. Spot also offers the OCO order ("One-Cancels-the-Other"). Since there is no leverage in spot, there is no liquidation before the stop there either.

How SonarSignal sets the stop on Bybit

When you create a box with a stop via the Trading Desk, SonarSignal sends the stop to Bybit together with the entry order and has it trigger on the Mark Price, so that it kicks in before a liquidation. The stop applies to the entire position. Bybit is used in One-Way mode.

Frequently asked questions

– Why is my Bybit stop loss not working? Usually it comes down to the trigger (Last instead of Mark Price close to liquidation), a limit stop that didn't get filled, slippage or Price Protection.

– Last, Mark or Index Price: which is better for a stop loss? Bybit names the Mark Price as a commonly used trigger for stop losses because it kicks in before liquidation. The Last Price is closer to execution, and the Index Price protects against spikes on a single exchange.

– Can I set multiple take profits? Yes, with Partial Position, up to 20 TP/SL per position.

– Is there a stop loss in spot? Yes, as a TP/SL order or together with a limit order, triggered on the Last Traded Price.

– What does Reduce-Only do? The order can only reduce the position and never open a new opposite position.

Further reading

– Bitcoin stop loss: how far price spikes below obvious lows

– Trading Desk: draw a box and arm it

– What a trading bot really does, and what it can't do

Risk disclaimer

This guide explains settings and is not investment advice. Even a correctly placed stop loss does not guarantee a specific exit price. Futures trading can lead to a total loss.

Not investment advice. This post is for information and education. It is not investment advice and not a recommendation to buy or sell. Trading cryptocurrencies and leveraged products can lead to the total loss of the capital employed.
Share:XTelegramWhatsAppRedditFacebookLinkedIn

More posts