> For the complete documentation index, see [llms.txt](https://trada-llc.gitbook.io/trada-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trada-llc.gitbook.io/trada-docs/copy-trading/configure-receiver/lot-sizing-modes.md).

# Lot-sizing modes

Each receiver decides how large its copied trades are, independently of the sender and of other receivers. You pick one of five modes in the receiver's **Trading** tab.

## Lot Multiplier (default)

Copies the sender's lot size and multiplies it by a value you set.

The **Suggest** button sets the multiplier so the sender and receiver risk the same proportion of their balances (1:1 risk):

```
Suggested multiplier = Receiver balance / Sender balance
```

**Example** — sender balance $50,000, receiver balance $5,000. Suggest sets the multiplier to 5,000 / 50,000 = **0.10**. If the sender opens 1.00 lot, the receiver opens 0.10 lots.

## Fixed Lot

The receiver always opens the **same lot size**, whatever the sender does and whatever the balances are.

**Example** — fixed at 0.20 lots. Whether the sender opens 0.50, 1.00, or 2.00 lots, the receiver opens **0.20 lots** every time.

## Balance Multiplier

Sizes each trade by the **balance ratio** between receiver and sender, so risk tracks balances automatically rather than a manual multiplier.

```
Lot = Sender lot × (Receiver balance / Sender balance)
```

**Example** — sender $10,000, receiver $30,000 → ratio 3. If the sender opens 0.50 lots, the receiver opens 1.50 lots.

## Equity Multiplier

The same idea as Balance Multiplier, but it uses **current equity** (including open P\&L) instead of balance.

**Example** — sender equity $8,000, receiver equity $16,000 → ratio 2. If the sender opens 0.40 lots, the receiver opens 0.80 lots.

## Fixed % Risk

The receiver risks a fixed **percentage of its account** on every trade. Trada calculates the lot size automatically from the stop-loss distance and that percentage.

**Example** — 1% risk, receiver balance $10,000 → $100 at risk. With a 50-pip stop-loss, Trada sizes the lot so the maximum loss is about $100.

{% hint style="warning" %}
Fixed % Risk needs a stop-loss to size against. Make sure the sender sets a stop-loss, or configure one in the receiver's [SL & TP](/trada-docs/copy-trading/configure-receiver/sl-tp-modes.md) settings — otherwise the risk can't be calculated.
{% endhint %}

## Guarding the result

Two advanced settings (on the **Trading** tab) keep sizing within safe bounds:

* **Max Lot Size** caps the final size after the mode is applied. A computed 3.50 lots with a 2.00 cap is sent as 2.00.
* **Force Minimum Lot Size** raises a calculated size up to the broker's minimum when it would otherwise be too small — useful with Fixed % Risk on a smaller receiver.

See [Add & configure a receiver](/trada-docs/copy-trading/configure-receiver.md) for all advanced settings.

## Related

* [Add & configure a receiver](/trada-docs/copy-trading/configure-receiver.md)
* [Stop-loss & take-profit modes](/trada-docs/copy-trading/configure-receiver/sl-tp-modes.md)
* [Formulas & metrics](/trada-docs/reference/formulas.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://trada-llc.gitbook.io/trada-docs/copy-trading/configure-receiver/lot-sizing-modes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.