> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/faq/faq-pour-le-parametrage/pourquoi-je-ne-peux-pas-changer-de-police-de-caractere-dans-les-template-demail.md).

# Why can't I change the font in email templates?

There are several reasons why you may not be able to change the font in emails sent from Yoplanning, and this relates to technical aspects of email delivery as well as software design choices. Here are some explanations:

1. **Email Client Compatibility**: Emails should be designed to be compatible with a wide range of email clients (like Outlook, Gmail, Apple Mail, etc.), each with their own HTML and CSS rendering capabilities. Using a custom font can cause compatibility issues, as not all fonts are supported or rendered the same by all email clients.
2. **Design preferences**: The Yoplanning developers have made the decision to limit the customization options to maintain a certain uniformity and professionalism in the communications sent. This helps ensure that messages are readable and aesthetically pleasing, regardless of the platform they are opened on.
3. **Readability Issues**: Standard fonts are often chosen for their readability on various devices and screen sizes. Changing the font can affect how the message is received and understood by the recipient, especially if the chosen font is difficult to read or unconventional.
4. **Email deliverability**: Using non-standard fonts can potentially affect email deliverability. Emails that use complex layout techniques or non-standard elements may be more likely to be marked as spam by some spam filters.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.yoplanning.support/en/faq/faq-pour-le-parametrage/pourquoi-je-ne-peux-pas-changer-de-police-de-caractere-dans-les-template-demail.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.