# Fixing Fonts appear as bold or do not load (Kirki issue)

**Updated: 15th March 2024**

A font rendering issue appeared this week within the Kirki plugin. Fonts now either appear all bolded, or in some cases, don’t render correctly at all, reverting to the browser defaults.

This appears to be due to how Kirki retrieves fonts from Google’s API. It looks for woff fonts rather than the woff2 type. Something has changed within Google’s API and the woff versions are not retrieved correctly.

### Modify Kirki directly

This approach changes the core Kirki plugin to ensure that it retrieves woff2 files rather than woff.

Edit this file:\
sala/inc/admin/kirki/modules/webfonts/class-kirki-fonts-downloader.php

Replace **line** 191 with this line:

`$user_agent = 'Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0';`

Next install the [Transients Manager](https://wordpress.org/plugins/transients-manager/) plugin.

And look for:\
**kirki\_remote\_url\_contents**

And delete that transient. This has an expiry of 7 days so it will eventually flush by itself if you wait long enough.

Test the site now, and the fonts should display again.

You can remove the Transients Manager plugin afterwards.


---

# Agent Instructions: 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:

```
GET https://uxper.gitbook.io/sala-wp/faqs/fixing-fonts-appear-as-bold-or-do-not-load-kirki-issue.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.