> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/platform/live-cockpit/widgets/predefined-widgets/image.md).

# Image

With the "Image" widget, you can upload a locally stored image and display it on the dashboard.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FZL619tR6KSxlTkcnbtMh%2FGroup%20683.png?alt=media&amp;token=de5601ee-9f72-4ae3-b71e-87a79ea8a8be" alt=""><figcaption><p>An "Image" widget in the dashboard</p></figcaption></figure>

## Configure Widget

{% @supademo/embed url="<https://app.supademo.com/demo/i_SW8nAOyhQI48q1Y2xZ2>" demoId="i\_SW8nAOyhQI48q1Y2xZ2" fullWidth="true" %}

1. Make sure you are in the Dashboard menu.
2. Click on "Add widget"
3. Click on "Image"
4. Select the primary asset. The name of this asset appears in the title bar of the widget.
5. Select the asset for which you want to add an image.
6. If other[ -> files are associated](https://docs.buildings.ability.abb/collection/mandatory-base/assets/attach-documents-to-assets.md) with the selected asset, they will be displayed.
7. Click on the "Upload file" field and upload an image file. Alternatively, you can also drop image files via drag and drop. Supported formats: .jpg, .png
8. Optional: Repeat the process to upload more images.
9. If multiple images have been uploaded: You can choose which image is displayed in the widget. Click on an image to select it. The selected image is marked with a black border.
10. Optional: Select how much space your new widget should occupy on the dashboard.
11. Click on "Add widget"


---

# 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.buildings.ability.abb/collection/platform/live-cockpit/widgets/predefined-widgets/image.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.
