> For the complete documentation index, see [llms.txt](https://docs.werwolv.net/imhex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.werwolv.net/imhex/common/fonts.md).

# Fonts

By default ImHex uses the `Proggy Clean` font, the default one used by ImGui, however it's also possible to load custom fonts.

{% hint style="info" %}
Proggy Clean is a pixel perfect bitmap font which means scaling it only works well if it's done in integer increments. Any scaling factor inbetween will cause the font to look blurry. Because of that, setting the font size is disabled by default.
{% endhint %}

### Supported fonts

Any `TTF` or `OTF` font is generally supported. However, things might look off when using a font that doesn't have monospaced glyphs. So called "Nerd Fonts" such as the fonts found on this GitHub repository, usually work great: <https://github.com/powerline/fonts>

### Changing fonts

To change your font, first open the `Settings` interface through `Help -> Settings` and open the `Fonts` tab. After that, either enter the path to your font in the `Custom Font Path` text field or click on the folder icon next to it to use the file picker.

<figure><img src="/files/q1DNkIVArKnPOEw7qcdE" alt=""><figcaption><p>A cutom font being selected in the Settings interface</p></figcaption></figure>

{% hint style="warning" %}
The Font file is not copied, only the path is stored in ImHex's settings. Don't remove the font file after it has been selected or ImHex will revert back to the default font.
{% endhint %}

After a custom font has been selected, the `Font Size` slider also becomes available and can be used to specify the font's scaling.

ImHex needs to be restarted now for the changes to come into effect.


---

# 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.werwolv.net/imhex/common/fonts.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.