> For the complete documentation index, see [llms.txt](https://dasus.gitbook.io/dasus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dasus.gitbook.io/dasus-docs/trading/tp-sl.md).

# Take Profit / Stop Loss

A **Take Profit** (TP) closes some or all of a position when the market reaches your target; a **Stop Loss** (SL) closes it when the market reaches the level where you cut the loss. Both are trigger orders that live on Hyperliquid: they keep working with the tab closed and the wallet disconnected. TP/SL is available on perps in both [Lite](https://dasus.gitbook.io/dasus-docs/the-app/lite-mode.md) and [Pro](https://dasus.gitbook.io/dasus-docs/trading/interface.md); spot and prediction markets have no TP/SL.

## How they work

* Hyperliquid evaluates the trigger against the **mark price**, not the last trade — a single wick in a thin book does not fire it.
* When it triggers, a **market order** closes the size (reduce-only, sent with a price bound so it fills). If you set a limit price for the TP or SL instead, a limit order is placed at that price.
* The **Gain / Loss** fields and sliders are leveraged: they show the profit or loss on the **margin** of the position (the ROE), and in USDC.

## Three ways to set them

### 1. Attach them to a new order

In the Pro order form, tick **Take Profit / Stop Loss** on a Market or Limit order and fill **TP Price · Gain** and/or **SL Price · Loss** (the Gain/Loss box toggles between % and $). The reference for the % is the price you will enter at: the current price for a market order, your limit price for a limit order. The form checks the side (*Take Profit must be above the entry price* for a long, and so on).

The TP and SL are sent **in the same action as the entry**: if the entry fills, they are active from the first second. With a resting limit order they become active when the limit fills — until then they protect nothing. If Hyperliquid rejects the TP/SL, the entry is rejected with it, so a position is never opened without the protection you asked for.

In Lite, the **Add TP / SL** button opens a sheet with the same fields; the hint reads *Sent with your order, so the position is never open without protection. Leave one blank to skip it.*

### 2. Set them on an open position

Open **TP/SL** on the position (Positions table, Lite position card, or the **Edit position TP/SL** button in the order form). The **TP/SL for the position** modal shows the coin, position, entry and mark price, and for each of TP and SL a price, a Gain/Loss in % or $, a slider (TP up to +300%, SL up to −100%) and the **Expected gain / Expected loss** in USDC.

| Option             | What it does                                                                                                                |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------- |
| **Configure size** | Protects only the amount you set (slider or field, in the coin or USDC). By default the TP/SL applies to the whole position |
| **Limit price**    | Uses a TP Limit Price / SL Limit Price instead of a market close                                                            |
| **Clear**          | Empties a TP or an SL; confirming with both empty removes the existing triggers                                             |

The modal pre-fills the triggers the position already has, so editing means changing the numbers and confirming. The side is checked against the **current mark price**, not the entry — you can move a stop above your entry once the trade is in profit, as long as it stays below the mark.

The modal's own note says it best: *By default, take-profit and stop-loss orders apply to the entire position. Orders are cancelled automatically after the position is closed. A market order triggers when the stop-loss or take-profit price is reached. If you configure the size above, the TP/SL order will be for that size regardless of how the position changes in the future.* A full-position TP/SL scales with the position (it still closes all of it after you add or reduce); a configured size stays fixed.

### 3. Drag the lines on the chart (Pro)

Your TP and SL show as lines on the Pro chart. Drag a line to a new level; a popup (*Move take profit* / *Move stop loss*) confirms the old and new price before it is sent. The line's ✕ cancels it. A line cannot be dropped on the wrong side of the current price.

## One TP and one SL per position

Dasus keeps **at most one TP and one SL per position**. Whenever you place a new one — from the order form, the modal, the chart or a stand-alone Stop/Take order that protects the position — the previous trigger of the same kind is cancelled once the new one is confirmed. A duplicate that slips through (for instance from another front-end) is removed automatically a little later, with a *Duplicate TP/SL removed* notice.

Two deliberate exceptions:

* TP/SL attached to a **resting** limit order do not replace the position's current stop, because they are not active yet. Protection first.
* Partial-size ladders (several TPs at different sizes) are left alone; only full-size duplicates of the same kind are considered redundant.

{% hint style="info" %}
Hyperliquid can take up to a minute to list a new trigger order in its own feeds. Dasus shows yours immediately from the exchange's confirmation, so if a TP/SL seems slow to appear elsewhere, wait rather than placing a second one.
{% endhint %}

## Where you see them

* **Positions** → the **TP/SL** column shows the trigger prices, including a stand-alone stop that protects the position even if it was placed without Reduce Only.
* **Open Orders** → each trigger is its own row, with *Trigger Conditions* (Price above / below X) and Reduce Only.
* The chart lines, and the **Order History** once they fire or are cancelled.

## Warnings

* **Stop near the liquidation price.** The order form warns *Your Stop Loss is at or very close to the liquidation price (\~X). You could be liquidated before it triggers* when the SL is within 1.5% of the estimate. The position modal shows a popup — *Your stop-loss is very close to the liquidation price — the position may be liquidated first* — with **Place anyway**. Keep a buffer; see [Liquidation](https://dasus.gitbook.io/dasus-docs/trading-concepts/liquidation.md).
* **Execution price ≠ trigger price.** A triggered market close fills at the best available prices; in a fast market the fill can be worse than the trigger.
* **A stop is not a guarantee.** If the price gaps through both levels, the position can be liquidated before or despite the stop.

If [Guardian Mode](https://dasus.gitbook.io/dasus-docs/trading/guardian-mode.md) is on with a required stop, only the SL attached to the order counts as its protection — "I'll add one later" does not pass.

## Lite vs. Pro

|                                       | Lite                    | Pro |
| ------------------------------------- | ----------------------- | --- |
| Attach TP/SL to a new order           | Yes (Add TP / SL sheet) | Yes |
| Set or edit TP/SL on an open position | Yes (same modal)        | Yes |
| Price-based trigger                   | Yes                     | Yes |
| Gain/loss in % or $                   | Yes                     | Yes |
| Partial size (Configure size)         | Yes                     | Yes |
| TP/SL with a limit price              | Yes                     | Yes |
| Drag lines on the chart               | —                       | Yes |

## Tips

* **Decide the stop first.** Know what you will lose before you think about what you hope to gain.
* **Give the trade room.** On volatile markets very tight stops get hit by noise; size down instead — see [Margin & Leverage](https://dasus.gitbook.io/dasus-docs/trading-concepts/margining.md).
* **Scale out with partial TPs.** Taking part of the position off at a first target lets the rest run with less exposure.
* **For entries, use stand-alone triggers.** Stop Market / Stop Limit / Take Market / Take Limit in the order form also work as entries — see [Order Types](https://dasus.gitbook.io/dasus-docs/trading/order-types.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dasus.gitbook.io/dasus-docs/trading/tp-sl.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
