Learn · Crypto futures

Crypto Leverage Risk Tiers and Position Limits

Jump to sections

Short answer

A futures contract’s headline maximum leverage usually applies only within a particular size range. Your existing position and eligible pending orders can push the request into a tier that allows less leverage and requires more margin. Identify whether the rejection concerns total exposure, a single-order limit or available collateral before changing the ticket; those problems need different fixes.

Visit Bybit

Bybit separates total risk-tier capacity from the maximum size of one order. That is useful when a BTCUSDT order is rejected even though its selected leverage looks valid. The dated example below shows which limit applies.

Why is my crypto futures order rejected when I have enough balance?

You choose 125x, enter a BTC order and see a position-limit error despite having funds available. Adding more money may not solve it. The exchange can be limiting how much exposure is permitted at that leverage, rather than reporting a shortage of collateral. The wording of the rejection matters more than the highest number on the leverage slider.

Different limits require different responsesThese checks can apply together; passing one does not establish that the others pass.Scroll sideways for all columns.
What failed?What to inspect first
Leverage / risk tierTotal relevant exposure at the chosen leverage, including applicable pending orders.
Single-order quantityThe maximum permitted size for that order type.
Available marginFunds usable by this account after other reservations and collateral rules.
Account or product eligibilityThe specific entity, contract, account classification and any account restrictions.

A useful diagnosis keeps those categories separate. Reducing one ticket can resolve a per-order cap while leaving total exposure unchanged after several orders. Lowering leverage can permit a larger position bracket but require additional margin. Transferring collateral can satisfy a funding requirement without increasing a hard position limit. A successful adjustment must address the rule that actually blocked the request.

The examples here concern linear BTCUSDT perpetuals and ordinary isolated or cross-margin risk tiers. Portfolio-margin accounts evaluate combinations of exposures under different rules, so a single-contract table is not a complete model for them. This is a scope distinction, not a reason to turn every rejected order into a complicated portfolio calculation.

BTCUSDT: a 200 USDT increase that changes the permitted leverage

Bybit’s public risk-limit response retrieved at 23:13 UTC on 7 October 2026 showed a first BTCUSDT tier ending at 300,000 USDT with maximum leverage of 150x. The next tier extended to 2,000,000 USDT and allowed up to 100x. These are dated public parameters, not a statement that every regional account can access those settings.

The two observed tiers used in this exampleBybit BTCUSDT linear contract, 7 Oct 2026. Rates and deductions below concern the position maintenance calculation before its separate closing-fee reserve.Scroll sideways for all columns.
Position-value rangeMaximum leverageMaintenance rateDeduction, USDT
Up to 300,000150x0.33%0
Above 300,000 to 2,000,000100x0.50%510

Hold price fixed at an assumed 100,000 USDT per BTC so that the arithmetic is easy to follow. A request for 2.999 BTC has a value of 299,900 USDT. A request for 3.001 BTC has a value of 300,100 USDT. Both quantities respect the observed 0.001 BTC step. There are no existing positions or other orders in this teaching example.

Only 0.002 BTC apartAssumed mark and entry: 100,000 USDT · selected leverage: 125x

2.999 BTC

Position value
299,900 USDT
Tier maximum
150x
Passes this tier check

3.001 BTC

Position value
300,100 USDT
Tier maximum
100x
125x exceeds this tier

Other account and order checks still apply. These are calculated examples, not submitted tickets.

At 125x, the first request fits the first tier’s leverage constraint. The second does not: its value enters a bracket whose maximum is 100x. Having enough cash for 300,100 ÷ 125 does not override that cap. To assess the larger request, the trader must use a permitted leverage setting and meet the resulting margin requirement, or reduce exposure.

What changes in the opening margin budget?

For the smaller request at 125x, base initial margin is 299,900 ÷ 125 = 2,399.20 USDT. For the larger request at 100x, it is 300,100 ÷ 100 = 3,001.00. Base margin rises by 601.80 even though position value rises by only 200. The extra requirement mainly comes from changing the leverage setting across the entire proposed position.

