> 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/volume-themes/faq/theme-setup-and-updates/can-i-use-custom-fonts.md).

# Can I use custom fonts?

How to use a brand font in Volume: the Shopify font picker, Theme Companion's Fonts module, and your own .woff2 files loaded from a stylesheet you add to the theme.

The font picker in **Theme settings → Typography** only lists Shopify's own font library. A font from that list needs no code at all. A file of your own goes in through Theme Companion, or — for more than one custom family — through a stylesheet you add to the theme.

### Use a font from the picker

**Theme settings → Typography** holds three pickers: **Headings → Main**, **Headings → Secondary**, and **Body font → Font**. Page titles, section headings, buttons and captions do not load a fourth file — each of them is set to one of these three. A text logo is the exception: it has its own **Font** picker on the **Logo** block.

The pickers also include a **System fonts** group. Those fonts are already on the shopper's device, so choosing one downloads nothing — see [Fonts](https://staylime.com/docs/volume-themes/faq/performance-and-troubleshooting/my-pagespeed-score-is-low.md#fonts).

***

### Add one custom family with Theme Companion

Theme Companion's **Fonts** module supports Volume and all its presets — Laceup, Crisp, Velum and Storm. See [Managing fonts](https://staylime.com/docs/theme-companion/fonts/managing-fonts) and [Supported themes](https://staylime.com/docs/theme-companion/getting-started/supported-themes).

The library holds 1 custom font and 1 Google font. The custom font is one family, not one file — add a variant per weight and style (400 Regular, 700 Bold), each a `.woff2` up to 5 MB. Confirm the web license before you upload: a licence bought for print or desktop does not always cover a website. Google fonts added here are downloaded into the store, so the storefront never calls Google.

**Apply to themes** writes the family into the theme's font pickers. After that, **Theme settings → Typography** and the **Logo** block's **Font** picker keep working exactly as before, and every place that uses that picker picks up the new family. **Remove** returns the picker to the font chosen in the theme. Applied fonts live in the theme assets, so they survive a theme update and stay in the theme if the app is uninstalled.

That covers one custom family plus one Google family. A second custom family, or three different families across headings and body, needs the steps below.

***

### Add your own font files

This route is code. Your `@font-face` rules go in a stylesheet of your own, and one line in the theme layout loads it. Work on a duplicate of your theme and preview it before you publish.

