> For the complete documentation index, see [llms.txt](https://docs.proliquid.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proliquid.xyz/workflows/liquidation-levels.md). # Liquidation levels Use the liquidation levels workflow when you want to understand where forced buying or forced selling may appear on a Hyperliquid market. The [Liquidation](/features/crypto-liquidations-tracker.md) tab shows large positions and liquidation risk zones alongside price, liquidity, funding, and whale context. ## When to use it Use this workflow when: * Price is approaching a visible liquidation cluster. * A fast move may force one side of the market out. * You want to identify areas where volatility could expand. * You are planning entries, exits, or risk controls around known pressure zones. Liquidation levels can move as traders add margin, reduce exposure, or close positions. ## Tabs to open

Step	Open this	Why
Detect	Liquidation	Identify clusters, large positions, and risk zones.
Validate	Chart	Compare liquidation zones with trend, support, resistance, and recent fills.
Check liquidity	Orderbook	See whether visible depth supports the expected move.
Cross-check	Whales, Funding, and News	Confirm whether other context supports the setup.
Execute	Trade form	Choose a controlled order type.

## What to validate Before trading around liquidation levels: * Confirm the cluster is close enough to matter. * Check whether price is moving toward or away from the zone. * Review whether funding suggests crowded long or short positioning. * Look for related whale trades or liquidations. * Check whether a news event is driving the move. * Decide in advance where the idea is invalidated. ## Order types that fit

Situation	Order type
Fast breakout into liquidation pressure	Market with controlled slippage
Waiting for price at a specific zone	Limit
Maker-only entry near an active level	Chase
Building exposure across a liquidation range	Scale
Entering after the first liquidation wave	TWAP or Burst depending on urgency

## What to monitor afterward After submitting: * Watch [Positions](/terminal-sections/positions.md) for exposure, margin, TP / SL, and unrealized PNL. * Track fills in [Trade history](/terminal-sections/trade-history.md). * Re-check [Liquidation](/features/crypto-liquidations-tracker.md) after the market updates. * Watch [Whales](/features/whale-alerts-and-large-trades.md) for large trades or fresh liquidations. ## Common mistakes * Treating liquidation clusters as guaranteed magnets. * Trading old liquidation data without checking refresh timing. * Ignoring orderbook depth during a liquidation cascade. * Using too much leverage near a volatile zone. * Forgetting that traders can add margin or close before liquidation. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.proliquid.xyz/workflows/liquidation-levels.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.