Pip Value on Gold and Indices: Why Your Calculator Is Wrong

Most pip-value calculators are built for forex, where a pip is a standardised concept: 0.0001 for most pairs, 0.01 for JPY pairs, worth about $10 per standard lot on USD-quoted majors. Point them at gold or an index CFD and they start guessing - because on those instruments “pip” has no standard definition. The correct answer never comes from a calculator's assumption; it comes from two fields in your broker's contract specification: tick size and tick value.

The only formula that always works

Value of a price move = (move ÷ tick size) × tick value × lots

Tick size is the smallest price increment the symbol quotes; tick value is what that increment is worth per 1.0 lot. Both are printed in the symbol's specification in MT4/MT5 (right-click the symbol → Specification). This works for every instrument - forex, metals, indices, energies - because it bypasses the word “pip” entirely. (For the forex baseline, see what is a pip in forex.)

Why gold breaks calculators

On a typical 100 oz XAUUSD contract, a $0.01 move is worth $1 per lot. But is a “pip” $0.01 or $0.10? Platforms disagree. A calculator assuming $0.10 reports a pip value ten times larger than one assuming $0.01 - and a trader who sizes a stop “in pips” off the wrong convention builds a position 10× too large or too small. An illustrative check: if your intended stop is a $3.00 move on 0.5 lots, the risk is (3.00 ÷ 0.01) × $1 × 0.5 = $150 - no pip definition required.

Why indices break them differently

Index CFDs quote in points, and the point value per lot is broker-defined: the “same” index might be worth £1, $5 or $10 per point per lot depending on where you trade, sometimes with different contract sizes across account tiers at a single broker. A calculator that hard-codes one convention is right only by coincidence. Cross-broker EA portability makes this worse: identical strategy, identical lot input, entirely different monetary risk - the core issue explored in position sizing for indices.

Three compounding complications

1. Account currency. Tick values are quoted in the contract's currency. A GBP account trading a USD-denominated index needs the conversion applied - and that rate moves.
2. Spread eats in the same units. A 30-cent gold spread is 30 ticks of cost per round trip; evaluating it demands the same tick maths as the stop.
3. Risk rules depend on the answer. Every downstream calculation - the 1% rule, position size, drawdown projections - inherits an error in pip value at full magnitude. Get the value 10× wrong and the whole risk framework is 10× wrong.

Common mistakes

• Trusting a web calculator over the platform specification. The specification is the contract; the calculator is a guess about the contract.
• Assuming a backtest and a live account share conventions. Verify tick size and tick value on the exact live symbol - suffixes like .raw or .pro can carry different specs.
• Quoting stops “in pips” on non-forex instruments at all. Quote them in price units ($3.00 of gold, 40 index points) and convert with tick maths.

The automation answer

This is a problem software should solve at the source. EAs built with Nebula read tick size, tick value and contract size from the live symbol at runtime and derive lot sizes from your configured risk cap - so the “which pip convention?” question never enters the risk calculation. The maths above is still worth knowing: it's how you audit any system, including ours.

Trading carries a high level of risk. Nothing here is financial advice; past performance does not predict future results.