Using custom fonts without rendering as bitmaps


Your subscription is configured for Outlook Client for Exclaimer Cloud - Signatures for Office 365 or for Exclaimer Cloud - Signatures for G Suite. You'd 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 Fall Back Fonts. These are a series of font types that start with your Custom Font, but falls back on to other fonts which are similar, if your custom font isn't available.  

So, if someone receives a message which 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. An example of this is below:

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

To do this, follow steps below:

  1. Having created your signature with required elements, select any element to access properties. Properties are shown for whatever element you selected - in the example below, we selected a table element:


  2. At the top of the Properties window, you'll see a 'breadcrumb trail' for related elements - you need to select the first entry in this trail, which will always be Signature:


  3. Use the Font Family option to select (or type) the required font type. In this example, we've selected Calibri:


  4. Now, 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:

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


  5. Save your changes.


Haven't found a solution to your problem?

Please click the button below, login to the Exclaimer Cloud portal and raise a support ticket. A member of the Exclaimer Support team will then be in touch.

Raise a support ticket