BNB Chain BEP-20

Remove Liquidity on BNB Chain

Withdraw from a PancakeSwap or Uniswap position on BNB Chain, whether it is an LP balance or a concentrated position NFT. Take out 1% or the lot, with earned fees settled alongside and wrapped BNB turned back into spendable BNB. 0.01 BNB.

0.01 BNB service fee plus network gas

How to Remove Liquidity on BNB Chain

Connect and pick

PancakeSwap and Uniswap holdings appear in one list, v2 LP balances beside v3 position NFTs, which saves you working out which exchange or version you are in before you begin.

Choose how much leaves

From 1% to everything. Stop below the full amount and the position stays open on its existing bounds, still earning against whatever you leave.

Read what is coming back

Principal and accrued fees are listed apart, and if the price has drifted outside your bounds the review says which single asset the principal has become.

Sign once

The reduction, the separate fee payout a concentrated position requires, and unwrapping WBNB into BNB all travel under one signature.

code_off

No Code Required

Create and launch tokens without writing any code. Visual configuration for all features.

visibility

Fully Transparent

All token data is publicly visible and verifiable on block explorers.

hub

Multi-Chain

Available on Solana, Ethereum, Base, Arbitrum, Polygon, and BNB Chain.

shield

Full Ownership

You have full control. We never hold your keys, tokens, or authority.

Frequently Asked Questions

Connect whatever wallet owns it and the position is located for you across PancakeSwap and Uniswap. Choose a percentage from 1 to 100, check the payout, and sign. Concentrated positions need more than one protocol call before anything reaches you, and all of them travel together here.

On this chain the most common cause by a distance is the token itself rather than the pool. A token that taxes transfers hands the pool less than the contract expected, so the withdrawal reverts every time until the tolerance is raised above the tax rate. Tokens with a maximum transaction size are the same problem wearing different clothes: the position has to come out across several smaller attempts instead of one. Both are far more prevalent on BNB Chain than elsewhere, and the long-standing forum threads about withdrawals failing here are overwhelmingly about one or the other. A paused token blocks the payout outright until it unpauses, and a token whose transfers cannot be made to work at all was never going to release the liquidity.

No. A failed withdrawal changes nothing except the gas it consumed, and the position sits exactly where it was. That is worth saying plainly because the failure looks alarming and the search results for it are full of people offering to help for a fee. Raising the tolerance, reducing the amount, or waiting for a paused token to reopen are the actual remedies, and all of them are things you do yourself.

Both, and on v2 pairs as well as v3 positions on either. That is unusual here: competing tools tend to pick one exchange, and the one that ranks best for this on BNB Chain never names PancakeSwap anywhere on its page despite PancakeSwap being the larger venue by some way.

A v2 pair gives you fungible LP tokens representing a share of the whole liquidity pool, and they burn in proportion when you withdraw. A v3 position is concentrated liquidity in an NFT covering a specific price range, earning trading fees only from swaps that cross it, and nothing burns proportionally: the position's liquidity is reduced instead. This matters because at least one competing page describes the v2 behaviour as though it applies to everything, which will mislead anyone holding a concentrated position.

Yes, together in one transaction. The protocol does not do this on its own, though: a concentrated position treats the reduction and the payout as separate calls, and stopping after the first records a debt in your favour without transferring anything at all. Both are always sent here.

Anything between 1% and 99% keeps it open on the bounds you originally chose, earning against the remainder. Repeating that costs nothing beyond gas.

Burned, once it is empty, which frees up the storage and retires the identifier for good. Both exchanges hand the emptied NFT back to you through their own interfaces instead, so this departs from what you may be used to. Where those bounds might be wanted again, taking 99% leaves the position intact for a later deposit.

Price ran past one of your bounds, so the pool had already traded the position down to a single asset before you withdrew anything. Whichever one arrived tells you the direction it went. Fees are counted separately from principal and frequently arrive in both tokens even when the principal does not, though a position whose fees were collected earlier will have none left to pay.

Real BNB. Pools hold the wrapped form, so a withdrawal returns WBNB until something converts it, and that conversion runs inside the same transaction rather than leaving you to do it afterwards.

0.01 BNB plus gas, published on the page rather than held back until a wallet connects. Two other tools charge the same, one charges 0.025 BNB, one charges 0.06 BNB, and one declines to say. Since the price is matched, the difference is what the tools at that price cannot do: reach a concentrated position you already own, or cover both exchanges from one page.

Neither, and both are functioning as designed. A locker releases on its own schedule and not before, which its contract will confirm. Burned LP went to an address nobody holds the keys to, so that liquidity stays in the pool permanently. Offers to reverse either for a payment are describing something the contracts do not allow.

On This Chain the Token Is Usually the Problem

Withdrawals fail more often on BNB Chain than on comparable networks, and the reason is not the exchanges. It is the density of tokens that charge a tax on every transfer, cap the size of a single transaction, or can be paused by whoever deployed them. Any of those will stop a withdrawal that is otherwise perfectly well formed, because the pool tries to send you an amount and the token interferes with it arriving.

The signature of the tax case is a withdrawal that reverts at exactly the same point every time regardless of size, and the fix is to raise the tolerance above whatever the token charges rather than nudging it up a fraction. Maximum transaction limits look different: large withdrawals fail and small ones succeed, so the answer is to take the position out across several attempts. A paused token fails everything until the owner unpauses it, and nothing on your side changes that.

This is worth spelling out because the best-ranking answers to it are forum threads several years old, and the pages written to capture that traffic mostly suggest raising slippage and stopping there. Slippage is the fix for one of these causes and irrelevant to the others.

Two Exchanges, and Most Tools Only Admit to One

PancakeSwap is the larger venue on BNB Chain and Uniswap also runs here, so a position you are trying to close might be on either. Very little tooling reflects that. One competitor covers PancakeSwap and not Uniswap. Another is Uniswap-branded throughout and does not print the word PancakeSwap once on its BNB Chain page, on the chain where PancakeSwap is dominant, because the page is a generic template dropped onto a BNB address.

The practical cost of that is having to know, before you start, which exchange and which version your holding belongs to, and then finding the right tool for it. Reading the position and working out where it lives is something software should do rather than something you should have to establish. Both exchanges and both versions are handled here from the same page, and the version is detected rather than asked for.

There is one place the exchanges genuinely differ and any liquidity provider here should know it: their concentrated pools do not share the same fee tiers, so an apparently identical pair can be two separate markets. If you want that detail before providing liquidity again, adding liquidity covers it.