> For the complete documentation index, see [llms.txt](https://docs.vitaracharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vitaracharts.com/readme/background-images.md).
# Background Images
How to set the Vitara charts’ backdrop images.There are two ways to insert the background image:
#### Using a relative path (the image needs to be placed in VitaraCharts folder)
**Step 1:**
Copy the image which you want to set as a background for Vitara charts in the following folder.
```
Tomcat\webapps\MicroStrategy\plugins\VitaraCharts\custom\images
```
**Step 2:**
Open edit popup window, goto background tab, click on “Enable background image” checkbox.
**Step 3:**
Enter the name of the image with the extension (.png or .jpg) into the text box. Example:
Note: Image name is case sensitive.
#### Using Image URL or full path
We can directly copy the image web URL or full path in the text box.\
Examples:
We have options like - original/fit to chart/fill chart/custom, to make the image to fit with the Vitara chart. The opacity option can reduce the intensity of the background image on the Vitara chart. Below we can see a screenshot of Stacked Column Chart with a background image.
---
# 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://docs.vitaracharts.com/readme/background-images.md?ask=&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.
