# Cookie Banner Font Source Settings | Secure Privacy Guide

> [CMP v1] Learn how to change the font source for your Secure Privacy cookie consent banner — switch between Google CDN and Browser Default in the Colors and Styling settings to resolve CSP issues or avoid third-party font requests.

- Canonical: https://support.secureprivacy.ai/article/cmp-v1-how-do-i-change-the-font-for-the-cookie-banner
- Product: Consent Management
- Category: Secure Privacy Legacy
- Published: 2026-03-06T12:44:00+00:00
- Updated: 2026-03-22T20:43:11.338+00:00
- Reading time: 2 minutes

---

By default, Secure Privacy's cookie consent banner uses the **Raleway font** loaded from Google's CDN. You can change the font source to use browser default fonts instead — useful if your Content Security Policy blocks external CDN requests or if you prefer not to load fonts from Google's servers.

## Who Is This For?

-   Website administrators customizing the font source for their Secure Privacy cookie consent banner
    
-   Developers resolving Content Security Policy (CSP) issues caused by Google CDN font loading
    
-   Privacy-conscious website owners who prefer not to load third-party fonts from Google's infrastructure
    

## How to Change the Cookie Banner Font Source

The **Font Source** setting offers two options:

-   **Google** — loads the Raleway font from Google's CDN (default)
    
-   **Browser Default** — uses the visitor's browser default font, with no external CDN request
    

To change the font source:

1.  Log in to your Secure Privacy dashboard and navigate to your cookie banner settings.
    
2.  Open the **Colors and Styling** sidebar menu.
    
3.  Locate the **Font Source** option and select either **Google** or **Browser Default**.
    
4.  Click the green **Save** button to apply the change.
    

![Secure Privacy Colors and Styling sidebar showing Font Source options — Google CDN and Browser Default — with Save button](https://pub-7bd19505838640d0a08ef1bd6ec3fb9b.r2.dev/articles/f53408e04ab9020b7c17-af3b81ffdb38.webp)

## Frequently Asked Questions

### Why would I switch from Google CDN to Browser Default for the font source?

The most common reason is a **Content Security Policy (CSP)** that blocks external font requests from Google's CDN — which can cause the banner to display incorrectly or trigger console errors. Switching to Browser Default eliminates the external CDN dependency. It also avoids making a network request to Google's servers on page load, which can be relevant for visitors in regions with stricter privacy expectations around Google services.

### Will switching to Browser Default change how my cookie banner looks?

Yes, slightly. The Raleway font used by default has a specific appearance. Switching to Browser Default means the banner will use the visitor's browser system font instead — which varies by browser and operating system. If visual consistency is important, test the banner appearance after making the change.

### Do I need to rescan or make any other changes after updating the font source?

No. Changing the font source only affects how the banner's font is loaded in the visitor's browser. It does not affect your cookie scan results, blocking configuration, or compliance score. The change takes effect as soon as you click Save.

## See Also

-   [Secure Privacy Pricing Plans Overview](https://support.secureprivacy.ai/article/secure-privacy-pricing-plans--consent-management-platform)
    
-   [Website Visits vs Page Views vs Consent Explained](https://support.secureprivacy.ai/article/website-visits-vs-page-views-vs-consent-explained)
    
-   [Secure Privacy Volume Discounts | Custom Consent Storage Pricing](https://support.secureprivacy.ai/article/secure-privacy-volume-discounts--custom-consent-storage-pricing)