Themeisle Docs

Appearance

How to load Neve fonts locally ​

Hosting the  Google Fonts locally in the Neve theme can be easily achieved in two ways:

Please note that implementing the solution provided in this doc, all the fonts of your website will be hosted locally, including the ones from the third-party plugins.

The WordPress filter provided in this article enables the usage of the WPTT webfont-loader, and there is no additional action required, such as downloading fonts/css.

🖲 Enabling the option in Customizer ​

The Google Fonts can be hosted locally by simply enabling its toggle:

1. Navigate to Appearance > Customize > Typography.

2. Enable the Local fonts hosting toggle.

Note: If you choose the second scenario ( using a code snippet ), it's important to keep in mind that it overrides the toggle.

📝 Using a code snippet ​

Neve fonts can be loaded locally by adding the following code at the end of the functions.php file of your child theme. The same approach also applies to the Typekit fonts.

add_action( 'wp_print_styles', function() {
    add_filter( 'neve_load_remote_fonts_locally', '__return_true' );
} );

📝 Note: A ready-made child theme for Neve is available for download in this guide.

🧩 Installing a Site Specific plugin ​

This plugin is a dedicated file that contains the above code snippet, being a more straightforward approach.

1. Download the plugin at this link - download.

2. Just navigate to Plugins > Add New, and upload the archive that you've previously downloaded.

Troubleshooting: local fonts are enabled but fallback fonts appear ​

If you still see fallback fonts after enabling local hosting, it usually means the local font CSS or font files are not loading correctly, or another optimization setting is changing how that CSS is delivered.

Check for caching or CSS optimization conflicts ​

Caching and performance plugins can interfere with local font loading. WP Rocket is one common example, but the same behavior can happen with other optimization plugins too.

1. Temporarily deactivate your caching/performance plugin and reload the page.

2. If the font starts loading correctly, reactivate the plugin and test by disabling optimization options one by one.

3. Start with these settings first:

  • Optimize CSS Delivery
  • Minify CSS
  • Remove Unused CSS
  • CSS/JS Delay or Defer options
  • Font loading or font preload options

📝 Info: Test one change at a time so you can identify exactly which setting causes the conflict.

Clear caches and retest ​

After each change, clear all cache layers before testing again:

  • Plugin cache (for example, WP Rocket cache)
  • Hosting/server cache
  • CDN cache (if you use one)
  • Browser cache

Then retest in a private/incognito window.