Exness Lot Size Calculator
A figure returned here is an answer, not a permission. The most common complaint about a sizing tool is that a platform refused the size it produced, and that is four different refusals with four different owners: the instrument step, the free margin on the account, the instrument ceiling, and a result that never appeared at all.
An Exness lot size calculator turns your risk into a position size: enter your account balance, how much you are willing to risk per trade and your stop-loss in pips, and it returns the volume in lots. Sizing your position to your risk is the core of trading risk management. Pro mode sizes in your account currency, checks the margin the size needs and sets the stop from the instrument's measured average daily range; switch to Simple for a quick lots-from-risk figure.
—
Calculations use spreads and contract specs measured on a live Exness Standard account (2026-09-11). Figures are indicative — spreads may fluctuate and actual results will vary.
What lot size fits a $1,000 account risking 2%?
Risking 2% of a $1,000 account puts $20 at risk. With a 30-pip stop-loss on EUR/USD, where one pip per lot is worth about $10.00 at measured specs, the size is about 0.07 lots — around 7,000 units, needing about $40.62 of margin at 1:200 leverage.
Figures are indicative, from spreads and contract specs measured on a live Exness Standard account (2026-09-11). Converted to a local currency, the same amounts follow the current exchange rate, which changes through the day.
Frequently asked questions
Why does the lot size depend on the stop-loss?
Does the method change in another deposit currency?
Why did a platform refuse the volume this page returned?
Which refusal can change on its own between two attempts?
Is a result that differs from an earlier run a bug?
What does an empty result field mean here?
Why does re-running the calculation not help against a refusal?
How do I compare this figure against one from another tool?
Have an idea to make this calculator better? Share it with the team on Live Help →
Every suggestion is read — feedback helps improve these tools.
An answer is not a permission
A calculator answers an arithmetic question and stops there. Whether the resulting volume can actually be placed is a separate question, decided by rules that live somewhere else entirely and that the arithmetic knows nothing about. The two questions are asked in the same breath, which is why the answers are so often blamed on each other.
The gap between the two is the source of nearly every complaint on a page like this. A figure appears, it looks reasonable, a platform declines it, and the tool gets the blame for producing a number that was correct for the question it was given.
Sorting a refusal takes one look at the message rather than a second run of the calculation. Re-running produces the same figure, because the figure was never the disputed part.
Four refusals and the side each one belongs to
A size below the smallest step the instrument accepts is an instrument-side refusal. It shows up on small accounts and tight stops, where the arithmetic honestly lands beneath what the instrument is willing to trade, and no amount of re-entering changes it.
A size the free margin will not carry is an account-side refusal. The volume is a legal one for the instrument and the account simply does not have room for it at that moment. It is the only one of the four that can change on its own between two attempts.
A size above the ceiling for that instrument is an instrument-side refusal again, from the other end, and it is the rarest of the four. A result that never appears is a device-side fault and belongs with the other empty-box symptoms: it survives every input and vanishes on another machine.
The refusal that is not a refusal
A figure that changes between two sessions is read as instability and reported as a bug more often than any other behaviour here. In almost every case one input changed and the change was not noticed, which makes it an input-side matter rather than a fault in anything.
The way to settle it is to write the inputs down before the first run rather than to compare the two outputs afterwards. Comparing outputs is how the argument starts; comparing inputs is how it ends, usually in one line.
The same habit disposes of a second complaint, that the figure disagrees with one produced elsewhere. Two tools given different inputs produce different answers with perfect consistency, and the disagreement carries no information about either of them until the inputs are known to match.
Turn a refused size into a named owner
- Read what was declined rather than re-running the calculation. The figure is not the disputed part and it will come back identical.
- If the volume is smaller than the instrument accepts, treat it as an instrument-side limit and stop looking for a setting to change.
- If the volume is legal but the account cannot carry it, treat it as an account-side state, which is the one that can differ between two attempts minutes apart.
- If nothing appears in the result field at all, test the same inputs on a second device before drawing any conclusion about the tool.
- If a figure differs from one you saw earlier, compare the inputs and not the outputs.
- Record which of the four owners the answer landed on, so the same symptom does not start the same search a second time.
None of the steps above alters an account or a position; the whole sequence is reading rather than acting, which is why it is cheap to run first.
Refusal, owner, and what actually moves it
| What the platform does | Side that owns it | What changes the outcome |
|---|---|---|
| Declines a volume as too small | Instrument side | Nothing in the tool; the limit is a property of the instrument |
| Declines a volume the account cannot carry | Account side | Room on the account, which can differ between attempts |
| Declines a volume as too large | Instrument side | Nothing in the tool; a ceiling exists at the other end too |
| Nothing appears in the result field | Device side | A second device settles it in one attempt |
| Figure differs from a run made earlier | Input side | Comparing the inputs, not the two figures |
| Figure differs from another tool | Input side | Confirming both tools were given the same inputs |
Only one row in the table can change on its own between two attempts, and knowing which one saves repeating the other five.