> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/advanced-topics/custom-parts-workers-scripts-and-libraries/custom-favicon.md).

# Custom Favicon

## Description

The LogicNets system allows you to assign a favicon--a shortcut or tab icon--to your published applications, which allows you to more fully customize their look and feel. The system then displays this icon on your users' browser tab when they are using your LogicNets-based applications.

**Note:** This function is currently only for those customers who have created their own custom installer. You may need to work with LogicNets for more information on creating your own custom installer.

**Node Type:** This function is not associated with a particular node type.

**Used With:** This function can be used with all published packages that are distributed using a custom installer.

## Add a Favicon to Your Project

Put the icon you want to display as your favicon in the company folder and name the file "favicon.ico". When the installer finds this icon in the company folder, it replaces the standard favicon with this version.


---

# 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://community-test.logicnets.com/release-9/platform-documentation/advanced-topics/custom-parts-workers-scripts-and-libraries/custom-favicon.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.