Avada Fonts Not Loading: Google Fonts Mode, Custom Uploads and Missing Icons

Wrong typeface, invisible text or hollow icons

Font trouble on an Avada site shows up in three ways, and they have different causes. Headings or body text appear in a fallback font. Text is invisible for a beat on slow connections, then pops in. Or icons from Font Awesome, used everywhere from buttons to footers, show as empty shapes or nothing at all. Check which, on which pages, and whether a logged-out visitor sees the same, then work through the causes below in order.

The general fonts guide explains how fonts reach any WordPress page. This one follows Avada's own route, which runs through four areas of Global Options: Typography, Global Typography, Privacy and Performance, plus the Features list under Advanced.

The Avada settings that decide which font arrives

Google Fonts Mode and the copy nobody refreshed

Avada can fetch Google Fonts from Google's servers or host them on yours. The switch is Google Fonts Mode, under Avada > Options > Privacy: CDN retrieves them through the Google Fonts API, Local hosts them on your server so visitors' browsers never contact Google. Many owners flip it to Local for privacy reasons, which is sensible, and then the fonts break because the page cache and Avada's compiled CSS still reference the old source.

Avada's documentation adds a caveat that explains a lot of confused support threads: the setting covers Avada's Google Fonts only. A form plugin, a slider or a page section built with another tool may keep calling Google directly. And the reverse happens too. Leave the mode on CDN while a privacy or optimization plugin blocks requests to Google, and the font request simply goes nowhere.

Check: open the browser's Network tab, filter by Font, and reload logged out. Requests to fonts.gstatic.com mean something is still using the CDN. Requests to your own domain that return errors mean the local copy is missing or stale. No font requests at all means the font is never asked for, which sends you to the typography causes further down.

Custom uploads, typography sets and the icon fonts

A custom font that was never complete

Custom fonts go in at Avada > Options > Typography > Custom Fonts, under a Font Name you then pick from any font-family dropdown. ThemeFusion's documentation asks for five files per font, .woff2, .woff, .ttf, .svg and .eot, and says each is required for full browser support. Two more traps sit in the same doc. WordPress may refuse the upload with 'Sorry, this file type is not permitted for security reasons', and Avada does not support variable fonts, so a single variable file from a type foundry will not work. Check: reopen the Custom Fonts entry and confirm every file slot holds a static font file.

An element with a mind of its own

Global Typography holds five default sets, Headings, Subheadings, Lead, Body and Small, and elements and heading levels can inherit from them. Avada marks inherited values in grey and local overrides in white. Change the Headings set and every title that inherits it follows, except the ones someone styled by hand. The same applies to variants: a set calling for a weight the font does not include falls back. Check: open a misbehaving Title element and look for white typography fields.

Icons switched off to save weight

Font Awesome subsets, Solid, Regular, Brands and, with Font Awesome Pro, Light, are chosen in Advanced > Features. The Performance Wizard's Icons step scans the site and recommends subsets to turn off, and can flag old version 4 icons so v4 compatibility can go too. Add a Brands icon to the footer after that scan and it has nothing to draw with. Check: inspect the empty icon, note its class prefix and confirm that subset is enabled.

Text that loads late is not text that failed

Font Face Rendering offers three choices, and the docs describe the trade-off honestly. Swap All renders faster with a possible flash of unstyled text. Block gives clean rendering but a longer wait before the first paint. Swap Non-Icon Fonts mixes the two. On a slow phone, Block can look like a page with missing words, and Swap All can look like the wrong font, when in both cases the right file is still on its way.

Preload Key Fonts can help or hurt. The Performance Wizard's Fonts step counts the variants in use and can preload key variants when the largest element on screen is text, and its docs note that fewer variants mean fewer requests. Preload All on a site with eight weights and the icon fonts, and the browser queues them all ahead of the hero image. If text shifts when the real font lands, the layout shift guide covers the fix, and the Avada speed guide covers the rest of the Performance tab.

Putting the right typeface back, in order

1. 1

   Read the Network tab

   Logged out, private window, filter by Font. Note which files load, which fail and which are never requested.

2. 2

   Settle the source

   Choose Google Fonts Mode Local or CDN in Avada > Options > Privacy, and make sure no privacy or optimization plugin is fighting that choice. Remove duplicate font loaders from other plugins where you can.

3. 3

   Rebuild Avada's files

   Press Reset Avada Caches under Performance, regenerate critical CSS if enabled, then purge the caching plugin, server cache and CDN. Stale compiled CSS is a common reason a correct setting looks wrong; Avada CSS not updating covers that in depth.

4. 4

   Repair custom and Adobe fonts

   Re-upload missing formats as static files. If WordPress blocks the upload, ask your host about the ALLOW_UNFILTERED_UPLOADS line Avada's docs mention, and take it out again afterward. For Adobe Fonts, confirm the ID and press Refresh TypeKit Fonts Cache in the back-end options.

5. 5

   Clear stray overrides

   Reset white typography fields on elements that should follow a Global Typography set, and confirm each set's variant exists in the chosen font.

6. 6

   Restore the icon subsets

   Enable any Font Awesome subset the site still uses in Advanced > Features, then reset Avada's caches again.

7. 7

   Tune rendering last

   Set Font Face Rendering to Swap Non-Icon Fonts as a starting point and preload only the variants the first screen needs. Test on a phone over a slow connection.

Keeping the brand font on the page

• Two families, few weights. Every variant is another file to fetch and another chance to fail.
• Fonts live in typography sets. Style headings through Global Typography, not element by element, so one change reaches every page.
• Re-run the Performance Wizard after design changes. Its earlier icon and font recommendations were based on the site as it was then.
• Keep the original font files. Store the full set of formats somewhere safe, because the uploads folder is not a backup.
• Reset and purge after every typography change, the same routine ThemeFusion recommends after updates.

Our hosting and maintenance plans check fonts and icons after each tested update. If fonts broke after a move to a new domain or to https, mixed content errors are worth ruling out. Other Avada faults are listed in the Avada repair hub, and the troubleshooting section covers other themes.

Eight settings for one typeface

A privacy toggle, a typography panel, typography sets, a custom font uploader, a rendering mode, a preload list, an icon feature list and a wizard that edits several of them. Each makes sense. Together they mean a font can be correct in four places and still broken by the fifth, and every caching layer can hold onto the broken version a little longer. That is a fair description of how a WordPress stack accumulates moving parts.

Next.js handles fonts in one module. next/font downloads the files at build time, serves them from the site's own domain and creates a matched fallback to limit layout shift, with no privacy toggle or preload list to manage. It costs more to build, and a new typeface needs a developer. Our Avada vs Next.js comparison weighs that fairly, and Avada to Next.js describes the move, after which your team edits words in Athena CMS and never touches a font setting. For a repair on the current site, our theme troubleshooting service will trace the missing file.