> 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/theme-settings/typography.md).

# Typography

Adjust Volume typography: use the Base size slider for quick scaling, or set individual heading sizes for desktop and mobile with granular controls.

A font that is not in the picker is covered in [Can I use custom fonts?](https://staylime.com/docs/volume-themes/faq/theme-setup-and-updates/can-i-use-custom-fonts.md).

### Quick Adjustment

In addition to selecting fonts for **Body** and **Headings**, you can instantly increase or decrease the size of all headings and body text at once, using the **Base size** range slider. This allows you to quickly modify the overall look and feel of your store without adjusting individual text elements.

<figure><img src="https://846450420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJZYrhya1ZIeTZS4wpBJB%2Fuploads%2F6CNNQgUq78rGIkGI8Uq3%2Fquick-adjustment.gif?alt=media&#x26;token=6759e7dd-c858-4ea2-b464-6903c65802a8" alt=""><figcaption></figcaption></figure>

If you need more precise control over each heading style, proceed to the next section.

***

### Granular Adjustment

For finer control, you can adjust each heading type separately. The theme allows you to set different sizes for **desktop** and **mobile** devices.

{% hint style="info" %}
The **Desktop font size scale** setting is a percentage of the **Base size**.

In the screenshot above, the Page title size is set to 150% of the Base size (40px), which equals 60px.
{% endhint %}

<figure><img src="https://846450420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJZYrhya1ZIeTZS4wpBJB%2Fuploads%2FdSmTYV20aYYVYOIj144Y%2Fimage.png?alt=media&#x26;token=6deb3016-8cfa-467b-903a-8ec51ea3f43c" alt=""><figcaption></figcaption></figure>

#### Headings

We provide detailed customization options for three types of headings:

* **Page title**
* **Section heading**
* **Secondary heading**

While the **Base size** setting affects all headings at once, you can scroll down to the individual heading settings to customize each one separately.

#### Subheading

In addition to heading settings, you can:

* Choose whether to use the **Heading** or **Body** font.
* Apply the **Make font bolder** option.

#### Caption

This is the smallest font used in the interface and captions. It should not be larger than the **Body** font size.

#### Buttons

The settings for button labels are similar to Subheading customization. You can individually adjust:

* **Main buttons** — Larger buttons used in prominent sections.
* **Secondary buttons** — Utility buttons for smaller interface elements.

{% hint style="success" icon="lightbulb" %}
In blocks or sections that include buttons, you can choose from three display styles: **Solid**, **Outlined**, **Link**.
{% endhint %}

***

### Turning uppercase off

There is no single uppercase switch in Volume. Each text role carries its own **Uppercase** checkbox in **Theme settings → Typography**: **Body font**, **Page title**, **Section headings**, **Secondary headings**, **Subheadings**, **Caption font**, **Main buttons** and **Secondary buttons**. The **Headings** group at the top has no **Uppercase** checkbox — it only holds the font pickers.

#### Find the style first, then the checkbox

Which checkbox governs a given line of text is decided by **the style that line is set to**, not by the section it sits in. Most sections have no uppercase setting of their own — Rich text, for one. Instead, each text field inside the block has a style selector (**Page title**, **Section heading**, **Secondary heading**, **Subheading**, **Body font**, **Caption font**), and that style's **Uppercase** checkbox in Typography is the one that applies.

So a heading set to **Section heading** follows **Section headings → Uppercase**. Switch the same heading to **Caption font** and it stops listening to that checkbox and follows **Caption font → Uppercase** instead.

To put a specific piece of text back into sentence case:

1. Open the block in the theme editor and note which **style** the field is set to.
2. Go to **Theme settings → Typography** and clear **Uppercase** under that heading.
3. If other text shares that style and should stay uppercase, switch this block to a different style rather than clearing the checkbox.

{% hint style="warning" %}
Step 2 changes every piece of text using that style across the store, not just the one you were looking at. Step 3 is the safer route when only one block needs to change.
{% endhint %}

{% hint style="info" %}
The presets ship with most of these turned **on**, so what you see in a fresh store is not the "off by default" picture the setting list suggests. Volume and Laceup uppercase page titles, section headings, secondary headings, subheadings, buttons and product card titles. Crisp and Storm leave page and section headings in sentence case but uppercase the **Caption font**, which is a common surprise. Body text is not uppercased in any preset.
{% endhint %}

#### Uppercase settings outside Typography

Clearing a Typography checkbox will not reach these — they have their own, and each has to be cleared separately:

| Where                                                                                                    | What it uppercases                                                       |
| -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| **Theme settings → Product card**                                                                        | Product title, price, and the same pair again for the small product card |
| **Theme settings → Quick search**                                                                        | Popular searches links                                                   |
| **Theme settings → Breadcrumbs**                                                                         | The breadcrumb trail                                                     |
| **Header** section                                                                                       | The menu links                                                           |
| **Announcement bar** section                                                                             | The bar text, plus a separate checkbox for each of its two link blocks   |
| **Mobile dock** section                                                                                  | The item labels                                                          |
| **Collection tabs**, **Product bundle**                                                                  | The tab labels; Product bundle also has variant label and variant text   |
| **Newsletter**, **Video banner**, **Image comparison**, **Footer reveal**, **Quick view**, **Cart page** | Their own headings and labels                                            |

Sections with a countdown also carry a **Make labels uppercase** checkbox for the countdown units.

***

### Highlighted and Secondary heading feature

#### Secondary heading

<figure><img src="https://846450420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJZYrhya1ZIeTZS4wpBJB%2Fuploads%2Fg4JNaZCBh53hOD1vbaSx%2Fimage.png?alt=media&#x26;token=21b77e98-7a84-485a-bda6-4ff51d28dd6e" alt=""><figcaption></figcaption></figure>

In the **Theme settings → Typography → Headings**, you'll find a **Secondary heading** picker. It's used in two cases:

1. If you wrap any word or phrase inside `{curly brackets}` in a section or block's Heading field, it will automatically pull the Secondary heading font.

<figure><img src="https://846450420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJZYrhya1ZIeTZS4wpBJB%2Fuploads%2FiEdnHN2CYlrcklVWulHg%2Fimage.png?alt=media&#x26;token=cc8dc044-bcb7-4e50-8962-45f166cf12aa" alt=""><figcaption></figcaption></figure>

2. In **Theme settings → Typography**, you can switch the toggle from **Main** to **Secondary** for a specific type of heading.

<figure><img src="https://846450420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJZYrhya1ZIeTZS4wpBJB%2Fuploads%2FdbgsLJlTSgbW3gRlbk3C%2Fimage.png?alt=media&#x26;token=fbcc87f0-ddc5-4c6f-a9ea-a7c372c2c64a" alt=""><figcaption></figcaption></figure>

{% hint style="warning" icon="hand-pointer" %}
For example, you can pair a bold accent font with your Main heading, or choose the same font in an Italic style for the Secondary heading to create more contrast.
{% endhint %}

#### Highlighted heading

If you wrap any word or phrase inside `[square brackets]` in a section or block's Heading field, that part will be highlighted using the **Highlighted background** color. This color is set in **Theme settings → Colors → Color scheme** applied to the specific section.

<figure><img src="https://846450420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJZYrhya1ZIeTZS4wpBJB%2Fuploads%2FAGlEpNoGpc7wUKYl9ISS%2Fimage.png?alt=media&#x26;token=717755fa-e4c1-4cfb-a1d7-08e2a472cf89" alt=""><figcaption></figcaption></figure>

You can also mix **Secondary heading** and **Highlighted heading** together to create unique and unexpected combinations.


---

# 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/theme-settings/typography.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.
