Contract Size: When the Quantity Field Does Not Mean the Number of Coins
You entered 10 in a futures order's quantity field. Did you buy 10 BTC? Depending on the exchange, you may not have. Some fields accept a number of contracts. The resulting exposure is determined by the contract size.
The same number can mean a different amount
Spot quantity is straightforward: entering 0.5 buys 0.5 coin. Futures vary by exchange. Some accept coin quantity; others accept a contract count. The number of coins represented by one contract is called the contract size or multiplier.
Method A: Enter coin quantity.
0.5 → 0.5 BTC.
Intuitive.
Method B: Enter contract count.
If one contract = 0.01 BTC:
0.5 → rejected where only integers are allowed.
50 → 0.5 BTC.
─────────────
Entering the same “10”:
A → 10 BTC.
B → 0.1 BTC.
→ A 100-fold difference.
Carrying habits from one exchange to another can create a position far larger or smaller than intended. The larger mistake can destroy an account. Start by checking the instrument's contract size in its specifications before ordering.
Calculating notional value
For a coin-denominated contract multiplier, actual exposure, or notional value, is the product of three values.
Notional = contract count × contract size × price.
─────────────
Example:
BTC contract size: 0.01 BTC.
Current price: $60,000.
Order: 20 contracts.
Coin equivalent:
20 × 0.01 = 0.2 BTC.
Notional:
0.2 × 60,000 = $12,000.
At 20x leverage, initial margin:
12,000 ÷ 20 = $600.
Working backward can be more useful: begin with the margin you want to allocate and derive the contract count.
Desired margin: $40.
Leverage: 20x.
→ Target notional: 40 × 20 = $800.
BTC $60,000; contract size 0.01 BTC.
One contract's notional:
0.01 × 60,000 = $600.
Contract count:
800 ÷ 600 = 1.33 contracts.
→ If only integers are allowed, round down to 1 contract.
─────────────
Actual allocation:
Notional $600; margin $30.
→ A $10 difference from the $40 target.
Integer contract counts can prevent an exact allocation. Larger contract sizes produce larger rounding differences. This often explains why a small position is below the intended amount. Rounding upward creates excess exposure, so rounding down is the safer convention in this example.
Why contract sizes differ between coins
Contract sizes vary by instrument. One purpose is to make the value of one contract comparable across differently priced coins.
A high-priced coin:
BTC $60,000.
Contract size 0.01 → one contract $600.
A low-priced coin:
An altcoin at $0.5.
Contract size 1,000 → one contract $500.
─────────────
Unit prices differ by 120,000 times,
but contract values are similar.
→ “10 contracts” has no useful size meaning without the instrument.
A common mistake is assuming equal contract counts diversify exposure evenly. Different multipliers can create very different notionals and a portfolio concentrated in one instrument. Compare notional values, not contract counts. See minimum order sizes and tick sizes for interacting quantity and price increments.
USDT-margined and coin-margined contracts use different units
Some products, including inverse contracts, do not express the contract size as a coin quantity.
USDT-margined, linear:
Contract size = coin quantity.
Example: one contract = 0.01 BTC.
PnL settles in USDT.
Coin-margined, inverse:
Contract size = dollar value.
Example: one contract = $100.
PnL settles in a coin such as BTC.
─────────────
Both are called one contract, but:
The first fixes quantity.
The second fixes dollar value.
→ Their PnL curves differ.
With a fixed-dollar inverse contract, the coin quantity represented decreases as price rises, and coin settlement adds another calculation layer. USDT-margined products are simpler for a beginner to calculate. See USDT-margined and coin-margined futures for the structural differences.
Three common contract-size mistakes
Misreading contract units commonly creates one of these mistakes.
1. A decimal-place misunderstanding
Enter 0.5 intending 0.5 BTC.
The contract-based field requires 50.
Where such a fractional count is accepted, the resulting position is one-hundredth of the intention.
2. A digit error in the opposite direction
Enter 100 from habit, intending 1 BTC.
Whether it represents 1 BTC depends on the instrument.
→ Insufficient margin or an oversized entry.
3. Copying a count between instruments
Reuse a BTC contract count for an altcoin.
→ Notional can become tens of times larger.
─────────────
Common protection:
Inspect the order confirmation's notional value.
The amount, not the count, is the reference.
Most exchanges display notional or required margin before confirmation. Even if contract counts are confusing, the money amount is easier to recognize. Checking that number before submitting helps prevent order-of-magnitude mistakes. Rejection is preferable to an unintended position. See price-limit bands for price-based rejections.
Partial fills and contract size
Whole-contract increments can also affect fills.
Order: 20 contracts, or 0.2 BTC.
Filled: 7 contracts.
─────────────
Filled position:
7 × 0.01 = 0.07 BTC.
Remaining order:
13 contracts = 0.13 BTC.
Where contracts cannot be divided,
fills occur in whole-contract increments.
Closing orders follow the same rule.
Caution:
If you close all but one contract,
that contract remains open.
→ “I closed everything, but a position remains.”
Rounding can leave a residual position after an intended full close, especially when closing a percentage and truncating fractional contracts. See partial fills for handling incomplete execution, cross and isolated margin for remaining margin exposure, and leverage for what changes in notional and margin.
Summary
2. Some exchanges accept contract counts.
3. Contract size defines the amount per contract.
4. Notional = contracts × contract size × price for the linear example.
5. Margin = notional ÷ leverage.
6. Contract counts often use integer increments.
7. The exact target allocation may therefore be impossible.
8. Rounding down avoids exceeding the target.
9. Contract sizes differ by instrument.
10. Comparable per-contract values are one design goal.
11. Equal counts do not mean equal exposure.
12. Compare notional amounts.
13. Inverse coin-margined examples use a dollar contract value.
14. A closing order can leave one contract behind.
15. Check the confirmation's money amount before entry.
A contract count alone does not tell you the position's value. It needs the contract multiplier and price. Mistaking the displayed count for comparable exposure makes position sizes vary unpredictably between instruments. Notional value gives you a consistent basis for comparison.
Note
The examples of 0.01 BTC per contract, 1,000 altcoins per contract, $100 inverse contracts, BTC at $60,000, 20x leverage and $40 margin are hypothetical illustrations, not actual specifications or measurements from a particular exchange. Contract sizes, minimum quantities, step sizes, fractional-contract rules, notional displays and inverse settlement currencies differ by exchange and product, and may change after notice. Check the exchange's contract specifications. This article explains order units and does not recommend a trading method or entry or exit timing. Understanding units does not prevent losses or guarantee returns. Leveraged trading can lose all principal. Decisions and outcomes remain your responsibility.
NOONOO TRADING invites you to follow live trading in our free chat.
Start in the bot📈 OKX trading fee discount for new registrations
Register for the OKX Fee Discount →