> For the complete documentation index, see [llms.txt](https://docs.arcticons.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcticons.com/faq/icon-requests.md).

# Icon Requests

With every release, you'll be able to request some missing icons that aren't included yet in Arcticons.

The most requested icons can be found on our [Request Dashboard](https://www.arcticons.com/dashboard/requests).

## Regular requests

These requests are free for everyone. But have a little chance to get made because of the huge numbers of requests.

You can request icons with our in-app tool:

1. Open Arcticons
2. Press the symbol in the upper-left corner and select `Icon Request`
3. Choose the missing apps you wish to submit, it's also possible to select/deselect all missing apps
4. Press the plane symbol and choose the app in the pop-up menu to send the icon request
5. Now you can check the information that will be sent via email, and if everything looks fine, simply send the email, and it's done!

In case you accidentally close the app during the process, and want to clean the cache, there is an option named `Clear Icon Request Data` in `Settings` to do that.

## Priority requests

If you want to see your icons within the next release cycle, you can buy requests via [Ko-Fi](https://Ko-fi.com/donno_), with this your icon will be the first one in the queue.


---

# 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.arcticons.com/faq/icon-requests.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.