> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/appendix/brokerage-set-up/marketing-template-guidelines/fonts.md).

# Fonts

There are 2 types of fonts that can be used on templates: Web Safe Fonts and Web Fonts.

#### Web Safe Fonts

Web Safe Fonts are a very small collection of fonts that are available on all devices. If you use a web safe font for your templates you can ensure that the font can be displayed exactly the same on all devices and clients.

Here is the list of web safe fonts:

1. **Arial**
2. **Verdana**
3. **Times New Roman**
4. **Courier New**
5. **Georgia**
6. **Comic Sans MS**
7. **Trebuchet MS**
8. **Impact**
9. **Helvetica**
10. **Tahoma**

The problem with web safe fonts, however, is that the selection of fonts is only limited to the above, making it almost impossible to create distinguished designs.

#### Web Fonts

Web Fonts are a technology that allows embedded fonts in your designs that may not be installed on everyone's devices. By using a web font, you can choose from tens of thousands of fonts to create distinctive designs.

The problem with Web Fonts is that rendering them is only supported on roughly 20% of email clients.

| Medium   | Estimated Support                                           |
| -------- | ----------------------------------------------------------- |
| Websites | [98%](https://caniuse.com/fontface)                         |
| Socials  | 100% (Socials are pre-rendered by Rechat)                   |
| Print    | 100% (Socials are pre-rendered by Rechat)                   |
| Emails   | [20%](https://www.caniemail.com/features/css-at-font-face/) |

{% hint style="info" %}
As you can see in the table above using a web font is OK pretty much on all mediums except for emails. If you use a web font, on most email clients, the web font is going to be ignored. That means you will use a font during your design process, but when the font lands on inboxes of your clients it's gonna be rendered differently.

This is not a limitation imposed by Rechat. Any program you use to send emails from will have a similar situation.
{% endhint %}

#### Fancy Fonts

A smart way of getting around the limitation of web fonts in emails is saving pieces of text as images (Using your desired web font) and embedding them into your email. This would make your email look identical across email clients using your desired web font.

At Rechat we have embedded this technique into our email platform using the Fancy Font emails blocks. This makes it very easy to type in any text into Rechat using your desired font and Rechat will take care of converting it into an email so it looks stellar on all platforms.

Also note that during your template design process we can make your templates use fancy fonts automatically.

However, using this technique comes with some trade-offs:

1. The emails will be slower to load.
2. The emails won't be selectable or searchable and less accessible.
3. The text-to-image ratio of the email will drop, which can contribute to the email landing in spam.

Therefore, we suggest using Fancy Fonts for headers and a web-safe font for larger text and body sections.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rechat.com/appendix/brokerage-set-up/marketing-template-guidelines/fonts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.