> For the complete documentation index, see [llms.txt](https://docs.injex.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.injex.fi/core-features/settings/slippage.md).

# Slippage

Slippage ensures that your transaction goes through even if the exchange rate changes slightly. The slippage, set by default at 1%, guarantees that after successful swap the user will receive **at least** 99% of the indicated amount. Users can adjust the slippage from 0.01% to 49.99%.

We allow, but highly discourage, the use of:

* Slippage < 0.1% - Low slippage may cancel the transaction due to a lack of liquidity. In such cases, the transaction will not go through, and your funds will be returned to your wallet, but you will pay the gas fee. **Funds spent on the gas fee are non-refundable.**
* Slippage > 1% - High slippage can result in losses due to an unfavorable exchange rate. High values can be used in low-liquidity markets, but do so with caution and an awareness of the associated risks.

Injex recommends using slippage of 0.5% - 1%. This is the golden mean to increase the likelihood of transaction completion with minimal risk of an unfavorable exchange rate change.

<br>


---

# 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.injex.fi/core-features/settings/slippage.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.