Crypto Futures Funding Rates

Live funding rates for Binance USDT perpetual futures. Positive rates mean Longs pay Shorts. Negative rates mean Shorts pay Longs. Updates automatically every minute.

Loading funding rates...

About this data

Perpetual futures have no expiry date, so exchanges use a funding rate to keep the futures price close to the spot price. When the rate is positive, traders holding long positions pay those holding shorts. When it is negative, shorts pay longs. Very high positive rates can show that many traders are leaning long, but they do not predict where price will go. Data comes from Binance, with Bybit used as a backup if Binance is not available in your location.

Related trading calculators

What this page shows

Shows live funding rates for perpetual crypto futures contracts across major exchanges.

How to read it

Positive rates mean long position holders pay short holders; negative rates mean short holders pay longs.

Why traders care

Funding rates reveal directional leverage bias in the market. Excessively high rates can warn of overcrowded trades.

Common mistakes

  • Assuming high positive funding rates guarantee an immediate price drop.
  • Ignoring upcoming funding settlement timestamps.

Frequently asked questions

What does a positive vs negative funding rate mean in crypto futures?

A positive funding rate means perpetual futures are trading at a premium to spot, so Longs pay Shorts. A negative rate means futures are at a discount, so Shorts pay Longs.

How often are crypto perpetual funding fees charged?

On most major exchanges (such as Binance and Bybit), funding is settled every 8 hours (00:00, 08:00, and 16:00 UTC), though some volatile contracts settle every 4 hours or 1 hour.

How can high funding rates cause a long or short squeeze?

When funding is deeply negative, shorts are heavily crowded; a sudden upward price move forces shorts to buy back and liquidate, fueling a rapid short squeeze.

This data can be delayed and is not a trading signal or financial advice. See our disclaimer.