You are using Exclaimer Cloud to deploy your signatures and would like to create a signature template that uses a Custom Font type without using the Render as Bitmap option.
To achieve this, you need to use a technique called 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 will enable you to control how the signature appears across all devices, as you can choose the most similar fallback font to your original font.
If someone receives an email that includes your signature defined with a custom font, and they don't have that font type installed, the next available font type will be used.
Example of Fallback fonts:
Adding Fallback fonts
To add Fallback fonts:
- Open the required signature template within the Signature Designer.
- Select the element you wish to update.
- From the right-hand side Properties pane, expand the Text section.
- Within Font Family, click MANAGE to open the Custom Font window.
The Custom Font window is displayed:
- Click X to remove the custom font.
- The uploaded custom font will no longer be available for selection in the Font Family drop-down list.
- From the Font Family drop-down list, type the required font stack with the fallback fonts, or select a font from the drop-down list.
NOTE: You only need to add a font stack once - the template will inherit these settings from the canvas.
- You can add any number of Fallback fonts in the sequence that you wish them to be considered if the first font can't be used. Each font type should be separated by a comma.