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

# Fonts

Maintain your brand consistency across your interactive demos by using fonts to match your company's branding. Guideflow provides an extensive font library with hundreds of fonts to choose from.

You can add custom fonts to your Guideflow workspace in 3 ways..

* Existing Font Library. 
* Upload the Font File. 
* By Linking the CSS File URL.

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/0p0ymoyayk>" %}

### How To Add Fonts.&#x20;

* Go to “**Settings**” from your Workspace Dashboard.&#x20;
* Select Fonts, under the **Branding Section**.&#x20;

Click on “**Add Fonts**” button to add a new Font.

### From the existing list:

<figure><img src="https://4163893681-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWblXMyxfkCwkQjxwW6TV%2Fuploads%2FeDO99Oe9NOjRDn3PrjYA%2Funknown.png?alt=media&amp;token=81df7e0b-6c30-42c4-a14b-07a5114d17af" alt=""><figcaption></figcaption></figure>

* Click on the “**Select**” dropdown.&#x20;
* Search & Select for the “**Font**” name you’d like to add.&#x20;
* Type text in the **Preview tab** to see how the font looks.&#x20;
* Hit on Save to add the font to your workspace.&#x20;

### Upload font file:

<figure><img src="https://4163893681-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWblXMyxfkCwkQjxwW6TV%2Fuploads%2F7ZQVHm2sSuvVk3x23F3s%2Funknown.png?alt=media&amp;token=49cd89d0-845f-436a-ba4d-c1973e81877c" alt=""><figcaption></figcaption></figure>

* Click on the “**Upload a New Font**” dropdown.&#x20;
* Select the **Font file** from your device.&#x20;
* Type text in the **Preview tab** to see how the font looks.&#x20;
* Hit on Save to add the font to your workspace.&#x20;

{% hint style="info" %}
⚠️ Note: We support the OTF, TTF, WOFF, WOFF 2 file types.&#x20;
{% endhint %}

### Linking CSS URL -&#x20;

<figure><img src="https://4163893681-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWblXMyxfkCwkQjxwW6TV%2Fuploads%2FdhllOJhECQvL5rsKQCpT%2Funknown.png?alt=media&amp;token=0227ecd7-6bc1-48d4-a691-489bd261def0" alt=""><figcaption></figcaption></figure>

* Paste the “**URL To CSS File**”.&#x20;
* Enter the Font Family name (the Font Name).&#x20;
* Type text in the Preview tab to see how the font looks.&#x20;
* Hit on Save to add the font to your workspace.


---

# 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.guideflow.com/help/branding/fonts.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.