> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/analytics+/working-with-analytics+/18.-image-support/images-in-cards.md). # Images in cards With Analytics+, you can embed images in each card or add a background image like a logo - let's jump in! ### 1. Tile-level images You can insert an image relevant to the card it is placed in i.e. embed an image corresponding to each small multiple category. When you use KPI presets with images, Analytics+ will automatically load the images from the field added to Tooltip-Text Categories.

**STEP 1:** Hover over the image and click the

icon to open the Image side pane. Select the Dataset option from the Tile dropdown to load images automatically from the dataset. Choose the custom option to select individual images for each panel.

**STEP 2:** Set the opacity, select the series, and set the aspect ratio of the image.

### 2. Background images Background images are used to brand reports or add context to the report content. You can upload a custom background image. Analytics+ will automatically convert an uploaded image into a watermark-style background image. **STEP 1:** Click the Image button on the toolbar to open the Image side pane.

**STEP 2:** Click the Upload button and select the background image from your system.

**STEP 3:** Set the opacity factor and aspect ratio from the Fit and Stretch options.

--- # 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.inforiver.com/analytics+/working-with-analytics+/18.-image-support/images-in-cards.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.