You are using Exclaimer Cloud and creating your email signature. You are unsure if the font you have chosen for your signature template design is web safe and available for use in your Exclaimer Signature solution.
Once you have established whether your chosen font is web safe or not, you can implement a font stack into your signature.
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 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 web safe 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.
To view the list of web safe fonts, see Web safe fonts and font stacks.
Inserting Font Stack
- Open the required signature template within the Signature Designer.
- Take the initial font type you are looking to use. In this example, we use Calibri.
- Now, create a Font Stack - this is simply a list of your chosen fonts.
Please ensure that you separate each font with a comma and space.
Example: Calibri, Candara, Segoe, Segoe UI, Optima, Arial, sans-serif.
NOTE: If you are unsure which fonts to use, look at the CSS Font Stack for a list of fonts that already have font stacks created.
- Now, select the full signature by selecting the outer edge of the template.
- From the right-hand side, Properties panes, expand the Text section.
- In Font Family, remove the current font type and replace it with your Font Stack - the list you created earlier (see step 3).
- Once you have made the changes, click SAVE CHANGES.
CAUTION! Due to the behaviour being out of our control, the Outlook client will use the first font (specified in the font stack) and then remove the remaining fonts (specified in the font stack) from the HTML coding.
We recommend you use font stacks for server-side signatures only.