{% hint style="warning" %}
Two places look right for these rules and are not. `assets/base.css` is replaced by a theme update, which takes your rules with it. **Theme settings → Custom CSS** rejects `src` — the line that points at your font file — as an invalid property, and will not save. Use a stylesheet of your own, as below. See [Where should I put custom CSS so an update does not wipe it?](https://staylime.com/docs/volume-themes/faq/theme-setup-and-updates/where-should-i-put-custom-css-so-an-update-does-not-wipe-it.md).
{% endhint %}

{% stepper %}
{% step %}

#### Prepare the files

You need `.woff2` — one file per weight and style you actually use. Regular (400) and Bold (700) cover most stores, and `.woff` is no longer necessary.

A family with a single weight still works, but every bold word on the storefront is then drawn by the browser instead of the type designer. See **One weight is not enough** below.
{% endstep %}

{% step %}

#### Upload them to Files

Upload each file in Shopify admin → **Content → Files**. Open the file and copy its URL. It starts with `https://cdn.shopify.com`.

Do not upload the font under **Edit code → Assets**. The admin code editor can corrupt a `.woff2` there, and the browser then rejects the file with a parsing error instead of showing your font. **Content → Files** is the only reliable home for the files themselves.
{% endstep %}

{% step %}

#### Create the stylesheet

Go to **Online Store → Themes → ⋯ → Edit code**. Under **Assets**, choose **Add a new asset**, then **Create a blank file**, pick `css` and name it `custom`. Volume ships no file by that name, so nothing is overwritten.

Paste your rules into the new `assets/custom.css`:

```css
@font-face {
  font-family: "Your Font";
  src: url("https://cdn.shopify.com/.../your-font-regular.woff2") format("woff2");
  font-weight: 400;
  font-style: normal;
  font-display: swap;
}

@font-face {
  font-family: "Your Font";
  src: url("https://cdn.shopify.com/.../your-font-bold.woff2") format("woff2");
  font-weight: 700;
  font-style: normal;
  font-display: swap;
}

:root {
  --font-body-family: "Your Font", sans-serif;
  --font-heading-main-family: "Your Font", sans-serif;
  --font-heading-second-family: "Your Font", sans-serif;
}
```

Use your own copied URLs in `src`. Both `@font-face` blocks share one family name, and `font-weight` has to match the weight of that particular file. For a serif, make the fallback `serif` rather than `sans-serif`.

Set all three variables even when you only have one family — leaving one out keeps the old font on part of the store. To mix families, give each variable its own name.
{% endstep %}

{% step %}

#### Load the stylesheet

Open **Layout → `theme.liquid`** and scroll to the end of the `<head>`. The last stylesheets there are `base.css`, then a short conditional block that loads `policy-pages.css`, then one that loads `rtl.css`.

On a new line after that last block, add:

```liquid
{{ 'custom.css' | asset_url | stylesheet_tag }}
```

The position matters: `custom.css` has to load after `base.css`, where the theme's own typography lives. Because it comes last, the three variables take effect on their own. `!important` is not needed anywhere here and is better left out.
{% endstep %}

{% step %}

#### Preview, then publish

Preview the theme and check a product page, a collection page and the footer, not only the home page.

If nothing changed, the usual causes are a URL that does not start with `https://cdn.shopify.com`, a family name spelled differently in `@font-face` than in `:root`, or the `custom.css` line missing from `theme.liquid`.
{% endstep %}
{% endstepper %}

#### What the three variables cover

Everything except the text logo. Headings, body copy, buttons, menus, prices, form labels and policy pages all build their font from `--font-body-family`, `--font-heading-main-family` or `--font-heading-second-family`, so overriding those three changes the whole storefront at once.

A text logo is set on the header section instead, so `:root` does not reach it. Give it a rule of its own:

```css
.logo__title {
  font-family: "Your Font", sans-serif;
}
```

This one works without `!important` as well. An image logo is a picture, so no font change reaches it.

#### One weight is not enough

The theme keeps applying `--font-body-weight`, `--font-heading-main-weight` and `--font-heading-second-weight` from the pickers. When a picker asks for 500 or 700 and your family only has a 400 file, the browser thickens the 400 outlines itself. The result is heavier than the real bold and usually looks clumsy beside it.

Two ways out — buy the missing weight and add a second `@font-face`, or pin the theme to the weight you have:

```css
:root {
  --font-heading-main-weight: 400;
}
```

#### Italic faces

Several presets — Volume, Crisp and Velum — set **Headings → Secondary** to an italic font, so check what yours is set to in **Theme settings → Typography** before you start. If that picker holds an italic font and your own file is already drawn italic, register the file as `font-style: normal` and pin the variable to match:

```css
:root {
  --font-heading-second-style: normal;
}
```

Without that pin the theme still asks for italic, the browser finds no italic face, and it slants an already slanted drawing a second time.

#### After a theme update

The files in **Content → Files** are untouched by an update. `assets/custom.css` and the added line in `theme.liquid` are code edits, so they stay behind in the old theme — copy both into the new version before you publish it. See [Will updating Volume erase my customizations?](https://staylime.com/docs/volume-themes/faq/theme-setup-and-updates/will-updating-volume-erase-my-customizations.md).

***

### Good to know

Every font file is one more download before text can appear. Two weights of one family is a sensible ceiling for most stores; a third and a fourth are paid for in loading time on every page. `font-display: swap` keeps text readable in a fallback font while the file arrives, instead of leaving a blank space.

If page speed is the priority, a **System font** from the picker downloads nothing at all.


---

# 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://staylime.com/docs/volume-themes/faq/theme-setup-and-updates/can-i-use-custom-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.
