> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/doc/en/advanced-features/tag-extensions/dynamic-images.md).

# Display dynamic images

Make sure the image is displayed exactly the way you want

You can display dynamic images when generating a document. Images can be stored directly in rich text area or URL fields.

However, we recommend storing the image as a Salesforce file, and then storing the Content Version ID on the record

* In your document template, open the assistant to access the desired object
* Find the rich text area or URL field that contains the image, or the text field that contains the Content Version ID
* Click the 3 small dots "..." and then "Configure image"
* Select "Original size" or "Custom size" to set the image size manually

{% hint style="success" %}
**Example**

Use `{!Account|Champtexte__c(img)}` if you keep the original size\
`{!Account|Champtexte__c(img,w=30,h=15)}` if you set a custom size, with a width of 30 and a height of 15\
`{!Account|Champtexte__c(img,w=100)}` if the width is 100 pixels and the height is resized automatically so that the image is not distorted
{% endhint %}

* Copy and paste the tag into your document

{% hint style="warning" %}
**Tip**

Set only one parameter (width or height) and leave the other on Auto. At generation, the parameter you did not set adjusts automatically so that the image is not distorted.
{% endhint %}

![Assistant: configure the image](https://content.gitbook.com/content/U1Chwyf7Cc7FN9BiEh0V/blobs/yK1j4SLpXyEn0OhRLRhd/extensions-balises-4.png)


---

# 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://university.gonexa.fr/doc/en/advanced-features/tag-extensions/dynamic-images.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.