> 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/contribute/creating-icons.md).

# Creating icons

## The Arcticons style

When creating icons, there are three key points to test your design to:

* **Recognizable**: There needs to be a clear link with the app, such as the word mark or logo.
* **Minimalistic**: Try using as fewer lines as possible, resulting in an easy-to-read icon.
* **Elegant**: Strive for the best-looking design you can make with the source material that you're working with. This is a bit of a personal preference, but make adjustments when necessary to keep your design clean. 

## Basic principles

* The size of your document should always be **48×48 px**.
* Every line has a stroke thickness of **1 px** and the color should always be #ffffff (white).
* Dots are **1,5×1,5 px** and have a fill (and no stroke) that should also be white.
* The maximum size of your icon should fit into the template circle icon (43×43 px).
  * Square-like icons should fit into the square template (37×37 px).
  * Rectangular icons should fit into the rectangle templates (31×39 px).

<figure><img src="/files/OeeZ7kBpWdaDQTWTq2UZ" alt="" width="563"><figcaption></figcaption></figure>

* We have created our own font for Arcticons icons, all letters, numbers and other glyphs have to use it for consistency.

{% hint style="info" %}
You can find the font as an SVG file inside the template folder.
{% endhint %}

* All lines should have **rounded caps** & **rounded corners**.

<figure><img src="/files/i16ib5qUEvslo8kxsvnw" alt="" width="563"><figcaption></figcaption></figure>

* Try to keep icons as simple as possible, unnecessary lines make icons harder to read.&#x20;

<figure><img src="/files/RH5B38hloHZJu4zIPa9w" alt="" width="563"><figcaption></figcaption></figure>

## Exporting & making them work

Export your icons as SVG files.

Make sure to remove the reference image before exporting.

We don't accept icons that are rastered (PNG, WebP), are too cluttered or don't follow the basic principles.&#x20;

## Start creating

{% content-ref url="/pages/eTCJtEdsBDWizDlauob4" %}
[Vector editing software](/contribute/vector-editing-software.md)
{% endcontent-ref %}

## Uploading to GitHub.

{% content-ref url="/pages/qoCxGfdDDfSAnlgVLhp2" %}
[GitHub guide](/contribute/github-guide.md)
{% endcontent-ref %}


---

# 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.arcticons.com/contribute/creating-icons.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.