Why are my fonts changing once it's been delivered?

Hello @Angel from eCohete,

Thank you for sharing your question with the Klaviyo Community. And thank you @caroline, @meets & @elisegaines for your insightful replies.

@Angel from eCohete, custom fonts may not render as expected on all devices or email clients.

Email clients that support custom fonts include:

• Apple Mail
• iOS Mail (the default email browser on iOS)
• Google Android (except Android 2.3, which doesn’t support the @import method used by Google and Adobe fonts)
• Samsung Mail (Android 8.0)
• Outlook for Mac
• Outlook App

Can you confirm if you are previewing on an email client that does not support custom fonts? If so, it would be expected that the fallback font is used.

Thanks and have a great day.

Hi @dov.derin !

Thank you for answering.

I’m not using an email client that doesn’t support custom fonts. Actually, in previous mails, I was able to see custom fonts at inbox. That’s pretty much what I don’t understand, what’s different now.

Have great day!

Hi @Angel from eCohete,

Thank you for your follow-up.

That code snippet looks good! Nothing has changed with respect to displaying custom fonts on Klaviyo’s end. The fact that the fonts are showing correctly in the Klaviyo editor and not in the inbox tells me that the inbox is impacting the ability for custom fonts to display. Can you confirm which inbox provider you’re using to preview the emails? Perhaps they have made a change we can dig into further.

Thank you @dov.derin !

I’m using Gmail. Something I noticed recently is that custom fonts are not shown in mobile devices (tried 3 at this time). Custom fonts appear perfectly on a desktop screen.

Have a good day!

Hi @Angel from eCohete,

Thank you for sharing that information with me.

Currently, Gmail is not an email client that fully supports custom fonts. You can find all of the email clients that do support custom fonts in my last reply. You can also find more information in Klaviyo's documentation on using custom fonts.

To be clear, it doesn’t mean the custom fonts will never work in Gmail, for example if you have the font pre-downloaded on your device you may see certain fonts display for mobile or desktop, but this is not consistent across all fonts and it will not work for recipients of the email unless they too have the fonts pre-downloaded on their device(s). This is a limitation on the email client side, rather than Klaviyo.

I would just keep this in mind if you choose to use custom fonts, always have a fallback web-safe font ready just in case.

Thanks and have a wonderful Thursday.

Hi, we’re currently having the same issue. We want to use Lato Light 300 for our body text. However, once we send a test / send it out, the font converts to a bolder font. Is this a fallback font issue? Please advise how to fix.

Hi there @jessgarcia, 

I’m sorry that your custom font isn’t exactly how you want it! Unfortunately, custom fonts aren’t always respected by inboxes  so there’s no guarantee that your chosen font is the one an inbox will show. This is why we suggest having fallback fonts you prefer in case your custom font, which is your first choice, isn’t able to be shown. If your bolded version if your fallback, that might be the case!

Hope this helps!

-Taylor 

Hi @all can anyone help me on this ,

we were not able to solve one issue: being able to display our custom fonts due to am OS not supporting a typeface. Is there a way to use custom code to embed typefaces/ our host typefaces on a server and override the fallback font necessity on an OS? or any possible solution through code to help us rectify this issue?