If you can't find the desired font that your brand uses, you can add any additional font to Chamaileon. Let it be a Google Font or a custom font of yours.
⚠️ Important: font support in email clients
Custom fonts do not work consistently across email clients.
They are mainly supported in:
Apple Mail (macOS, iOS)
Outlook for Mac
Most other clients (like Gmail or Outlook on Windows):
ignore custom fonts
and show a fallback font instead
--> This is a limitation of email clients, not Chamaileon.
Regardless, in order to add new fonts to your emails, you need to go to the Workspace Settings and choose the Custom font settings under Customization.
What font URL should you use?
You need to provide a Google Fonts or custom CSS URL that works in a normal website environment.
Important:
If the URL works in a website (CSS), it will generally work in email as well but not all weights.
To display a new font in the Chamaileon editor and your emails (depending on email clients), you need to provide a font URL under the font URL settings. Every font URL should include the following font styles:
Regular 400
Regular 400 italic
Bold 700
Bold 700 italic
As an example, the URL for Poppins would look like this:
https://fonts.googleapis.com/css2?family=Poppins:wght@400;700
For modern, non-static fonts, you can use the same url query structure (it is supported as legacy), or include the full axis, or define the 400/700, regular/italic range.
Example for Inter:
https://fonts.googleapis.com/css2?family=Inter:ital,wght@0,400;0,700;1,400;1,700
Why? = Font weight compatibility in emails
While many fonts include multiple weight variations (e.g. 300, 500, 600), most email clients reliably support only:
Regular (400)
Bold (700)
And their italic counterparts.
Other weights may not render as expected and are often automatically adjusted to the closest supported value because email clients not load multiple font files for the multiple weights. For the new, variable fonts, most clients fall back to the legacy rendering and download the old static files.
Example:
500→ may display as400600→ may display as700
For the most consistent results across all email clients, we recommend designing with regular and bold weights only, and treating other weights as optional enhancements.
⚠️ Don’t overcomplicate font weights
Even if you:
include multiple weights
or use advanced Google Fonts settings (like variable fonts)
Email clients will still:
ignore unsupported weights
fall back to 400 and 700
Bottom line:
Adding extra weights usually doesn’t improve results in email.
Set your font stack (fallback fonts)
Since many email clients ignore custom fonts, you must define a fallback font stack.
As an example, the Font stack for Poppins would look like this:
Poppins, Helvetica Neue, Helvetica, Arial, sans-serif
Google fonts and/or custom fonts won't show up most email clients!
According to Litmus only Apple Mail, Outlook for Mac, and iOS support web fonts properly.
In other email clients always a fallback font will appear, that's why it's important to choose your fallback fonts wisely when you define your font stack.
Choosing fallback fonts
To get the best visual match:
Use the same font type:
sans-serif → Arial, Helvetica, Verdana
serif → Georgia, Times New Roman
Choose similar proportions (x-height)
Always end with a generic family:
sans-serif,serif, ormonospace
Make sure that the fallback fonts have the same font type as the web font (serif or sans-serif)
Preferably use web-safe fonts as fallbacks:
Arial (sans-serif)
Helvetica (sans-serif)
Tahoma (sans-serif)
Trebuchet MS (sans-serif)
Verdana (sans-serif)
Garamond (serif)
Georgia (serif)
Times New Roman (serif)
Courier New (monospace)
Brush Script MT (cursive)
Choose fallback fonts that have similar x-height (letter height) to make sure that your email designs won't be messed up completely when only the fallback font shows up.
Using custom fonts
If you want to use your own font:
Host it publicly (your server or CDN)
Provide a CSS URL (similar to Google Fonts)
Make sure it includes the required styles (400 / 700 + italic)
If you would like to use your custom font, you need to host it publicly on the internet, the Font CSS should be compiled by your developer team, and finally, you need to provide us with a similar URL.