Parameter 'quantity' has too much precision.
Binance error -1111 (BAD_PRECISION) means a number you sent has more decimal places than the symbol allows. It is named after the parameter that failed, so you can see 'quantity', 'price' or 'quoteOrderQty' in the message.
What the official docs say
Binance docs, errors.md: "-1111 BAD_PRECISION - Parameter '%s' has too much precision." The futures docs word it "Precision is over the maximum defined for this asset."
Three common causes
- Python or JavaScript turned 0.1 + 0.2 into 0.30000000000000004 and the long tail was sent as it is.
- You formatted with a fixed number of decimals (always 8) while the symbol allows fewer.
- A quoteOrderQty (USDT amount) has more decimals than the quote asset allows.
How to fix it
- Find how many decimals the step or tick allows (stepSize 0.00001 means 5 decimals).
- Round DOWN to that step with Decimal, never with float math.
- Convert to a plain string without scientific notation (1e-05 is not valid).
- Send again.
Python (standard library only) example (runs as shown with sample numbers):
from decimal import Decimal, ROUND_DOWN
def floor_to_step(value, step):
v, s = Decimal(str(value)), Decimal(str(step))
return (v / s).to_integral_value(ROUND_DOWN) * s
qty = floor_to_step(0.1 + 0.2, "0.00001") # float noise: 0.30000000000000004
print(format(qty, "f"))
Current limits for popular symbols
| Symbol | Price step (tick) | Quantity step | Source and read date |
|---|---|---|---|
| Binance BTCUSDT | 0.01 | 0.00001 | data-api.binance.vision, read 2026-11-11 |
| Binance ETHUSDT | 0.01 | 0.0001 | data-api.binance.vision, read 2026-11-11 |
| Binance SOLUSDT | 0.01 | 0.001 | data-api.binance.vision, read 2026-11-11 |
| Binance BNBUSDT | 0.01 | 0.001 | data-api.binance.vision, read 2026-11-11 |
| Binance XRPUSDT | 0.0001 | 0.1 | data-api.binance.vision, read 2026-11-11 |
| Binance DOGEUSDT | 0.00001 | 1 | data-api.binance.vision, read 2026-11-11 |
Check your numbers
Pick a symbol, type your quantity and see the valid rounded quantity.
Check this automatically before every order: AIKIT (free 1,000 calls)
Disclosure: AIKIT is our own product. It returns sourced exchange and broker rules (with the official source and read date) and checks bot code against them. Facts and checks only, not advice.
Questions people ask
What is Binance error -1111?
BAD_PRECISION: a parameter has more decimal places than the symbol allows.
Why do I get it with a number that looks short?
Floating-point noise. 0.1 + 0.2 is 0.30000000000000004 in Python and JavaScript. Round with Decimal.
Does format with 8 decimals fix it?
No. Each symbol has its own step. Round to the symbol's step first, then format.
Sources
- https://raw.githubusercontent.com/binance/binance-spot-api-docs/master/errors.md (read 2026-11-16)
- https://raw.githubusercontent.com/binance/binance-spot-api-docs/master/filters.md (read 2026-11-16)
Symbol limits in the table: AIKIT facts read 2026-11-11 from the venue's own public API (links in the table). Exchange rules change; read the live values from the venue before you trade.
Related fixes
- Filter failure: LOT_SIZE (Binance spot)
- Filter failure: NOTIONAL (Binance spot)
- Order quantity must be a multiple of the lot size. (OKX spot and swap)
- Your order should meet or exceed the minimum order amount. (OKX spot and swap)
All error fixes. General information for education only. It is not financial advice, and trading can lose money.