> For the complete documentation index, see [llms.txt](https://docs.cubu.com/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cubu.com/guides/how-to-guides/admin-tasks/how-to-use-google-fonts-in-themes.md).

# How To: Use Google Fonts in Themes

Google Fonts is a computer font and web font service owned by Google. 

This article will guide you in referencing a Google Font from Cubu for use on Portals, Kiosks, Tickets, and Digital Signs.

## Choose a Font

* Open <https://fonts.google.com/>
* Browse the fonts library and select the font you wish to use.

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

* Click **Get Font**

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

### Click **Get Embed Code.**

Choose Web / \<link> to view the embed code.

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

Take note of the stylesheet **URL** and **font family**.&#x20;

For example, if this is the embed code shown on screen:

{% code overflow="wrap" %}

```html
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Lato:ital,wght@0,100;0,300;0,400;0,700;0,900;1,100;1,300;1,400;1,700;1,900&display=swap" rel="stylesheet">
```

{% endcode %}

* The URL is:

{% code overflow="wrap" %}

```
https://fonts.googleapis.com/css2?family=Lato:ital,wght@0,100;0,300;0,400;0,700;0,900;1,100;1,300;1,400;1,700;1,900&display=swap
```

{% endcode %}

* The font family is: "**Lato".**

## Use the Font in Cubu

* Go to Customer Engagement / Visual / Web Fonts.
* Click the New Web Font button to open the New Web Font dialog.
* Enter the font information:
  * Font Name: A unique name used to identify the font in Cubu.
  * Font Family: The font family you got in the previous step. Make sure you enter the **exact** name.
  * Font URL: The URL you got in the previous step.
* Click Create to create the font.

<div align="left"><figure><img src="/files/jxlPGnNbSdCD97SWaOa1" alt="" width="563"><figcaption><p>New Web Font Dialog</p></figcaption></figure></div>

Once the font is created, you can use it in Themes.

## See Also

{% content-ref url="/spaces/8vfRpZGqpk7N0egaXMQ8/pages/CCcdsUMljQiwxVcBeebP" %}
[Managing Fonts](/guides/admin-tools/customer-engagement/managing-fonts.md)
{% endcontent-ref %}

{% content-ref url="/spaces/8vfRpZGqpk7N0egaXMQ8/pages/5Z2dhWY3zJDxgod9BLcl" %}
[Managing Themes](/guides/admin-tools/customer-engagement/managing-themes.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.cubu.com/guides/how-to-guides/admin-tasks/how-to-use-google-fonts-in-themes.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.