> For the complete documentation index, see [llms.txt](https://docs.whiteswan.io/partner-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whiteswan.io/partner-knowledge-base/branding-and-white-labeling/branding-and-design/typography.md).

# Typography

Typography defines the fonts used across text elements in the experience, including headings, inputs, buttons, and links.

<figure><img src="/files/fb3SK36rBK89ynHGNodb" alt=""><figcaption></figcaption></figure>

***

#### What you can customize

**Global Custom Font**

* Set a default font applied across the entire interface
* Choose from free Google Fonts or upload your own font
* Each font family supports two different weights, bold and normal

If uploading your own custom font:

* Supported font formats include woff2, woff, eot, svg, otf, and ttf. If possible, using woff2 fonts is optimal. There are free online converters for this such as [this one](https://fontsource.org/tools/converter).
* Make sure to upload both a regular and a bold version of your font. The bold and the regular font may or may not be a part of the same font family depending on your preferences.&#x20;
* To easily find local fonts you can use Font Book on Macs and Fonts inside control panel on Windows.
* After defining a global custom font you can optionally override that font for links, buttons (both buttons in general as well as specific buttons) as well as inputs.

**Text Colors**

* Configure text color for light mode
* Configure text color for dark mode
* When you define a custom text color, we do a [WCAG color contrast check](https://accessibleweb.com/color-contrast-checker/), and you're only able to save the color if contrast is higher than 3:1.

***

#### How it works

* Global font acts as the fallback across all components
* Component-level font settings override the global font
* Uploaded fonts become selectable throughout the system

***

#### Tips

* Stick to **1–2 fonts max** for a clean, professional look
* Ensure readability across sizes (especially for inputs and buttons)
* Avoid overly thin fonts for accessibility reasons


---

# 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.whiteswan.io/partner-knowledge-base/branding-and-white-labeling/branding-and-design/typography.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.