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