> For the complete documentation index, see [llms.txt](https://docs.beefree.io/beefree-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beefree.io/beefree-sdk/server-side-configurations/server-side-options/services-options/add-a-favicon-to-emails.md).
# Add a Favicon to Emails
{% hint style="info" %}
Available for [Email](/beefree-sdk/visual-builders/email-builder.md) and [Page](/beefree-sdk/visual-builders/page-builder.md) builders and on all [plans](https://developers.beefree.io/pricing-plans). This page discusses how to enable the Favicon for the Email Builder.
{% endhint %}
## Overview
You can add favicons to email designs in the email builder. Adding a favicon directly to an email's HTML is beneficial when the email is viewed in a browser, and the end user would like a favicon to display in the browser tab.
When activated in the [Beefree SDK Developer Console](https://developers.beefree.io/login?from=website_menu), a new **Configure favicon** option becomes available in the **Settings tab** of the builder, where end users can select or edit their favicon.
The following image shows an example of what this looks like in the builder.
## How to Activate the Feature
The Favicon option is off by default and must be enabled in the [Beefree SDK Developer Console](https://developers.beefree.io/login?from=website_menu).
Take the following steps:
1. Log in to the [Beefree SDK Developer Console](https://developers.beefree.io/login?from=website_menu).
2. Navigate to the application where you’d like to activate favicon support.
3. Click on the **Details** button.
4. Navigate to **Application Configurations**.
5. Go to the **Settings** section.
6. Check the option for **Favicon enabled**.
7. Save your configuration.
Once enabled, a **Favicon section** will appear in the editor’s **Settings tab**, allowing end users to upload and manage favicon assets.
### JSON Template Example
When a favicon is added, the configuration is reflected in the template JSON under the `head.meta.favicon` object.
Example:
```json
{
"page": {
"head": {
"meta": {
"favicon": [
{
"handle": "request_image_url",
"url": "https://d15k2d11r6t6rl.cloudfront.net/public/users/Integrators/BeeTestingMachinePage/testmachine/upgrade-trial-modal.png"
},
{
"handle": "source",
"url": "https://d15k2d11r6t6rl.cloudfront.net/public/users/Integrators/BeeTestingMachinePage/testmachine/favicon_images/upgrade-trial-modal-dbe339-source.png"
},
{
"handle": "16-icon",
"url": "https://d15k2d11r6t6rl.cloudfront.net/public/users/Integrators/BeeTestingMachinePage/testmachine/favicon_images/upgrade-trial-modal-dbe339-16-icon.png"
},
{
"handle": "32-icon",
"url": "https://d15k2d11r6t6rl.cloudfront.net/public/users/Integrators/BeeTestingMachinePage/testmachine/favicon_images/upgrade-trial-modal-dbe339-32-icon.png"
},
{
"handle": "apple-touch-icon",
"url": "https://d15k2d11r6t6rl.cloudfront.net/public/users/Integrators/BeeTestingMachinePage/testmachine/favicon_images/upgrade-trial-modal-dbe339-apple-touch-icon.png"
}
]
}
}
}
}
```
### Additional Considerations
Consider the following when activating the Favicon option within the Beefree SDK Developer Console:
* **Cross-platform consistency**: Favicons will only display when an email is opened in a browser. They won’t appear directly inside email clients.
* **Multiple formats supported**: End users can upload different favicon sizes (e.g., 16x16, 32x32, Apple Touch icons) for maximum compatibility across platforms.
* **Landing page similarity**: This update brings favicon support for email in line with what was already available for [landing pages](/beefree-sdk/visual-builders/page-builder.md), ensuring consistency across experiences.
---
# 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.beefree.io/beefree-sdk/server-side-configurations/server-side-options/services-options/add-a-favicon-to-emails.md?ask=&goal=
```
`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.