Relevant Products: Exclaimer Cloud - Signatures for Office 365 | Exclaimer Cloud - Signatures for G Suite | Signature Manager Exchange Edition | Signature Manager Outlook Edition
Scenario
You are unsure whether the font you have chosen for your signature template design is web safe and available for use in your Exclaimer Signature Solution.
The table below displays a list of the most commonly used fonts, against the devices and operating systems they are available on:
Windows | iOS | iOS13 | Android | |
Arial | ✔ | ✔ | ✔ | ✔ |
Arial Black | ✔ | ✔ | × | × |
Calibri | ✔ | × | × | × |
Century Gothic | ✔ | × | × | × |
Comic Sans MS |
✔ | × | × | ✔ |
Courier New |
✔ | ✔ | ✔ | ✔ |
Georgia | ✔ | ✔ | ✔ | ✔ |
Impact | ✔ | × | × | × |
Tahoma | ✔ | × | × | ✔ |
Times New Roman |
✔ | ✔ | ✔ | ✔ |
Trebuchet MS |
✔ | ✔ | ✔ | × |
Verdana | ✔ | ✔ | ✔ | × |
Resolution
If your chosen font is not available across all operating systems, you can create a font stack with a list of fallback fonts.
- Font stacks are used to control how the font will appear to the recipient if they do not have access to your chosen font.
- Fallback fonts allow you to specify websafe alternatives to fall back on if needed. This allows you to control how the signature appears across all devices as you can choose the most similar fallback font to your original font.
Example of a fallback string:
Calibri, Candara, Segoe, Segoe UI, Optima, Arial, Sans-Serif
In this example, the initial font type is Calibri. If Calibri is not available to use, it will move onto Candara and so on until it reaches the "Sans-serif" font type.
You can use font stacks with a string of fallback fonts in any Exclaimer Signature Solution.