> For the complete documentation index, see [llms.txt](https://docs.lendle.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lendle.xyz/user-guide-for-ui-v1/markets/deposit/withdrawing-assets.md). # Withdrawing Assets {% embed url="" %} If you want to withdraw an asset, and thus swap your L-Token for the underlying asset, you should navigate to the **Dashboard** and click on 'Withdraw' for each market. When withdrawing assets you are decreasing your collateral amount and thereby decreasing your health factor. Please take this into consideration before withdrawing any assets to prevent being liquidated. {% hint style="info" %} For a withdrawal to succeed, there must be enough liquidity available. This means that if the amount borrowed equals the amount deposited, you can't withdraw your liquidity. \ Try again at a later time when others have paid off their loans of that asset. {% endhint %} --- # 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.lendle.xyz/user-guide-for-ui-v1/markets/deposit/withdrawing-assets.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.