> For the complete documentation index, see [llms.txt](https://docs.slerf.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slerf.tools/en/solana-guide/solana-priority-fee.md).

# Solana Priority Fees

Understand Solana base and priority fees, how a compute-unit price can improve scheduling during congestion, and how to choose a suitable setting.

On the Solana blockchain, priority fees are additional fees that users pay to speed up the processing of their transactions. This mechanism allows users to increase the priority of their transactions in the network by paying higher fees, ensuring that they are confirmed and processed by validators faster than other transactions with lower fees. This is similar to the Gas fees on the Ethereum network, where users can adjust the fees they pay based on their needs to complete transactions more quickly.

SlerfTools has established three levels of priority fees based on the Solana network conditions. For low priority, a transaction will not exceed 0.00015 SOL. For high priority, a transaction will not exceed 0.003 SOL.


---

# 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.slerf.tools/en/solana-guide/solana-priority-fee.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.
