> For the complete documentation index, see [llms.txt](https://docs.krystal.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.krystal.app/products/liquidity-management/lp-transactions/remove-liquidity.md).

# Remove Liquidity

> **At Krystal, you can remove liquidity manually or use our** :zap:**Zap-Out**:zap: **innovation:**
>
> * **Removing liquidity manually is a common practice on all DEXes. You first recollect the two tokens of your position. If these tokens are not what you want to hold, you need to perform additional swap transactions to convert them into your preferred token.**
> * **With** :zap: **Krystal’s Zap-Out**:zap:**, you can remove liquidity and swap those liquidity to your preferred token in ONE TRANSACTION.**

**Step 1: Pick a position and click "Remove Liquidity"**

You can remove liquidity (1) on the “Positions” tab of your [**"Profile"**](/products/liquidity-management/profile-dashboard.md) page, (2) on the [**“Position Details”**](/products/liquidity-management/profile-dashboard.md) page, or (3) on the [**"Strategy Details"**](/products/liquidity-management/profile-dashboard.md) page.

* From the "Positions" tab in your [**"Profile"**](/products/liquidity-management/profile-dashboard.md) page, click on the minus icon at the end of the position\\

  <figure><img src="https://github.com/KrystalDeFi/docs-gitbook/blob/main/docs/liquidity-farming/.gitbook/assets/image%20(125).png" alt=""><figcaption></figcaption></figure>
* Or from [**“Position Details”**](/products/liquidity-management/profile-dashboard.md) page, click on “Remove Liquidity” button in the “Liquidity” info box\\

  <figure><img src="https://github.com/KrystalDeFi/docs-gitbook/blob/main/docs/liquidity-farming/.gitbook/assets/image%20(126).png" alt=""><figcaption></figcaption></figure>
* Or from [**“Strategy Details”**](/products/liquidity-management/profile-dashboard.md) page, on the right-hand side, click “Remove Liquidity.”\\

  <figure><img src="https://github.com/KrystalDeFi/docs-gitbook/blob/main/docs/liquidity-farming/.gitbook/assets/image%20(128).png" alt=""><figcaption></figcaption></figure>

**Step 2: Choose between the Zap-Out or Manual option, amount to be removed, then click "Remove**

Zap-Out converts all your liquidity to any token you prefer, while Manual returns both LP tokens of the position. Then choose the percentage you want to remove. To completely close your position, select 100%.

<figure><img src="https://github.com/KrystalDeFi/docs-gitbook/blob/main/docs/liquidity-farming/.gitbook/assets/image%20(130).png" alt=""><figcaption></figcaption></figure>

**Step 3: Click on your wallet at the top right corner to see your balance.**

<figure><img src="https://github.com/KrystalDeFi/docs-gitbook/blob/main/docs/liquidity-farming/.gitbook/assets/image%20(131).png" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.krystal.app/products/liquidity-management/lp-transactions/remove-liquidity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.