Those are base amounts, not the total required order cost. Bybit’s order-cost documentation includes opening and estimated closing fees alongside initial margin. Use the account’s actual commission rate and order preview when budgeting. A 3,001 USDT wallet balance should not be described as sufficient for this larger request merely because it equals the base calculation.

An illustrative fee-inclusive opening budget

Assume a new isolated long, entry equal to mark at 100,000, taker opening and closing rates of 0.055%, and no other account reservations. For the smaller request, opening commission is 164.945 USDT and the estimated closing reserve is 299,900 × (1 − 1/125) × 0.00055 = 163.62544. Adding base initial margin gives 2,727.77044 USDT.

For the larger request at 100x, opening commission is 165.055 and the closing reserve is 300,100 × (1 − 1/100) × 0.00055 = 163.40445. Together with 3,001 base margin, the illustrative order cost is 3,329.45945 USDT before account-specific rounding. These are assumed new-order budgets, not live account quotes or maintenance requirements.

A Bitcoin futures ticket passes toward a mechanical aperture with 125x and 100x settings, illustrating how leverage constrains permitted position size
A lower permitted leverage can open a larger size range while increasing the collateral needed for that exposure.

Why the higher maintenance rate does not apply as a sudden full-position jump

The maintenance requirement answers a different question from the opening budget: how much support the position must retain. For the observed first tier, the base maintenance calculation at 299,900 USDT is 299,900 × 0.0033 = 989.67. For the next tier at 300,100, it is 300,100 × 0.005 − 510 = 990.50.

The 510 USDT deduction is essential. Without it, multiplying the entire larger position by 0.50% would produce 1,500.50—overstating this base requirement by exactly 510. The deduction accounts for the lower rate applied to the earlier portion of the exposure. It is not a discount coupon, a credit to your wallet or an amount you withdraw.

The boundary stays continuous in this maintenance calculation

At 300,000: 300,000 × 0.0033 = 990 USDT

At the same boundary using tier 2: 300,000 × 0.005 − 510 = 990 USDT

At 300,100: 990 + 100 × 0.005 = 990.50 USDT

Base position maintenance only. Closing-fee reserves and account-wide margin calculations are separate.

This is why the opening margin change and maintenance change in the previous example look so different. Opening at 100x instead of 125x affects the base opening allocation across the position. The tiered maintenance formula preserves the lower-rate treatment of earlier exposure through its deduction. Treating both as the same percentage calculation would hide that distinction.

Do not turn the maintenance subtotal into an exact liquidation price

The 990.50 maintenance subtotal is the tier component. The liquidation calculation also needs price, fees, eligible equity and margin mode; the linked liquidation guide combines those inputs.

How the first-tier deduction was interpreted

The API’s first-tier deduction field was empty in the saved response, while the second tier explicitly returned 510. We use zero for the first tier because there is no earlier bracket to offset, consistent with the documented formula. An absent field in a later tier would need investigation; it should not automatically be converted to zero.

See how maintenance tiers enter a liquidation estimate

Pending orders can use the capacity you thought was free

A ladder of unfilled buys is still a set of instructions that could increase exposure. Consider 2.4 BTC already long, with opening buy orders totaling 0.5 BTC. At an assumed mark of 100,000, that side represents 290,000 USDT for the risk-limit calculation. Another opening buy for 0.2 BTC would raise it to 310,000. Looking only at the new 20,000 order misses the reason it crosses the first boundary.

A hedge can consume capacity with little net directionIllustrative 180,000 long and 160,000 short, with no additional orders. Each platform retains its own tier boundaries.Scroll sideways for all columns.
Documented modelExposure counted
Bybit larger-side comparison180,000: larger of the two sides
Binance USDⓈ-M shared absolute position limit340,000: combined absolute quantities

