When launching your Webflow site, your custom fonts "jump" back to the fallback font in Google Chrome. This might be caused by improper font loading or caching issues.
1. Check Font Formats
- Verify that you're using all necessary formats including .woff2, which is preferred by most modern browsers due to better compression.
- Ensure that your Webflow site includes .woff, .woff2, and .ttf to cover various browsers.
2. Adjust Font Loading
- Consider using "Swap" or "Optional" as the font-display property if not already done. Although Webflow does not natively allow setting CSS properties like
font-display: swap, adding custom CSS in the Head Code section of your Webflow project settings can achieve this. - Go to Project Settings > Custom Code > Head Code and add the following:
<style>@font-face { font-family: 'YourFont'; src: url('yourfont.woff2') format('woff2'), url('yourfont.woff') format('woff'); font-display: swap; }</style>. Replace 'YourFont' and yourfont.woff2 with your actual font name and file.
3. Clear Cache
- Clear your browser cache and refresh the page to ensure you're testing with the latest resources loaded.
4. Inspect Webflow File Uploads
- Verify that your custom font files are correctly uploaded to the Webflow site's asset manager.
- Check that there are no broken links to the font files in CSS.
5. Review Fallback Font
- Ensure that your defined fallback font in the typography settings is intentional and correctly set.
Summary
By solving the custom font loading issue in Chrome, ensure you have all necessary file formats (especially .woff2), adjust font display settings using CSS for seamless loading, and clear your browser cache. Test thoroughly to ensure all changes take effect.