Why does my test email renders a different font than what it is on Email Composer?

Most likely you have a Custom Built Theme/Template for your Organisation that matches your branding. 

Each Theme has its own unique set of Styles that you can choose from when building your Email Composer Document. The different Styles have pre-defined values like background colour, heading colour, fonts, paddings, and text body colour to name a few. 

If your Test Email is not reflecting the Custom Fonts you have selected, you may have selected a Web Font as your primary font. Web Fonts will use the default Web Safe Fonts as back up if it is not supported. 


mceclip0.png

mceclip2.png

 

Web Fonts

Web Fonts are are not pre-installed on the user's system. The fonts are downloaded by the user's browser while rendering the webpage, and then applied to your text.

Not all Email Clients and Devices supports Web Fonts. 

Here is a quick guide on where Web Fonts are supported: 

mceclip3.png

Web Safe Fonts

Web Safe Fonts however, are fonts that are pre-installed by many operating systems. While not all systems have the same fonts installed, you can use a web safe font stack to choose several fonts that look similar, and are installed on the various systems. It offers a more convenient way of displaying your fonts accurately across different devices and email clients. It also saves more time in editing and testing your Email Documents. You can see the different Web Safe Fonts here.

If you want to make changes on your Themes/Templates or primary font, you can reach out to us at support@swiftdigital.com.au or contact your Swift Account Manager for further assistance. 


 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.