> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/web-manager/uploading-a-profile-image.md).

# Uploading a profile image

{% hint style="info" %}
If you want to use an image of your ENGAGE avatar as your profile image, you can do this in the ENGAGE application. For more information, see [Capturing a profile photo](/engage/avatars/capturing-a-profile-photo.md).
{% endhint %}

1. Go to [https://app.engagevr.io/](https://app.engagevr.io), and then log in.
2. From the side menu, select **Profile**.
3. On the Profile page, select **EDIT PROFILE**.
4. On the **EDIT PROFILE DETAILS** page, select the edit icon (<img src="https://3460182399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwVx6bvwqEE7tD0TYOcfj%2Fuploads%2Fgit-blob-606dbc50a086de59d0b167fcb7538356cbfc6e88%2Fedit_photo_icon.png?alt=media" alt="" data-size="line">) next to the profile image.
5. Choose one of the following options:
   1. Drag an image file onto the **Update your picture** panel.
   2. Select **UPLOAD PROFILE PICTURE**, and then select an image file.
6. After the image uploads, drag the small blue squares on the grid to choose which part of the image to use.
7. Select **SAVE**.


---

# 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.engagevr.io/engage/web-manager/uploading-a-profile-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.