How to use custom fonts without rendering as bitmaps? – Exclaimer Cloud Knowledge Base

Scenario

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.

Resolution

NOTE: The steps described here assume that you have already created an email signature. For more information, see how you can create an email signature.

To achieve this, you need to use a technique called Fallback fonts.

NOTES:

- 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:

Calibri, Candara, Segoe, Segoe UI, Optima, Arial, sans-serif

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 if you wish to add custom fonts.
Example:

The Custom Font window is displayed:

NOTE:
- Exclaimer Cloud only supports font files in the .ttf and .otf file formats.
- The max font file size acceptable is 1MB. For more information, please see Limitations within the signature template.
Click UPLOAD FONT.
The Open window is displayed.
If a custom font is uploaded, click the x to remove it.
Browse through your local/network drives to locate and select the required font file. Once selected, the font file is uploaded and the Custom Fonts window is updated.
Example:
Click OK to return to the properties window.
The uploaded custom font will be available for selection in the Font Family drop-down list.
From the Font Family drop-down list, select (or type) the required font type.
In this example, we've selected Roboto Light:

NOTE: You only need to add a custom font once - having added a font, it is available for use throughout this template to apply to any element, table, cell, group, and canvas.

Once you select the custom font for the selected element, a confirmation window is displayed asking if you are sure about using a custom font.
A warning is also displayed that this will render as a bitmap image, and text will not wrap unless a fixed width is applied to the text element.
You can add any number of Fall Back 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.

We recommend: The final two font types in the signature are common fonts, such as Arial and Sans-Serif (or Serif, if you are using a font type similar to Times New Roman):