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

# Managing fonts

The **Fonts** module has two tabs: **Library** — the fonts you've added to the store, and **Apply to themes** — where you connect them to your theme.

### Adding a custom font

Upload your own font in the **Library** tab: give it a name, then add one or more variants — each variant is a weight and style (for example, 400 Regular or 700 Italic) with its own font file. Files are **.woff2 only, up to 5 MB** per variant.

To upload, confirm that you have the rights to use the font for web — font licenses for print or desktop don't always cover websites, so check yours if you're not sure.

<figure><img src="https://1681854268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUyDyU30RpMsjQtm2Gbnm%2Fuploads%2FyDOHTJE1Won0a2hy4HsV%2FScreenshot%202026-08-20%20at%2014.08.34.png?alt=media&#x26;token=b13af2a0-8369-4896-9160-80e85046d92b" alt=""><figcaption></figcaption></figure>

### Adding a Google Font

Browse [Google Fonts](https://fonts.google.com) to pick a font you like, then search for it by name in the app, choose the variants you need, and add it to the library.

{% hint style="info" %}
Google Fonts added this way are downloaded and self-hosted in your store — your storefront makes no requests to Google's servers. Faster load times, and GDPR-compliant out of the box.
{% endhint %}

<figure><img src="https://1681854268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUyDyU30RpMsjQtm2Gbnm%2Fuploads%2FC4bKZQWTMP1mwPnar8jJ%2FScreenshot%202026-08-20%20at%2014.11.11.png?alt=media&#x26;token=02bb7a12-2a83-4af8-adbe-33f76790f1c9" alt=""><figcaption></figcaption></figure>

### Applying fonts to a theme

The **Apply to themes** tab shows your current theme — with a note if it isn't [supported](/docs/theme-companion/getting-started/supported-themes.md) — and your supported draft themes. For each supported theme, the app detects the theme's **font pickers** — the font roles the theme exposes, such as Body, Heading, or Accent (names vary by theme) — and you apply a font from your library to a specific picker.

Each picker shows what it's using now: the theme default or an applied font. **Remove** returns the picker to the theme default — the font chosen in your theme settings takes over again; **Replace** swaps in a different font from your library.

<figure><img src="https://1681854268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUyDyU30RpMsjQtm2Gbnm%2Fuploads%2FyCos572PAGCzPP7FAE10%2FScreenshot%202026-08-20%20at%2013.58.23.png?alt=media&#x26;token=f3e74867-ad05-490c-a1c0-e745ee2a151f" alt=""><figcaption></figcaption></figure>

From there, work in the Theme Editor as you always do: every section and block that uses that font role picks up the new font, and all the theme's typography settings keep working as usual.

Under the hood, the app follows Shopify's best practices for theme fonts: the font files are hosted inside your theme's assets. That also means applied fonts are ordinary theme customizations — they carry through theme updates like the rest of your edits, and they stay in your theme even if you uninstall the app.

### Library limits

You can keep **1 custom font and 1 Google font** in the library. When a slot is taken, the app says so — delete the existing font to add a different one.


---

# 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://staylime.com/docs/theme-companion/fonts/managing-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.