Website Fonts Not Loading? 7 Causes and How to Fix Them
Updated October 31, 2026
Web fonts fail when the browser can't download the file or the CSS doesn't match it. Look in the Network panel with the Font filter for red requests. A 404 means a wrong path, a CORS error means the font sits on another domain, and no request at all means the font name doesn't match.
Quick diagnosis
- Red 404 in the Network panel: the font file path is wrong.
- CORS error in the console: the font loads from another domain without permission.
- No font request at all: the
font-familyname doesn't match the@font-facerule. - Fine in Chrome, wrong elsewhere: a format that browser can't read.
Causes and fixes
The file path in `@font-face` is wrong
Most commonFont paths in CSS are relative to the CSS file, not the page. After a build change or a move to a new folder, the browser requests a file that isn't there.
Fix: Open the failed request in the Network panel, read the full URL, and correct the path or move the file.
A CORS error blocks a font from another domain
Browsers treat fonts as protected resources. A font on a CDN or a different subdomain needs a permission header, or the browser refuses to use it. This often appears after moving assets to a CDN or switching from www to the root domain.
Fix: Send Access-Control-Allow-Origin with your site's domain from the font server, or serve fonts from the same domain as the page.
The font name doesn't match
The font-family you use must match the one declared in @font-face exactly. A misspelling or a theme setting naming a family that was never loaded means no request ever happens.
Fix: Inspect the text in DevTools, open the Computed tab, and compare the rendered font with the name in your CSS.
The weight or style was never loaded
Loading only the regular weight and then using bold makes the browser fake it, or fall back. It looks like a font bug, but only part of the font set is missing.
Fix: Add each weight and style you use to the font import, and remove the ones you don't.
Your Content Security Policy blocks the font
A font-src rule that omits your font host stops the download and logs a console error. Google Fonts needs fonts.gstatic.com allowed for the files, plus fonts.googleapis.com for the stylesheet.
Fix: Read the console error, then add the host to font-src and, for the stylesheet, to style-src.
The format isn't supported
Old .ttf or .eot setups may fail in some browsers, or load slowly. WOFF2 works in all current browsers and compresses best.
Fix: Convert the font to WOFF2 and list it first in the src line, keeping WOFF as a fallback if you serve old browsers.
The font loads late and text flashes or hides
Sometimes the font loads correctly and arrives late. Browsers hide text for a moment or show a fallback, which looks like a bug on slow connections and can shift the layout.
Fix: Use font-display: swap, preload the main font file, and choose a fallback with similar proportions.
How to find it on your site
- 1
Filter the Network panel
Open DevTools, choose the Font filter and reload. Red rows show the failed files and their status codes.
- 2
Read the console
CORS and Content Security Policy problems appear here with the blocked URL.
- 3
Check the rendered font
Inspect the text and open Computed. The Rendered Fonts section names what the browser used.
- 4
Test a clean browser
Your computer may have the font installed, which hides the bug. Check in a private window on another device.
Fixes by platform
Shopify
Custom fonts go in Files or the theme's assets. Use the asset_url or file_url filters so the path stays right. Shopify's CDN handles the CORS header for theme assets.
WordPress
Optimisation plugins that combine CSS break relative font paths. Exclude the font stylesheet, then clear the cache. If you moved to a CDN, set the CORS header there.
Wix and Squarespace
Upload fonts through the site's font manager, not a code block. Fonts added through custom CSS need a host that allows cross-domain loading.
Custom code
Self-host WOFF2 files beside your CSS and use font-display: swap. Next.js users can rely on next/font, which handles hosting and preloading.
Frequently asked questions
Why is my website font not showing?
The browser could not download the font or the CSS name doesn't match it. Check the Network panel with the Font filter. A red 404 means a wrong path, a CORS error means a cross-domain problem, and no request means a name mismatch.
Why does my font work on my computer but not on other devices?
You probably have the font installed locally, so your browser uses that copy and hides the failed download. Test in a private window on another device to see what visitors see.
How do I fix a font CORS error?
Add an Access-Control-Allow-Origin header for your domain to font responses on the server or CDN, or host the fonts on the same domain as your site.
Why does text flash or disappear while the page loads?
The browser is waiting for the web font. Use font-display swap so visitors see a fallback right away, and preload the main font so it arrives sooner.