Skip to main content

​
Problem

The font in sent emails appears different from the font used during email composition.

​
Explanation

To ensure consistent rendering across sent emails, you must use web-safe fonts only. If a custom font is used, it may not be supported in the recipient’s inbox, leading to the use of fallback fonts supported by the mailbox. To gain control over this fallback font sequence, insert the following HTML code into your template, updating the font-family property with your desired web-safe fonts: For example, in the following HTML code, Noto Sans is the primary font. If Noto Sans is not supported by the recipient’s email client, it falls back to Arial. If Arial is also not supported, it then uses the sans-serif font.
To upload your own fonts and configure fallback fonts from the dashboard instead of editing HTML, refer to Custom Fonts.