---
title: "Applying Custom Fonts to Your Help Center (Including CDN/Cache Behavior)"
description: "Introduction"
canonical_url: "https://help.brainfi.sh/articles/applying-custom-fonts-to-your-help-center-including-cdncache-behavior-IFdvXXkxJ6"
md_url: "https://help.brainfi.sh/articles/applying-custom-fonts-to-your-help-center-including-cdncache-behavior-IFdvXXkxJ6.md"
---
# Applying Custom Fonts to Your Help Center (Including CDN/Cache Behavior)

## Introduction
This article explains how to apply a custom font to your Help Center. This feature allows you to go beyond the standard library and use a specific font that matches your brand's typography.

## Steps
1. In the Help Center agent's settings, scroll to the **Themes & Customization** section.
2. Locate the **Font** subsection.
3. By default, **Library** is selected. Click the **Custom** toggle switch to activate the custom font fields.
4. In the **Font URL** text box that appears, enter the complete URL to your font's stylesheet (a .css file).
5. In the **Font Family** text box, enter the name of the font family exactly as it is defined in the stylesheet.
6. Click the **Save changes** button at the top of the page to publish your font updates.

## If font changes don’t appear immediately (CDN/proxy caching)
In some environments, Help Center / widget font delivery can be routed through a proxy/CDN endpoint and cached for performance. This can delay theme font updates from showing up right away.

### Symptoms
- Theme updates are saved, but the Help Center/widget still renders with the old font settings.
- Clearing/pruning cache does not immediately resolve the issue.
- Network requests or logs reference a font proxy endpoint (example): `https://agent.brainfi.sh/api/font-proxy`.

### Why this happens (high level)
- The Help Center/widget may request fonts through a proxy endpoint (for example, `https://agent.brainfi.sh/api/font-proxy`).
- A CDN and/or intermediary cache can store font assets and/or font configuration responses to improve performance.
- Cached responses can delay propagation of new theme font settings until the cache expires or is invalidated.

### Troubleshooting / Resolution
1. **Confirm the Help Center/widget is using a font proxy endpoint**
   - Open browser dev tools → **Network** and look for requests to a font proxy such as `https://agent.brainfi.sh/api/font-proxy` (or your relevant proxy endpoint).

2. **Identify where caching occurs**
   - Determine whether caching is happening at the browser, Help Center/widget layer, CDN layer, or the proxy endpoint.

3. **Invalidate or expire the relevant cache**
   - If you control the caching layer, invalidate/purge cached responses for the font proxy endpoint.
   - If cache invalidation is not available, wait for the configured TTL (time-to-live) to elapse.

4. **Re-test after cache purge/expiration**
   - Reload the page with a hard refresh.
   - Verify the Help Center/widget now renders with the updated theme font settings.

### Additional notes
- If your desired font is available via Google Fonts, using Google Fonts as the delivery source may be a simpler option depending on your environment.
- If you see unexpected font proxy traffic, confirm who owns/operates the endpoint and what caching headers it returns.

## Summary
To use a custom font, navigate to the Themes & Customization settings for your Help Center agent. Enable the custom font option and provide the URL to your font's CSS file and the correct font family name.

If changes don’t appear immediately after updating fonts, check for CDN/proxy caching of font assets or configuration responses and invalidate or wait for cache expiration.