## I have uploaded a custom web font to the visual editor and applied it to an email, but it is not displayed properly in my email app.

The adoption of custom web fonts across[ email clients](🔗) is different. Some email clients have very limited support for custom fonts or no support at all.

The visual email builder inserts custom fonts into the email code, but it cannot control how those fonts are rendered by an email client app. In case the email client does not support a particular custom font, it uses a fallback font that is defined in the custom font CSS, which is usually a web-safe font of similar properties (serif for serif fonts, etc.).

## What is the difference between a web-safe font and a web font?

Web-safe fonts are a set of widespread fonts available on most devices, and most applications support these fonts, including email clients. Web fonts are not-so-popular fonts usually hosted on some SDN like Google fonts or Adobe Fonts and are attached to emails as links in the email’s CSS.

## Where can I find more information about custom fonts in emails?

You can find more information on the [BeeFee email builder support site](🔗). It is a very informative article covering the topics of font support in email apps. Additionally, it provides an overview of custom fonts support for the most popular email clients.

Did this article help you?

Please provide your feedback. We would like to know if our help center is effective in solving your queries. You can also leave comments and suggestions on how we can make our help articles better. You can also suggest topics you’d like us to cover.