> For the complete documentation index, see [llms.txt](https://docs.vapordex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vapordex.io/vapordex/liquidity-pools/concentrated-liquidity-pools/concentrated-liquidity-vs-standard-pools.md).

# Concentrated Liquidity Vs Standard Pools

As mentioned previously as a liquidity provider (LP) you now have the option to choose between the new Concentrated Liquidity pools or the Standard Liquidity pools already in existence. Concentrated Liquidity pools offer LPs some incredible benefits but they may not be right for everyone. Here are some things to consider when trying to figure out which type of pool you want to use.

When to use Concentrated Liquidity pools:

* If you have a specific price range in mind for providing liquidity.
* If you want to optimize return on capital.
* When you need more accurate and timely price information.

When to use Standard Liquidity pools:

* If you prefer simplicity and lower transaction fees.
* If you are new to providing liquidity and prefer a straightforward model.
* If you want to avoid the complexity and management involved with Concentrated Liquidity


---

# 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.vapordex.io/vapordex/liquidity-pools/concentrated-liquidity-pools/concentrated-liquidity-vs-standard-pools.md?ask=<question>&goal=<endgoal>
```

`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.