> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/documentation/images-in-documentation.md).

# Images in documentation

There are two types of images in documentation markdown files:

* Images that appear in integration/script/playbook README files. These images only appear in <https://xsoar.pan.dev/>. They do not appear in the product UI.
* Images that appear in pack README files and integration description files. These images appear in both <https://xsoar.pan.dev/> and in the product UI.

#### Relative URLs

When creating markdown README documents for playbooks, integrations, or scripts that appear in <https://xsoar.pan.dev/> only, you can use relative or absolute URLs. Relative URLs can NOT be used for content pack READMEs and integration description file images. For content pack READMEs and integration description file images, see the Absolute URLs section below.

You can use relative URLs to documentation images stored in the `doc_files` or `doc_imgs` directories. To use relative URLs, link the image using a relative path.

For example:

![relative\_url\_example.png](/files/EAVHb21Lk98kciiIHW19)

View the README.md file in GitHub's web interface and verify that the images display properly.

Examples of documentation using relative URLs:

* [Google Calendar](https://github.com/demisto/content/blob/master/Packs/GoogleCalendar/Integrations/GoogleCalendar/README.md)
* [G Suite Admin](https://github.com/demisto/content/blob/master/Packs/GSuiteAdmin/Integrations/GSuiteAdmin/README.md)

#### Absolute URLs

When creating markdown README documents for playbooks, integrations, or scripts that appear in <https://xsoar.pan.dev/> only, you can use relative or absolute URLs. When creating markdown files for content pack READMEs and integration description file images, you can only use absolute URLs.

To obtain an absolute URL to an image from GitHub:

1. Commit the image and push to GitHub.
2. View the file in the GitHub web interface.
3. Copy the URL from the **Download** button.

   ![](/files/UWi49dzFkbVEmXHCiRpk)

   Verify the URL you are copying is not referring to a branch which will be deleted after the pull request is merged. The URL should refer to a commit hash or the master branch.

   If you click the Download button, GitHub performs a redirect and the URL in the browser points to the domain: `raw.githubusercontent.com`. You can also use this URL as the absolute URL.
4. Embed the image in the README.md using a Markdown Image Link. For example: `![Playbook Image](https://github.com/demisto/content/raw/2d6e082cfb181f823e5b1446ae71e10537591ea6/Packs/AutoFocus/doc_files/AutoFocusPolling.png)`

   For more control of how the image displays, you can use the HTML \<img> tag. For example: `<img width="500" src="https://github.com/demisto/content/raw/2d6e082cfb181f823e5b1446ae71e10537591ea6/Packs/AutoFocus/doc_files/AutoFocusPolling.png" />`

   Examples of documentation using absolute URLs:

   * [URL to commit hash](https://github.com/demisto/content/raw/2d6e082cfb181f823e5b1446ae71e10537591ea6/Packs/AutoFocus/doc_files/AutoFocusPolling.png)
   * [URL to master branch](https://github.com/demisto/content/raw/master/Packs/AutoFocus/doc_files/AutoFocusPolling.png)
   * [URL after redirection](https://raw.githubusercontent.com/demisto/content/master/Packs/AutoFocus/doc_files/AutoFocusPolling.png) (also valid)

{% hint style="info" %}

### Note

To keep the main content repository small, images are limited to 2 MB. For larger images, follow the instructions for [Videos](/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/documentation/videos-in-documentation.md) about how to store large media files in the [content-assets](https://github.com/demisto/content-assets) repository.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/documentation/images-in-documentation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