Bybit includes relevant opening orders on each side and excludes reduce-only and close-on-trigger orders from its risk-limit calculation. Canceling an unused entry can release capacity; canceling a protective exit can remove protection without freeing that same capacity.

An ordinary opposite-side order can reverse a one-way position if oversized, so the engine assesses what it could create. A dormant conditional order may reserve margin differently from a resting limit; the resulting order still faces checks at activation. Several accepted triggers can consequently fail to open together.

Can your risk tier change even if you do not add to the position?

Yes, when the tier uses current position value. Three BTC at a mark price of 99,000 represents 297,000 USDT. At 101,000 it represents 303,000. The coin quantity is unchanged, but the value crosses the observed 300,000 boundary. This mechanism applies to the size measure, not simply to whether the position is currently profitable.

Bybit’s updated rules use mark price for position value and the combined exposure used by its risk limits. In cross margin, its position initial and maintenance calculations use mark price; in isolated margin, base initial margin remains linked to entry while maintenance uses mark. These differences are why an old entry-value screenshot can disagree with the current risk display.

That does not mean every crossing automatically changes the leverage setting you selected. Bybit describes automatic risk-tier adjustment within the permitted range, with a trial calculation, rather than silently turning your chosen leverage into any lower value needed. If you are near a boundary, leave room for price movement and inspect the actual account response instead of assuming the platform will repair the position for you.

A change in exchange parameters is a separate event

The exchange can also revise its schedule. A saved table may have been accurate when you opened but cease to describe new orders. Check the contract’s current margin parameters and account notices when behavior changes unexpectedly. The relevant question is which rule applies to your existing position and future instructions, not whether an older marketing page still advertises the previous maximum.

Automated strategies need the same distinction. A bot can keep calculating order sizes from an old cap while the exchange rejects every new opening instruction. Repeated retries do not restore the old limit. Pause the opening logic, refresh the product parameters and reconcile the actual position before assuming that the strategy is operating as planned.

Single-order limits, account caps and leverage are separate controls

The BTCUSDT instrument response collected alongside the risk tiers showed a maximum market-order quantity of 150 BTC and a maximum limit-order quantity of 1,500 BTC. These are per-order filters. They do not grant permission to hold either amount at 125x, and they do not replace the position-value tiers or account margin checks.

For a constructed 160 BTC request, the observed market-order filter is relevant even if another rule would also reject the trade. Splitting it into two 80 BTC tickets changes the single-order comparison, but not the eventual 160 BTC exposure. It therefore cannot be described as bypassing the position limit. Each instruction still needs valid account capacity and adequate margin.

Price and quantity increments are another distinct source of rejection. The collected BTCUSDT record used a 0.10 USDT price tick and 0.001 BTC quantity step. An invalid increment can reject a small order that is far below every risk boundary. Correcting the increment should preserve the intended maximum price or exposure rather than rounding upward blindly.

An account can face a lower limit than the public contract table

Regional product access, account classifications and exchange-imposed account restrictions can be more restrictive than a generic instrument response. For example, Binance’s current leverage guidance describes separate restrictions for newly opened futures accounts and regular users’ subaccounts. A public maximum is a product parameter, not an individualized account permission.

This matters when comparing exchanges for a planned strategy. The useful comparison is the size and leverage available to your eligible account on the required contract. A larger promotional maximum can be irrelevant if your intended exposure immediately falls into a lower bracket or your account is subject to a stricter cap.

A short sequence for resolving the actual rejection

  • A per-order size rejection: compare quantity with the instrument’s order filter.
  • A leverage/tier rejection: compare existing exposure plus relevant open orders with the active tier.
  • A maintenance mismatch: use that tier’s rate and deduction together.

Keep the parameter timestamp and account mode with a disputed rejection. Those identify whether a rule changed between the preview and submission. A larger permitted order is still a separate decision from an affordable loss.

Size from the loss budget after resolving the contract limit

Risk-tier and position-limit questions

