> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/zh/wu-dai-ma-ti-yan/avatar-studio-experiences/customizing-your-avatar.md).

# 自定义你的头像

了解如何使用 Avatar Studio 配置器从视觉和行为上个性化你的 Convai 头像。

## **概述**

创建角色后，您可以使用 **Avatar Studio**.

{% embed url="<https://youtu.be/-08pVVY5yQo>" %}

## 可自定义的内容

在 Avatar Studio 中，您可以：

* **选择示例虚拟形象，**

  从现成的高保真虚拟形象库中挑选。
* **自定义外观**\
  调整面部特征、服装、发型及其他视觉元素，展现角色的个性。
* **上传自己的虚拟形象**\
  想要独特的设计？上传自己的 3D 虚拟形象模型，全面掌控其外观。
* **设置智能动画**\
  配置挥手、点头、回应和思考等动作，让这些动作在对话过程中根据语境触发。
* **选择虚拟环境**\
  将虚拟形象置于沉浸式数字场景中，使场景契合体验的基调和用途。
* **调整互动行为**\
  微调虚拟形象的沟通方式，例如说话风格、语气和与用户互动的偏好。
* **适配设备与品牌**\
  自定义虚拟形象界面在不同设备上的表现，并使其与品牌的视觉形象保持一致。

完成自定义后，只需 **保存并发布** 虚拟形象，即可在角色的对话中使用。


---

# 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.convai.com/api-docs/zh/wu-dai-ma-ti-yan/avatar-studio-experiences/customizing-your-avatar.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.