Does depositing more collateral raise the maximum position at my selected leverage?

It can solve a margin shortage, but it does not by itself rewrite the contract’s leverage-to-size schedule. If the requested exposure exceeds that schedule, a permitted lower leverage or smaller exposure may be needed. A separate account cap can still apply.

Is a risk tier the same as a VIP fee tier?

No. A risk tier governs exposure and margin requirements; a VIP fee tier governs commissions under the exchange’s fee program. Lower fees may reduce order cost, but they do not automatically move the account into a larger position bracket.

Can several smaller orders avoid the total position limit?

No. Smaller tickets may satisfy a per-order maximum, but eligible pending orders and resulting positions still count toward the relevant exposure cap. The total does not disappear because it was divided among order identifiers.

Does reducing my position immediately guarantee a lower maintenance rate?

The resulting value must actually fall into a lower applicable tier, and the exchange must apply its adjustment rules. Remaining opening orders or a changing mark price can keep effective exposure higher than the reduced position alone suggests.

Why is my small-cap perpetual limited more than BTC?

Each contract has its own risk schedule. A smaller market can have less capacity to absorb a forced close, so the exchange may allow less leverage or position value. BTC’s table cannot establish the limits for an unrelated token.

Can the same BTC ticker have different limits in USDT and inverse futures?

Yes. They are different contracts with different settlement and value conventions. Select the product category and exact symbol when reading risk data. A BTCUSDT notional cap in USDT should not be treated as an inverse BTCUSD coin-margin amount.

Is a rejected leverage increase evidence that the exchange is broken?

Not by itself. The account may already have exposure incompatible with the requested setting, an account restriction may apply, or the product schedule may have changed. The rejection reason and current parameters provide a better diagnosis than the headline maximum.

Sources and research 10 source references

Risk tiers and instrument filters were collected from Bybit public endpoints on 7 October 2026 at 23:13 UTC, with raw responses retained. The BTC price of 100,000 USDT and all proposed positions are teaching assumptions. Maintenance deductions, boundary continuity, quantity steps and illustrative fee reserves were recalculated. No private account, order acceptance or regional eligibility was tested.

Source register and access

  1. Crypto Leverage Hub · retained Bybit API responses: BTCUSDT risk tiers and order filters · 7 Oct 2026Historical snapshot · observation date retained · Reviewed 7 Oct 2026 · Dated example · original values preserved
  2. Bybit: Risk limits: effective exposure, pending orders and position modesLink checked · Reviewed 7 Oct 2026 · Product rule · next editorial check due 2027-01-05
  3. Bybit Developers: Public risk-tier data and maintenance deductionsLink checked · Reviewed 7 Oct 2026 · Variable parameter · next editorial check due 2026-10-21
  4. Bybit: Maintenance margin and deduction formula for USDT contractsLink checked · Reviewed 7 Oct 2026 · Product rule · next editorial check due 2027-01-05
  5. Bybit: Margin calculation changes: mark price and margin modeLink checked · Reviewed 7 Oct 2026 · Product rule · next editorial check due 2027-01-05
  6. Bybit Developers: Instrument information: quantity limits and price incrementsLink checked · Reviewed 7 Oct 2026 · Product rule · next editorial check due 2027-01-05
  7. Bybit Developers: Order, leverage and margin rejection codesLink checked · Reviewed 7 Oct 2026 · Product rule · next editorial check due 2027-01-05
  8. Bybit: Order cost: margin, opening fee and closing reserveLink checked · Reviewed 7 Oct 2026 · Product rule · next editorial check due 2027-01-05
  9. Binance: USD-M leverage brackets and hedge-mode position limitsLink checked · Reviewed 7 Oct 2026 · Product rule · next editorial check due 2027-01-05
  10. Bybit Developers: Place order: matching and instruction compatibilityLink checked · Reviewed 7 Oct 2026 · Product rule · next editorial check due 2027-01-05